NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[[ACL]]

Originally Posted by Lmiller1708

So you guys still can't write to the cache partition?
If so try changing this line on the MAKEDEV's

mknod -m 0666 /dev/mtd/mtd4 c 90 6
to
mknod -m 0666 /dev/mtd/mtd4 c 90 8

I stated this before but never looked at the push, but I was also uncertain about it... Sorry about that.

But maybe the cache getting corrupt is something different... Kinda like the losing of some widgets on the Android home screen?

As for not being able to write to the recovery partition are you still using the same starting place as before. 0x4000000?

I won't be able to test for a while today for I forgot my phone at home.

I say test it out. move the dalvik cache to the cache partition and beat it up.. . im using the default mtdparts on git. But i cant format the recovery partition it since it keeps saying its protected. So we may need to shift stuff around a bit.

Originally Posted by Lmiller1708

Nate if you keep getting your Android install stuck in a bootloop it means you are most likely having some permission issues.
Specifically this file: /system/etc/dbus.conf
Here is what the Vogue changes them too...
chown 1002:1002 /system/etc/dbus.conf
chmod 0444 /system/etc/dbus.conf


@ACL,
How are you creating your andriodinstall.tgz?
I'm thinking we are having issues with permissions coming right from the tgz.

Here is mine... Probably not right but it works once I run the fixperm script

echo "Making androidupdate.tar"
cd androidupdate
chown -R 0:0 *
tar -cvzf ../androidupdate.tar *
chown -R lance:lance *
cd ..
echo "Moving androidupdate.tar"
cp androidupdate.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Making androidinstall.tar"
cd androidinstall
chown -R 0:0 *
tar -cvzf ../androidinstall.tar *
chown -R lance:lance *
cd ..
echo "Moving androidinstall.tar"
cp androidinstall.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

cp install-seq.sh ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Completed..."

Hmm bootloop you say ? we need logs bro. Permissions issues are easy to spot since android bitches about it. So yes you could be right, the android may have bad permissions on the tgz which we need to fix. I havent had a boot loop in ages tho so that my be something else.

[steveholtam]

Originally Posted by [ACL]

damn

fopen /etc/ppp/pap-secrets failed = 2

Means the files are not found. Have you figured out how to adb yet ? this might be a 1 line fix .. adb into the device and do the following

ls /system/etc

ls /data/ppp

Print out that you see. If /data/ppp has files, if it does then check if there is a ppp link inside /system/etc. If no link is found then remount system as rw using the command below.

mount -o rw,remount -t yaffs2 /system

Once thats done you can make the llink manually

ln -s /data/ppp /system/etc/ppp

I'll get to this when I get home today.

Oh, one quick question. Is it ok to flash and install the update file in one step? Or should I flash, boot, and then run the update on the second boot? Just making sure either way would work.

[[ACL]]

Originally Posted by steveholtam

I'll get to this when I get home today.

Oh, one quick question. Is it ok to flash and install the update file in one step? Or should I flash, boot, and then run the update on the second boot? Just making sure either way would work.

Ahh .. sorry but yeah, this is all done in one shot. I should have mentioned that before.

[steveholtam]

Awesome, that is what I was thinking, and doing. But just wanted to make sure. I've even ran the update again afterwards to be doubly sure I was getting the updates right.

Also, I've also noticed the panel is still very slow to wake. Could we move to a newer Kernel? And maybe FRX05 while were at it? Yeah, yeah, I'm getting excited... NAND is so awesome. The masses have no idea how cool it is booting Android without an SD card needed!

[[ACL]]

Originally Posted by steveholtam

Awesome, that is what I was thinking, and doing. But just wanted to make sure. I've even ran the update again afterwards to be doubly sure I was getting the updates right.

Also, I've also noticed the panel is still very slow to wake. Could we move to a newer Kernel? And maybe FRX05 while were at it? Yeah, yeah, I'm getting excited... NAND is so awesome. The masses have no idea how cool it is booting Android without an SD card needed!

