yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] smashman42:
Thanks, one step closer - /sdcard mounts ok & I can see everything & run flash_image recovery ..... but it still acts the same after flashing :(

If only this SPL had fastboot boot so I could fastboot the recovery.img, that's how I rooted the .0004 S=on SPL the phone came with cause it didn't have fastboot flash

C:\Users\Smashman>fastboot boot recovery-RA-sapphire-v1.7.0G.img
downloading 'boot.img'... OKAY [ 1.716s]
booting...

And she hangs, damn HTC locked down SPL.

With the init.d squashed I can't put a file in to flash the recovery on boot, is there another way to make it auto-flash on boot when there is less RAM used? Via ADB shell during boot /sdcard isn't mounted, wonder if I can mount it the way you suggested or alternatively push the file to data & flash during boot via ADB that way...

Nope, pushed to /data ok & it is already mounted but the flash doesn't work, can mount /sdcard early & try flashing from there but it fails too, I guess I just keep trying unless there is another suggestion?
[G1 Android Development] darkguy2008:
Hey, how can you run fix permissions? is it a script or an option somewhere? Thanks!
[G1 Android Development] ezterry:
a script.. most roms you can:

* via adb run 'adb shell fix_permissions'

* at the command line as root (ie after running 'su') run 'fix_permissions'

* if you have rom manager choose 'Fix Permissions'

* Also while sometimes apps2sd gets confused fix permissions is also can be run in recovery.
[G1 Android Development] smashman42:
don't suppose you'd any any suggestions for my corrupt recovery problems ezterry?
[G1 Android Development] cj chitwood:
The init.d should be unsquashable. I saw someone reference that somewhere in the last 3 or 4 pages (for me, that's 15 to 20 for most). Maybe try that and see if you can do it that way, but even then, if it doesn't flash for you manually after mounting /sdcard it won't flash during init.d I don't think....

I'm no expert but I think you're the happy father of a new baby brick. EDIT: Well, maybe not brick. New baby... brick with flashing lights?

You say via ADB shell during boot /sdcard is not mounted. What stops you from mounting it if you're in ADB? Or were you just pointing out that the phone doesn't mount /sdcard until the very end of the boot process?
[G1 Android Development] cj chitwood:
NOW I KNOW WHAT THAT MEANT!!!!

Settings/COS/Lockscreen/Gestures --> Build Gesture

So for whomever was F/C on that -- that's why...

sorry, I'd look for whom, but I have to go rock my baby to sleep
[G1 Android Development] smashman42:
Yeah, in the normal boot process /sdcard isn't mounted until the very end, but even during boot manually mounting it (which works) isn't enough the flash still fails, it either won't run or gives out of memory errors. Even tried swap & killing pretty much everything to get free ram & best I could get was only one out of memory error.

I've got a working install of the 2011/06/04 release it is just unstable & reboots a lot, so not quite bricked but not a happy place either.

If I had another phone I'd give unrooting a go
[G1 Android Development] Maxamillion:
Hey you guys I have the 5.31.11 build, and lately my broswer has been getting a lot of force closes and I have been getting a lot of force closes saying android.acore. has stopped working. Has anyone else experienced this. I haven't updated yet because I really like this build.
[G1 Android Development] BlackF09:
Reverted/modified squashed ini.d

I tried replacing the init.d.sqf with my own created that includes firerat's 25swap activation script*) but was not very successful (permission an owner was correct), it wasn't mounted at all. I'm not sure if my used squasfs version (3) is the cause or if there is another one. But I could add the init.d files afterwards normally. I don't see/have any problems running this ROM (current version 0608) now.

The ROM version of init.d.sqf is of version 4 (regarding 7-Zip). If I find time, I'll try installing the version 4 tools.

If you want to have the same modification try it that way (you need some Linux knowledge, and as always be careful!):

extract the ini.d-files from the rom's init.d.sqf file (it's in COS-DS-06082011-signed_l1.zip\system\etc\init.d\), e.g. with 7-Zip or take the attaced here ;)

copy the extracted and custom init.d files to a directory on your sdcard

flash the rom via recovery, but don't reboot

go to shell and do a "mount -a"

cd to /system/etc/init.d and rename init.d.sqf to e.g. init.d.sqf.bak

copy from sdcard your ini.d-files

correct permissions of the files: chmod 600 (and the owner if necessary)

