Database Develop

G1 Hero flash strange problems

Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?

viccyran said:
Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?
Click to expand...
Click to collapse
Hit the back button, see if that loads up Rosie.

lukekirstein said:
Hit the back button, see if that loads up Rosie.
Click to expand...
Click to collapse
nope :[ just stuck at htc screen. i can hit end phone call to go to screen lock again, but when i pull it down back to htc screen

I would recommend then reformatting your SD card. Hero stores weird things on the SD card and can sometimes cause problems even between Hero builds (like in your case.) See if that works for you :]

lukekirstein said:
I would recommend then reformatting your SD card. Hero stores weird things on the SD card and can sometimes cause problems even between Hero builds (like in your case.) See if that works for you :]
Click to expand...
Click to collapse
i managed to format using both the panasonic SD tool, and tablerm on parted.. any other trhings i could do?

viccyran said:
Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?
Click to expand...
Click to collapse
does anyone think thtis could be because of an improper flash or when i activated swapper (even though swapper was automatic on jachero doh), it wrote some corrupted files in some god forsaken place that they cant write to now?
and if so, how would i wipe it clean? i reflashed to rc29 nbut im not sure i f that did the whole job

:( Random Problem......Help, Please! :(

Right then,
Already searched on this one and not yet seen a solution to my problem. I own a T-mobile G1 and my phone crashes after it has booted up, or will not boot up properly: either the T-mobile G1 screen stays on for 5-6 seconds then I get a black screen, or it boots up then freezes with a black screen, or it won't switch on at all.
I currently have:
T-Mobile G1 with Root
2.22.19.26I radio installed
1.33.2005 "Death" SPL installed
Amon_RA's RA-v1.2.3 recovery installed
MghtyMax "What a feeling" 1.9.1 Hero ROM installed
fat32, ext3 and linux-swap on class 6 8Gb sdcard
I can get to recovery (sometimes.....it doesn't always get that far) and fastboot, so hopefully it's not bricked. I have already tried wiping (ALT+W) and formatting the ext2 (from the option in RA's recovery menu and also via console); removing all the partitions and starting afresh recreating them (after removing them of course), and as I can get to recovery (sometimes) I have tried flashing a different ROM (SENSEhero 1.3.3 unthemed) but still get the same issue.
I have flashed quite a few ROMs recently and not had any issues, so any help on this one would be most appreciated!

matthenry87 said:
Check your SD Card. My buddy had the same "black screen" problem and I discovered his SD card was slightly popped out. I clicked it back in and boom. problem solved. For him at least!
Click to expand...
Click to collapse
I'll give it a go..........

Seems like it is a problem with the sd card. Removed it and plugged it into my pc via a card reader and it couldn't recognise the card. Amazon here we come! Thanks for the help!

Give us a logcat from ddms.bat.

Binary100100 said:
Give us a logcat from ddms.bat.
Click to expand...
Click to collapse
he already solved it....

Not again......
B-man007 said:
he already solved it....
Click to expand...
Click to collapse
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ

adb logcat
you can also run ddms.bat and get the log from there

misterzak said:
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ
Click to expand...
Click to collapse
well trying to solve the problem by trying another sdcard is not a fix... since some roms do rely on the ext contents for things to work properly. what i suggest is having the 3nd card completely wiped and partitioned correctly..then move a rom onto the card and flash like u normally would.

Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......

misterzak said:
Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......
Click to expand...
Click to collapse
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say

B-man007 said:
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say
Click to expand...
Click to collapse
Thanks for that. I assume if they ask me to return it to them to reflash the original bootloader and recovery screens so that they cannot tell I've been "playing" with my phone...

Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.

B-man007 said:
Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.
Click to expand...
Click to collapse
If I flash RC29 (or RC7 for me) will this brick the phone as I currently have Death SPL. I'm sure I've read that somewhere on here?

Unrooted.......
I've now reverted back to RC7 (as I'm in the UK) and all seems okay....for now.
I will run it like this for a day to see if it still crashes or does anything funny. If it doesn't, I will re-root and start again!
Thanks for the help with this. I will update if it continues to crash.

Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio

EVT Board.........
B-man007 said:
Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio
Click to expand...
Click to collapse
Now this is interesting, RC7 was fine. Re-rooted the phone, fine. Flashed AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip ROM, fine. Flashed Amon_RA's v1.2.3.img recovery, fine. This is where it gets fun, partitioned my card within the recovery to FAT32, ext2 and linux-swap, then rebooted into recovery. The phone crashed. So, I thought there must be an issue with the sdcard. Put in the stock 2Gb card with the RC7 DREAIMG.nbh file on and pressed camera+power to go back to RC7. It came up with an red code 00058002, then went back to the bootloader screen. It stated at the top that it was an EVT board. Searched all of the Dream Q&A section for EVT and absolutely nothing. Tried going into bootloader again and that screen started to warp and the graphics and pixels started to jumble up.
Any ideas?

wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe

B-man007 said:
wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe
Click to expand...
Click to collapse
I flashed the AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2 ROM and booted it up fully. Then using the Terminal Emulator within Dev Tools I flashed Amon_RA's recovery. All went well until I partitioned the sdcard. It won't boot up at all into the home screen or recovery, just bootloader, although it did this before when it first started crashing. I'm gonna leave it tonight and try again tomorrow.
Do you know anyone else on here who has any idea on this one? Seems like I'm the first!

This is probably an issue with the recovery itself...though ive never read about anything like your having.
ill bump this thread and see if anyone can help...maybe david can (ill tell him to get on here)

why dont you give a differant recovery image and dont try to partition just try with a fat32 sdcard on a cyan rom or something see what happens with that

looking to hero! Some questions

Hello all,
I'm curious about somethings for turning my g1 to the hero (rosie?) rom (wow it looks beautiful).
The first being Where can I actually find it? I found two sites that offer it but doesn't seem like its from the developer themselves (who I'd trust more).
Secondly, which developer has the best performance (e.g. speed, ect.). I've read that it is a deadly slow Rom and I already lack patience for my g1 now (It's the stock firmware). The hero its self looks much smoother, am I wrong?
If I can't risk my phone being bricked should I bother trying it? (I had it JF rooted in the summer which I did successfully on my first try, and I un-rooted it.)
Is there a text document with how to install with a video that coincides?
Lastly, Is Cyanogen a better rom? (this has next to nothing to do with the hero rom )
Hopefully I didn't miss a thread on this I searched for like an hour.

skratched1 said:
The first being Where can I actually find it? I found two sites that offer it but doesn't seem like its from the developer themselves (who I'd trust more).
Hopefully I didn't miss a thread on this I searched for like an hour.
Click to expand...
Click to collapse
You cant just start driving, you have to learn the basics.When you get in a car there a many things that you need to do first is learning and even taking test.
You must have root first and a recovery image and im guessing your all stock.The dream section has all the info needed to root now is up to you to decide if you want to read it.
-Best regards

