PPCGeeks
Page 56 of 69 « First 6465455 56 575866 Last »
Show 40 post(s) from this thread on one page

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   Android On TP2 Development (http://forum.ppcgeeks.com/forumdisplay.php?f=319)
-   -   NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery (http://forum.ppcgeeks.com/showthread.php?t=134598)

natemcnutty 03-27-2011 01:21 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2074586)
Nate. must have broken something. Cant seem to boot off the autobuild version of the initrd.

Missing commits to tinboot? I got the recovery even smaller but hangs on main logo. no double vib so im assuming it may be the same issue as before. Right now the nbh is about 3.4mb
My tinboot2.S is the same as git. All I did was name it recovery.tgz, put it in /bootenv/initrd, and then built initrd.gz. Then I copied that into /tinboot-linux-msm/kernel, and built the rest. Here is my build script:
Code:
#!/bin/sh
#-------------------------------------------------------------------------
# Build Script for linux-msm-rhod-nand (Android on HTC) kernel, modules, XIP, and NBH
#-------------------------------------------------------------------------
#
# Set the following variables
# ANDROID -- Root director for Android files
ANDROID=~/Desktop/android
# TINBOOT -- tinboot directory
TINBOOT=$ANDROID/tinboot-linux-msm
# TOOLCHAIN_PATH -- directory containing the arm toolchain
TOOLCHAIN_PATH=$ANDROID/toolchain/arm-2010.09/bin/arm-none-eabi
#-------------------------------------------------------------------------

#build initrd and copy to Tinboot
cd $ANDROID/bootenv
sh buildInitrd
cp -f initrd.gz $TINBOOT/kernel

#-----start build XIP-----
# remove old XIP if it exists
cd $TINBOOT
if [  -f xip/rhod ]; then
    rm xip/rhod
    echo Deleting old XIP
fi

# make XIP folder if it does not exist
if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi

# compile tinboot XIP

echo "Start compiling tinboot/xip for rhod....."
$TOOLCHAIN_PATH-as  tinboot/tinboot2.S -o tinboot.o --defsym rhod=1 --defsym MTYPE=2292
$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip
mv tinbootxip xip/rhod

# cleanup tinboot
rm tinboot.o

# make sure XIP build was successful
if [ ! -f xip/rhod ] ; then
    fail "XIP build failed. XIP file was not found."
fi


#-----start build NBH-----
# clean up previous log file
if [ -e "tools/log" ]; then
rm tools/log
fi

# compile tinboot
cp tools/rhod_payload2 os.nb.payload

echo "Inserting tinboot into payload"
wine tools/osnbtool -c os.nb.payload 1 xip/rhod >> tools/log
mv os.nb.payload.NEW os.nb.payload >> tools/log

echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin os.nb.payload os-new.nb.payload >> tools/log

echo "Creating os.nb portion of nbh"
tools/nbmerge < os-new.nb.payload > os-new.nb

echo "Creating NBH"
wine tools/yang.exe -F RHODIMG.NBH -f os-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log

# clean up payloads
rm os.nb.payload
rm os-new.nb.payload
rm os-new.nb

# clean up tinboot directory
rm -rf xip
mv -f RHODIMG.NBH ~/Desktop
I know this works because I had arrrghhh and others flash the 5MB one that had full busybox in recovery without any issues. Do you think it could be a toolchain difference, or is it possible I'm compiling the NBH differently?

[ACL] 03-27-2011 01:26 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2074614)
My tinboot2.S is the same as git. All I did was name it recovery.tgz, put it in /bootenv/initrd, and then built initrd.gz. Then I copied that into /tinboot-linux-msm/kernel, and built the rest. Here is my build script:
Code:
#!/bin/sh
#-------------------------------------------------------------------------
# Build Script for linux-msm-rhod-nand (Android on HTC) kernel, modules, XIP, and NBH
#-------------------------------------------------------------------------
#
# Set the following variables
# ANDROID -- Root director for Android files
ANDROID=~/Desktop/android
# TINBOOT -- tinboot directory
TINBOOT=$ANDROID/tinboot-linux-msm
# TOOLCHAIN_PATH -- directory containing the arm toolchain
TOOLCHAIN_PATH=$ANDROID/toolchain/arm-2010.09/bin/arm-none-eabi
#-------------------------------------------------------------------------

#build initrd and copy to Tinboot
cd $ANDROID/bootenv
sh buildInitrd
cp -f initrd.gz $TINBOOT/kernel