do other modifications or tweaks (like adding gmail.apk to /system/app, deleting GenieWidget.apk from there or add/delete ringtones;

always correct the permissions with chmod!

)

type reboot to boot the new and modificated ROM

check via console's free or SetCPU's memory infos if swap is activated (it seems that compcache needs to be set off)

I have added the extracted init.d scripts from ROM build version 06/08/2011 plus firerats autoswap (as Zip because the forum doesn't allow files w/o file extension).

Of cause this has to be done every time you flash a new ROM!

*) the script is created when used firerat's script fr-patch141-BETA3.sh to activate a swap file or partition
[G1 Android Development] cj chitwood:
I've not experienced a lot of f/c after periods of use. Usually, if I'm going to get them, it's right off the bat.

Try fix_permissions, clean out cache/dalvik-cache maybe...
[G1 Android Development] chris122380:
After enabling the Androidian theme in theme chooser and reboot I then get a boot loop. I get the boot loop after the SD mount. The only fix was for me to do a restore from before enabling the theme. Why can't I use a theme? If themes don't work lets remove the Theme Chooser to save space.
[G1 Android Development] lunotown:
you can try to use fastboot to reflash your recovery image:

fastboot flash recovery recovery.img

if your spl locked, then you might have to find one of htc's original nbh images to downgrade. Then upgrade your radios, recovery, and all that other stuff again. In this case, the command would be:

fastboot flash nbh htcimage.nbh
[G1 Android Development] ezterry:
if you have access to the rom but not recovery

If you have problems and are using 1.33.0013d go to fastboot and run 'fastboot erase recovery'

then use flash_image or rom manager to flash recovery.

Make sure you don't run it until the rom completes loading.. and kill any extra services to minimize the out or memory errors

If you loose access to both rom and recovery then as lunotown indicated.

