Database Develop

G1 Hangs on the First Boot Screen

arrgh i dunno whats wrong with my G1 it doesnt boot anymore for some reason
im running on the RC9 SDCard hack version
ive done a wipe and re installation still no success
any help people thank you!

Same problem... waiting for solution.

Did you 2 happen to add something new prior too the 2 points of reboots??
You have to realize, example, if i reboot......install a theme, install the theme, and go on my merry way with my phone. I happen too be one that doesnt reboot for a week. When i do reboot the phone, guess what, it'll lock up on me, if that theme, or whatever, is not meant for my rom.
So try to back track your steps too figure out, what you modded between the two points of rebooting.

My G1 Also hangs.
Hello XDA, long time reader here.
I was wondering if I could get some heads on this one please. My G1 hangs with any non-t-mobile ROM. Here is what I captured from adb logcat... google didn't turn any promising results. Logcat just repeats the following over, and over.
E/AndroidRuntime( 111): Unable to register all android natives
D/AndroidRuntime( 112):
D/AndroidRuntime( 112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 112): CheckJNI is OFF
D/AndroidRuntime( 112): --- registering native functions ---
W/dalvikvm( 112): ERROR: Unable to find decl for native Landroid/content/res/As
setManager;.getCookieName (I)Ljava/lang/String;
E/JNIHelp ( 112): RegisterNatives failed for 'android/content/res/AssetManager'

pgv100 said:
Hello XDA, long time reader here.
I was wondering if I could get some heads on this one please. My G1 hangs with any non-t-mobile ROM. Here is what I captured from adb logcat... google didn't turn any promising results. Logcat just repeats the following over, and over.
E/AndroidRuntime( 111): Unable to register all android natives
D/AndroidRuntime( 112):
D/AndroidRuntime( 112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 112): CheckJNI is OFF
D/AndroidRuntime( 112): --- registering native functions ---
W/dalvikvm( 112): ERROR: Unable to find decl for native Landroid/content/res/As
setManager;.getCookieName (I)Ljava/lang/String;
E/JNIHelp ( 112): RegisterNatives failed for 'android/content/res/AssetManager'
Click to expand...
Click to collapse
I have a dumb question, did you root your phone?

Oh my gosh, I'm so neglectful...
I did the 1 touch-root method. (though a similar event happened with manual rooting)
I'm running CyanogenMOD 1.4 + JF recovery image.
I tried to load CyanogenMOD 4.0.1's from the SD card after having wiped/factory state'd the phone.
I'm not in a bad way because i did backup and was able to recover.
Thanks for helping me out

pgv100 said:
Oh my gosh, I'm so neglectful...
I did the 1 touch-root method. (though a similar event happened with manual rooting)
I'm running CyanogenMOD 1.4 + JF recovery image.
I tried to load CyanogenMOD 4.0.1's from the SD card after having wiped/factory state'd the phone.
I'm not in a bad way because i did backup and was able to recover.
Thanks for helping me out
Click to expand...
Click to collapse
I don't take anything for granted anymore. A guy couldn't get the Cyan recovery installed for 3 days and it turned out he hadn't rooted his phone.
Well, the major difference between a Tmobile ROM and the Cyanogen ROM is that the Tmobile ROM will not look for an ext partition during boot. I'm assuming that you have one set up. If so, did you wipe it? That would be my firts suggestion. There is probably something there that is keeping the other ROMs from booting. Wipe it, wipe the phone memory and reinstall the ROM.
The other idea that I had is that you need to check the version of the SPL that you are on. If somehow you were still on the original SPL that would cause a problem.

Mike,
Thanks for the hints. I will try them as soon as I am able. I do not currently have an ext3 partition on my SD card (instructions did not mention such a thing in the order I was following them).
For the sake of complete documentation, I was following the guide on Androidandme.com (http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/)
Here is the strategy I am going to try (assume a card different from my Nandroid backup):
Partition SD card with 1/2 FAT, 1/2 ext3 partition
Format both partitions accordingly
Load Cyanogenmod 4.0.1 on to FAT partition
Execute 1-touch root method on phone
In Cyanogen's Recovery, wipe data
apply Cyanogen's ROM
Make log of boot activity (if failure) -OR- Celebrate with the happy dance.
Is this what you had in mind?

pgv100 said:
Mike,
Thanks for the hints. I will try them as soon as I am able. I do not currently have an ext3 partition on my SD card (instructions did not mention such a thing in the order I was following them).
For the sake of complete documentation, I was following the guide on Androidandme.com (http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/)
Here is the strategy I am going to try (assume a card different from my Nandroid backup):
Partition SD card with 1/2 FAT, 1/2 ext3 partition
Format both partitions accordingly
Load Cyanogenmod 4.0.1 on to FAT partition
Execute 1-touch root method on phone
In Cyanogen's Recovery, wipe data
apply Cyanogen's ROM
Make log of boot activity (if failure) -OR- Celebrate with the happy dance.
Is this what you had in mind?
Click to expand...
Click to collapse
That should work. I glanced over the instructions that you were following. Maybe I missed it but I didn't see it telling you to install the HardSPL anywhere. At the end it said installing the Haykuro SPL was optional. As a part of that process, check which radio and SPL you are on and update those as well if needed. Do that before you install any ROMs.