#-----start build XIP-----
# remove old XIP if it exists
cd $TINBOOT
if [  -f xip/rhod ]; then
    rm xip/rhod
    echo Deleting old XIP
fi

# make XIP folder if it does not exist
if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi

# compile tinboot XIP

echo "Start compiling tinboot/xip for rhod....."
$TOOLCHAIN_PATH-as  tinboot/tinboot2.S -o tinboot.o --defsym rhod=1 --defsym MTYPE=2292
$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip
mv tinbootxip xip/rhod

# cleanup tinboot
rm tinboot.o

# make sure XIP build was successful
if [ ! -f xip/rhod ] ; then
    fail "XIP build failed. XIP file was not found."
fi


#-----start build NBH-----
# clean up previous log file
if [ -e "tools/log" ]; then
rm tools/log
fi

# compile tinboot
cp tools/rhod_payload2 os.nb.payload

echo "Inserting tinboot into payload"
wine tools/osnbtool -c os.nb.payload 1 xip/rhod >> tools/log
mv os.nb.payload.NEW os.nb.payload >> tools/log

echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin os.nb.payload os-new.nb.payload >> tools/log

echo "Creating os.nb portion of nbh"
tools/nbmerge < os-new.nb.payload > os-new.nb

echo "Creating NBH"
wine tools/yang.exe -F RHODIMG.NBH -f os-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log

# clean up payloads
rm os.nb.payload
rm os-new.nb.payload
rm os-new.nb

# clean up tinboot directory
rm -rf xip
mv -f RHODIMG.NBH ~/Desktop
I know this works because I had arrrghhh and others flash the 5MB one that had full busybox in recovery without any issues. Do you think it could be a toolchain difference, or is it possible I'm compiling the NBH differently?
ahh i see the differences. The payload is diff plus you are using osnbtool.

I lost track of all the payloads we had. Is your rhod_payload2 different that the rhod_payload we use for git? remember autobuild uses exactly wahts on git.

natemcnutty 03-27-2011 03:15 PM
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by [ACL
]
Quote:
Originally Posted by natemcnutty (Post 2074614)
My tinboot2.S is the same as git. All I did was name it recovery.tgz, put it in /bootenv/initrd, and then built initrd.gz. Then I copied that into /tinboot-linux-msm/kernel, and built the rest. Here is my build script:
Code:
#!/bin/sh
#-------------------------------------------------------------------------
# Build Script for linux-msm-rhod-nand (Android on HTC) kernel, modules, XIP, and NBH
#-------------------------------------------------------------------------
#
# Set the following variables
# ANDROID -- Root director for Android files
ANDROID=~/Desktop/android
# TINBOOT -- tinboot directory
TINBOOT=$ANDROID/tinboot-linux-msm
# TOOLCHAIN_PATH -- directory containing the arm toolchain
TOOLCHAIN_PATH=$ANDROID/toolchain/arm-2010.09/bin/arm-none-eabi
#-------------------------------------------------------------------------

#build initrd and copy to Tinboot
cd $ANDROID/bootenv
sh buildInitrd
cp -f initrd.gz $TINBOOT/kernel

#-----start build XIP-----
# remove old XIP if it exists
cd $TINBOOT
if [  -f xip/rhod ]; then
    rm xip/rhod
    echo Deleting old XIP
fi

# make XIP folder if it does not exist
if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi

# compile tinboot XIP

echo "Start compiling tinboot/xip for rhod....."
$TOOLCHAIN_PATH-as  tinboot/tinboot2.S -o tinboot.o --defsym rhod=1 --defsym MTYPE=2292
$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip
mv tinbootxip xip/rhod

# cleanup tinboot
rm tinboot.o

# make sure XIP build was successful
if [ ! -f xip/rhod ] ; then
    fail "XIP build failed. XIP file was not found."
fi


#-----start build NBH-----
# clean up previous log file
if [ -e "tools/log" ]; then
rm tools/log
fi

# compile tinboot
cp tools/rhod_payload2 os.nb.payload

echo "Inserting tinboot into payload"
wine tools/osnbtool -c os.nb.payload 1 xip/rhod >> tools/log
mv os.nb.payload.NEW os.nb.payload >> tools/log

echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin os.nb.payload os-new.nb.payload >> tools/log

