PPCGeeks
Page 225 of 274 « First 125175215223224 225 226227235 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-29-2011 04:13 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2075832)
Ok Thanks! :)

It should not matter if the su is in the xbin or system... or even linked... Since the path includes them both.
Ahh, I was thinking /system/xbin was before /system/bin in the PATH, and the su in /system/xbin isn't the right one. Guess it really doesn't matter, but I noticed that was a common theme in most root programs and thought it might fix some of the issues. Guess not :P

I guess all we really need to do is copy su and busybox from /bin to /system/bin during the first time script.

I agree with ACL that we should move anything ROM related out of the install-seq.sh and move it into the scripts that are run on the ROM's first launch. Any ideas or commits you have for that, let me know ;)

Lmiller1708 03-29-2011 06:31 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2075850)
Ahh, I was thinking /system/xbin was before /system/bin in the PATH, and the su in /system/xbin isn't the right one. Guess it really doesn't matter, but I noticed that was a common theme in most root programs and thought it might fix some of the issues. Guess not :P

I guess all we really need to do is copy su and busybox from /bin to /system/bin during the first time script.

I agree with ACL that we should move anything ROM related out of the install-seq.sh and move it into the scripts that are run on the ROM's first launch. Any ideas or commits you have for that, let me know ;)
Just used the system.ext2 method with FRX06 and it worked great!
Booted up with no issues except data... Here is my log: 03-29 22:19:37.280: INFO/DEBUG(173): debuggerd: Mar 1 2011 18:59:25 03-29 22:1 - Pastebin.com

For the install-seq.sh:
Code:
sed -i 's/ro.sf.lcd_density = 210/ro.sf.lcd_density = 240/' /system/build.prop
EDIT: No data on second boot either... My modules are not loaded...
Still looking at it...

But I do not like the new keylayout! :) How can I get back to the other? Thanks!!!


EDIT2:
I get a invalid arg with this command: mount -t squashfs -o ro,relatime /dev/block/loop3 /system/lib/modules

natemcnutty 03-29-2011 07:17 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2075972)
Just used the system.ext2 method with FRX06 and it worked great!
Booted up with no issues except data... Here is my log: 03-29 22:19:37.280: INFO/DEBUG(173): debuggerd: Mar 1 2011 18:59:25 03-29 22:1 - Pastebin.com

For the install-seq.sh:
Code:
sed -i 's/ro.sf.lcd_density = 210/ro.sf.lcd_density = 240/' /system/build.prop
EDIT: No data on second boot either... My modules are not loaded...
Still looking at it...

But I do not like the new keylayout! :) How can I get back to the other? Thanks!!!


EDIT2:
I get a invalid arg with this command: mount -t squashfs -o ro,relatime /dev/block/loop3 /system/lib/modules
For the first part, I see this in your log, and later on it says the radio is disabled. I don't know enough to explain why, but that's what sticks out to me.

Code:
  1. 03-29 22:23:37.770: INFO//system/bin/tc(172): Cannot find device "rmnet0"

  2. 03-29 22:23:37.770: INFO/logwrapper(172): /system/bin/tc terminated by exit(1)

  3. 03-29 22:23:37.780: INFO/ActivityManager(219): Force stopping package com.android.provision uid=10040

  4. 03-29 22:23:37.800: INFO/Process(219): Sending signal. PID: 419 SIG: 9

  5. 03-29 22:23:37.890:  INFO/ActivityManager(219): Starting activity: Intent {  act=android.intent.action.MAIN cat=[android.intent.category.HOME]  flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher }

  6. 03-29 22:23:37.910: INFO//system/bin/tc(172): Cannot find device "rmnet0"

For keylayout, you can try modifying the rhod400 navipad file and flip the power/home buttons. If that doesn't work, you may have to make the adjustment in the kernel's gpiokeys and then comment out the navipad part.

Finally, the squashfs issue is because you probbaly used squashfs-tools from apt-get which installs version 4. You have to go to their site, grab 3.4, unzip, then go to the squashfs-tools folder, do MAKE, then sudo MAKE INSTALL. Get the 3.4 version here: Official Squashfs LZMA

Lmiller1708 03-29-2011 08:08 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by natemcnutty (Post 2076028)
For the first part, I see this in your log, and later on it says the radio is disabled. I don't know enough to explain why, but that's what sticks out to me.

