yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] jazzmoe76:
Ok , I blew out tons of useless crap on my lappy to make some room. I am currently downloading Ubuntu. I chose Ubuntu because its what I see used on most android based forums. Ill get the kitchen going tomorrow. I am also going to sign up for an upload site so that I am able to upload things for others to grab and work on themselves. Anyone that wants to get involved, please let us know and share whatever files you are working on as well so that we are not all working on the same things.

---------- Post added at 03:54 AM ---------- Previous post was at 03:44 AM ----------

I would like some input from my fellow noob wanna be devs. It would seem that the more polished devs are going to bring us some nice ics stuff soon. Should we start with sense 3.0 or 3.5 to cut our teeth on as suggested by WC. Should we just grab a custom rom and start working on stand alone add-ons. Or should we dive face first into Ics?
[HTC Vivid, Raider, Velocity] Infinimint:
I'm a little rusty, but I would recommend using a stock Gingerbread RUU. Go through the process and learn how to add things manually, don't use a base Rom, you won't learn nearly as much.

Overview different features in other roms and try to implement them yourself, it'll benefit you in the long run.

If you want a decent noon challenge, try taking a stock sense Rom and make it look identical to AOSP. Edit the framework and explore around, have fun with it :)
[HTC Vivid, Raider, Velocity] jazzmoe76:
Sounds good to me. Anyone else?
[HTC Vivid, Raider, Velocity] pstevep:
I will be around to help you guys if you have any questions or anything. Obviously I don't have a vivid so I won't be a ton of help, but I do know a bit, and can usually find answers.

I'm going to sticky this. All i ask is that everyone keeps it civil and work together.

You guys are on the right track currently. Keep it up.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Thanks man!!
[HTC Vivid, Raider, Velocity] Mad Medik:
I think GB makes sense for us to cut our teeth on (although its a mute point for us Bell users...)

MM
[HTC Vivid, Raider, Velocity] zzoinks:
I’m a software developer by trade and I’ve always had an interest in trying my hand at “cooking” a ROM. This thread seems like a safe place to ask some noob-ish questions.

As I understand it there are several layers that go into making a complete ROM. The Android OS layer (along with other add-on software, manufacturer overlays, etc.) and the abstraction layer that contains device drivers which allow the OS to talk to the hardware. I’m guessing that this separation is what will allow us to take, for instance, the OS from an HTC One (including Sense 4.0, ICS, Beats audio, etc.) and port it over to the Vivid. We create a ROM that has the OS from the source device running atop of the abstraction layer of the target device.

How are these handled as part of ROM cooking? What pieces of the RUU are OS related and which are hardware related? Is there any actual compilation from source code happening here or is it a matter of mixing and matching compiled code and tweaking config files?

Another area that concerns me is testing – What do developers use for testing? An actual device (scary) or an emulator? I’ve only got one Vivid and it’s my daily driver.

Thanks,

-Brett.
[HTC Vivid, Raider, Velocity] pstevep:
As far as porting from another device, the initial port is semi easy, especially if you are using the kitchen that people have been mentioning (i can't remember the guy's name). The kitchen pulls the files from your ruu that are needed for running the rom on your device. The hard thing for you guys, I say hard because it's tedious, is images will have to be resized, because your screen is different. As far as beats and those kinds of things, you can port over the apps but it may not function totally, Beats especially because the drivers are closed source in the kernel. So some of those things are a bit harder. After using the kitchen to port the rom stuff will still need to be tweaked to get everything working. There is a pretty decent guide floating around for porting sense roms, if I get a second on a computer, i will try to link it.

As far as testing, I personally know of no emulators. I do all of my stuff on my phone. It's a pain and will cause heart attacks, but it's also real world. My first port, my phone was unusable for 2 days, it was quite a mess. But it's all learning.
[HTC Vivid, Raider, Velocity] ghostdogg:
dsixda is the name of the user who created the kitchen. Here is the link, http://xdaforums.com/showthread.php?p=5626292, that post resides in the General Android Development section of the forum which is full of great information.

The sense port tutorial I believe pstevep mentioned is located here, http://xdaforums.com/showthread.php?t=1222746

Hope those can help bridge a few gaps.