echo "Creating os.nb portion of nbh"
tools/nbmerge < os-new.nb.payload > os-new.nb

echo "Creating NBH"
wine tools/yang.exe -F RHODIMG.NBH -f os-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log

# clean up payloads
rm os.nb.payload
rm os-new.nb.payload
rm os-new.nb

# clean up tinboot directory
rm -rf xip
mv -f RHODIMG.NBH ~/Desktop
I know this works because I had arrrghhh and others flash the 5MB one that had full busybox in recovery without any issues. Do you think it could be a toolchain difference, or is it possible I'm compiling the NBH differently?
ahh i see the differences. The payload is diff plus you are using osnbtool.

I lost track of all the payloads we had. Is your rhod_payload2 different that the rhod_payload we use for git? remember autobuild uses exactly wahts on git.
Ahh yes. The payload 2 is really important. That's the one I fixed the partition table! In the other payload, fatfs partition overwrites tinboot area on reboot.

Also, using nbtools fixes the partition tables based on size of tinboot's XIP.

[ACL] 03-27-2011 04:37 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2074630)
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)



Ahh yes. The payload 2 is really important. That's the one I fixed the partition table! In the other payload, fatfs partition overwrites tinboot area on reboot.

Also, using nbtools fixes the partition tables based on size of tinboot's XIP.
ok so this is a new creation? nothing we have on git rite. Upload it so i can put it on git and have autobuild make one of these nbh with the recovery on it.

natemcnutty 03-27-2011 05:29 PM
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by [ACL
]
Quote:
Originally Posted by natemcnutty (Post 2074630)
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)



Ahh yes. The payload 2 is really important. That's the one I fixed the partition table! In the other payload, fatfs partition overwrites tinboot area on reboot.

Also, using nbtools fixes the partition tables based on size of tinboot's XIP.
ok so this is a new creation? nothing we have on git rite. Upload it so i can put it on git and have autobuild make one of these nbh with the recovery on it.
You have the rhod_payload2 already on git. It's the one I made a few weeks back. Maybe autobuild was just never updated. Try using my script :)

[ACL] 03-27-2011 06:02 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2074699)
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)



You have the rhod_payload2 already on git. It's the one I made a few weeks back. Maybe autobuild was just never updated. Try using my script :)
ahh ok.. i forgot u made that one. I though it was the original original we used. Ok never mind ill try it out.

pts69666 03-27-2011 06:22 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
You know what I find a bit odd? Data works for me in Android; however, when I flash back to WinMo, I have no data. When I try to update data profile, I get an error 1012. I flash back to Android, and I have data again. Is it a sign? =P

natemcnutty 03-27-2011 09:05 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by pts69666 (Post 2074715)
You know what I find a bit odd? Data works for me in Android; however, when I flash back to WinMo, I have no data. When I try to update data profile, I get an error 1012. I flash back to Android, and I have data again. Is it a sign? =P
Yikes, that doesn't sound good. I hope nothing we are doing in Android is affecting Windows Mobile. A good thing to test would be flashing stock and see if that fixes data in WinMo. I don't think we can affect the radio firmware from within Android, but I guess anything is possible.

MassStash 03-27-2011 09:47 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
[acl], double check the auto build script is useing payload2, that was my prob being stuck there... hopefully that easy

arrrghhh 03-27-2011 10:04 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by pts69666 (Post 2074715)
You know what I find a bit odd? Data works for me in Android; however, when I flash back to WinMo, I have no data. When I try to update data profile, I get an error 1012. I flash back to Android, and I have data again. Is it a sign? =P
lol, it is a sign.

I don't have this experience tho. Have you tried different WinMo ROM's, or OEM like nate suggested?

Stock should include radio firmware.

davidchan 03-27-2011 10:49 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
thanks for sharing!!!i like it!!

[ACL] 03-28-2011 12:37 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it

a460162314 03-28-2011 02:03 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
I got some other feedback.
V version of the phone to normal use.
But there he was, the screen no longer wake up after shut down, need to restart to resolve.
S version of the phone,Even the use of CDMA SIM cards.
Same constantly reboot.
While the other is stuck in more: SMD: ch 0 Opening -> Opened.
And someone said to me,They do not have permission to access the phone ROOT.
But when I tested, I have ROOT permissions.
Keep up, man, look forward to your updates.
Good luck

natemcnutty 03-28-2011 02:15 AM
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by [ACL
]nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it
That sounds great ACL. I'll take a look at it and update the how-to thread tomorrow. Got myself a Xoom today, so I've been a little preoccupied :-P

