Related
Im looking to use qtek's sense 1.5 since it is the most stable hero rom of them all+ camera wrks like it should. ima do a ap2sd script.(ima use this until cyanogen posts a full enclair (2.1/2.0) upgrade to 4.2.14 or somethin like that idk lol...and ive done some extensive searching for the boot.img/RAM Hack to remove 10mb from the GPU and add it to the existing 97mb for use. I have a MT3G and i even looked in the sapphire forums and used search. Can someone enlighten me on this matter?
ima tell yo, boy, this is da dream forumz, lol, so ya be wanna be lookin at da sapphire forums, yo, lol
jubeh said:
ima tell yo, boy, this is da dream forumz, lol, so ya be wanna be lookin at da sapphire forums, yo, lol
Click to expand...
Click to collapse
U fial at eglish, yo. Boi!
jubeh said:
ima tell yo, boy, this is da dream forumz, lol, so ya be wanna be lookin at da sapphire forums, yo, lol
Click to expand...
Click to collapse
i get all my roms from here because the MT3G is PVT Board 32B and the sapphire forums mainly support PVT Board 32A to almost like 95%. I cant flash any of those roms or i'll brick my phone.
boimarc89 said:
i get all my roms from here because the MT3G is PVT Board 32B and the sapphire forums mainly support PVT Board 32A to almost like 95%. I cant flash any of those roms or i'll brick my phone.
Click to expand...
Click to collapse
I would ask in their Q&A section then, someone is bound to be able to help you
Meh, fail troll has failed.
Get the boot.img from the ramhack thread (select any you wish), make a note of which version of CM kernel you're getting the boot.img for, then get a CM build of that version and pull out the /system/lib/modules and /system/modules directories (you'll need these later so you can have wifi working etc).
In linux, download "extract-kernel.pl", "extract-ramdisk.pl", and the "mkbootimg" binary (google them) and add them to your $PATH (for example, toss them in ~/bin and when you open a terminal, export $PATH = $PATH:~/bin).
The reason the hacked boot.img can't boot the Hero build is because of differences at the ramdisk, so you just need to repack a new boot.img with the ramhacked-kernel and the desired target ramdisk.
First, extract the kernel from the ramhacked boot.img (extract-kernel.pl boot.img), then extract the ramdisk from the QTek boot.img (extract-ramdisk.pl boot.img). When you extract the ramdisk, you'll end up with a bunch of directories, a couple init.rc files, and a .gz, that one is the already-compressed ramdisk, so now all you have to do is (mkbootfs --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz -cmdline "no_console_suspend=1 console=null" -o 10mbBoot.img).
After you have your 10mbBoot.img, you can rename it to boot.img (or flash it through fastboot) and the rom will have the 10 MB ramhack now.
Now, remember those /system/lib/modules and /system/modules? From /system/lib/modules you need wlan.ko and from /system/modules you need modules.sqfs. The reason is that the modules are created against the kernel, so, if you change the kernel, the modules won't work anymore. So, now you have to take the two you got from CM's kernel and toss them to the Hero rom with the hacked kernel, and that is the short and long of it.
By the way, does the 10 MB ramhack work on the Sapphire? (they should rename the Sapphire forum "Magic" since the 32a board is the Magic and the 32b is the Sapphire).
Here's a good guide, but this is from the hero roms forum. The difference is we don't use an offset when packing our boot.imgs
http://forum.xda-developers.com/showthread.php?t=551711&highlight=extract-kernel.pl
jubeh said:
Here's a good guide, but this is from the hero roms forum. The difference is we don't use an offset when packing our boot.imgs
http://forum.xda-developers.com/showthread.php?t=551711&highlight=extract-kernel.pl
Click to expand...
Click to collapse
is there a simpler method bcuz im unfamilliar with running`linux codes and scripts unfortunately. is there a boot.img available for flashing in terminal because i bricked my phone a few min ago trying this boot.img from WG build Y`w/ CM 4.2.13 (shoulda known betta lol)
boimarc89 said:
is there a simpler method bcuz im unfamilliar with running`linux codes and scripts unfortunately. is there a boot.img available for flashing in terminal because i bricked my phone a few min ago trying this boot.img from WG build Y`w/ CM 4.2.13 (shoulda known betta lol)
Click to expand...
Click to collapse
For someone who just bricked their phone, you seemed awfully nonchalant. =/
BoomBoomPOW said:
For someone who just bricked their phone, you seemed awfully nonchalant. =/
Click to expand...
Click to collapse
i just reflashed sappimg.nbh, updated the spl, and redid everything lol...
do u kno what boot.img with the ram hack works w/ qteknologys official sense rom?
boimarc89 said:
i just reflashed sappimg.nbh, updated the spl, and redid everything lol...
do u kno what boot.img with the ram hack works w/ qteknologys official sense rom?
Click to expand...
Click to collapse
then you didnt brick it you just flashed wrong.........
People will usually call "brick" anything that doesn't lead to a home screen >.<. What you got instead is a soft-brick which can be recovered from easily (just fastboot flash boot the old boot.img), so going sappimg.nbh was a bit overdoing it.
I thought you had working knowledge of linux. Your best option is asking for people to do it for you rather than asking them how to do it.
Post me some links for the rom you want to use and the kernel you want to use. If I'm in a good mood later tonight when I'm off of work I'll make you a noob-friendly update.zip that you can apply on top of the QTek rom so you get your 10 MB hack (again, does it really work on sapphire???).
jubeh said:
Post me some links for the rom you want to use and the kernel you want to use. If I'm in a good mood later tonight when I'm off of work I'll make you a noob-friendly update.zip that you can apply on top of the QTek rom so you get your 10 MB hack (again, does it really work on sapphire???).
Click to expand...
Click to collapse
yea it does but only on 32B..i been wanting to build a hero rom or atleast modify linux codes and scripts but idk where to start or how and where to gain basic knowledge of it .u and devs like cyanogen, WesGarner and eugene make it sound soooo easy ..but heres the link to the exact build i got from qtek
http://forum.xda-developers.com/showpost.php?p=4754143&postcount=6
if u can, can u do sneak an a2sd script in there for me too because it doesnt come with it lol. thanks for you help
Here it is:
Q-Tek_32B_3.03.990.6_10MBHack.zip
It's Cyanogen's latest 4.2.13 kernel with BFS-313 (for a speed boost on a Sense rom) on top of Q-Tek's Magic-Sense port for Sapphire (3.03.990.6)'s ramdisk.
The rom does seem to implement a2sd, so there's something you're doing wrong.
Flash Q-Tek's rom first, and then this (doesn't matter of your reboot in between). Don't ask me how to flash or I'll have to shoot you.
jubeh said:
Here it is:
Q-Tek_32B_3.03.990.6_10MBHack.zip
It's Cyanogen's latest 4.2.13 kernel with BFS-313 (for a speed boost on a Sense rom) on top of Q-Tek's Magic-Sense port for Sapphire (3.03.990.6)'s ramdisk.
The rom does seem to implement a2sd, so there's something you're doing wrong.
Flash Q-Tek's rom first, and then this (doesn't matter of your reboot in between). Don't ask me how to flash or I'll have to shoot you.
Click to expand...
Click to collapse
thanx a million mann..i owe u one!!!!
where i go to read up on how to start doing linux stuff as a beginner....dummie edition lol
Need Help.
jubeh said:
Meh, fail troll has failed.
Get the boot.img from the ramhack thread (select any you wish), make a note of which version of CM kernel you're getting the boot.img for, then get a CM build of that version and pull out the /system/lib/modules and /system/modules directories (you'll need these later so you can have wifi working etc).
In linux, download "extract-kernel.pl", "extract-ramdisk.pl", and the "mkbootimg" binary (google them) and add them to your $PATH (for example, toss them in ~/bin and when you open a terminal, export $PATH = $PATH:~/bin).
The reason the hacked boot.img can't boot the Hero build is because of differences at the ramdisk, so you just need to repack a new boot.img with the ramhacked-kernel and the desired target ramdisk.
First, extract the kernel from the ramhacked boot.img (extract-kernel.pl boot.img), then extract the ramdisk from the QTek boot.img (extract-ramdisk.pl boot.img). When you extract the ramdisk, you'll end up with a bunch of directories, a couple init.rc files, and a .gz, that one is the already-compressed ramdisk, so now all you have to do is (mkbootfs --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz -cmdline "no_console_suspend=1 console=null" -o 10mbBoot.img).
After you have your 10mbBoot.img, you can rename it to boot.img (or flash it through fastboot) and the rom will have the 10 MB ramhack now.
Now, remember those /system/lib/modules and /system/modules? From /system/lib/modules you need wlan.ko and from /system/modules you need modules.sqfs. The reason is that the modules are created against the kernel, so, if you change the kernel, the modules won't work anymore. So, now you have to take the two you got from CM's kernel and toss them to the Hero rom with the hacked kernel, and that is the short and long of it.
By the way, does the 10 MB ramhack work on the Sapphire? (they should rename the Sapphire forum "Magic" since the 32a board is the Magic and the 32b is the Sapphire).
Click to expand...
Click to collapse
I'm sorry to kick an old thread, but I've tried this method with multiple kernels for 1.5 hero roms and I seem to break wifi everytime (yes I'm pushing the wlan.ko and modules.sqf). Is there something in the kernel itself that I need to change in order to not break the wifi? Thanks.
Red.
Everything needs to go in /sdcard/andboot
FILES YOU NEED:
the nbh flashed to your phone
an sd card with the andboot folder at the top level
an androidinstall.tar file plopped into the andboot folder
thats it
then just hold down volume up or dpad center or the middle of your touchscreen when booting and go through the menu to choose where to put things and then install the system. (for those without a dpad, pretend the touchscreen is a giant dpad)
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up (camera on kaiser/polaris) just like the nand people (but don't pick nand to store the files, it won't work)
---------
all the files
basefiles for the haret folks out there
Grab the nbh files for your device. Only difference between eclair and non-eclair is that eclair is set up to use the newer hw3d driver, non-eclair is set to use the older one (for donut/cupcake)
These do not use rootfs. They remove it completely and free up that extra space in your nand for a bigger, cleaner system.
They also have my new menu-based installer! Yay! Just hold-down volume-up or dpad center or the middle of your touchscreen
THIS WON'T WORK WITH ANY OF THE OLDER SYSTEMS! THE SYSTEM MUST INCORPORATE THE APPROPRIATE FILES FROM ROOTFS (and the rom cooks will let you know when theirs is ready)
The first system to use this is based on eclair 2.1 with working sleep and audio
Here's my tattoo system for this method
FYI Craig & I spent a lot of time on these!!!
How to create a build
How to make your build work with this
So it actually isn't that hard.
Extract your sqsh to a folder somewhere, so you have, say /android/system
Mount/extract whichever rootfs worked best with your system somewhere else, say /android/rootfs
Code:
cp -a /android/rootfs/init.etc/* /android/system/etc
cp /android/rootfs/lib/donut/* /android/system/lib
cp /android/rootfs/lib/modules/* /android/system/lib/modules
cp /android/rootfs/lib/hw/* /android/system/lib/hw
cp /android/rootfs/init.cfg/init.donut.rc /android/system/sysinit.rc
You'll need to modify the sysinit.rc a bit, as in the rootfs some things are commented out that shouldn't be, and it references a few things in /bin or /etc that aren't there anymore.
Also, don't forget to uncomment the line near the top of sysinit.rc that creates a symlink from /system/etc to /etc
Once you are done, just do this to create the installer:
Code:
cd /android
tar cvf androidinstall.tar system
Soon, I may upload some packs for making the process easier, with updated sysinit.rc's for each system type. If I have time, we'll see...
Note, you can update the contents of the .tar file from windows/izarc/winrar/etc and it'll still work. you don't need to keep messing about with linux anymore if you don't want to
How to update things
How to create an update pack
Since not everyone gets things right the first time, and we keep getting updates, the rootfs made it easy to install updates without downloading the whole system again.
Well now anyone can create an update pack
just create a tar file called androidupdate.tar, make sure it has everything in a /system folder with whatever files you want, drop it into /sdcard/andboot and reboot holding down volume-up (camera on kaiser/polaris). Choose the update option and you should be good to go.
If things get wonky when you try to boot up, give the fix permissions option a shot in the installer, if it still fails, try wiping the dalvik cache, that can fix things up too.
About the installer
I ripped it off from here, but put about 6 or 7 solid hours into getting it to fit and react with the keys/screen
May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?
sshark said:
May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?
Click to expand...
Click to collapse
whats a rootfs hahaha
Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.
nabicat said:
Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.
Click to expand...
Click to collapse
what the..... that was random
Holy cow.. like there's nothing even in this thread and it's already filling up..
I think I know what it is..
Vilord ported Dalvik from 2.5 which now includes native support for HW accel for MSM7500..
jesus.
Do we still need to have three partitions on the card? Or would one FAT32 partition be sufficient?
@vilord:
is everything needed for the rootfsless nbh in the git? I would like to test this with ´my kaiser
This works for Polaris? Really thanks!
the bootenv git should have everything needed for this. I haven't tested on my polaris yet, but it should "just work" on polaris and kaiser as long as martin's method to drop the active key into /proc works on all hardware.
What happens to the .conf files?
What about /media ?
Thanks for all of your efforts
conf files are no longer used from the sd card.
If the cook put things in the right places, there should be a /system/etc/userinit.conf that gets parsed during android boot, but it is up to the cook to not screw that up.
This way is a lot cleaner, but it does a LOT less handholding for lazy cooks.
the upside is that it is *very* easy for anybody to fix a broken androidinstall by just piecing together what needs to change into an androidupdate.tar
/media is still used if it is on your SD card, but there's enough space and things are fast enough that media files should be included in /system now
This is a HUGE development for rom devs.
I will be honest in saying I've been having a hard time not hitting the 90MB cap with my next Warm Donut release.
Infact, I spent 4 hours yesterday de-odexing and compressing the classes.dex back into the jars and apks to save space.
With this new method this gives us ALOT more space. I applaud you for doing this. It breaks alot of the current builds but at the same time gives us a ton more flexibility for future.
And what I really like from this is it removes the confusion and headaches on configuration, giving the power to the ROM dev to include the necessary settings.
Question though. Different phones (Vogue, Polaris, Kaiser) may require different configurations. In the past it was a simple "just use this conf with this phone"
Thanks again
so when running from haret - getting an error about looking for a system file, I have all the files in andboot folder, any ideas on what I'm missing.
Know what would be really nice? In the setup, the ability to change LCD_Density and resolution.
This would eliminate the confusion users may have in editing the build.prop and rom files to change these values.
I guess the ROM devs could distribute separate files/tars for each res/density but that gets redundant if you know what I mean.
I'm using haret, but I dont see any option to choose to install not to nand, i get into the installer and it says install system so i click that but then it just goes through installation and fails. How do i choose to install to sd card?
*Update: These instructions now seem to be outdated. I will started an updated thread here: http://forum.xda-developers.com/showthread.php?t=648045
------------
(sorry I tried to post some live links, but the forum won't allow them cause I'm a new user, so this may not be as helpful as I hoped...)
I just spent some hours wading through the forums to find complete instructions for installing the newer android builds using the WM haret.exe linux booter (rather than flashing the entire phone and loosing WM) on my touch Vouge.
I am a bit of a newb, but since I did not find complete instructions, and had to figure some things out using trial and error I thought I would post what I did figure out here in hopes of helping others.
First ignore the install instructions here. sourceforge.net/apps/trac/androidhtc/wiki/HowToInstall . They are old and need to be updated.
Erase all previous android files from your sd card
Go here: sourceforge.net/projects/androidhtc/files/
haretinstall.zip
open the zip and place the andboot folder and all its contents on the / directory of your SD card
then download eclair252_androidinstall.zip
unzip eclair252_androidinstall.zip to get androidinstall.tar
copy androidinstall.tar to your sdcard /andboot folder
(unnecessarily steps deleted - see below)
Then on your phone's file explorer run haret.exe from /andboot folder on you sd card
click run and immediately hold the volume switch up as linux boots
the boot menu appears. choose install
if the installation hangs hold volume up again, and choose quit
As I said I'm new at this, so my instructions may be off or misguided. If so please post with corrections. I just know I was looking for a guide like this and couldn't find one so hope this helps someone.
umbilicalbungee said:
(sorry I tried to post some live links, but the forum won't allow them cause I'm a new user, so this may not be as helpful as I hoped...)
I just spent some hours wading through the forums to find complete instructions for installing the newer android builds using the WM haret.exe linux booter (rather than flashing the entire phone and loosing WM) on my touch Vouge.
I am a bit of a newb, but since I did not find complete instructions, and had to figure some things out using trial and error I thought I would post what I did figure out here in hopes of helping others.
First ignore the install instructions here. sourceforge.net/apps/trac/androidhtc/wiki/HowToInstall . They are old and need to be updated.
Erase all previous android files from your sd card
Go here: sourceforge.net/projects/androidhtc/files/
download basefiles.zip
open the zip and place the andboot folder and all its contents on the / directory of your SD card
then download eclair252_androidinstall.zip
unzip eclair252_androidinstall.zip to get androidinstall.tar
copy androidinstall.tar to your sdcard /andboot folder
then download vogueeclairnbh.zip
unzip vogueeclairnbh.zip to get VOUGIMGx480.NBH
copy VOUGIMGx480.NBH to your sdcard /andboot folder
Then on your phone's file explorer run haret.exe from /andboot folder on you sd card
click run and immediately hold the volume switch up as linux boots
the boot menu appears. choose install
if the installation hangs hold volume up again, and choose quit
As I said I'm new at this, so my instructions may be off or misguided. If so please post with corrections. I just know I was looking for a guide like this and couldn't find one so hope this helps someone.
Click to expand...
Click to collapse
Actually, you just answered my question (which I never posted) about NoRootFS.... Thanks for posting this!!!!
THANK YOU!!!
can you explain what is the benefits of doing it this way compared to the way its always been for me. it was as simple as downloading the sqsh package zip file from my favorite build here. witch included all the files i needed to run anroid. I copied the android folder from the zip file to the root of my sd card and simply ran haret exe. It used to be complicated but not now that most builds include all the basefiles needed for boot. I never had to hold any volume buttons or install anything. i probably look dumb for asking this.
incubus26jc said:
can you explain what is the benefits of doing it this way compared to the way its always been for me. it was as simple as downloading the sqsh package zip file from my favorite build here. witch included all the files i needed to run anroid. I copied the android folder from the zip file to the root of my sd card and simply ran haret exe. It used to be complicated but not now that most builds include all the basefiles needed for boot. I never had to hold any volume buttons or install anything. i probably look dumb for asking this.
Click to expand...
Click to collapse
Although I have not yet tried myself because I have a Polaris and WiFi is not yet working, my understanding is that NoMoRootFS makes more space available for the ROM and makes it easier for developers to roll out updates. In the thread for Myn's (most excellent) Warm Donut, there are several themes and updates that can only be applied to Rev2 if you have installed via NoMoRootFS.
umbilicalbungee said:
First ignore the install instructions here. sourceforge.net/apps/trac/androidhtc/wiki/HowToInstall . They are old and need to be updated.
Erase all previous android files from your sd card
Go here: sourceforge.net/projects/androidhtc/files/
download basefiles.zip
open the zip and place the andboot folder and all its contents on the / directory of your SD card
then download eclair252_androidinstall.zip
unzip eclair252_androidinstall.zip to get androidinstall.tar
copy androidinstall.tar to your sdcard /andboot folder
[*]then download vogueeclairnbh.zip
[*]unzip vogueeclairnbh.zip to get VOUGIMGx480.NBH
[*]copy VOUGIMGx480.NBH to your sdcard /andboot folder
Then on your phone's file explorer run haret.exe from /andboot folder on you sd card
click run and immediately hold the volume switch up as linux boots
the boot menu appears. choose install
if the installation hangs hold volume up again, and choose quit
Click to expand...
Click to collapse
I think that this step is not needed. The NBH files were made for flash your phone. If you run Haret is not needed.
Am I right?
ryomahino said:
I think that this step is not needed. The NBH files were made for flash your phone. If you run Haret is not needed.
Am I right?
Click to expand...
Click to collapse
correct. with the OP method, the .nbh file is just taking up space. you never need to do anything with a .nbh file if you are using haret. OP, please fix and I will add to my list of FAQs, otherwise very informative. thx.
Help
I can't get this to boot on my Vogue. The black Linux screen pops up & starts running but stops. The last line says...
[ 2.226233] Rebooting in 3 seconds.._
I've followed your instruction to the letter & can't see to get it to work. Anyone have suggestions?
Emmie0702 said:
I can't get this to boot on my Vogue. The black Linux screen pops up & starts running but stops. The last line says...
[ 2.226233] Rebooting in 3 seconds.._
I've followed your instruction to the letter & can't see to get it to work. Anyone have suggestions?
Click to expand...
Click to collapse
Did you get into the install menu by holding volume up? easiest and quickest way to help you is if you describe exactly what you did - I know it is similar to the OP, but just give a step by step in your own words.
I did all of the steps but linux boot stops at : failed to reach system.img on SD Card...
tatnai said:
Did you get into the install menu by holding volume up? easiest and quickest way to help you is if you describe exactly what you did - I know it is similar to the OP, but just give a step by step in your own words.
Click to expand...
Click to collapse
Did didn't get past the Linux menu. It only ran for about 4 or 5 seconds then locked up. I had to soft reset to get my phone functioning again.
I did exactly what the instructions in the 1st post said to do.
Downloaded andboot file to \storage card\andboot
Downloaded androidinstall.zip & placed in the andboot file
Clicked haret.exe
Selected run while holding up the volume key
I read in the post that the below items were not necessary so I skipped them:then download vogueeclairnbh.zip
unzip vogueeclairnbh.zip to get VOUGIMGx480.NBH
copy VOUGIMGx480.NBH to your sdcard /andboot folder
I'm running stock rom. My carrier is nTelos (CDMA).
I notice that your rom version and radio version are not the latest. You may have to ungrade those before you can get it to run.
Emmie0702 said:
Did didn't get past the Linux menu. It only ran for about 4 or 5 seconds then locked up. I had to soft reset to get my phone functioning again.
I did exactly what the instructions in the 1st post said to do.
Downloaded andboot file to \storage card\andboot
Downloaded androidinstall.zip & placed in the andboot file
Clicked haret.exe
Selected run while holding up the volume key
I read in the post that the below items were not necessary so I skipped them:then download vogueeclairnbh.zip
unzip vogueeclairnbh.zip to get VOUGIMGx480.NBH
copy VOUGIMGx480.NBH to your sdcard /andboot folder
I'm running stock rom. My carrier is nTelos (CDMA).
Click to expand...
Click to collapse
Stevevo said:
I notice that your rom version and radio version are not the latest. You may have to upgrade those before you can get it to run.
Click to expand...
Click to collapse
always good to have latest radio. i don't know if it will interfere with you booting linux, usually it creates problems with gps or data once you are in android. but who knows, anything is possible I suppose.
list the files that are in /sdcard/andboot/ emmie0702
I've always wanted to update me ROM but there is not a Server cab out there that will give me back my settings for nTelos. Its a small cell network therefore no one has bothered to create one (I really can't blame them). So I've never tried it out of fear of Bricking my phone. For some reason nTelos did not offer WiFi, GPS or MMS with this phone through their network (didn't know that until AFTER I bought it). They have it for other phones but not this one for some reason. That was a little annoying when I 1st got it but I've leaned to live without it. I love my phone even w/o those things. I get pics emailed to me & can email them to other's phone through their carrier address (eg [email protected]). WiFi would be nice but I never use GPS. As far as the Radio. I assume it sort of the same step. I pretty much have to install it & it will wipe out or "Hard Reset" my phone, right...causing me to losing all my network info?
Here are the files I have in the andboot folder:
androidinstall
default
haret
initrd
READE-BASEFILES
zImage
zImage-eclair
** I could not file the "eclair252_androidinstall.zip" file to download so I downloaded the androidinstall.zip under the "2010-01-05" folder from sourceforge.net/projects/androidhtc/files/. Could that be the problem or could it be a combination of my Radio/ROM & the androidinstall tar I downloaded?
Thanks for the help guys!
is it androidinstall.zip or androidinstall.tar?
tatnai said:
is it androidinstall.zip or androidinstall.tar?
Click to expand...
Click to collapse
File Name: androidinstall
File Type: WinRAR archive (.tar)
Emmie0702 said:
I've always wanted to update me ROM but there is not a Server cab out there that will give me back my settings for nTelos. Its a small cell network therefore no one has bothered to create one (I really can't blame them). So I've never tried it out of fear of Bricking my phone. For some reason nTelos did not offer WiFi, GPS or MMS with this phone through their network (didn't know that until AFTER I bought it). They have it for other phones but not this one for some reason. That was a little annoying when I 1st got it but I've leaned to live without it. I love my phone even w/o those things. I get pics emailed to me & can email them to other's phone through their carrier address (eg [email protected]). WiFi would be nice but I never use GPS. As far as the Radio. I assume it sort of the same step. I pretty much have to install it & it will wipe out or "Hard Reset" my phone, right...causing me to losing all my network info?
Here are the files I have in the andboot folder:
androidinstall
default
haret
initrd
READE-BASEFILES
zImage
zImage-eclair
** I could not file the "eclair252_androidinstall.zip" file to download so I downloaded the androidinstall.zip under the "2010-01-05" folder from sourceforge.net/projects/androidhtc/files/. Could that be the problem or could it be a combination of my Radio/ROM & the androidinstall tar I downloaded?
Thanks for the help guys!
Click to expand...
Click to collapse
you should be able to update your radio without touching your rom, there is a radio only version of 3.42.50, see the faqs noob guide to flashing, it is in there.
I am unsure what you downloaded; it looks like you have the right basefiles, but if you got androidinstall.zip from 2010-01-05 I don't think it will have anything compatible with the norootfs method, and is probably causing your problem.
delete androidinstall.tar, download this and drop the androidinstall.tar that is inside into your sdcard/andboot/ folder. then run haret and keep holding volume up until you see the install menu. then post back.
tatnai said:
you should be able to update your radio without touching your rom, there is a radio only version of 3.42.50, see the faqs noob guide to flashing, it is in there.
I am unsure what you downloaded; it looks like you have the right basefiles, but if you got androidinstall.zip from 2010-01-05 I don't think it will have anything compatible with the norootfs method, and is probably causing your problem.
delete androidinstall.tar, download this and drop the androidinstall.tar that is inside into your sdcard/andboot/ folder. then run haret and keep holding volume up until you see the install menu. then post back.
Click to expand...
Click to collapse
OK. Same thing...phone locks up at the same place. I downloaded the file you attached & downloaded the VOGUIMG.nbh file that was linked on PPCGeeks. I followed the instructions on PPCGeeks post "This is the vogue radio 3.42.50 designed for the vogue (this is not the titan port). I removed it directly from the bell rom and recomplied it as a radio only .nbh. This is a radio only rom designed to be flashed from bootloader from sd card and doesn't require a hard reset. Copy VOGUIMG.nbh to root of fat32 micro sd card 2gb or less and place phone in bootloader and it will run."
I still get the same outcome. Both your attachment & the VOGUIMG.nbh file are located \Storage Card\ on my phone. When the Radio instructions say its designed to be flashed from Bootloader what exactly does that mean? Do I need a program for that or is it suppose to start when I Run the default.txt after I select haret in the andboot folder?
the place you got the link to the radio only version also has instructions on how to flash your phone - see the before starting area. short: get into bootloader mode, then flash.
I still think there is something else that you are doing wrong, I just can't put my finger on it right now; i'm hoping others will be able to help.
tatnai said:
the place you got the link to the radio only version also has instructions on how to flash your phone - see the before starting area. short: get into bootloader mode, then flash.
I still think there is something else that you are doing wrong, I just can't put my finger on it right now; i'm hoping others will be able to help.
Click to expand...
Click to collapse
OK. I figured out how to get it in bootloader mode (power button + camera + soft reset). The Red/Blue/Green screen pops up & then a Grey screen that says "loading...". Its been "loading" for over 5 minutes now. What could be the problem?
I want to edit the system.sqhs and insert new fonts.
someone know how to do it?
in linux
unsquashfs system.sqsh
here is a tutorial
http://forum.xda-developers.com/showthread.php?t=610303
Maikeu Locatelli said:
in linux
unsquashfs system.sqsh
here is a tutorial
http://forum.xda-developers.com/showthread.php?t=610303
Click to expand...
Click to collapse
Hey Maikeu,
Is there a tutorial something like that except for topaz maybe? I can successfully unsquashfs the XDAndroid 2.1 system.sqsh just fine...but when I try to unsquashfs the 1.6 (TopazKernal16) system.sqsh, it makes it to about 70% then stops saying "Killed".
If you could point me in the right direction for help, that would be great! If it makes a difference, I'm actually using Vector Linux instead of Ubuntu.
Thanks!
iceman198 said:
Hey Maikeu,
Is there a tutorial something like that except for topaz maybe? I can successfully unsquashfs the XDAndroid 2.1 system.sqsh just fine...but when I try to unsquashfs the 1.6 (TopazKernal16) system.sqsh, it makes it to about 70% then stops saying "Killed".
If you could point me in the right direction for help, that would be great! If it makes a difference, I'm actually using Vector Linux instead of Ubuntu.
Thanks!
Click to expand...
Click to collapse
Ok...it took me forever but I figured it out...
Just a couple things to note (in case anyone else is trying to do this)...when you "unsquash" the system.sqsh, it creates a "squashfs-root" folder where everything is. Move all that stuff up a folder so it's all in the "system" folder and you can delete the "squashfs-root".
Also, when using "mksquashfs" make sure to use " -nolzma" at the end...Don't quite know what it is, must be something with compression because I notices the end sqsh file is slightly bigger...but that's what you have to tag on so when booting Android it can actually mount the sqsh file.
iceman198 said:
Hey Maikeu,
Is there a tutorial something like that except for topaz maybe? I can successfully unsquashfs the XDAndroid 2.1 system.sqsh just fine...but when I try to unsquashfs the 1.6 (TopazKernal16) system.sqsh, it makes it to about 70% then stops saying "Killed".
If you could point me in the right direction for help, that would be great! If it makes a difference, I'm actually using Vector Linux instead of Ubuntu.
Thanks!
Click to expand...
Click to collapse
Sorry, i never tried and i dont understand a lot of this to help you, i know only how to unpack and repack, really sorry.
Have a lot of people that know, but i dont know why, they dont help us.
i know that the squashfstools 4 dont works, it unpack, but the repack dont works in kernel of pphusson, the 3.3.7 works good for me
http://ftp.debian.org/debian/pool/main/s/squashfs/
iceman198 said:
Ok...it took me forever but I figured it out...
Just a couple things to note (in case anyone else is trying to do this)...when you "unsquash" the system.sqsh, it creates a "squashfs-root" folder where everything is. Move all that stuff up a folder so it's all in the "system" folder and you can delete the "squashfs-root".
Also, when using "mksquashfs" make sure to use " -nolzma" at the end...Don't quite know what it is, must be something with compression because I notices the end sqsh file is slightly bigger...but that's what you have to tag on so when booting Android it can actually mount the sqsh file.
Click to expand...
Click to collapse
is rename the "squashfs-root" to "system" is good enough ?
yosidia said:
is rename the "squashfs-root" to "system" is good enough ?
Click to expand...
Click to collapse
yeah, that will work...but you can just keep it the same name without every creating a "system" folder. I don't even bother using the "genext2fs" tool...I just "unsquashfs" it and it will create the "squashfs-root" folder and then when I'm done modifying it, just
Code:
mksquasfs squashfs-root system.img -nolzma
and that should do it.
You'll know if it doesn't work cuz Android will error while loading system.sqsh. =)
-wrong topic-
This is being released for TESTING PURPOSES ONLY. This is not intended to be a full release.
This is an SD Card release ONLY, if you want to flash the entire phone, visit the original thread. Beyond that, the build is 100% unchanged from the 7/10/2010 release of Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] - this is not the all languages release, just the standard RLS10 as downloadable from here.
All original information is in Incubus' original thread: http://forum.xda-developers.com/showthread.php?t=712310
I may just be being impatient, but this froze up on me a couple of times right after completing setup and beginning sync. Still, I have been able to fully install, boot the phone through HaRET, get text messages, and a little more. I've barely had much time to test this, but it's a step above your traditional proof of concept, so try it out!
Note, this release is not intended to either show up Incubus26Jc, nor claim his work as my own. I simply made the conversion and RAR'd it up. I'm sure Incubus26Jc chooses not to make an SDCard version available for his own reases and possibly doesn't want his name associated for whatever reason, I didn't clear this release in advance, and if requested, I will delete the thread.
>>>Direct Download Nu-Incubus Super FroYo 2.2 RLS10SD<<<
NuAngel said:
I actually bought a few pieces of software to do the conversion, but I figured a few bucks was worth it for something fun like this. Although, if anybody would like to donate a few bucks to the cause, PM me and I can get you my paypal address.
Click to expand...
Click to collapse
What exactly did you "convert"? And what software did you need? From first glance it just looks like you just threw the tar in with all the sdcard files found in other builds. The extracted tar and tgz are the same size... and you said that it's 100% the same thing... so why do we need a separate thread for this? Just ask Incubus if he could add the andboot files in a separate download in the original thread...
Well, in most basic terms all I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel
NuAngel said:
Well, I'll just say the most basic thing I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel
Click to expand...
Click to collapse
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...
egzthunder1 said:
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...
Click to expand...
Click to collapse
I am using Androidinstall.tgz files. Just install it to the SD card using the norootfs method that has been used for a while. His builds aren't anti-SD card from what I can tell...
Thanks for the kind words, EGZ. Wasn't trying to take any attention away from Incubus at all, I just wanted to tinker with it, myself, which was why I released it! I don't really intend to keep up with future releases, unless people actually want me to continue.
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Do I understand this correctly?
Are you basically just wanting to install the Incubus FroYo build on the SD card? I was unsure about the exact method to do this as well. Here are the steps I followed to make it happen.
I think I did something similar to what you are doing here, except the convert the tgz to tar. All I did was take the tgz file and rename the extension to tar. No zipped or rar file program needed. Then I grabbed the basic haret files from Myn's eclair along with the updated zImage file. I threw it all in the andboot dir on the SD card. Everything installed just fine. Is this what you are trying to accomplish?
Vivafutbol - yup, pretty much the same process - I just never expected renaming the TGZ to TAR to work - they're similar fromats, but not identical... surprised it worked!
Still, if anyone is interested in checking it out, they can download it from the link above, no need to do any work.
NuAngel
NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..
NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
Just out of curiosity, what program did you have to purchase that does this?
milanche said:
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..
Click to expand...
Click to collapse
Doesn't HaRET just boot the zImage? Then in the kernel is where you would activate the system image like in the old days, or the adroidinstall.tar or tgz?
Forget I tried.
Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.
NuAngel said:
Forget I tried.
Click to expand...
Click to collapse
It's great that you tried. You won't get the experience unless you do try.
The only problem I have with all of this is that you indirectly asked if people would donate to you. You couldve done a little research and found out that you didnt need to spend any money.
I'm not trying to attack you, you just couldve went about it differently. Asked Incubus if he could host it in the original thread (and at least given you credit), or if he would mind if you opened a new thread. I'm not speaking for him but I'm sure he would'nt have mind.
Again, I think it's great that you tried this on your own. We need more people like that in this community.
NuAngel said:
Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.
Click to expand...
Click to collapse
I did it manually as well, and I didn't even rename the .tgz to .tar
I admit I had to hunt around for some files, so this does help, thank you
Its not my rom either. Its dzo's rom. I just done a few things to it. The reason i never put up sd install files in the roms is because of all the problems people usually have until they flash nand and all is better. I can put the haret files on the OP if you would like. No harm done buddy.
I saw your windows rom but haven't tried it yet because i'm still using nfsfan. Apreciate someone new taking an interest in vogue. Also I did flash froyo to my sd card but did have to read quite a bit. I am sure I would have appreciated being spoon fed. Thanks.
Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel
NuAngel said:
Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel
Click to expand...
Click to collapse
Also, the initrd.gz is very old (Maybe before the .tgz support was implemented). Try using THIS ONE (taken from HERE) with the tgz to see if it works.
I hope you did not take my post on the negative side. At the very least this thread has created some good conversation about how these files actually work together. I did have to search around for a while to get an understanding of which files should be used.
I personally like the SD version of the builds, because I don't have the guts to wipe out the windows install and risk breaking this great little device.