Not trying to steal your thunder pstevep, just thought I'd save you the time!
[HTC Vivid, Raider, Velocity] pstevep:
No worries. Thanks man.
[HTC Vivid, Raider, Velocity] zzoinks:
Thanks for the info and links pstevep/ghostdogg. In particular I hadn't considered how the varying screen resolutions would complicate things. Although, it seems like the One S would be a good candidate because it has a qHD screen like the Vivid. That is, one it is released...

-Brett.
[HTC Vivid, Raider, Velocity] jazzmoe76:
I went with the dual boot Ubuntu on my Windows machine. How do I access files on my C: from Ubuntu? I can get to any external memory and my network, but not the drive it exists on...

Last thing, Kitchen appears to be pretty straight forward. I started it this first time with a custom rom, just to see what it was all about. I assume that I need to just follow the menu to execute what needs to be done. I can only assume that this latest ics RUU isnt as easy to manipulate as it thisw custom GB rom appears to be. Also, can I have multiple work folders with multiple roms? I assume I can, I just want to be sure.
[HTC Vivid, Raider, Velocity] zombie.raised:
just mound a folder

sudo mount -t vboxsf temp foo

temp can be the folder in C:'temp and foo is the on unix sid e

This may presume some addon that come with virtubox etc..

Here is a link if you need more details

https://forums.virtualbox.org/viewtopic.php?t=15868
[HTC Vivid, Raider, Velocity] jazzmoe76:
Ok, I'm holding my breath, I'm about to flash a rom that I messed with... Arrruuughhh!!! Here's hoping... If this works, then I'm going to move on and start playing with stock roms to see what I'm able to do/learn.

---------- Post added at 04:14 AM ---------- Previous post was at 04:03 AM ----------

Well, that was quick, I got an error "status 6" lol!
[HTC Vivid, Raider, Velocity] zombie.raised:
before you build the rom ensure that you look at all the warnings with update_script
[HTC Vivid, Raider, Velocity] jazzmoe76:
Ok, I saw 2. They were both something about mounting 4 and mounting 6. What do I do about them? (cue all the laughing devs)
[HTC Vivid, Raider, Velocity] zombie.raised:
i don't remember seeing these messages so not sure what it means.
[HTC Vivid, Raider, Velocity] pstevep:
I'm not entirely sure, but the updater script is crucial, so more than likely we may need to get someone who has made one for the Vivid to help. The kitchen may not configure it right if it doesn't support the vivid, heck it didn't configure my first one right and it supported my phone.

Just wait till you feel really good about what you are doing, and then Bork something you aren't sure how to fix. Those are the butterflies.
[HTC Vivid, Raider, Velocity] jazzmoe76:
:D I bet, thats funny! Thanks for the advice fellas. I just went back through this thread and bookmarked all of the useful links within firefox on my new Ubuntu OS. Thanks to all that posted them. My head is starting to swim... WC mentioned that we should start with kitchen, so I would assume that it works on some level. I now understand that the rom needs to complete building with no errors to work properly. I wonder if there is some sort of script swap from your original rom to the newly created one that'll fix it? I have a lot of reading to do...
[HTC Vivid, Raider, Velocity] zombie.raised:
take back comments -
[HTC Vivid, Raider, Velocity] :
Um the custom roms the work is already done...this as i said isnt learning....you wont see whats what without using a stock ruu rom.zip...everything in the custom roms has already been done so its really a no brainer....and you guys just are not listening....the kitchen sure will extract any rom.zip....but new ics it will not do some of the needed functions.....start with a lower ruu so you actually learn the kitchen first and what the function are and how to manipulate the files in the rom....until you guys get that down a bit anything is else is pointless honestly...working backwards...the reason im telling you guys to do it this way is I am self taught and this is the route i was instructed to go...have to learn to crawl before you walk

---------- Post added at 11:38 PM ---------- Previous post was at 11:29 PM ----------

And sure zombie.....can look at a script all day long, but if you dont know what your looking at or what it actually does or means, then what good is even looking?Google any and everything you dont know what is, there are explanations for everything youll run across
[HTC Vivid, Raider, Velocity] jazzmoe76:
I was listening.... See above

---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------