hmm. I notice that it gets slow when the CPU is being abused. So keep an eye on the cpu usage. This is why i tell everyone not to reset with the button on the side. That forces android to do all this checking on the backend consuming resources. Once its idle, you shouldnt seen any panel slowness. Oddly enough haret seems to be more resilient in this area. Maybe because they are using ext2.

Yeah we are due to make the new frx05. After i post the cyanogen i suppose we can start there. Or if you want to venture into it, by all means go on.

[[ACL]]

Originally Posted by natemcnutty

I doubt we have the same problem as the HD2 because they can't even format that section, but I guess we could test it pretty easily by taking some space away from the data partition and see if the issue goes away. Could it be running out of space on the cache? What if we upped it to 64 MB instead?

nahh the cachent isnt running out of space. That was the first thing i checked, but then i noticed errors on dmesg.

Since cache partition begins at 1E000000, the errors start showing up at 1ff31000 which is really close to the end. We will need to try a few things to see whats up.

A good test to see is if you or lmiller can move your dalvik cache over to this partition. And recreate my issue. Simple link should do the job. Right away android gets angry since a corrupt dalvik cache is trouble for any app in the bad area.

I'll try to reduce the mtd parts and see if the problem keeps happening. I'll reduce the mtd from to end at 1FE00000 which is about 510mb (skipping the last 2mb).

Now a separate issue is the recovery. which is marked as protected. we can read it but writing to it does not work. So i get the feeling this needs to be extended as well.

[[ACL]]

Originally Posted by steveholtam

Awesome, that is what I was thinking, and doing. But just wanted to make sure. I've even ran the update again afterwards to be doubly sure I was getting the updates right.

Also, I've also noticed the panel is still very slow to wake. Could we move to a newer Kernel? And maybe FRX05 while were at it? Yeah, yeah, I'm getting excited... NAND is so awesome. The masses have no idea how cool it is booting Android without an SD card needed!

i took lmillers advice and redid the permissions on the androidinstall.tgz. So download it again and give it a try

[Lmiller1708]

Originally Posted by [ACL]

i took lmillers advice and redid the permissions on the androidinstall.tgz. So download it again and give it a try

I'm able to get the 3G Icon now and was able to ping 8.8.8.8 with reply's

But still no dns...

Noticed when we do a netstat we have a couple of files missing... Maybe that has something do do with the dns??? Not sure just shooting in the wind.

[[ACL]]

Originally Posted by Lmiller1708

I'm able to get the 3G Icon now and was able to ping 8.8.8.8 with reply's

But still no dns...

Noticed when we do a netstat we have a couple of files missing... Maybe that has something do do with the dns??? Not sure just shooting in the wind.

I had that issue too. It was because the /system/bin/pppd isnt the same as the one in /bin. We need to move the one from rootfs on xdandroid into /system/bin/. Hmm i completely forgot if the one i just uploaded had that.. sheesh..

the correct pppd loads the scripts on /etc/pppd. The wrong one does not. I already told stine bout it so he will fix it

also i had luck with this mtd parts

mtdparts=msm_nand:0x20000000@0x0(nand),0x600000@0x6000000(recovery),0x0A000000@0x4800000(system),0xF800000@0xE800000(userdata),0x1E00000@0x1E000000(cache)

No more corruption and we can format the recovery with no issues.

[steveholtam]

My data reads:

