Related
THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're using the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
DISCLAIMER:
I take no responsibility for anything that may happen to your phone/computer. Use at your own risk.
PURPOSE:
This is for informational/testing purposes. And for people to stop asking, "can somebody port X rom!!! PLZ!!!"
PREFACE:
I made this as a quick tool to port ROMs from the Dream/Sapphire forums to work with our phones. It's a very quick and dirty script I threw together using bash, so there's probably some problems with it. This tool is simply designed to make a copy of the Dream/Sapphire ROM. Once you get the setup, it's really easy and you'll be porting like crazy.
I did this all on Ubuntu 9.10 so things might not work properly if you're using another distro.
THANKS:
All credit goes to the people that made this possible, in no particular order...
dzo, vilord, mssmison, zen, enatefox, pmos, jamezelle, craig0r, cyanogen, and so many more. If I forgot you, I'm sorry, but you know if you helped in some way.
THE SETUP:
1) Download this file
2) Extract the folder to your desktop. Then copy and paste the following code into the terminal:
Code:
sudo mv -f $HOME/Desktop/Android/genext2fs /bin/genext2fs; sudo chmod 755 /bin/genext2fs; sudo dpkg -P squashfs-tools; sudo dpkg -i $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo rm -r $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo chmod 777 $HOME/Desktop/Android/*.build.script
3) Now go into synaptic package manager, search for squashfs-tools, select it and under Package, check Lock Version so that way it won't try to update.
4) Now cruise over to the Dream android development forum or the Sapphire android development forum and download the ROM you would like to port. Place the zip file in the Android folder. (no need to rename)
5) Place any .apk's you would like built into the system in the Apps folder.
ADVANCED SETUP:
If you would like to tweak the system before building, open the script in a text editor and you'll find a line to uncomment that will halt the script until you are ready.
HOW TO RUN:
Either run the script from a terminal
Code:
./$HOME/Desktop/Android/HERO.build.script
or
./$HOME/Desktop/Android/Donut.Build.script
Or double click and Run in Terminal
You will get a prompt for your password to use the sudo command. THIS IS NOT SAVED ANYWHERE OR MAGICALLY SENT TO ME. It is just to get the system.sqsh setup for you to use.
You will now see a Donut/Hero folder inside the Android folder. Inside that will be a nice little system.sqsh with the date ready to boot!
*Rename to system.sqsh when you put on your SD card*
Grab the latest basefiles from vogue-android and you're good to go.
~~~~~~ To get an output of what's happening run in a terminal as described above but add " > build.txt" and you'll see a txt file in the Android folder. ~~~~~~~
CHANGING SYSTEMS:
If you want to port a new rom, replace the .zip.
UPDATES:
1) Download the updates from HERE
2) Extract to the Android folder overwriting if necessary.
3) Copy and paste the following code into a terminal:
Code:
sudo chmod 777 $HOME/Desktop/Android/*.script
CLEANUP:
If you follow the advanced setup and/or accidentally closed the terminal before the build finishes, run the cleanup script. This will unmount everything that might be mounted and delete all folders that are made during the process.
DOWNLOADS:
If you're too lazy or just want a quick link:
Main "Android porting" folder
Updates
Input, testers, bugs, and tweaks to the scripts are appreciated!
FAQ:
Why does my system.sqsh not work?
Most likely cause is that you're not using the correct version of squashfs-tools. You'll have to find version 3.X for the distro you're using. Version 4.X will NOT work!!!
When I try to boot a system.sqsh I just made I keep getting something about android power wake locks. WTF?
You're probably trying to port an eclair or cyan ROM. These don't work at the current state. Hopefully soon I'll get these working.
Will update more when they arise.
CHANGELOG:
11-27-09:
-Created a cleanup script in case the terminal is closed during the build process.
-Bug fixes in Donut and Hero scripts
11-24-09:
-Added an Apps folder for apk's you want built into the system.
-Bug fixes in scripts
11-22-09:
-Combined everything needed into a zip file
-WAY easier to setup
11-20-09:
-Added feedback to make more user friendly
-Append time to system.sqsh
loserskater said:
Input, testers, bugs, and tweaks to the scripts are appreciated!
Click to expand...
Click to collapse
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
garynsa said:
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
Click to expand...
Click to collapse
What did you change?
Glad to see it's working.
loserskater said:
What did you change?
Glad to see it's working.
Click to expand...
Click to collapse
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
garynsa said:
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
Click to expand...
Click to collapse
Make sure you use the genext2fs that I referenced.
That one works with -a and might take care of some issues. try that and see if it works.
Updated script to now move system to a Hero or Donut folder.
Working on the cyanogen build now...
EDIT: Here's a cyanogen script that gets it to boot, but sits at a black screen. I haven't had much time to test it so it might boot further than that if you leave it. If somebody wants to test this out or tweak it in some way go for it.
It uses the donut.sqsh in the Android folder so you shouldn't have to do anything with it except make it executable.
EDIT 2: Still working on cyan builds... that script didn't work.
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
jamezelle said:
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
Click to expand...
Click to collapse
Good point, forgot to mention that. Updated first post.
I'm hoping it will help people start to learn to tweak system's. But I have a slight feeling wer're going to start seeing a lot of "MLIGN/DWANG/etc's Android Rom" threads from random people.
Hi
Was able to port the DWANGs build using your script. Thanks a lot for making life this simple. Howev3er, hero build is still not working. Tried your genesxt2fs. Is it possible to get the links to correct base hero version to use? I tried magic and normal version. It keeps giving me black screen and doesnt completely boot. I think the base hero version is not the right one i am using
Thanks
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
loserskater said:
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
Click to expand...
Click to collapse
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
garynsa said:
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
Click to expand...
Click to collapse
Glad to see its working. Thanks for the feedback!
Most things working
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
garynsa said:
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
using u
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
Click to expand...
Click to collapse
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
loserskater said:
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
Click to expand...
Click to collapse
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
garynsa said:
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
Click to expand...
Click to collapse
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
loserskater said:
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
Click to expand...
Click to collapse
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
garynsa said:
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
Click to expand...
Click to collapse
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
loserskater said:
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
Click to expand...
Click to collapse
Android folder... but its not a big deal as one can easily change it while startign the script
Soft chewy center
Here are instructions and downloads that will have you on your way in no time, to running Linux on an IPAQ hx4700.
Step 1: Download a disk image
Ubuntu light weight X desktop download
Android download currently this barely boots
Step 2: Uncompress the file
See p7zip link
Step 3a: Copy the image to a CF or SD card using Linux
Open a terminal and navigate to the directory where you extracted the img file.
Code:
cd somedirectory
Copy the image to the card using dd
Code:
sudo dd if=image-name.img of=/dev/sdx
Where x is the destination of your card. Note there is no partition number "i.e. /dev/hda1" Just the destination letter /dev/hda
Step 3b: Copy the image to a CF or SD card using Windows
Code:
stub
Step 4: Edit startup.txt if you are using a SD card
Code:
stub
Step 5: Run HaRET
Safely remove the card from your computer, insert it in to your hx4700 navigate to the card directory using the file manager then click on haret.exe
Hard crunchy shell
Stuff for the masochist that lives inside you.
Kernel 2.6.21-hh20
Found the source tarball for 2.26.21-hh20 on this link.
I found an android patch for 2.6.21 at this link.
Finally I hammered out this patch that applies smoothly with no fuzz.
And here is my .config file.
Android usb gadget and the low memory killer currently need some love. But without configuring them the kernel compiles nicely
A-Z build instructions
Code:
stub
HaRET
I use HaRET to boot linux on the hx4700, until that day comes when I have learned enough about the hx4700 to provide a ROM, tinboot isn't really that hard to use.
Also the latest HaRET does not boot the hx4700 maybe it is being built with a newer instruction set, until I get a newer version compiling there is an older version in the .img files that works fine.
stub- haret from source
Filesystems
These xxx.img files should be written to a cf card using dd, or sd card if you change startup.txt and the swap file in /dev/fstab. The card should be no less than 1 GB. Gparted can resize/move your partitions if you have a larger card.
I have to admit I don't have a 1gb card to test the img file on, only a 4 and 2 GB card. If someone who does have one finds out that it doesn't boot or something let me know.
Card image layout:
fat16 16mb [haret] partition 1
ext 880mb [root] partition 2
linux-swap 128mb [swap] partition 3
Creating an Ubuntu file system
Creating a file system to run Linux on the hx4700 via HaRET. Rootstock is a tool the will pull down precompiled packages suitable for various devices, from a server. Then install, unpack, and configure them on a disk image file system inside a virtual machine, all without you leaving the comfort of your x86 compatible environment.
For rootstock I followed this guide link.
I used this command to create the image.
Code:
sudo ./rootstock --fqdn ubuntu --login xda --password xda --imagesize 3G --seed tslib,build-essential,openssh-server,lxde,gdm --dist jaunty
I'm still thinking of including gnome-core simply for more function but lxde will have to do as the session manger. Gnome is just to heavy.
Light weight X download link at top of page
working:
the Mouse pad is configured
all drivers and firmware load
auto login via gdm.conf
/etc/network/interfaces is preconfigured for usb net and stubbed out for wireless.
not working:
touch screen - needs configured
wireless?? - I think only OPEN or WEP is supported ATM.
Android
stub- building the android filesystem
android.img download link located at top of post
now if I could just get the hang of making my forum post... not ugly
Nice! very nice!
Marvelous news, THX man!
...i love you! :']
As soon as I found this thread I smiled like a giddy school girl. My hx4700 might just be useful once again! I know nothing on programming... but i'd be glad to help out in any way possible!
Update folks,
I was up all night slaving away at this but, WE HAVE AN ANDROID PATCHED KERNEL!!! its 2.6.21.hh20 with android patches. This means the drivers should be easier to get worked out.
And Android almost boots, I suspect its the generic "goldfish" file system or some other trivial thing stopping it from booting all the way.
After mounting root and running /init, It shows the message "A N D R O I D_" then freezes well not really freezes the cursor continues to blink. but still almost there...
edit - links added
thanks
thanks a lot it's very usefull
Just seen a boot animation, it just got real people... but still not booting all the way.
keep up the good work...seems that this is the only development going on for my trusty iPaq 4700.......
I just want to say thanks for all the supportive comments. It's a real shot in the arm when I'm feeling over whelmed by the complexities of this. I did something really stupid with "sudo dd" last night and boogered up my root file-system, so I'm spending today re-setting up my build environment
All of the hardware is supported but just not pushed upstream but I’m working on a new 3.0 kernel right now for the universal when I finish I will add the hx4700 patches and post the source and message you. But I know wifi, Bluetooth, touchpad, sound, led, and all buttons work in 3.0. And these are the same on the universal and I have these working with froyo now. But I can post my 2.6.36 kernel I’m using now after I make a few corrections.
Here's my form page link
And this is where some of my code and android builds are: link
The common.tar.gz is my old 2.6.36 kernel I have to make some corrections and fix the hx4700 code I messed up and reload it in a day or so.
--I had to post this here as I got a message that you cannot receive private messages.
Thanks!
Don't know why you got that message, I did get your PM.
Could you make a tutorial, step by step how to run android(haret, etc.) on hx4700, please?
I'm noob in windows mobile tools
im currently running Angstrom on my hx4700
but would love android too..
havent tried any of these images yet. but ill probably have some
spare time this week..
/Kyndal
On tenterhooks ...
It failed to boot (couldn't mount /dev/hda2 I think) when I tried to install and run from a Compact Flash, so I'm in the middle of dd-ing to an SD card instead. Fingers crossed ...
EDIT: It boots fine from the SD card.
However, it's rather sluggish at best, and there don't seem to be many productivity apps -- and no onscreen keyboard. Still, it's a start!
EDIT 2: Attached a small photograph for the curious. Sorry about the blur, but I couldn't manage a better shot, given the lighting and the camera's fudged-up CCD.
kyndal said:
im currently running Angstrom on my hx4700
Click to expand...
Click to collapse
How in the world did you manage that? I've been trying to get Angstrom working on my hx4700 for months now, without success. (Aside from an old bootpack that literally has no useful programs.)
I haven't had much luck with any "new" Angstrom builds from the
narcissus online builder..
Right now. im running an older X11 build
booting from SD card .img file
Functional.. but ya. not up to date..
/Kyndal
kyndal said:
I haven't had much luck with any "new" Angstrom builds from the
narcissus online builder..
Right now. im running an older X11 build
booting from SD card .img file
Functional.. but ya. not up to date..
/Kyndal
Click to expand...
Click to collapse
I would like a copy of this .img file (cleaned of personal stuff, of course). It'd be nice to have a usable Angstrom for a change.
you can try it out with the prebuild images (OLD)
apparently im not allowed to post external links yet...
so go to this address
angstrom-distribution.org/releases/2007.12/images/hx4700/
and download
Angstrom-x11-image-glibc-ipk-2007.12-hx4700.rootfs.img.bz2
Angstrom-boot-2.6.21-hh20-r6-hx4700.exe
extract the .img file from bz2 to a FAT SD card
and place the .exe there too..
run the .exe select the img file. can be a little fiddly on the "touchpad"
"enter" is like in the middle. and half the time moves the cursor up/down
this linux lives in the loop .img file on vfat..
not on partitions. so pretty easy to try..
run these commands to get online with wifi
su
/sbin/modprobe acx
/sbin/modprobe hx4700-acx
/sbin/iwconfig wlan0 essid ACCESSPOINT
/sbin/ifconfig wlan0 up
/Kyndal
kyndal said:
you can try it out with the prebuild images (OLD)
Angstrom-x11-image-glibc-ipk-2007.12-hx4700.rootfs.img.bz2
Angstrom-boot-2.6.21-hh20-r6-hx4700.exe
Click to expand...
Click to collapse
Yeah, I've tried the image before - months ago -- but I didn't know about those commands /sbin! I'll give them a try and see if I can get anything useful installed (the image comes without any useful GUI - or even CLI, for the most part - applications).
EDIT: Unfortunately, even though the package manager seems to be capable of fetching the correct packages (it's hard to tell), it consistently fails to install them -- I even tried installing man and nano (one at a time) and was met with failure even though the URLs check out. (abiword took longer before failure, hence my suspicion it downloads fine).
I apologize for derailing the thread like this, but this is the only place I've found since I got interested in putting Linux on my iPAQ where someone is actually *answering* my questions.
It's ok Strife89, I appreciate you all actively helping out, I was out of town house hunting last week.
Maybe everyone here could come up with a "wish list" request for packages to be installed among other useful things/configuring/etc, so we can all help polish the ubuntu installation, and make it something nice/useful.
As far as android goes, I have more confidence in the kernel than I do the file system, as to where I am right at this moment, donut will boot and show a boot animation. That is as far as I have gotten, but still it is progress.
I look forward to working with anyone interested with helping out, so lets here some thoughts/suggestions.
Well let me add mine first I guess we need a clearer easier tutorial on getting linux booting from the sd or cf card. both of these options have subtle differences and need better defined instructions.
edit- As far as installing apps to the ubuntu.img. The usbnet interface is configured on the hx4700 side hopefully, if some one wants to do some googling on how to get it setup all the way on the PC side of things, I think we would all appreciate that. Then we could just ssh in and apt-get anything we wanted to try out or change. Later we could make it part of the download/tutorial after testing.
Just wanting some feedback on the best rooting method and the most stable and battery sipping from/kernel combo..... looked through the dev section and see that you guys don't have aosp so throw some suggestions out there for me! Thanks!
Sent from my Nexus S 4G using Tapatalk
look at sfhub's thread in the dev board. doesn't count towards odin, and it does other stuff for you too
I updated ota to ek02. Then I used the auto root method. Next I did the no ciq in auto root. Now would be a good time to do a backup in recovery in case you mess up something. You can then use root explorer to add .old (or whatever) to the bloat apps in /system/app. Then grab adfree to put an anti advertisement modified hosts file in. Reboot. Run sprint ID and search then choose clean pack. That puts a stock launcher in that is very stable and I imagine is pretty small in file size. Next I create a black picture with camera and make the picture the wallpaper and lock screen picture. Black is good for amoled because (I think) that the less the screen has to illuminate, you might eek a little more battery life. If not, I prefer simple and not flashy.
I'm weird, I will make XP/vista/7 run the windows classic theme with all eye candy turned off with black back ground and system settings for performance.
If I run stock rooted, that's my setup. I am running calkulin's 2.0.1a ROM "bare" (ek02). I don't know how stable his el22 is.
That's what I'm running right now and I'm happy with it. I'd run stock rooted but, I'm not 100% sure, he claims his rom is fast and is better with the battery. That's my two cents.
I also used the sfhub root method [though had to modify it quite a bit since I'm on Ubuntu]. But it seems pretty painless and low risk. Then I put down the Blazer Rom. I can't compare battery usage to Calkulin but it seems good so far.
JPSloan1 said:
I also used the sfhub root method [though had to modify it quite a bit since I'm on Ubuntu]. But it seems pretty painless and low risk. Then I put down the Blazer Rom. I can't compare battery usage to Calkulin but it seems good so far.
Click to expand...
Click to collapse
You shouldn't have needed to "modify" it that much.
Most of the scripts are running on the phone. The stuff on the PC side is just copying files to the phone and presenting an organized menu.
The manual install instructions should have covered what you needed to do.
If you let me know what you needed to change, I'll try and make the process smoother for linux users.
Well, it's a slick setup for windows users as a one-click .bat file for windows, but I don't think those run on Ubuntu, so I just went and followed the logic in the .bat file and executed from the terminal line by line. If there were an executable script for Linux it would be much simpler I think, but most Linux users should be able to figure it out.
It's been a few days but other things I recall:
-Had to install a linux-executable version of adb.
-Had to do some work to get the proper USB mount on Ubuntu. When I plugged the phone in, it recognized it as a USB device, but that was not sufficient to push using adb. Samsung doesn't offer much help for linux users but I found some posts online to do the required modifications to my system config: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
JPSloan1 said:
Well, it's a slick setup for windows users as a one-click .bat file for windows, but I don't think those run on Ubuntu, so I just went and followed the logic in the .bat file and executed from the terminal line by line. If there were an executable script for Linux it would be much simpler I think, but most Linux users should be able to figure it out.
Click to expand...
Click to collapse
I'm not sure if you are aware, but you didn't need to "follow the logic" of the windows batch file, as the instructions for Mac and Linux referred you to the manual install instructions of the 2nd post, which basically lays out the steps for you in an easier to follow format.
Installing adb and the samsung drivers for your platform were left as an exercise for the reader.
Thanks, I did see those additional instructions. Looking back I think those worked for the "Option A" rooting, but then to install EK02+CWM I didn't see the command line options, so I think that's where I had to "follow the logic."
Either way it was a great method. Thanks for the work.
JPSloan1 said:
Thanks, I did see those additional instructions. Looking back I think those worked for the "Option A" rooting, but then to install EK02+CWM I didn't see the command line options, so I think that's where I had to "follow the logic."
Click to expand...
Click to collapse
Section D covers all the rest of the scripts. They all follow the same pattern, su to get root priviliges, then run the script.
The "logic" on the windows side is mostly to make things user-friendly. If you are using adb shell, you just get down to business real quick and run the meat of the install which are all sitting in unix shell scripts.
So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit
great guide good job
Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...
Updated adding unyaffsmbn tool... Thanks antdking!
Added Volume tweak for speaker to sound harder.
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:
Guys We have got Official Support From XDA Please Move This Thread To Our Device Section
Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183
Great Guide Man! Thanks a lot.
So over the last few days I was able to get efi-droid to load onto my nextbit robin. I got lk.img to boot, display screen properly and was also able to finalize my device using the porting guide available on the efi-droid github. At one point I was able to get uefi_boot.img to load and list my internal rom but after starting fresh (restoring PC) I can't get it to fastboot boot after recompiling. Who knows, maybe I missed a key variable.. The fact that I was able to get it to load and display my internal and boot from it is a sign that this modification (with the right config) is able to be fully ported to this device.. I have decided to steer away from the project because I just don't have the knowledge to do this entirely.
My current config files:
https://github.com/AnierinBliss/uefi_ether (lk.img boots with fastboot access and display working with this config although I'm pretty certain that the fstab.multiboot is invalid)
Efi-droid porting guide:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
Some notes for your build environment:
execute sudo -s before source build/envsetup.sh for every terminal you open so that fastboot can interact with finalize_device device/nextbit/ether which comes later in the port process
You'll want to do this as well to make sure you don't get build errors:
cd uefi/lkl git checkout a063e1631db5e2b9b04f184c5e6d185c1cd645cb
Quick note on sudo -s: If you set up the udev rules correctly using existing guides, you don't need to run the compilation as root and so you save yourself the annoyance of having your output files owned by root
Alexandroid99 said:
Quick note on sudo -s: If you set up the udev rules correctly using existing guides, you don't need to run the compilation as root and so you save yourself the annoyance of having your output files owned by root
Click to expand...
Click to collapse
Moderator would only move it to the q&a section which is fine for now because in all reality it really is a question. Who knows, the dev for efi droid has been rewriting a lot of his code due to the "big rewrite" in his words. So I might give it another go from scratch within the next few days unless someone else wants to give it a try. It's possible to port it and I for one have seen it in action. Hopefully one day we can multi boot this beast.