I just started with a custom rom as suggested before to see what kitchen was all about. Now that I see, I understand what you are talking about...
[HTC Vivid, Raider, Velocity] Infinimint:
One thing I've noticed about the kitchen is that is converts the updater-script to update-script which is somewhat primitive and can break things. Seeing how early the errors occur, it may be a mounting/formatting issue.

REMEMBER: Only edit updater-script/update-script with a PROPER text editor!!! I recommend Notepad++ for Windows, Gedit for Linux, and Text Wrangler for Mac. These are all free.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Thank you. I just went through and made some tweaks and didn't let kitchen change my updater-script and everything worked. I am typing this on the newly created rom as we speak. Just got done with titanium backup. Now its on to taking a stock rom and rooting, tether, deodex, etc. This is pretty fun to play with. At least for now, prior to my first brick/semi brick.

---------- Post added at 07:20 AM ---------- Previous post was at 06:57 AM ----------

Man... I have a lot to learn. I understand what you are saying about editing text within the construct of a program to change the properties, I just need to figure out how to interact with Gedit in conjunction with kitchen to make it all jive...
[HTC Vivid, Raider, Velocity] Infinimint:
Well, the structure of a rom is quite simple.

/boot.img | Contains the kernel and the ramdisk.

/META-INF | Contains the signature of the rom (needed by some recoveries).

/META-INF/com/google/android/updater-script | The rom installer read by the recovery when being flashed.

/system/app | Contains all system applications.

/system/bin | Contains most of the binaries that can be accessed through terminal.

/system/xbin | Contains some binaries and busybox which contains tons of commands.

/system/build.prop | Info about the rom as well as some default settings.

/system/customize/resource | Contains wallpapers, boot animation, etc.

/system/fonts | Contains all the system fonts.

/system/framework | Contains the framework, can be decompiled and themed.

/system/lib | Contains all the drivers.

/system/media/audio | Contains all system sounds including ringtones and notifications.

/system/media/weather | Contains weather animations for HTC Sense.

/system/tts/lang_pico | Contains languages.

/system/usr | Contains key-mapping.

/system/etc | Contains a bunch of configurations for all sorts of stuff.

/system/etc/init.d | Contains startup scripts if you have busybox run-parts built in.

I didn't cover everything, but that's the basics which is enough to get you by. Just explore around.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Can someone let me know if this is what I should start with... Thank you in advance.

http://xdaforums.com/showthread.php?t=1417507

---------- Post added at 06:25 PM ---------- Previous post was at 06:07 PM ----------

nm, it has been rooted, deodexed, zipaligned. can someone point me to the same file without any devolopment?

---------- Post added at 06:36 PM ---------- Previous post was at 06:25 PM ----------

sigh... nm, I'm an idiot. I found them ALL :)

---------- Post added at 06:53 PM ---------- Previous post was at 06:36 PM ----------

Ok, I am officially flailing away in the dark here. Sorry for my incoherent rambling here. I found all of the stock RUU's but not the stock .zip's. Does this have anything to do with what I need to do or are the .zip's avail elsewhere?

"You can extract the ROM.zip from any RUU to install via ZIP

Start the RUU and once at the first main screen click Start>Run and type

%temp%

now, find the newest folder and in there will be a ZIP file called Rom - copy this to your desktop and rename it PB99IMG. Now copy this to your SD card and start the phone in HBOOT (turn it on whilst holding volume down). It will find the file and start the update. Just follow the instructions..."

I've searched and looked through 30-50 pages throughout this forum thus far and have not found a list of stock .zip roms to start with in kitchen... Am I missing something?
[HTC Vivid, Raider, Velocity] zombie.raised:
Just download the RRU you want from football's thread and run the exe and get the rom.zip or firmware.zip from temp folder.

That is your starting point
[HTC Vivid, Raider, Velocity] Mad Medik:
Hopefully I have understood the question. FYI - I have not done this (yet) but am going on what I understand from previous posts.

The RUU is an executable container and the Rom.zip is inside that container. So the previous poster was saying that you start the RUU. In doing so, it will create a folder in the TEMP directory and will put the ROM.zip file in it. You stop at this point, and copy that Rom.zip from there to wherever you want it. In the case of the ph39 thing, the zip needs to have that exact name and be in the root directory of the sdcard for it to be picked up and flashed in hboot.