Moved to Q&A

@pgv100 You said you wanted to partition half your card as ext3. I'm not sure how big your card is, but huge ext3 partitions are not a good idea. Anything under 1GB is fine, personally I use 512mb, and that's waaaay more than I will ever need. So my advise is, choose a size between 256mb and 1GB, anything bigger is overkill and will cause some stability issues.

@Mike,
Thanks for all your help. I'm happy to report what seems to be a consistently rebootable ROM. So, HardSPL was not required. But the change to an ext3 partition WAS required for me.
Thanks again!
@Adrian,
I ended up with a 700ish meg partition (before I read your hint). Looks like I got lucky, huh? Thanks for your hint also.

error: run 'wipe dalvik' via adb- RESOLVED

I've done an exhaustive search of all forums (plus asked a very experienced developer) and found this problem I'm having posted only once, and it was on a hero. Therefore, I saw no other choice than to post this.
I have a rooted MT3G, running recovery image 1.3.2g.
I am just trying to upgrade to the next cyan, but when I wipe, I get the error message in the subject line while i try to run dalvik cache, and also same error when I try to wipe extensions.
I removed the battery, pulled the sd, reinstalled it, then the battery, rebooted in recovery and tried again. no dice.
I've never had this happen before and I've done quite a few wipes.
Help?
Sorry if this is in the wrong place, etc. I just need some help from someone more experienced than I. It would be much appreciated.
Thank you,
HK

Yes, it is in the wrong place -- You asked a question so it should belong in the Q&A section.
On my G1/Dream dalvic cache is on the ext partition /system/sd/dalvic-cache.
What is the recovery image 1.6? Flash the recovery image in my sig, not the one for the Dream, but for your phone and run the option if you can't find the commands to do it.
Are you having any problems with the rom install, why do you want to wipe it -- most of the time it doesn't cause problems.
Alternitively you can backup your fat32 partition and remake the partitions and you will be set.

Truly sorry about the post in the wrong place. I'm sure mods will rectify that soon.
I'm sorry, i had a typo in my original message. Running 1.3 recovery image.
I did not try to install anything further after experiencing this problem- i stopped, restored nandroid, rebooted, asked my friend (who is also stumped) and came here.
Thanks again,
HK

Hellykitto said:
Truly sorry about the post in the wrong place. I'm sure mods will rectify that soon.
I'm sorry, i had a typo in my original message. Running 1.3 recovery image.
I did not try to install anything further after experiencing this problem- i stopped, restored nandroid, rebooted, asked my friend (who is also stumped) and came here.
Thanks again,
HK
Click to expand...
Click to collapse
You should go here instead, this isnt really Dream related at all. (Sapphire=MT3G)
http://forum.xda-developers.com/forumdisplay.php?f=480
Oh and Amon_RA has a newer version out now that better.Your sd could be a prob if your getting a error when trying to wipe in rec mode.

When you get this just take out ur battery, sd card, and then put the sd in, battery in, reboot or boot to recovery. No more prob.

I did try pulling the battery, then sd, then putting all back and rebooting in recovery. tried it again, but still had the same problem.
Tomorrow I will try an updated recovery image and see what happens.
Is it likely that somehow my sd has corrupted?

Hellykitto said:
I did try pulling the battery, then sd, then putting all back and rebooting in recovery. tried it again, but still had the same problem.
Tomorrow I will try an updated recovery image and see what happens.
Is it likely that somehow my sd has corrupted?
Click to expand...
Click to collapse
Have you tried just clearing out the dalvik-cache with terminal or adb? You can just remove everything in the folder. Since you have a MT I would recommend that you use adb. Go into recovery and do this.
Code:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
That should clear it

i'm having the same problem! and the sd folder don't have the dalvik-cache! so that cd \system... don't work for me!
ps- htc magic!

As I noted in the title thread, this has been resolved. I figured I would come back and post what I did for others who are having this problem as well, and who might need the same fix.
As it turns out, a theme was causing my problem. I had loaded Alien Aqua a while back, right after I upgraded to 4.2.8. However, for some reason, my phone was reading the original Cyan that I installed- 4.2.4. While this was not causing a problem, apparently it was causing conflicts and corruption.
I re-flashed my root base, then flashed the most recent Cyanogen. No problems whatsoever. All traces of the theme are gone, no force closes, blazing fast phone.
Thanks for the help!