Thank you. I am very comfortable with the rooting process. I just don't want to do it unless the rosie rom is worth it!

Basically, Hero is incomplete. It doesn't have Bluetooth nor full Google Voice integration, and it runs 1.5. However, at the rate the devs are going on Hero 2.1 the version it runs could change very soon.
For now, stick with Cyanogen as it is a better Rom. Hero doesn't really work on the G1, it's slow and there is a lot of core function missing. It will never be an everyday ROM. I think of it like a concept car. Its cool in a "look what we can do" sort of way, but just wait for the next HTC Android phone.

skratched1 said:
Thank you. I am very comfortable with the rooting process. I just don't want to do it unless the rosie rom is worth it!
Click to expand...
Click to collapse
video here:follow in order
1.http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
2.http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
3.http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/
-Best Of Luck To You!
P.s. Better get started

Wii60 said:
Basically, Hero is incomplete. It doesn't have Bluetooth nor full Google Voice integration, and it runs 1.5. However, at the rate the devs are going on Hero 2.1 the version it runs could change very soon.
For now, stick with Cyanogen as it is a better Rom. Hero doesn't really work on the G1, it's slow and there is a lot of core function missing. It will never be an everyday ROM. I think of it like a concept car. Its cool in a "look what we can do" sort of way, but just wait for the next HTC Android phone.
Click to expand...
Click to collapse
Its not slow...You must be running a super old version..Hero 2.1 roms and 1.5 roms are both very fast...King's 2.1 is very fast and close performance to cyanogen, please dont misinform people.All current hero roms are fast, in a 2.1 rom you can achieve 20mb+ free ram which is about the same to a cyanogen rom. Maybe you used a old jac rom months ago.
-"Times are changing boy, you need to catch up"

Ace42 said:
Its not slow...You must be running a super old version..Hero 2.1 roms and 1.5 roms are both very fast...King's 2.1 is very fast and close performance to cyanogen, please dont misinform people.All current hero roms are fast, in a 2.1 rom you can achieve 20mb+ free ram which is about the same to a cyanogen rom. Maybe you used a old jac rom months ago.
-"Times are changing boy, you need to catch up"
Click to expand...
Click to collapse
I'm sorry to say, but no I have tried many Hero configurations on my class 6 as recently as a month ago. The fact is that even if there were drivers for all of the hardware over time Hero really starts to bog down. It will not always perform after that post-setup peak it has.
If you want working hero wait until the first 2 weeks of January when the Passion comes out.

