Database Develop

Black screen o Death part II

I posted this herehttp://code.google.com/p/cyanogenmod/issues/detail?id=329
This has been happening for me for a few cyan updates now, and also on the HTC 1.6
image currently
the g1 was "charged", when i got home i took it off the charger and cranked up all
the bells and whistles. within 5 minutes the g1 goes black except for the keys for a
moment and then they go dead as well. no reboot. just goes dead. when i do reboot it
it sometimes wont go throught the whole reboot without shutting back down. does not
happen when it is on the charger. really hard to calibrate the battery when your g1
wont stay on without the charger and when it is it says its charged! i would post it
on the bug tracker, but i can't tell if it's my battery or the rom
and i'm running the death spl 8g card, cyan recovery and newest update, with only a
fat32 and no ext or swap
an update.. maybe check into the device staying awake. seems like with everything
running(gps, 3g, blutooth, etc) and with the phone sleeping, it doesn't crash, but if
the settings to never timeout the screen are active and you leave it on, it crashes
within a few minutes.

you should have an ext partition (the swap is recommended but not required). I only say you should get the EXT because the problem may come when all your apps are in the fat32 drive... it doesn't unmount correctly when you shut down or reboot your phone so your apps / partition sometimes get messed up... this MIGHT be why you get the black screen because it's corrupting the running processes (that are running from the fat32 (apps2SD)) when you reboot the phone(or mount the drive on the computer through usb) while they're being used.... repartition your card to include a EXT3 partition and reinstall the rom... let me know if that works. Post #69 hope this post helps, lol

i have had an ext2 ext3, swap, no swap, all with fresh partitions.

jaaronmoody said:
i have had an ext2 ext3, swap, no swap, all with fresh partitions.
Click to expand...
Click to collapse
awww so i wasted post #69 lol... Did you keep the 1.6 HTC rom? or did you upgrade it to CM 4.2.3.1? Maybe it's the HTC rom that's the issue? install the 1.6 htc and move to cm 4.2.3.1 (you can go straight from htc1.6 to 4.2.3.1, just follow the instructions) and start with fresh fat/ext/swap partitions... i personally use 100mb for swap (just in case i try a rom that uses more than 32mb by default i don't have to repartition)
edit: sorry, just noticed you said it's been happening on a few CM builds already....
try this: make sure you have CM1.4 recovery, new radio and new spl... new partitions (fat/ext3/swap) install the HTC1.6 rom, as soon as it reboots into recovery install the 4.2.3.1CM update. reboot phone and boot everything up as normal....
If it doesn't work after 100% fresh install like that... then maybe it's just a phone issue?

mrandroid said:
awww so i wasted post #69 lol... Did you keep the 1.6 HTC rom? or did you upgrade it to CM 4.2.3.1? Maybe it's the HTC rom that's the issue? install the 1.6 htc and move to cm 4.2.3.1 (you can go straight from htc1.6 to 4.2.3.1, just follow the instructions) and start with fresh fat/ext/swap partitions... i personally use 100mb for swap (just in case i try a rom that uses more than 32mb by default i don't have to repartition)
Click to expand...
Click to collapse
thanks for your help, but I originally formatted and followed cyan's instructions for his newest legal rom. i had this problem still, and then tried to fresh install the stock 1.6 from htc, and still. i think it's an aosp thing. i have had everything running( 3g gps sync blutooth ) for a couple of hours while the phone has been asleep and i can wake it. but if i turn the screen on, its only a matter of minutes before a crash. it's all posted on the cyanmod code.google site http://code.google.com/p/cyanogenmod/issues/detail?id=329

Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death

i used to get the blackscreens. i dont get them anymore. turning off compatibility mode in spare parts helped. try that. untick and reboot.

AustinKnight45 said:
Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death
Click to expand...
Click to collapse
pershoot said:
i used to get the blackscreens. i dont get them anymore. turning off compatibility mode in spare parts helped. try that. untick and reboot.
Click to expand...
Click to collapse
I don't have advanced task manager or spare parts. thanks though