(in some odd cases I've heard of flash_image failing as well and the fastboot method is required)
[G1 Android Development] Maxamillion:
i already tried fixing permissions, but ill try clearing cache and dalvik cache from recovery.
[G1 Android Development] obiwanbartek:
I've found that COS-DS 04/06/2011 (DD/MM/YYYY, yes I am European :p ) is suffering a battery drain sometimes. I had similar situation with latest CyanogenMod (6.1) lately. Then battery drain started "to work" after connecting to USB, and "worked" until first reboot. Now, with COS-DS, I think it was started by bluetooth (I was using my headset for a moment, first time with COS). Most battery use under Settings -> About -> Battery shows "Android OS". It dropped form 100% (disconnected from wall) to 75% in one hour. Any clue how to deal with it? Change kernel?
[G1 Android Development] cj chitwood:
Kernels seem the preferred method. 08/06/2011 would have a different kernel than 04/06/2011, and if you don't want to upgrade the whole rom, the kernel is available as of 06/06/2011. See OP.

That said, I've read a lot of people have had issues with the WiFi causing drain if it was enabled, but I haven't read about Bluetooth drains. The WiFi details are a little lost on me in memory, but here's my experience... I'm running 04/06/2011 here (until my battery is charged, then I'm upgrading to 08/06) and I noticed my phone drains fast regardless except if WiFi is on, whether connected or not. I'm not getting the best battery life I ever have, but I am getting quite decent battery life.

I saw a screenshot a while back about a picture being worth 1000 words, and I had a similar screenshot... the battery drained wicked fast until WiFi was turned on, whether it connected or not. I think it was EZTerry who stated it seemed to be a driver or service running when it shouldn't be, poking the WiFi hardware even when it shouldn't, that was causing the drain. I don't know if a fix has been had yet...
[G1 Android Development] smashman42:
Did all that, gutted the rom out with Titanium backup so it was pretty much a stock empty rom, the flash went through without errors but still recovery wouldn't boot, got stuck at the exact same place.

So I tried unrooting & appear to have a brick even though the sappimg went through & flashed ok without any errors (OS bootloops, won't get past splash)

Still have bootloader (1.33.0006 so perfect SPL) so I guess if I can get a MicroSD adapter I could try making a gold card, which is only going to repeat what I've already done isn't it? Otherwise she's a bin job :(
[G1 Android Development] cj chitwood:
I think before I threw it away I'd buy the stuff for a JTAG kit. Got to be less expensive than a whole new phone. Unless you're not worried about that.

I mean worst case you're out a few bucks and some time, and you've learned nothing. Best case, you've got all the parts already and you save the phone.

On another note, I updated my phone around 11:00 last night, no wipe, and went to bed at around midnight thirty. Battery was at 100%, and I pulled it off the charger when I went to bed. Left my phone on the nightstand, asleep (but NOT suspended) with WiFi on (but of course not connected since it was sleeping) and checking 7 hours later I've lost only 9% battery. Again, not the best I've seen, but certainly not bad at all.

Haven't used it much, though, so we'll see about responsiveness et al later on...
[G1 Android Development] obiwanbartek:
I've noticed another weird thing with BT headset. I have a sony erricsson one (HBH-PV705, it has only one button and vol+, vol-). Yesterday everything worked well, when phone was ringing, pushing headset button would answer the phone, pushing it again (when in call) would end the call, and pushing it when phone is "idle" would start voice recognition. But today, everything I can do with this button is to start this damn voice recognition. When someone is calling, the call doesn't get answered, but only shows "Listening..." windows from voice recognition. The same with ending a call. Call is still on, and only recognition windows is showing in. Very weird.
[G1 Android Development] smashman42:
I thought you needed some fancy hardware for JTAG? Got a link with more info?

Edit: Scratch that, should have ran the google search first :p

I'm hoping my provider will let me upgrade phones early on the contract, might get a free Nexus S if I'm lucky, but I'd still like to resurrect this phone if I can
[G1 Android Development] roalex:
"won't get pass splash" means nothing, does adb see the device, can you get the logcat ? is so...its probably something silly going on.
[G1 Android Development] Khizzer:
how do live wallpapers work on this??

i used a previous version of this rom

live wallpapers lagged soo much
[G1 Android Development] smashman42:
Sorry, boot splash comes up but it reboots after about 10sec, no ADB access at all

Fastboot mode sees the phone but can't really do much with this SPL (1.33.0006), everything is "failed (remote: not allowed)"
[G1 Android Development] obiwanbartek:
Now I am sure that BT with handset is causing battery drain (as of COS 04/06/2011). The story is: I left phone over night - battery dropped about 4-5% (as usual), in the morning I started BT, started headset, connected them, made one short (<1 min.) call using headset, hangup, disconnected handset, turned BT off, left phone for 1h 30min - battery dropped about 15% (!).
[G1 Android Development] uvt_novice:
Roalex, could you please also add to the 1st post the link to kernel downloads. Thanks.
[G1 Android Development] uvt_novice:
I've experienced almost the same thing when used bluetooth headset to listen to the music and to talk...battery was fallen too quick.

I think that this is (bluetooth connection) closely similar to that was discussed about kernels and wi-fi (wifi connection) battery drain
[G1 Android Development] roalex:
its needed by that build alone, the others have it already.
[G1 Android Development] cripgballerkundikusu11:
sloow and bat battery life but stable and is a good rom
[G1 Android Development] cripgballerkundikusu11:
i had experienced the same problem
[G1 Android Development] morTimar:
2011/06/11 - home key without function

Hi,

anybody with the same problem?

Pressing home key does not bring me to home screen.

Bye morT
[G1 Android Development] obiwanbartek:
The 06062011 kernel for COS 06042011 is battery drain-free for me. Whooaa! But I still can't hangup with my BT handsfree button. :(

P.S. How to check which kernel do I have at the moment (original for COS 0604 or alternate from 0606)?
[G1 Android Development] id242:
Menu > Settings > About phone... read "Kernel version".

EDIT: Never mind this post... I just noticed that while the description states the major kernel version (2.6.36.4), it doesn't mention the minor kernel version/date. I guess that just means you need to pay better attention/remember what you are flashing :) or roalex should think about inserting his revisions date in to the kernel description.
[G1 Android Development] obiwanbartek:
Yeah, good point.
[G1 Android Development] jj71787:
I dont know if something is wrong with my phone but I have been trying this rom for awhile and my phone is slow its unusable. when I open messages from someone it will close it and go to all the messages on its own. When I try to go to the web it will go back to the home screen. Its slow at opening apps especially the dialer. I keep getting home screen force closes.
[G1 Android Development] Maxamillion:
What are your settings?what is your setup? Do you have swap, swap tends to make phones lag.

Did u wipe before flashing this rom?
[G1 Android Development] smashman42:
Successfully made a goldcard even though the phone wasn't booting, flashed a different sappimg that has a fastboot boot enabled SPL (1.33.0009 with 3.22.x radio) - yay, I thought...

Fastbooting any recovery (ra 1.7.0, 1.6.2 & CW2.5.0.7 - even RA1.2.0!) acts the same as it did previously when flashed to the recovery partition - comes up to the line at the bottom that lists the recovery build number & stalls, Still no ADB access in the bootlooping rom - that's gotta be hardware failure, right?

I've got a 3rd sappimg variant to try (Vodafone 1.33.0007 CRC24 one) then I guess I'm **** out of luck. :( Edit: won't let me downgrade to lower SPL, that means the goldcard isn't, right?
[G1 Android Development] cj chitwood:
Just a guess... open terminal, and type "uname -a". What does it show?

I mean, it is basically linux after all.

[Edit!]

Mine says:

$ uname -a
Linux localhost 2.6.36.4-cos #1 PREEMPT Sun Jun 5 15:54:37 EEST 2011 armv6l GNU/Linux
$

[/edit!]
[G1 Android Development] cj chitwood:
I assume that when you fastboot boot a recovery, it does not overwrite the existing recovery. So, I assume it either loads it over the USB directly, or, it copies it to the same part of the partition as when it's going to overwrite before unpacking and flashing it, it simply doesn't flash after unpacking. Either way, it tells me that the existing on-the-chip recovery obviously isn't the problem. But even trying multiple recoveries... And for EVERY one, it does the same, showing the mod version at the bottom and that's it? That seems very strange, because if it were a hardware problem like a corrupt block on the NAND, I would expect not even that to work (or at least not as predictably).

Have you tried, from recovery, doing any of the shortcut keys, ... oh, wait, you have a sapphire.... That's why I'll always have a physical keyboard.

Wasn't there a trick to pulling up a soft keyboard and a terminal emulator in the recovery without using menu options to do it? Like, hitting menu+VOLUP or something like that? I seem to recall that from like 2 years ago when Haykuro was all the rage. I'd see if maybe by some miracle you actually do still have the functionality without the menus being displayed -- maybe the problem is simply in output, not actual operation. Follow? Seems very odd, though, for so many recoveries to behave the same way. Then again, I don't know how recoveries boot. If, for instance, it always displays the recovery name before actually booting it, then yeah, that could be expected behaviour with a bad NAND block.

There's got to be a way to repartition that chip to get bad blocks redirected. Wonder if it requires JTAG to do it, though.

JTAG completely out of the question?
[G1 Android Development] jj71787:
i wiped everything.

i never put swap on unless it is by default
[G1 Android Development] Maxamillion:
Have u tried running a fix permissions?
[G1 Android Development] jj71787:
no I saw it mentioned a few times how do i run it
[G1 Android Development] darkguy2008:
0123456789
[G1 Android Development] Maxamillion:
U can download the rom manager app from the market and chose the fix permissions option, or you can go to terminal emulator and type "su" and then type"fix_permissions"
[G1 Android Development] smashman42:
Before it failed when booting to recovery after splash 1 for a second the screen I'm stuck on would appear, then the menu would pop up which is what made me think bad nand block, but fastbooting it doing it too? I thought it runs it in RAM as a virtual filesystem but if there is a bad block where it unpacks it initially I guess that might make sense.

With overseas post JTAG isn't really worth it, the places I could find selling the gear want nearly as much again just to post it down under. I guess I could send the phone away to someone with the gear?

Also this Prepaid Ideos u8150 makes JTAG seem even more unaffordable, there are CM6 & CM7 ports for it & other than the lower res screen it is similar specs to a 32B Magic anyway (not sure how much of the 256mb RAM is system accessible). Or if I'm lucky my provider might let me upgrade contract early & get a Nexus S, they have them available free on my plan ATM.

Meh, shouldn't have unrooted & should have just dealt with the unstable system, half a phone is better than no phone. :D

Thanks for the help everyone.
[G1 Android Development] gzzf:
Hi roalex, I should say it's a wonderful ROM for my T-mobile G2, however I have a little proble about the lockscreen gesture. Could you please find a way to sovle it or give a remedy. Thanks for you great work!
[G1 Android Development] roalex:
its a known bug, as stated on the first post.
[G1 Android Development] Maxamillion:
My phone just rebooted itself while I was on the browser for about 5 minutes. This is the first time this has happened to me, what should I do? I already tried wiping dalvik cache and run fix permisiions.
[G1 Android Development] Sheist!:
Menu>Search broken and superuser: error "cannot be installed in default location"

"Application cannot be installed in the default install location", Market update attempt of Superuser.

Noticed it in 6/11/2011, did NAND restores (after Ohsaka superwipe and all Amon Ra wipe options each time) back to 0608 and then again to 0604 but problem remains. fix_permissions does not help, nor does (surprisingly) trying each of the different install locations (i.e. internal, let system decide, SD, etc) and rebooting. Even Internal, gives same error in Market, which shows Superuser 2.6.3.2 as update, yet I see installed version is 2.3.7, with Su binary v2.3.1-ef; checking for updates there does nothing. Try to install 2.3.7 from saved .apk just to see what it does: "application not installed".

Same with SU Update Fixer, which worked in the past on a different superuser install issue. Same error installing it from market, and "application not installed" when tried to install a saved copy of the .apk.

Random new apps and other saved apps update and install fine.

Something is jacked with embedded permissions.

Also, Menu>Search is broken. It does nothing on all 3 latest ROM releases 6/4, 6/8 and 6/11.

Using Launcher Pro, but that isn't the reason. Menu>Search worked previously, but I don't really use it much so not sure exactly where it stopped.
[G1 Android Development] roalex:
Well, how about install google search o.O
[G1 Android Development] Sheist!:
No, it does not. The Google Search does install, but Menu>Search doesn't work. Running fix_permissions again, but I am not hopeful. Have already done that several times today.

The Market "Update" prompt is annoying. Googling the error suggests I can just change the default install location and sidestep the issue, but no dice.

In the past, we could mount /system rw in terminal and uninstall anything manually, such as the old Terminal, but with /system not mountable as read-write anymore (right?), I can't see what to do as a user to get around this.
[G1 Android Development] roalex:
Sure it is
[G1 Android Development] ringochan:
Wow, you're lucky. You only had one 'reboot' during the entire time you had your phone? It happens to me 1 - 2 times a week. And I'm sure it happens to many Android phones whether it's rooted (w/custom roms) or not.

Afaik, those 'reboots' can be caused by several different reasons, but I've seen out-of-memory conditions and cpu overclocking are very common. If your problem is not repeating, I don't think you need to worry.

On the other hand if it happens repeatedly when the phone is running a specific task, it can be because of corrupt cache or something. Did you clear the Browser's cache in the settings?

Oh, and was it a 'soft (just Android restarts)' or 'hard' reboot?
[G1 Android Development] Sheist!:
Sheet-durned. The old mount/rm/pm uninstall did work. The Gods be praised!

:)
[G1 Android Development] ringochan:
I see what you mean. I didn't know the issue until you mentioned it because I don't use 'menu/search' at all. But I remembered seeing :

PackageManager( 138): Not granting permission android.permission.GLOBAL_SEARCH to package com.google.android.googlequicksearchbox (protectionLevel=3 flags=0x10be44)

Apparently, google search isn't getting the necessary permission.

So when you hit 'menu/search', this would happen:

W/SearchManager( 230): No global search activity found.

If you want the 'menu/search' to work, the simplest solution might be to install the original quicksearchbox apk. I wouldn't do it myself, though. That's a waste of space.
[G1 Android Development] BlackF09:
CM bug fixes

I wonder what "CM bugs" are? Bugs from CyanogenMod?
[G1 Android Development] roalex:
Indeed im using the CM framework + stuff. Who is curios can just check the github, all changes are there.

@ringochan

yup, thats it, but i removed the damn apk simply taking space when is a version which is updated on the market, i will sort it out in the launcher though, not a big deal imo.
[G1 Android Development] chris122380:
This only started happening to me on builds after 6/4/11. I am running the newest build and I still get reboots when using the browser or using the back button on a frozen app. (I did post on this last week).
[G1 Android Development] BlackF09:
I almost never get spontaneous reboots, just to give a contrast...
[G1 Android Development] Maxamillion:
i am running the 5/31/11 build, and it was a soft reboot.

i am also constantly getting an android.core force closes and whenever i hit the home button, it does not bring me to home but goes back to whatever i was doing like another app.

i have all the default settings, and i have cpu set to 3sumthin min and 576 max at ondemand.
[G1 Android Development] roalex:
wipe then flash it fresh
[G1 Android Development] Maxamillion:
ok will try.