Bad flash? I seem to have a reasonably common issue, but can't find a solution.

I'm unsure if this is two problems or one, but just hoping somebody around here might have a clue what is up with my Nexus.
The background:
Worked my way up through the Cyanogen ROMS without any issue, switching from AmonRa to ClockworkMod about half way through.
Obviously I had to get Froyo on the phone, so installed Paul's and was happily on FRF50.
No issues whatsoever so far, until I noticed FRF72 was about today.
Tried to install the 1.8M patch - and it failed - ah well.
Tried to revert back to FRF50 with my nandroid backup and that failed as well...
..I am now worried.
I deleted some caches - and my nandroid backup worked... then I started fiddling again.. and same errors re-appeared.
Finally got the backup to take again - and I'm now leaving my phone well alone.
The errors:
When trying to install a flash image (every one I've tried so far) I get an error very similar to this one in the log:
...
calling command format
Formatting BOOT:...
mtd: not erasing bad block at 0x00220000
calling command write_raw_image
Writing BOOT:...
mtd: not writing bad block at 0x00220000
E:No space left on device
minzip: Process function elected to fail (in inflate)
E:Error writing BOOT:
E:Failure at line 69:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/clockworkmod/download/...​
I've just got one bad block listed above, but quite often more than one and on a seemingly wide selection of addresses.
I've not managed to get a single image to install on my phone at all (even going back to the OOB stock image).
When the Nandroid restore fails, it seems to write OK to the boot, but then just hangs locking the entire phone (batter out time) when writing the the data or system partitions.
I ended up going partition by partition to restore the image (2 goes on system, 7th time the charm on data).
The questions:
1) I assume I've got duff blocks on my partitions.
2) I assume I've got so many on root, that space is 'less than expected' - hence the no space left errors?
3) So assuming there's limited space, why does the restore seem to work, but images flashing onto boot fail?
4) Is the issues with nandroid restore likely to be the same (happens with the last 3 backups I've taken)? I don't seem to get a log written as it's just hanging.
5) Is my flash 'degrading' - I'm fine if stuff is marked as duff in the factory, but the ability of my flash seems to still be in a bit of 'flux'
7) Is there anyway I can scan the flash on my phone to get an overall status of the memory (~ChkDsk)?
The Big question:
8) Is there anything I can do, other than get the phone back to HTC?
I'm assuming an inability to flash a standard 'released by google build', would count as being a fault.
Most advice just seems to be to:
a) clear stuff
b) format stuff - oh and you sometimes get the bad block messages.
c) Just don't try to force write to those bad blocks, by writing less to the partition.
d) Google may alter the size of the partitons in the future, so there's enough working blocks for me in each of them.
Any help would be most welcome. I'm feeling quite glum about the whole drama.

hmmm
Im no expert but what Id try is:
1.wipe
2.fresh DL amon_ra again ->flash
3.wipe cache and anyother option
4.fresh DL pauls first fyo50 root rom ->flash
5.wipe
6.fresh DL of the new fyo72 of your choice -> flash
7.wipe
8.fresh DL of clockwork
9.reboot
all your problems seem to have came from clockwork upgrade... once again im no expert, and "I reserve the right to be wrong" lol I love that saying... GOODLUCK bro!

Thanks
Didn't have any luck though.
Boo.

[Q] Installation of CyanogenMod RC2 fails (Status 7)

I've been trying to flash the latest nightly or the RC2 and it keeps failing.
I've tried with both recovery-RA-nexus-v2.0.0.img (Amon_Ra) and recovery-clockwork-2.5.0.7-passion.img (Clockwork).
I've tried using radio-4.06.00.12_7.img, FRG83-radio-5_12_00_08.zip, FRG33-radio-5_08_00_04.zip.
I've tried update-cm-6.1.0-RC2-N1-signed.zip and cm_passion_full-274.zip.
I've tried formatting my microSD card.
I've tried downloading each of the files I've mentioned at least twice.
Every time I try to flash either RC2 or any nightly, I get this:
Code:
Welcome to CyanogenMod-6.1.0-RC2-N1!
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/update-cm-6.1.0-RC2-N1-signed
.zip
(Status 7)
Installation aborted.
On Amon_Ra I did 'Wipe ALL userdata', and it still didn't work.
On HBOOT I did CLEAR STORAGE as well.
I can use adb and fastboot if needed. But the ROMs just don't seem to want to install .
I'm confused and I've googled around but I haven't found any solution.
I was using RC1 previously, if it's relevant.
Any help is greatly appreciated! I don't really like bothering people, but I just can't figure out what to do. I tried searching, I always try searching .

I had a problem flashing stuff with amon 2.0 . I went back to amon 1.9 alpha and everything flashed with no problem. I never used clockwork so i dont know with that. Hope this helps.