Code:
  1. 03-29 22:23:37.770: INFO//system/bin/tc(172): Cannot find device "rmnet0"

  2. 03-29 22:23:37.770: INFO/logwrapper(172): /system/bin/tc terminated by exit(1)

  3. 03-29 22:23:37.780: INFO/ActivityManager(219): Force stopping package com.android.provision uid=10040

  4. 03-29 22:23:37.800: INFO/Process(219): Sending signal. PID: 419 SIG: 9

  5. 03-29 22:23:37.890:  INFO/ActivityManager(219): Starting activity: Intent {  act=android.intent.action.MAIN cat=[android.intent.category.HOME]  flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher }

  6. 03-29 22:23:37.910: INFO//system/bin/tc(172): Cannot find device "rmnet0"

For keylayout, you can try modifying the rhod400 navipad file and flip the power/home buttons. If that doesn't work, you may have to make the adjustment in the kernel's gpiokeys and then comment out the navipad part.

Finally, the squashfs issue is because you probbaly used squashfs-tools from apt-get which installs version 4. You have to go to their site, grab 3.4, unzip, then go to the squashfs-tools folder, do MAKE, then sudo MAKE INSTALL. Get the 3.4 version here: Official Squashfs LZMA
Ahh... Could not get the 3.4 version installed? When I do a make I get can't find the zlib.h file...

Also I grabbed the squash file from the autobuild and have it mounted...
But when I do a depmod I get: depmod: chdir:2.6.27.46-01268-ga175a7c: No such file or directory

Any Idea?

pts69666 03-29-2011 08:55 PM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Sorry for the late response; however reflashing the radio fixed my data issues. I don't know if the radio was corrupted or if it was just bad luck on my part. Just sharing experiences!

natemcnutty 03-29-2011 09:26 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 Lmiller1708
Quote:
Originally Posted by natemcnutty (Post 2076028)
For the first part, I see this in your log, and later on it says the radio is disabled. I don't know enough to explain why, but that's what sticks out to me.

Code:
  1. 03-29 22:23:37.770: INFO//system/bin/tc(172): Cannot find device "rmnet0"

  2. 03-29 22:23:37.770: INFO/logwrapper(172): /system/bin/tc terminated by exit(1)

  3. 03-29 22:23:37.780: INFO/ActivityManager(219): Force stopping package com.android.provision uid=10040

  4. 03-29 22:23:37.800: INFO/Process(219): Sending signal. PID: 419 SIG: 9

  5. 03-29 22:23:37.890:  INFO/ActivityManager(219): Starting activity: Intent {  act=android.intent.action.MAIN cat=[android.intent.category.HOME]  flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher }

  6. 03-29 22:23:37.910: INFO//system/bin/tc(172): Cannot find device "rmnet0"

For keylayout, you can try modifying the rhod400 navipad file and flip the power/home buttons. If that doesn't work, you may have to make the adjustment in the kernel's gpiokeys and then comment out the navipad part.

Finally, the squashfs issue is because you probbaly used squashfs-tools from apt-get which installs version 4. You have to go to their site, grab 3.4, unzip, then go to the squashfs-tools folder, do MAKE, then sudo MAKE INSTALL. Get the 3.4 version here: Official Squashfs LZMA
Ahh... Could not get the 3.4 version installed? When I do a make I get can't find the zlib.h file...

Also I grabbed the squash file from the autobuild and have it mounted...
But when I do a depmod I get: depmod: chdir:2.6.27.46-01268-ga175a7c: No such file or directory

Any Idea?
What I did was uninstalled the squashfs-tools that I had installed originally, then downloaded the 3.4 tar.gz. I extracted that right in my Downloads folder, then in bash, I browsed into the squashfs-tools folder and did make, then sudo make install. The sudo is really important there.

[ACL] 03-30-2011 06:23 AM
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.
I tried ES explorer for root but its asking for a specific rom (cyano or some other crap). lol

The request for 'root' is a real hack in android. It doesnt work like you think. Most devs try to write to a section they arent allowed to to cause the superuser apk request to pop up and allow it. Thats it..lol. They dont have the power to go to the shell and execute, its all done internally. they dont select the user to run as. Haret runs wide open. They dont have ro set for any partitions. If you want to run the same way, just mount rw for everything in your initrd. Also reorder your path so where ever you have busybox installed is first. :-)