C:\Program Files\Android\android-sdk\platform-tools>adb ls /system/etc
000041ed 00000800 12cea692 .
000041ed 00000800 12cea693 ..
000081a4 0000000e 4d4e6a66 group
000081a4 00000019 4d4e6a66 hosts
000081a4 0000003b 4d4e6a66 shadow
000081a4 00000019 4d4e6a66 passwd
000081a4 00000094 4d4e6a66 default.prop
000081a4 000001f1 4d4e6a66 profile
000081a4 00000017 4d4e6a66 shells
000081a4 000001d9 4d3a47e3 pvplayer.cfg
000081a4 00000511 4d3a47e3 vold.fstab
000081a4 0000013d 4d3a47e3 vold.conf
000081a4 00011669 4d3a47e3 NOTICE.html.gz
000041ed 00000800 12cea64e bluetooth
000081a4 000017b0 4d3a47e3 media_profiles.xml
000081a4 0000076a 4d3a47e3 AudioFilter.csv
000041ed 00000800 12cea64e permissions
000041ed 00000800 12cea691 wifi
00008168 000004b0 4d3a47e3 init.goldfish.sh
000081a4 000000e8 4d3a47e3 gps.conf
000041ed 00000800 12cea692 firmware
000041ed 00000800 12cea64e security
000081a4 00002a40 4d3a47e3 event-log-tags
00008120 000003a7 4d3a47e3 dbus.conf
000081a4 00001464 4d3a47e3 AudioPreProcess.csv
000041ed 00000800 12cea693 keymaps
000081a4 00002696 4d4e6a66 apns-conf.xml
000041ed 00000800 12cea691 dhcpcd
000081a4 00000055 4d3a47e3 01_qcomm_omx.cfg
00008124 0000adfe 4d3a47e3 AudioPara4.csv
C:\Program Files\Android\android-sdk\platform-tools>


C:\Program Files\Android\android-sdk\platform-tools>adb ls /data/ppp
000041ed 00000800 12cea691 .
000041f9 00000800 4d758616 ..
000081ed 00001534 4d73f10b ip-up-vpn
000081a4 00000000 4d73f12e pap-secrets
000081a4 00000000 4d73f0dd chap-secrets
000081a4 00000065 4d73f119 options.smd
000081ed 000001ce 4d73f0f5 ip-down
000081a4 0000005d 4d73f121 options.smd1
000081ed 0000050f 4d73f0ff ip-up
C:\Program Files\Android\android-sdk\platform-tools>

Since I don't see a ppp link inside /etc I did the manual copy, and now have a link in the /etc folder as shown:

C:\Program Files\Android\android-sdk\platform-tools>adb ls /system/etc
000041ed 00000800 4d758a17 .
000041ed 00000800 12cea693 ..
0000a1ff 00000009 4d758a17 ppp
000081a4 0000000e 4d4e6a66 group
000081a4 00000019 4d4e6a66 hosts
000081a4 0000003b 4d4e6a66 shadow
000081a4 00000019 4d4e6a66 passwd
000081a4 00000094 4d4e6a66 default.prop
000081a4 000001f1 4d4e6a66 profile
000081a4 00000017 4d4e6a66 shells
000081a4 000001d9 4d3a47e3 pvplayer.cfg
000081a4 00000511 4d3a47e3 vold.fstab
000081a4 0000013d 4d3a47e3 vold.conf
000081a4 00011669 4d3a47e3 NOTICE.html.gz
000041ed 00000800 12cea64e bluetooth
000081a4 000017b0 4d3a47e3 media_profiles.xml
000081a4 0000076a 4d3a47e3 AudioFilter.csv
000041ed 00000800 12cea64e permissions
000041ed 00000800 12cea691 wifi
00008168 000004b0 4d3a47e3 init.goldfish.sh
000081a4 000000e8 4d3a47e3 gps.conf
000041ed 00000800 12cea692 firmware
000041ed 00000800 12cea64e security
000081a4 00002a40 4d3a47e3 event-log-tags
00008120 000003a7 4d3a47e3 dbus.conf
000081a4 00001464 4d3a47e3 AudioPreProcess.csv
000041ed 00000800 12cea693 keymaps
000081a4 00002696 4d4e6a66 apns-conf.xml
000041ed 00000800 12cea691 dhcpcd
000081a4 00000055 4d3a47e3 01_qcomm_omx.cfg
00008124 0000adfe 4d3a47e3 AudioPara4.csv
C:\Program Files\Android\android-sdk\platform-tools>

After all that, I still have no data. I tried the Android APN, and the Sprint APN. Attached is the new logcat -b radio

I do see ppp trying to start now...

Thanks!