I hope I used the right terminology and that made sense.

MM

Sent from the Matrix
[HTC Vivid, Raider, Velocity] jazzmoe76:
Does this need to be done in windows? Within Ubuntu, I keep clicking the .exe and nothing is happening... The file exists in my download folder. Is it maybe a bad download?
[HTC Vivid, Raider, Velocity] :
GIve it about 10 minutes....uploading file you need

http://www.fileswap.com/dl/0y1AzkdVRr/PH39IMG.zip.html
[HTC Vivid, Raider, Velocity] jazzmoe76:
Thank you :) That will definitely help get me started. Does this need to be done in windows tho? Once I figure it out, I was planning on taking all of the RUU's and making them into zips and uploading them for all. My plan was to make that my first actual contribution to this community.
[HTC Vivid, Raider, Velocity] kevsthabest:
.EXE files are windows executable, you can use WINE to run the file and grab the rom.zip from in ubuntu. there is a script you can use for it also (openruu i think it was called)

You can also build roms in windows if your more comfortable in that enviroment. Linux is required only when you compile roms from source (ie Cyanogenmod or Miui). but just building a rom you really dont compile anything.
[HTC Vivid, Raider, Velocity] :
drop that into kitchen(original update folder) and create working folder from kitchen menu...thats original untouch rom.zp....just renamed to be able to flash on locked phone....kitchen will find it if placed into the folder ive mentioned
[HTC Vivid, Raider, Velocity] ghostdogg:
It can be done on your Ubuntu build. You'll need to install WINE so you can run windows executable files in Ubuntu. Then grab a copy of OpenRUU. I extract OpenRUU to a new folder in my home directory. Run "1extractrom.sh" and get to the point where it asks you to run the RUU with wine. Right click the RUU file and choose "Open with wine windows program loader" and allow the file some time to get started. Eventually it will show a new "windows" window and a status bar of its progress. Once the bar is about three squares from finishing you then click enter in the terminal window running the OpenRUU script. If successful it will extract the rom.zip to your home directory and your good to go. If it doesn't work try again and wait until only two squares are left in the progress bar. Its all about timing, if you try multiple times and cant get it to work it can be done manually. Let me know if you need to know the manual route.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Very helpful, thank you fellas! I am very new to Linux and surely more comfortable in windows. So, last thing (at least for now ;) ) within windows, or linux, I an just unzip any of the roms, and then say, add an apk to the correct area, then re-zip and load on my phone? Or from there move it to kitchen and root, deodex, whatever. Then recompile within kitchen and load on my phone? I know this information is available throughout various resources, I'm just hoping to cut to the chase. I learn much easier by doing rather than reading. Once I get this started, I will begin to go through all of the how-to's...
[HTC Vivid, Raider, Velocity] Infinimint:
.exe files are not executable in a linux environment without virtualization or WINE.

Go on a Windows PC for two seconds and open the RUU. Next, open Task Manager. Go to the Processes tab. Find the RUU (ARUWizard.exe). Right click on the process and click "Open File Location". The rom.zip will be in there.

Now go download unyaffs.exe (Google it). Extract the rom.zip on your desktop and put unyaffs.exe in the extracted folder. Hold shift and right click in the file browser. Click "Open command windows here".

Type in "unyaffs.exe system.img" and take the extracted files and put them in a new folder called "system".

Type in "unyaffs.exe userdata.img" and take the extracted files and put them in their necessary location in the newly created "system" folder. For example, if they are apk files (apps), put them in the "system/app" folder, etc.

Now delete everything in the rom.zip extracted folder besides "boot.img" and the "system" folder.

Now take the META-INF folder from a previous rom that you already have downloaded. If you don't have one, go download one from in the forum.

Compress all of the files in the Rom extracted folder and rename the .zip to whatever you like. You've now created a rom. Try flashing it.

Chances are it will not work immediately, so go to "META-INF/com/google/android" and edit the "updater-script" file and make sure all the files mentioned in it exist. Once done, recompress all the files again. Try flashing again. It *should* work.

Also, don't forget to "fastboot flash boot boot.img".
[HTC Vivid, Raider, Velocity] ghostdogg:
There are many many many ways to skin this cat :)