installed angrybirds with no issues.. so i'll leave it up to you gents to figure it out. If i cant replicate, i cant fix :-(. I'll try a fresh install instead of my restored data to test further. Also for spare parts and all that stuff, make an update.tgz and lets put it up. Simple enough to do so. I dont want to included it in the rom itself since.

I was thinking more about this direct conversion from the img and realized that the fixperms script will never run since its not there. Not sure if this is gonna work out well in the long run. God knows what they will change forcing us to update the script.. At this stage its easy enough to update the recovery we do have a work around.

Lmiller1708 03-30-2011 07:22 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2076290)
I tried ES explorer for root but its asking for a specific rom (cyano or some other crap). lol

The request for 'root' is a real hack in android. It doesnt work like you think. Most devs try to write to a section they arent allowed to to cause the superuser apk request to pop up and allow it. Thats it..lol. They dont have the power to go to the shell and execute, its all done internally. they dont select the user to run as. Haret runs wide open. They dont have ro set for any partitions. If you want to run the same way, just mount rw for everything in your initrd. Also reorder your path so where ever you have busybox installed is first. :-)

installed angrybirds with no issues.. so i'll leave it up to you gents to figure it out. If i cant replicate, i cant fix :-(. I'll try a fresh install instead of my restored data to test further. Also for spare parts and all that stuff, make an update.tgz and lets put it up. Simple enough to do so. I dont want to included it in the rom itself since.

I was thinking more about this direct conversion from the img and realized that the fixperms script will never run since its not there. Not sure if this is gonna work out well in the long run. God knows what they will change forcing us to update the script.. At this stage its easy enough to update the recovery we do have a work around.
Could not agree more about the keys and no home button! Never made sense to my why they changed it... The less haret stuff the better.

Humm... Not sure why angerybirds would install for you...
I have installed the most recent autobuild with no success in getting the modules to load.

I was able to get the 3.4 version of squashfs working. What I had to do was install I the zlib (apt-get install zlib1g)

I also notice that the SDCard does not mount. I have to pull it out and then reinsert it for it to mount... After that it does not even show up in the settings/SDcard.

[ACL] 03-30-2011 09:03 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by Lmiller1708 (Post 2076304)
Could not agree more about the keys and no home button! Never made sense to my why they changed it... The less haret stuff the better.

Humm... Not sure why angerybirds would install for you...
I have installed the most recent autobuild with no success in getting the modules to load.

I was able to get the 3.4 version of squashfs working. What I had to do was install I the zlib (apt-get install zlib1g)

I also notice that the SDCard does not mount. I have to pull it out and then reinsert it for it to mount... After that it does not even show up in the settings/SDcard.
fear not my good man i'm looking into the autobuild. I think i made a last minute change to move to loop0 from loop3.. hope it wasnt that.

yeah sd got effed up somewhere in there. In odd news however my phone charged lol. i completely drained it last week and i guess i didnt drain it enough, but after leaving it on the charger got to 50%.. enough to boot safely and continue charging.

Lmiller1708 03-30-2011 09:31 AM
Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 
Quote:
Originally Posted by [ACL] (Post 2076323)
fear not my good man i'm looking into the autobuild. I think i made a last minute change to move to loop0 from loop3.. hope it wasnt that.

yeah sd got effed up somewhere in there. In odd news however my phone charged lol. i completely drained it last week and i guess i didnt drain it enough, but after leaving it on the charger got to 50%.. enough to boot safely and continue charging.
Good your charger is working! I will try it out the next time my dies... ;)

Couple of things...
First with the recovery...
If the install fails you do not get notified on the screen... You can only see it in the log. :(

My Install-seq.sh script is working like it should... But I'm still having troubles with the modules They seem to be installing correctly but gives me this in the bootlog and when I do a depmod in the command: depmod: chdir(2.6.27.46-01268-ga175a7c): No such file or directory

I also have apps in my androidupdate.tgz that are not getting installed, everything.

Last but not least the system is getting mounted at rw on boot... :)

Any Ideas?


All times are GMT -4. The time now is 05:57 PM.
Page 225 of 274 « First 125175215223224 225 226227235 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