After doing some more research I tried
Code:
fastboot boot boot.img
And it let me boot into RC2. I even rebooted and it seems to be working... According to the log, I have some bad sectors.
I tried doing
Code:
fastboot flash boot boot.img
But it gave me an error.

I dont use cmd for anything unless absolutely needed. I just do straightfoward download to sd root and flash through recovery. Maybe the rc2 file your using is bad.
you mentioned bad sectors and such so try downloading a rc2 file from a different site, might work. Try using a different version recovery as well. That could help as well.

u gotta r00t ur gibson first

I am having the same problem.
The bootloader is definately unlocked. I am pretty sure it is rooted as I can use titanium backup and give it root access.... What is the issue?

Maybe it is something related with your HBOOT version. I have mine 0.33.0012 and I have the same error you have. Really my error is in another rom based on 6.1.0RC2 and it seems it is related with the size of the kernel.
Previous kernel was near 1.2MB smaller than this one and maybe HBOOT 0017 manages better internal memory to give space to bigger kernel. Maybe updating HBOOT to 0017 solves this issue.
I am also looking into this problem here at xda to see what experts say

It isn't something as simple as not formating the SD card correctly is it?

No, Status Error 7 means that an image write failed, this is typically because the image doesn't fit on the partition and all of your symptoms point to this. Bad blocks on the /boot partition will cause this.
Old but relevant info I posted some time ago: http://forum.xda-developers.com/showpost.php?p=6851045&postcount=1556 (don't use the files on that page!).
Now, the CM stock kernel is really, really small... so if that doesn't fit then you may have a major challenge installing any custom rom...
I've verified my rom (Kang-o-rama) works on most phones with bad blocks on boot, I spent a lot of time making this so but still, if you have too many bad blocks it will not fit.
One of my users got his Nexus replaced because he had so many bad blocks no kernel would fit once he'd removed the stock one...
Code:
fastboot boot boot.img
Doesn't write the kernel to /boot so you won't encounter the problems (just don't reboot).
Code:
fastboot flash boot boot.img
Attempts to actually write the image.
I think you're in replacement zone actually... if you wipe your current /boot partition you may never get another kernel on there. Be careful.

[Q] I897 Boots only to CWM recovery. Help Please.

Hey Guys,
Running CyanogenMod 10.1.2. on Samsung (AT&T)i897. Was using phone, it rebooted as if it crashed. It boots only to the clockwork recovery screen (v6.0.3.6)
Tried reboot- just reboots to cwm recovery
Tried putting the latest cwm 10.3 on external zip and install: IT fails with error "no file_contexts"
Installed adb, (I using linux if that matters) and can connect to phone, and see the file structure (I am a complete noob, but figured out this much)
ANy suggestions on what to try?
thanks in advance.
Edit: Found a log file:
Warning: No File_contexrs
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc ueventd=runnning
int.svc.recovery=running
sys.usb.config=mass_storage.adb
init.svc adbd=running
sys.usb.state=mass_storage.adb
I: checking foir extendedcommand...
I:Skipping execution of extendedcommand, file not found
W: Failed to mount /dav/lvpool/userdata (no such file or directory)
I: can';t format unknown volume: /emmc

U probably r gonna have to mount storage through the cwm recovery, save ur stuff to ur pc, and then wipe data/factory reset and see if it will reboot.
But...u could try to wipe cache, dalvik cache after u mount and save ur stuff. Not sure if it will work, but worth a try before u wipe data/factory reset.

tried mounting and
Im going to guess I have a hardware failure as Mounting external_Sd gives error "unable to mount external_sd"
with that in mind I continued:
tried wipe cache/dalvik & reboot- no change.
Tried wipe data/Factory reset:- no change.
I believe I am dead in the water. A shame as phone is only 9 months old.
Thanks for the help
JOhn Kilbert

The last thing to try is to restore the original Samsung firmware via Odin one-click. Take a look at sticky threads in Captivate Android Development section, latest AT&T ROM is available. Are you sure the phone is only 9m old? The last Captivate was manufactured around 10/2011, I believe.

Val D. said:
The last thing to try is to restore the original Samsung firmware via Odin one-click. Take a look at sticky threads in Captivate Android Development section, latest AT&T ROM is available. Are you sure the phone is only 9m old? The last Captivate was manufactured around 10/2011, I believe.
Click to expand...
Click to collapse
I will try that and try pushing the captivate.zip to the internal SD and see if I can install from there
Yes, I am sure its 9 mos old, I just bought another one at lunch today from amazon

4 numbers under the battery show manufacturing month and year. What numbers you have there? Just curious...

Val D. said:
4 numbers under the battery show manufacturing month and year. What numbers you have there? Just curious...
Click to expand...
Click to collapse
The new phone say m39 & 11/11 not sure which is hte date code, the other 2 captivates (both dead) do not have a date but say rev 0.4