jaaronmoody said:
I don't have advanced task manager or spare parts. thanks though
Click to expand...
Click to collapse
your cyanogen build comes with the spare parts application.

pershoot said:
your cyanogen build comes with the spare parts application.
Click to expand...
Click to collapse
currently i'm on the stock 1.6 htc build

jaaronmoody said:
currently i'm on the stock 1.6 htc build
Click to expand...
Click to collapse
download spare parts from the market.

will try and report

jaaronmoody said:
death spl
Click to expand...
Click to collapse
Maybe the spl I just switched to the DEATHSpl last week and now this is happening

AustinKnight45 said:
Is anyone running Advanced Task Manager, someone typed in market that it was doing he black screen of death so I uninstalled it and reinstalled it and it was still acting weird so I unchecked "show Auto-End notification" and it seems to be working a lot better no black screen o death
Click to expand...
Click to collapse
advanced task manager does not attribute to the black screen of death. it works flawlessly on donut (from what i can see/observe).

pershoot said:
download spare parts from the market.
Click to expand...
Click to collapse
AustinKnight45 said:
Maybe the spl I just switched to the DEATHSpl last week and now this is happening
Click to expand...
Click to collapse
no go on the spare parts, maybe the spl??? doubt it though

AustinKnight45 said:
Maybe the spl I just switched to the DEATHSpl last week and now this is happening
Click to expand...
Click to collapse
it has nothing to do with the SPL. try the spare parts trick and see if that helps. even if it slows it down to once every 3-4 days would be an improvement.

pershoot said:
it has nothing to do with the SPL. try the spare parts trick and see if that helps. even if it slows it down to once every 3-4 days would be an improvement.
Click to expand...
Click to collapse
i did and it happened minutes after reboot, and i'm getting real close to a dreaimg.img test

jaaronmoody said:
i did and it happened minutes after reboot
Click to expand...
Click to collapse
wipe out your sdcard's ext partitions (not the fat32), and do a full wipe. reinstall the rom, get spare parts, untick compatibility mode, reboot, and then observe.

pershoot said:
wipe out your sdcard's ext partitions (not the fat32), and do a full wipe. reinstall the rom, get spare parts, untick compatibility mode, reboot, and then observe.
Click to expand...
Click to collapse
seriously, i installed the rom on a fresh wipe and format and i just installed spare parts and unchecked the box

lol dam ok..........what about your SD card could it be its going to crap out on you...

Need help for MT3G