vistazifta 03-28-2011 03:38 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2074893)
That sounds great ACL. I'll take a look at it and update the how-to thread tomorrow. Got myself a Xoom today, so I've been a little preoccupied :-P
enjoy ur new toy man and im sure u already have ubuntu running on it and accessing it via local vnc lol

pts69666 03-28-2011 06:36 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Ill try the stock ROM after work and let you guys know if it fixes data.

Lmiller1708 03-28-2011 07:29 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2074794)
Quote:
Originally Posted by pts69666 (Post 2074715)
You know what I find a bit odd? Data works for me in Android; however, when I flash back to WinMo, I have no data. When I try to update data profile, I get an error 1012. I flash back to Android, and I have data again. Is it a sign? =P
Yikes, that doesn't sound good. I hope nothing we are doing in Android is affecting Windows Mobile. A good thing to test would be flashing stock and see if that fixes data in WinMo. I don't think we can affect the radio firmware from within Android, but I guess anything is possible.
You are correct there should be no harm at all to the radio. I'm about 99.9% sure... :)

Quote:
Originally Posted by pts69666 (Post 2074926)
Ill try the stock ROM after work and let you guys know if it fixes data.
Did you remember to run the provisioning for your carrier once you flashed the new winmo ROM? If you have never had to do that in the past you might have to now. ;) And make sure you have rebooted a couple of times just to be safe.

I have flashed back and forth many time with both of my TP2's with no issues at all.

Lmiller1708 03-28-2011 07:38 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2074863)
nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it
Great Job ACL! As soon as my Darn VM gets up and running again I will give it a try! It like to just freeze up after about 2 - 3 hours of use... Wish I could just run with out!

Anyway how can I add a section to the recovery? I plan on making the install script today right from the system.ext2.

Quote:
Originally Posted by natemcnutty (Post 2074893)
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)
That sounds great ACL. I'll take a look at it and update the how-to thread tomorrow. Got myself a Xoom today, so I've been a little preoccupied :razz:
Ahh new toy! Have fun with it! I'm hoping to get a ThunderBolt soon for work! :)

EDIT: Has anyone tried my system FRX06 yet?

[ACL] 03-28-2011 08:58 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2074930)
Anyway how can I add a section to the recovery? I plan on making the install script today right from the system.ext2.
Just edit the install-seq in the recovery/sbin directory. right now our install seq is similar to the old seq but with some differences you may notice.

But in there you can have it check if there is the system.img and do your dirty business.

pts69666 03-28-2011 11:46 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
I ran the provisioning built into the ROM (it had Sprint provisioning in it) and I ran a provisioning cab file. Both to no avail. Government computers don't like USB devices, so I can't try flashing stock ROM until I get off.

natemcnutty 03-28-2011 12:50 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by pts69666 (Post 2075036)
I ran the provisioning built into the ROM (it had Sprint provisioning in it) and I ran a provisioning cab file. Both to no avail. Government computers don't like USB devices, so I can't try flashing stock ROM until I get off.
Although you may have no way to get it on there, you can actually extract the NBH from the stock ROM's EXE and flash that from the sd card as well.

[ACL] 03-28-2011 03:41 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
finally got word about the autobuild server. Looks like we had a power supply issue.

I'm going to back up some stuff tonight and have an alternate download link. Wistlitl is going to upgrade us to a new server so make sure to thank him if yall see him on IRC.

natemcnutty 03-28-2011 03:54 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2075221)
finally got word about the autobuild server. Looks like we had a power supply issue.

I'm going to back up some stuff tonight and have an alternate download link. Wistlitl is going to upgrade us to a new server so make sure to thank him if yall see him on IRC.
That's a bummer about the power supply. Glad that Wiltilt is able to help us out. If you have a backup of the autobuild stuff, can you shoot me the details? I'd love to see how that all works and maybe set my server up to do something similar :)

pts69666 03-28-2011 04:29 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075079)
Although you may have no way to get it on there, you can actually extract the NBH from the stock ROM's EXE and flash that from the sd card as well.
SD reader is still a USB device. =P If any USB device is plugged in, it forwards it over to the sysadmins... :x

Off work now, but too tired/lazy to flash atm. Will flash after nap and gym. =P