I personally like to do things "right" or most commonly the hardest way possible so I dont have to rely on scripts or tools to do it for me. As helpful as they can be they can also cause just as much trouble. If you can accomplish these tasks without any "script/tool" assistance than you'll have a better understanding of how the tool does its job and will be more likely to be able to remedy any glitches you run into.

In the case of building Android ROM's the "right way" is from a Ubuntu 10.xx build environment (where google does its work from). Windows isn't the native build environment so it introduces its own set of problems. Most of which have been overcome by other users already but if you don't know where the problem comes from its hard to find a solution.

Wild Child and I seem to be from the same mindset when it comes to this type of thing. I started with a Windows build environment back in the windows mobile days but had so many little quirky problems even then that I made the jump to linux permanently.

Dont get my wrong, you'll still have weird stuff happen in Ubuntu or whatever distro you choose but the accessibility to fix those problems is much better! Documentation is more readily available and many of the more advanced devs use and create their tools for linux.

It sounds like your looking for the easiest way to start but in my opinion shortcuts aren't going to make things easier for you in the long run. I understand the end goal is to create a custom ROM and then debug and improve it. Things get very repetitious once your building and if you add unnecessary steps or multiple OS's into the mix its much more likely you'll forget steps or just end up adding wasted time for yourself.
[HTC Vivid, Raider, Velocity] Infinimint:
+1 Very well said.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Ok, I'm running out of my allotment of daily "thanks" button... So thanks to all of you for your input. I am in agreement. I'd like to keep this to Ubuntu, which will also help me learn Linux at the same time. My "WINE" got about 90% of the way downloaded and then error-ed. I tried removing it and that error-ed. Sooooo. I dunno, I'm going to reboot and see if I have better luck. My head is starting to get swimmy.... I'm going to go to my desktop and print out a lot of this thread for reference. Thanks again!

---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------

I think I figured out why it was error-ing. There are 400+ updates for Ubuntu. Updating now...
[HTC Vivid, Raider, Velocity] ghostdogg:
Its looking like a "How to initialize a new build environment" how-to is in order.... I'll see if I can whip something together.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Awesome! Thanks!
[HTC Vivid, Raider, Velocity] jazzmoe76:
Does it take roughly a year and a half for the "windows" window to open, or is something wrong?

---------- Post added at 10:06 PM ---------- Previous post was at 10:02 PM ----------

Error.... -5001 has occurred while running setup. Please make sure you have finished any previous setup and closed other applications. If the error still occurs, please contact your vendor.

---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------

I am removing WINE, rebooting and downloading again...

---------- Post added at 10:22 PM ---------- Previous post was at 10:08 PM ----------

I can't seem to get wine working. I keep getting errors. Any ideas? Or can I grab a diff wine? I'm using the (Meta) package
[HTC Vivid, Raider, Velocity] jazzmoe76:
Im re-downloading the RUU now. Maybe it was messed up...
[HTC Vivid, Raider, Velocity] ghostdogg:
Where did you get wine from? I recommend just grabbing the debian installer from their homepage.
[HTC Vivid, Raider, Velocity] jazzmoe76:
I got it from Ubuntu software center... Thanks, Ill try that. I'm now thinking that the download of the RUU got messed up tho.
[HTC Vivid, Raider, Velocity] :
Ive never been able to get an ruu extracted in wine....waste of time....the PH39IMG.zip I uploaded it the original rom.zip from the 1.63 first release...its just renamed so that it can be flashed via hboot on a gb phone.
[HTC Vivid, Raider, Velocity] jazzmoe76:
Crap... Now I don't know what to do... I just uninstslled Ubuntu so that I can start fresh again. It kept crashing and running way slower than yesterday. WC, I'm unfamilier with what 1.63 means. The RUU I was trying to extract was the first sense 3.5 rom. Do u have that one handy? If I am unable to get the RUU to extract, it will be a good starting spot for what I'm trying to achieve.

---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------

For ATT Vivid that is..
[HTC Vivid, Raider, Velocity] :
Those all other carriers builds....try with what ive uploaded first...thats the original 3.0 rom that came with the phone@1.63 build....get that one working first....just my opinion...

Also i use Linux Mint 10.10 for the rom stuff