Hey all, I need some serious help for my Mytouch3G. My MT3G just stays at boot screen all the time now every time I flash a custom rom. The last rom that worked for me was Super D 1.6 blk and other roms before that. I don't know what's wrong now, I tried using my Nandroid restore, wiped everything, other roms. I even tried re-rooting, so I had to go back to stock (which worked so I know it's not bricked).
I know this is the G1 Q&A but I since MT3G is compatible with most roms I posted here.
Also, I can boot into recovery and fastboot. Please help? All I want now is to go back to Super D 1.6 .

Try re-rooting the phone.

you probably dont have the latest radio ,and (or) spl, also make sure you wipe before flashing.

Do you have apps on sd card? If you do - you may need to reformat your EXT, regular wipe doesnt to it. And yes, you do need correct SPL and radio.
Good luck.

I would also try posting in the correct forum next time. This is the Dream forum, I don't care how close they are in specs and such, this is the dream forum. There is a magic forum for you to try out next time

djluis48 said:
Try re-rooting the phone.
Click to expand...
Click to collapse
zachattack052 said:
you probably dont have the latest radio ,and (or) spl, also make sure you wipe before flashing.
Click to expand...
Click to collapse
borodin1 said:
Do you have apps on sd card? If you do - you may need to reformat your EXT, regular wipe doesnt to it. And yes, you do need correct SPL and radio.
Good luck.
Click to expand...
Click to collapse
Thanks guys, will try.
JAguirre1231 said:
I would also try posting in the correct forum next time. This is the Dream forum, I don't care how close they are in specs and such, this is the dream forum. There is a magic forum for you to try out next time
Click to expand...
Click to collapse
Hey thanks asshole, you're truly helpful. And I have tried posting in the magic forum and I got no response.

ElahC said:
Thanks guys, will try.
Click to expand...
Click to collapse
You should wipe via Amon_Ra when going rom to rom and wipe before using your backups.
There is no reason for foul language either

After installing a new rom my phone freezes at the 2nd load screen

I did everything right and after I reboot when in safe mode, it loads the "tmobile G1 screen but the 2nd load screen loads forever and does not change. I waited over an hour last night and it did not finish loading.

Should be in Q&A mate.
What rom ? what version ? what does it say if you run a logcat.
Try reflashing it via the recovery console.

safe mode refers to windows and recovery mode is the one your talking about.You should at least give other info like your SPL,radio,ROM,recovery,etc..

The ROM is SuperD192
using latest spl and radio
is there any other roms that you recommend?

anthonyc9 said:
The ROM is SuperD192
using latest spl and radio
is there any other roms that you recommend?
Click to expand...
Click to collapse
Of course:
http://forum.xda-developers.com/showthread.php?t=538456
Flash the rooted base, then flash the expansion from the above link

This is what i did in order.
1. formatted SD card
2. ran the recovery
3. rebooted in recovery mode and flashed the radio
4. rebooted again and flashed the spl.
5. rebooted and flashed the ROM

anthonyc9 said:
This is what i did in order.
1. formatted SD card
2. ran the recovery
3. rebooted in recovery mode and flashed the radio
4. rebooted again and flashed the spl.
5. rebooted and flashed the ROM
Click to expand...
Click to collapse
I'm not sure which radio and SPL you flashed was it these:
http://www.google.com/url?sa=t&sour...Wbt0kE3c8xtD9CWMg&sig2=2_QLVSY7frWDfnh2v7u6pA

yes, those were the exact ones

anthonyc9 said:
yes, those were the exact ones
Click to expand...
Click to collapse
At least you can read cause most people flash the SPL then radiod and get a nice paper weight to display.Get Amon_RA:
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
After updating to that wipe everything then flash Super-D.

anthonyc9 said:
The ROM is SuperD192
using latest spl and radio
is there any other roms that you recommend?
Click to expand...
Click to collapse
the latest spl and radio you say.............
and how do we now you didn't do something stupid and use the wrong ones?
is it too much to post at least the version numbers?
--
but anyway,
take out the SD Card, and open it on your computer
copy all the files into a new directory call my Phones SD card
now put it back in the phone
go into recovery
somewhere in the Recovery (I'm not going to give any specifics, which is tbh only fair cos you didn't give any. )
is format/part SD Card, do it ....
swap size,,, I duno, 32mb,64mb, 96mb? up to you...
Ext2 errm 512mb is good
rest is fat32
now, put your ROM on the sd card , and flash it
...
next time Wipe Data/cache , Dalvik-cache, sd:ext before you flash the ROM
Oh and do a nandriod back up BEFORE you wipe Data/cache , Dalvik-cache, sd:ext, before you flash the ROM and might be a good idea to read up next time before you Wipe Data/cache , Dalvik-cache, sd:ext before you flash the ROM Oh and do a nandriod back up BEFORE you wipe Data/cache , Dalvik-cache, sd:ext, before you flash the ROM

so i am going to use this as a recovery instead? and just follow the same steps i did in the past?

Pm me, I'll walk you through sorting this out in simple plain english.

Ace42 said:
At least you can read cause most people flash the SPL then radiod and get a nice paper weight to display.Get Amon_RA:
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
After updating to that wipe everything then flash Super-D.
Click to expand...
Click to collapse
so i update to that recovery instead of the one im using, then just follow the same steps?
Sorry i am very new to this. I appreciate all of your help!

anthonyc9 said:
so i update to that recovery instead of the one im using!
Click to expand...
Click to collapse
do you honestly expect an answer?
YOU HAVE NOT SAID WHICH RECOVERY YOU ARE USING?
sorry for the caps, but come on, this is't about being new to rooting, this is being new to common sense
1/ which recovery
2/ which radio
3/ which SPL
4/ which ROM
you could cheat by posting a link to the guide you followed
if it was written on the back of a beer mat, take a pic of it
I'm sorry for being so rude, I am actually trying to help you
people will be able to answer your questions better if you give information..

I am pleased to say he is now up and running.
And to the senior members on this thread take your heads from up your arses. **** we were all new once and just waffling **** at someone loaded with jargon and expecting them to understand is a ****in joke.
I have to say I'm very disappointed to be classed as the same as you people and apologies for the language but some people need telling straight. Go get over your ****in selfs!
If ANY of you had given him a chance you would have found him to be a great guy that listened to instructions and had a fairly good understanding for someone so new.
You so called 'Senior Members' disgust me. *Le Sigh*

Help installing Gumbo 1.5c

I know that this is a REALLY dumb thread to start but I and a lot of other people need help with gumbo 1.5c.
Most of us get stuck on a bootloop after the flash.
i am going from: Modaco 2.2 to 1.5c
i did wipe: factory reset and ext4
plz help

andyandrwew said:
I know that this is a REALLY dumb thread to start but I and a lot of other people need help with gumbo 1.5c.
Most of us get stuck on a bootloop after the flash.
i am going from: Modaco 2.2 to 1.5c
i did wipe: factory reset and ext4
plz help
Click to expand...
Click to collapse
Hmm... You really shouldn't have any problems if you've taken the steps above. Did you have A2SD when you were on Modaco 2.2? If so, you might want to format your card to FAT32 -- that would fix the bootloop.

hmmm
it looks like my ext partition never got wiped
i reinstalled modaco 2.2 and had all my apps back exen after the "wipe" in recovery.
i repartitioned my sdcard and rewiped and am reflashing again...we will see

nope
ITS THE KERNEL!!!
idk what about the kernel but it is the kernel.
im pretty sure you cant go from stock or Modaco to Gumbo...

andyandrwew said:
im pretty sure you cant go from stock or Modaco to Gumbo...
Click to expand...
Click to collapse
You'd be wrong.

andyandrwew said:
ITS THE KERNEL!!!
idk what about the kernel but it is the kernel.
im pretty sure you cant go from stock or Modaco to Gumbo...
Click to expand...
Click to collapse
posguy99 said:
You'd be wrong.
Click to expand...
Click to collapse
Exactly. I did precisely that, Stock - Modaco Modified - then Gumbo, haven't looked back since. It can be done. And I doubt it was the kernal -- do you have any specific error messages or anything that could help us solve this?

no
I don't have any error messages. I did post a copy of logcat on the gumbo Rom page.

andyandrwew said:
I don't have any error messages. I did post a copy of logcat on the gumbo Rom page.
Click to expand...
Click to collapse
Okay. Listen, if I were -- I would run the RUU, go back to factory and begin your process of rooting and installing a custom ROM again, that should fix your problems and won't take you any longer than 20 to 30 minutes at most.

alright will try
I will try.

pseudoremora said:
Okay. Listen, if I were -- I would run the RUU, go back to factory and begin your process of rooting and installing a custom ROM again, that should fix your problems and won't take you any longer than 20 to 30 minutes at most.
Click to expand...
Click to collapse
did not work. i am going to try going from ext4 to ext3 and see how that works. i headr ext4 can be "bad".
[edit]: IT WAS THE ext4!! i have gumbo 1.5c now!! woo hoo!! this ROM is AMAZING!!

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.

Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App

okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.

i tried also and still no luck .. i hate this

to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.

So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.

I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.

i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!

sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass

il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™

Yeah I'm using clockwork 2.5.0.1.

sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.

So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App

sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH

Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).

got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?

sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!

There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.

mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.

touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help