Database Develop

Phone stuck at G1 Screen

Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks

Do you have Amon Ra recovery?

No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)

When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.

I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating

1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.

why is it that that 99% of newbs are on cyanogen

@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.

Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu

what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.

airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok

thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!

very quick question..
did you wipe dalvik-cache?

Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik

Please help unable to install any rom??

Hey sorry if this has been asked before i couldn't find it anywhere so there is some problem with my phone i don't know what is happening every time i use to install a new Rom it use to install perfectly without any fc's boot loop errors etc, but from past 2 days i don't know why any ROM i try to install (even the one which i use to work perfectly) will not install perfectly there will be fc's boot loop error wont pass the X when i switch on the phone. Please help its driving me crazy

Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too

ilostchild said:
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
Click to expand...
Click to collapse
yes i did Wipe data/factory reset ,Wipe cache,Wipe Dalvik-cache but just now i discovered that after doing this and still last installed rom has not been wiped its still there wtf what should i do and yes i did install 2.6.34.1_AVS-925mV_BFS_1113Mhz kernel how do i completely wipe everything???

Umm also do wipe sd partition, then do another wipe factory and cache-.. then do a repair sd then try to flash new rom.. this is what i usually do when i install new roms

still no luck i even did clear storage then wiped everything and i dont use app2sd(ext) i dontunderstand what to do i even tried with the clockworkmod's recovery still the same

sorry man, My only guess and idea is try to flash back to a normal kernal, then flash rom.. only thing i can come up with atm, or you can wait and see if some one that comes up with a better solution

where can i find norman kernel or any kernel which can fix this?

[Q] Extremely slow boot-time when new rom

Hi, tried serveral roms now but after I restart the phone and with the new rom installed it takes forever to boot. Havent got past the bootlogos at all. Have tried to let the phone boot for like an hour or so...
Normal original rom works fine. What is wrong?

Try doing a full wipe
Sent from my HTC Tattoo using XDA App

I have tried wipe data and dalvik cache.. no good

digitalaflaesk said:
I have tried wipe data and dalvik cache.. no good
Click to expand...
Click to collapse
hi
if u have done a nand backup of ur orignal shipped rom then do a nand restore and if thing are ok then do the wipe and flash any cooked rom u are comfy with
this is what i do when i have problems with cooked roms
hope it helps good luck

haree said:
hi
if u have done a nand backup of ur orignal shipped rom then do a nand restore and if thing are ok then do the wipe and flash any cooked rom u are comfy with
this is what i do when i have problems with cooked roms
hope it helps good luck
Click to expand...
Click to collapse
Yes, I have done a nand backup and restored to my original rom and it works.
After that I then wipe both data and dalvik cache and install a rom. I still get the slow boot time of the rom, or should it take long? More than a hour?
With example with SPQRom I get the blue android on skateboard for like forever, have not get passed that screen.
Something must be wrong?

I tried booting up without a sd-card and nothing changed, same problem. I believe it must be that I dont have any space left on the phone.
Is there a command in recovery to type to see available space?

I have these kind of problems a long time. Nothing works. I tried all above plus many times, plus other things, as format sd card, change sd card, wipe through adb, wipe system, and others I cannot remember.
I have the same problem with SPQRom, version 0.4.1 and I solved once by manually push the libaudio files in lib directory after rom flashing. But maybe your error is different.
I have similar problem with version 0.5, but in this case the problem appears in earlier stage(in first TATTOO screen). And I have this problem with other versions and roms like fyodor's, ikxdf's... And this happens only with 2+ custom roms and in some versions not all. With 1.6 roms I never had problem(with any rom or version I tried).
So I don't know if is device's problem or rom's building.

Oops, that does not sound good at all.
I have only tried 2.2 roms, maybe should try with a 1.6 rom and see if it works..

Ok, so a 1.6 rom works. Damn.
HCDR.ROM http://forum.xda-developers.com/showthread.php?t=723255
Anyone has a solution??

Tried kiljacken rom (2.1) and that did not work.
So i did a restore, similar to what I have done before to get the phone working, and now that wont get past the boot logo.
Does anyone have a clue what is going on?

[Q] Installing Custom ROMS, why stock?

Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.

before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.

The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over

So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?

I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot

I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot

I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot

I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.

you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.

mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.

Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.

Can't Upgrade cyanogenmod, stuck at HTC screen

Hi,
I've been trying to upgrade my Hero from cyanogenmod 6.1 RC1 for a while now. Every new rom I try to install just hangs the phone at the initial HTC screen. I've tried wiping every partition I can possibly wipe before I install the new ROM's but no go. The only way to get my phone back is to install 6.1 RC1 again.
Not sure what to do. I've tried different memory cards too.
Any suggestions? Maybe my phone just doesn't like the new 7.X roms?

Try reflashing your recovery. You might want to check out Ra1.7. Or you could try this after you reflash your recovery
Backup all of your data to your pc. Then format your sd threw your pc and restore factory defaults. Then format it again threw your recovery with no partitions no swap just all fat/system. Then redownload the rom of your choice+gapps. Then perform a fully wipe as in data,cache davilk-cache. Then flash the rom then the gspps and see if the rom will reboot.
Locked & Loaded

yeah you should definitely use the wipe function in the recovery menu before you flash the new rom,
if that doesn't help, restore to the original and start over, maybe use different recovery, i use the the amonra, it's been working well

Thanks, I will give it another go in a day or two and let you know how it goes.