Ace42 said:
video here:follow in order
1.http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
2.http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
3.http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/
-Best Of Luck To You!
P.s. Better get started
Click to expand...
Click to collapse
Going to try this tonight. Read and watched the videos. seems very simple. thank you!

need help!
When following this guide http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/ (I already did the one click root with no issues)
In part II of the guide
. Download the custom SPL for your device:
T-Mobile G1 – Here
MyTouch 3G – Unneccessary, skip this section and proceed to Section III.
3. Plug in your phone and mount the SD card (pull down on the notification bar and select the SD card notification then click Mount in the pop up window).
4. After the SD card shows up on the computer, put the SPL zip file on to the memory card.
5. Once it is done transferring to the memory card and you have renamed it, unplug the phone from the computer.
6. Turn off the phone and then turn it back on by holding down the Home and Power button to get to recovery mode (keep holding it until the recovery screen with the writing and black background come up). Here i get to the ! so I hit Alt + L to get to the recovery screen. It gives me the menu to reboot, apply zip, wipe. However at the bottom of the screen it says E: Can't open /cache/recovery/command
7. Once the recovery screen is up, click on Wipe Data. Once that is done, click on Apply Update.zip and wait for it to finish. I wipe the date and then apply zip. I then get this message __ Install from sdcard... Finding update package... Opening update package... Verifying update package... E: No signature (5 files) E: Verification failed Installation aborted
I'm assuming this means the SPL file is corrupt but I don't know much and probably am wrong.
How can I fix this? I got this far with no issues and so close to being done!

skratched1 said:
need help!
I'm assuming this means the SPL file is corrupt but I don't know much and probably am wrong.
How can I fix this? I got this far with no issues and so close to being done!
Click to expand...
Click to collapse
Just rename to update not update.zip and make sure the sd is Fat32 not Fat or NTFS.
radio goes first i think make sure you did that section.

Ace42 said:
Just rename to update not update.zip and make sure the sd is Fat32 not Fat or NTFS.
radio goes first i think make sure you did that section.
Click to expand...
Click to collapse
SD is fat32 and the update.zip just says update
My radio is 2.22.19.26I that is the most current, right?
tried again still the same message. Any other suggestions? should i unroot and start over again?

skratched1 said:
SD is fat32 and the update.zip just says update
My radio is 2.22.19.26I that is the most current, right?
tried again still the same message. Any other suggestions? should i unroot and start over again?
Click to expand...
Click to collapse
Yes you have current radio no need to flash it again unless you want a new paperweight.

Def no paper weight!
I tried again and Still the same message. What do I Do? thanks for all the help.

skratched1 said:
Def no paper weight!
I tried again and Still the same message. What do I Do? thanks for all the help.
Click to expand...
Click to collapse
Try to redownload the file.

did that twice once from the link in the video and once from http://code.google.com/p/sapphire-port-dream/
both gave me the same results.

UP AND RUNNING JACHERO
Thanks a bunch ace. In the two minutes its been up it's looked as good as I wanted it to!

so my son grabbed it this morning, it froze i took the battery out. Now it keeps going to the hero screens over and over again. what should I do?

If I were you I would try re-flashing. Do you have a custom recovery.img? Like Cyan's or Amon-Ra's? If you do, try wipe cache, wipe ext part, wipe cache, and then re-flash. That's always the first thing I do when my phone starts getting buggy.

Cyanogen 4.2.11.1 Issues

Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,

D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83

staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?

cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.

Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.

how do i install this Cyanogen on my G1 with 1.6 firmware ?

simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3

But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.

Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.

Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^

I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.

I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.

D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.

cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back

D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.

okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.

Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?

borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?

Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!

[Q] X8 reboots by itself

Hi all,
this is my first post so first of all I want to say how amazing this community is !!
I've installed gingerDX v018 just following the xda instructions and all has gone smoothly.
Anyways, I'm posting 'cause sometimes my x8 reboots by itself, usually during the night (each time I heard the logo animation alert ). I guess the timing is not significant, but it happens quite every night.
Do you have any idea of what could it be?
There is some x8 log I could read from or may I use the terminal emulator app?
P.s. I didn't flash the kernel, so I'm still using the stock K. No overclocking apps (not yet).

Do a full wipe. The GingerDX thread says there's no need to do a full wipe after update, that must have confused you.