[ACL] 03-28-2011 04:32 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075236)
That's a bummer about the power supply. Glad that Wiltilt is able to help us out. If you have a backup of the autobuild stuff, can you shoot me the details? I'd love to see how that all works and maybe set my server up to do something similar :)
Ill send you over the script i got from Netripper. Its very flexible incase you wanna run your own autobuilds.Its good because it will always use a clean pull from a separate machine thats not affected by dirty code. But i'll shoot you over the email.

natemcnutty 03-28-2011 08:44 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2074863)
nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it
Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.

[ACL] 03-28-2011 11:50 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075424)
Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.
yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade :-)

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.

natemcnutty 03-29-2011 12:55 AM
Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by [ACL
]
Quote:
Originally Posted by natemcnutty (Post 2075424)
Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.
yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade :-)

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.
That sounds awesome. I am still having issues getting FRX06 working properly. I can get it to boot without issues, but I cannot get data working for the life of me. The method of copying directly out of system.ext2 and then using the androidupdate.tgz to fix the rest seems to work great though :-)

arrrghhh 03-29-2011 12:55 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2075491)
yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade :-)

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.
Good news bro! That is very good news indeed... No more need to constantly reflash!

Lmiller1708 03-29-2011 07:20 AM
Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.2; en-us; MSM Build/FRX05) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

Quote:
Originally Posted by [ACL
]
Quote:
Originally Posted by natemcnutty (Post 2075424)
Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.
yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade :-)

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.
That's great news acl!
Can't wait to test it out...

Lmiller1708 03-29-2011 07:24 AM
Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.2; en-us; MSM Build/FRX05) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

Quote:
Originally Posted by natemcnutty
Quote:
Originally Posted by [ACL] (Post 2074863)
nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it
Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.
Thanks nate!
I didn't even get time to work on it yesterday... :-(
Going to redo my VM today, I did a snapshot so I will try that frist...

What problems are you having with FRXO6? Just not able to get it to boot at all? Did you try mine?

[ACL] 03-29-2011 01:16 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
i think its safe to say the recovery is 'stable'.

With that said im thinking of releasing the next kernel updates via update.tgz. This way no wipe is needed until the next major release. But since we can back up and restore with no probs now this isnt going to be a big issue.

Im tacking some bugs so there will be plenty of updates.

natemcnutty 03-29-2011 03:06 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2075710)
i think its safe to say the recovery is 'stable'.

With that said im thinking of releasing the next kernel updates via update.tgz. This way no wipe is needed until the next major release. But since we can back up and restore with no probs now this isnt going to be a big issue.

Im tacking some bugs so there will be plenty of updates.
Yeah, recovery has been perfect for me since your first release. I'm loving it :)

I'll definitely test out your kernel release via update.tgz. Probably good to get that ironed out early.

Also, there are still a handful of issues with the ROM's that I think we need to find some chef help on. Maybe stinebd might have some ideas on some of this too. I believe all of these are just ROM related things that should be fixable by someone who knows what they are doing:

1) We still don't have real root (despite having su and busybox in /system/bin and /system/xbin)
2) Data never works on first boot
3) App2sd doesn't work (may be root related)
4) Some applications refuse to install (but work on Haret)

[ACL] 03-29-2011 03:15 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075789)
Yeah, recovery has been perfect for me since your first release. I'm loving it :)

I'll definitely test out your kernel release via update.tgz. Probably good to get that ironed out early.

Also, there are still a handful of issues with the ROM's that I think we need to find some chef help on. Maybe stinebd might have some ideas on some of this too. I believe all of these are just ROM related things that should be fixable by someone who knows what they are doing:

1) We still don't have real root (despite having su and busybox in /system/bin and /system/xbin)
2) Data never works on first boot
3) App2sd doesn't work (may be root related)
4) Some applications refuse to install (but work on Haret)
1) hmm something isnt right with your setup bro. I swear to you i have the root apk, the busybox 1.9 and titanum backup installed. I did notice one of the apks to install busybox requests to mount /system as rw, but the other one does it for you. So try a few out.

2) data on first is worth a look. But since im restoring from my old backup, im never really firsr booting ..lol

3) that i have not tested. Will do tonight

4) need specifics. Each app writes to logcat as to why they cant install. Some even give you a list of things to fix :-)

Lmiller1708 03-29-2011 03:25 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2075797)
Quote:
Originally Posted by natemcnutty (Post 2075789)
Yeah, recovery has been perfect for me since your first release. I'm loving it :smile:

I'll definitely test out your kernel release via update.tgz. Probably good to get that ironed out early.

Also, there are still a handful of issues with the ROM's that I think we need to find some chef help on. Maybe stinebd might have some ideas on some of this too. I believe all of these are just ROM related things that should be fixable by someone who knows what they are doing:

1) We still don't have real root (despite having su and busybox in /system/bin and /system/xbin)
2) Data never works on first boot
3) App2sd doesn't work (may be root related)
4) Some applications refuse to install (but work on Haret)
1) hmm something isnt right with your setup bro. I swear to you i have the root apk, the busybox 1.9 and titanum backup installed. I did notice one of the apks to install busybox requests to mount /system as rw, but the other one does it for you. So try a few out.

2) data on first is worth a look. But since im restoring from my old backup, im never really firsr booting ..lol

3) that i have not tested. Will do tonight

4) need specifics. Each app writes to logcat as to why they cant install. Some even give you a list of things to fix :-)
1) I'm also using the same setup at ACL. Works just fine :) Superuser.apk, dl from the market. The Vogue also has to use this...

2) Same issue for me... (On Last Install)

3) Untested too..

4) *birds will not install for me... :( Only SD app I have tried.


This should also be added the install-seq.sh:
Code:
# Fix build.prop for NAND
sed -i 's/lib\/froyo/system\/lib/' /system/build.prop
sed -i 's/210/240/' /system/build.prop

# Remove system/etc/ppp folder...
rm -R system/etc/ppp

natemcnutty 03-29-2011 03:34 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2075804)
1) I'm also using the same setup at ACL. Works just fine :) Superuser.apk, dl from the market. The Vogue also has to use this...

2) Same issue for me... (On Last Install)

3) Untested too..

4) *birds will not install for me... :( Only SD app I have tried.


This should also be added the install-seq.sh:
Code:
# Fix build.prop for NAND
sed -i 's/lib\/froyo/system\/lib/' /system/build.prop
sed -i 's/210/240/' /system/build.prop

# Remove system/etc/ppp folder...
rm -R system/etc/ppp
Yeah, so the root is weird. What I mean by a real root is that on first boot, I log into Market, install Titanium Backup, and it tells me I don't have root. I then install Busybox and Titanium is happy, but other programs like ES File Explorer won't let me run as root. Terminal says unknown uid when I type busybox whoami, but it does let me su, then issue commands which works properly.

Haret users don't have to do anything like this, so that's why I'm wondering what we need to do to clean up the ROM. Also, I'm thinking we should toss spare parts into the ROM like Haret used to unless we want to change the value for the End key. Having no Home button is extremely annoying.

As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.

Lmiller1708 03-29-2011 03:42 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075811)
Yeah, so the root is weird. What I mean by a real root is that on first boot, I log into Market, install Titanium Backup, and it tells me I don't have root. I then install Busybox and Titanium is happy, but other programs like ES File Explorer won't let me run as root. Terminal says unknown uid when I type busybox whoami, but it does let me su, then issue commands which works properly.

Haret users don't have to do anything like this, so that's why I'm wondering what we need to do to clean up the ROM. Also, I'm thinking we should toss spare parts into the ROM like Haret used to unless we want to change the value for the End key. Having no Home button is extremely annoying.

As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.

Yeah I was thinking about doing the same thing for the 210 to 240 version...
I will leave it up to you. :)

natemcnutty 03-29-2011 03:59 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2075816)
Yeah I was thinking about doing the same thing for the 210 to 240 version...
I will leave it up to you. :)
Cool, I'll get that code committed when I get home today and have a chance to test it one more time.

Also, anyone care to try this out for root?

rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su

Lmiller1708 03-29-2011 04:02 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075830)
Cool, I'll get that code committed when I get home today and have a chance to test it one more time.

Also, anyone care to try this out for root?

rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
Ok Thanks! :)

It should not matter if the su is in the xbin or system... or even linked... Since the path includes them both.

[ACL] 03-29-2011 04:03 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075811)
As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.
lets wait on this commit. Lmiller and i talked about having a custom script per update like android. So if anything the update-seq script needs to be modded to check for a pre-exec script and a post-exec. This way we can have custom scripts when needed anytime we have an update instead of recompiling all the time.

android does it the say way but with only one script. :-)


All times are GMT -4. The time now is 05:13 PM.
Page 56 of 69 « First 6465455 56 575866 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0