if what Chris95X8 said dosnt work then your stuck for a while until someone makes a -all-in-one sorta fix. i used to have this problem and after a while it rebooted itself and it got stuck in a bootloop so do the full wipe as soon as posible imo.
i did a full wipe and now its back to normal. no more auto reboots either now.
if that dosnt work then reinstall the rom.

I thought I did. I mean, after the installation I did a full wipe to avoid reboot looping I experienced during my first time installation.
My installation steps actions:
- installed v018 zip
- installed extra zip
- ran Factory Reset (full wipe) option
- ran Wipe cache partitionoption
- reboot phone
Did I miss any steps?

wilbso said:
if what Chris95X8 said dosnt work then your stuck for a while until someone makes a -all-in-one sorta fix. i used to have this problem and after a while it rebooted itself and it got stuck in a bootloop so do the full wipe as soon as posible imo.
i did a full wipe and now its back to normal. no more auto reboots either now.
if that dosnt work then reinstall the rom.
Click to expand...
Click to collapse
If I run out of options I'll try to install the v019

Anªk|n said:
I thought I did. I mean, after the installation I did a full wipe to avoid reboot looping I experienced during my first time installation.
My installation steps actions:
- installed v018 zip
- installed extra zip
- ran Factory Reset (full wipe) option
- ran Wipe cache partitionoption
- reboot phone
Did I miss any steps?
Click to expand...
Click to collapse
hmmm you didnt miss anything...i will search around for an answer for you...if there is one...

wilbso said:
hmmm you didnt miss anything...i will search around for an answer for you...if there is one...
Click to expand...
Click to collapse
Thank you.
In the meanwhile this w/e I'll try to disinstall one app at a time, to see if there are some conflict. It has rebooted just 5 minute ago.

i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..

maliceomalice said:
i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..
Click to expand...
Click to collapse
oh man, thats a bummer... heres some smileys to cheer you up
there you go.
---------- Post added at 08:00 PM ---------- Previous post was at 07:54 PM ----------
Anªk|n said:
Thank you.
In the meanwhile this w/e I'll try to disinstall one app at a time, to see if there are some conflict. It has rebooted just 5 minute ago.
Click to expand...
Click to collapse
ok, some answers show that it is either the rom or battery, they also suggest to have it sent off to have it looked at, see if anything is mucked up or something. sorry if it isnt much but its all i could find so far

maliceomalice said:
i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..
Click to expand...
Click to collapse
Hope they will solve the issue. let us know if they will
wilbso said:
ok, some answers show that it is either the rom or battery, they also suggest to have it sent off to have it looked at, see if anything is mucked up or something. sorry if it isnt much but its all i could find so far
Click to expand...
Click to collapse
Thank you wilbso, sending it off will be my very last resource. Anyway for now I've removed weather widget from the lockscreen and Homescreen, just to exclude any (?) refreshing data problems. Next step will be to install some task killer and so on.
I'll write if anything work it out!

Coverage
How's coverage in your area?
I had frequent reboots on low signal areas (very bad) and the phone tried to connect 3G to check e-mail. Anyway, after each reboot, I cleaned dalvik and cache, and then eventually it went away after moving from CM7 to GingerDX.

I think another possible problem is the ram cuz you said that you dont use task killers so the problem may be the low ram(every gb problem)if you confirm that this is the problem i sugest you should use advanced task killer form market

I don't think it's a ram problem, I suggest a full wipe an pay attention when you restore, do not restore system app or app data, the problem could be there...

crazy x8. Full wipe is the solution for prob in almost cases in x8 using custom roms. Wierd

@Chris_Castro:
2g signal looks stable, 3g poor, but at home I'm using wi-fi. But just to be sure I'll check the force 2G signal option, so we will see.
@X8invisible13:
I had the same idea yesterday, so I've installed Memory Booster - RAM Optimizer, here my ram data:
total memory: ~ 175MB
memory avaiable: ~26MB
and reading here and there they look to be average values. But one of the next tests will be to install the latest gingerDX rom, or some other cool roms and test each app at a time.
@evil_chris:
mmm, I'm quite the noob here, so I don't have any backup data or backup apps. I was playing around with HS/LS, sliders, icons when I experienced first problems, so had no time to deepen backup systems.
But I got what do you mean, so as I said, the next installation will be a naked one.
Last episode happened yesterday morning, I checked the locked screen, w/o unlocking it, and after 20 sec it rebooted. Just after I logged in it rebooted again
Anyways Thanks guys

I Cleaned Dalvik and cache, and removed the overclock and now looks good