Database Develop

Stuck at G1 screen :(

I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)

emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Did you even wipe when going between the 2 roms?

Ace42 said:
Did you even wipe when going between the 2 roms?
Click to expand...
Click to collapse
Mmmm I usually do, but maybe thats were I went wrong. I've wiped since and it's still stuck though.

emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.

Bavilo said:
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.
Click to expand...
Click to collapse
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'

emoray said:
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'
Click to expand...
Click to collapse
"update" means coming from the previous xrom. you must wipe coming from cyans rom.

emoray said:
I'm currently stuck at the g1/tmobile screen.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
Click to expand...
Click to collapse
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought

jmhecker said:
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought
Click to expand...
Click to collapse
Ahhh well that'd been great if I hadn't just wiped my SD card to reformat the ext partition! DAMN!
Is it possible to mount the CD card whilst in recovery mode? Then with a clean EXT2/SD card, a wipe and reflashing the rom should work surely?

ums_enable if you have a custom recovery - do it in the console
and next time post in the right section please

not the right post
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
just wipe and start from scratch .repartition ,reflash and you'll be good

try hooking it up to adb and get a logcat while its on the boot screen and see if it is doing something, might just need to wait it out. My G1 was recently on the G1 boot screen for over an hour while busybox was re-writing a filesystem.

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

Phone refuses to boot after new ROM

EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance

ksharp5580 said:
EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance
Click to expand...
Click to collapse
Wipe everything (data, dalvik, and your SD card) and reflash. Yes, I know you just partitioned that's probably the problem.

This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?

ksharp5580 said:
This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?
Click to expand...
Click to collapse
it just wipes the ext it doesnt undo the partition

I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?

ksharp5580 said:
I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?
Click to expand...
Click to collapse
You want both data and dalvik at a minimum. If you want to try to reflash without reformatting your card, do the following:
Boot to recovery
Wipe data/factory reset
Wipe dalvik
Flash the ROM
(optional but I always do this anyway - takes 10 seconds and is extra insurance)
Wipe data/factory reset
Wipe dalvik
Boot
If that doesn't work, I'd recommend removing your microSD card and formatting it cleanly on your PC (fat32 format) and re-copying the ROM and attempting the above again.
Give it a go and report back.

if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7

Question, why would u wipe after installing the rom?
Sent from my ADR6300 using XDA App

no reason to, but most roms it won't hurt anything, as it only wipes /data and /cache, however, some roms do add apps to /data/app on flashing, and you would be removing those apps then.

Is that a Hero thing or is that in general?
I just had someone test the ClockworksMod on Darktremor Apps2SD for a Nexus One and it worked just fine.
danaff37 said:
if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7
Click to expand...
Click to collapse

I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App

Actually, was just looking back into it, and I may be wrong on it's compatibility, but it is just in my experience that it doesn't work too well for whatever reason. I like the idea of some of the features it offers, but it never worked right on backing up and restoring for me, and I may have just assumed that was the reason. Our I may have confused it with amon ra 1.7
Sent from my Hero CDMA using XDA App

I use Godspeed and been really happy with it. I was just curious since I've never used ClockworksMod.
danaff37 said:
I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App
Click to expand...
Click to collapse

Can you switch to Clockworkmod after using Amon Ra (via rom manager?)

I've installed Amon Ra on my Nexus One as part of the process to get cyanogen running on it. I did the fastboot oem unlock + flash amon ra + manual update zip process.
Part of the reason was that for some reason I could never boot into clockwork recovery (yes I followed the wiki to the letter), and could only access the standard recovery (which doesn't allow custom roms, says the signature is invalid), the one in blue font. So I flashed amon ra instead and that worked fine.
Can I now flash back to clockwork, and even better, just do it via rom manager? Is there any risk or downside?
This is because I'm reading that amon ra doesn't have a wipe option, and that its better to wipe when you upgrade roms (or is that another fallacy or am I mis interpreting things)
cheers

1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?

LFact said:
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
Click to expand...
Click to collapse
1.) I'm pretty sure I'm booting into amon_ra, it has a nandroid backup option.
My attempt (fail) to install clockwork was exactly the same as how I successfully installed amon: via fastboot flash recovery /path/to/recovery-RA-nexus-v2.1.1-CM.img after unlocking the bootloader. I didn't manually find and delete those files you specified (wouldn't even know how TBH), just followed the Cyanogen wiki.
2.) Cool good to know. I suppose then there's no point in changing really. I was just reading posts and saw it referenced several times. Maybe they were out of date or early on in the piece.
Out of curiosity, is it worth wiping if you're just upgrading between the same version e.g. cyanogen 7.03 to future 7.04?

I much prefer Amon 2.2.1 It is 2.2.1 which is the latest version, not 2.1.1
Stay away from CW 3.+
Amon has a Data/Factory reset wipe for installing new roms, I wipe 5X with it. And, a Dalvik Cache and Cache options. Do those 5X also
If doing nightlies, just wipe the caches
Here is a link to a System Wipe zip you can flash from recovery. That is probably what they were taliking about. CW has that option and Amon will on the next version, I think.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Ken
PS:
Otherwise, like mentioned you will default back to CW even if you flashed 2.2.1 thru Rom Manager on reboot.
Or, you can flash Amon thru fastboot and remove the two scripts mentioned above by LFact

Thanks mate I'll just keep using Amon
So you're saying to wipe I have to flash that zip, there's no way of just wiping it from the menu options before flashing the relevant ROM?
But in any event since I'm on CM7 I'll only be doing minor version bumps for the foreseeable future lol
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?

Sorry wrong thread.
Sent from my PC36100 using Tapatalk

@wintermute000
Yes, flash the system wipe zip from recovery like any zip. Only a few seconds. Hopefully , it will be in next Amon version.
Never an issue with Amon--
Get Quick System from market and use it to boot into recovery--exc app
Then you don't need Rom Mgr or CW--better that way
If you install Amon thru Fastboot or Terminal, it will not be erased on reboots--you still need to delete the two scripts mentioned before any rebooting
See post three on this link--DR has a flash able zip to do it--nandroid always first on this stuff
http://www.nexusoneforum.net/forum/...330-custom-recovery-wont-stick.html#post99962

wintermute000 said:
Thanks mate I'll just keep using Amon
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Click to expand...
Click to collapse
If you type
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
in terminal and it shows error message such as 'no file or directory', it means they were already removed. (I think ROM manager automatically remove them when flashing Clockwork recovery. When I changed to RA recovery, I found out those 2 files were gone)

If you're still curious about changing recovery, you can. I accomplished this yesterday by using Amon to flash a ROM with root access, then I downloaded CwM from the market. Installed the recovery using CwM. It's a simple process as long as you have root. As for going back to Amon, I haven't tried that.

Those files are gone (I didn't do rm, I just did basic ls in those directories). So I guess somehow during my Amon flashing it deleted it. Good to know.
Thanks for your patience all, I think I'll just stick to Amon then if I can just as easily wipe using a zip file if I need to. From what I've read I won't need to wipe anyway if I'm upgrading minor versions (i.e. CM7.03 to say 7.04 or nightly) and that's all I'm interested in doing. Hopefully by the time CM8 comes around I'll have taken the plunge on something dual core!!!
The whole reason I started investigating root/flash etc. was to give my N1 more legs until the price/performance point for the dual core phones gets to a better state, and its more than done that, I'm kicking myself for not doing it earlier. I guess once you're familiar with it then its a piece of cake, but I was reluctant for ages as I didn't want to screw up my PHONE (as opposed to say a tablet).

You don't need to remove those files since after you loaded Amon_RA, you installed CyanogenMod. Those files are used in Stock Android to replace whatever recovery you may have with the stock recovery on every boot.
I would still download the flashable zip that rugmankc linked to for formatting /system. Like I said in the CM forums, it normally isn't necessary when upgrading from minor versions, but sometimes it is the only thing you can do to fix a phone. I figure it is better to download it and never use it, then need it and having a hard time finding it.

+1 bass
@wintermute000,
I still wipe Dalvik Cache and Cache between nightlies. Seemed like the time or two I didn't do it, I had an issue.
The deal on using System Wipe if flashing new rom or if a lot of versions in between is:
When you flash a new rom it wipes system, but backs up some files from old rom first and reinstalls them as part of the new rom. After while things get cluttered, so a system wipe prolongs more serious issues. It has reduced the amount of times I need to do a complete wipe and/or sd card redos.
All Props to Temasek on this stuff
Ken

[Q] Boot loops after working/flashing normally

I keep getting the same problem with various ROM's I flash.
When a flash a ROM I first wipe everything by fastboot, superwipe or a combination of the 2, then I use the wipes in recovery, wipe my ext, and repair ext. Then I proceed to flash the ROM and applicable kernels.
First boot goes fine, and so does consecutive reboots/power offs. After about a week, at a seemingly random time, I reboot, then I get a boot loop.
The last time I got a boot loop, was after a week of using froyo by laszlo and I wiped cache, and dalvik-cache, then rebooted, and boot looped overnight.
Other times it would bootloop just after rebooting the phone (and not wiping anything).
Any tips to prevent this from happening?
Thanks (and sorry if I missed some info)

did you flash any custom mtd files? or have you tried a manual wipe of everything? i usually do the superwipe, than manual wipe in recovery.. wipe everything there is!! data, cache, dalvik cache, sd partition, battery stats and rotate... maybe even re format your sd card... not sure what it could be.. but i did have a slightly similar issue in the past but im always sooo paranoid about bricking so i just un-rooted than started again from scratch lol if you choose to do so this guide may be able to help you! http://forum.xda-developers.com/showthread.php?t=1098899

I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?

HiddenShadow said:
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
Click to expand...
Click to collapse
uhhhmmm maybe try re rooting...? maybe you just got a bad download file and it's acting screwy.. try link i recommended in first comment and feel free to ask me any questions.. im not sure what else would be ausing the problem..

Boot loops
I use to have similar problems. As for the froyo by laszlo, make sure that you have EXT4 partition.

If you still have problems, give me details about your radio and spl.

Well I tried rebooting this evening, no boot loop, but randomly I just lost all my contacts, but it did resync okay later
My radio is 2.22.28.25 and SPL is 1.33.0013d, and no I dont use a custom mtd
Heres a logcat:
http://pastebin.ca/2074938
Edit:
I used to have apps moving to sd-ext automatically, even when there was quite a bit of space on the internal, this isn't happening anymore, so maybe whatever the problem was, its now fixed. Heres what I did:
Formatted the sd card in ubuntu and made a fat32 and ext4 partition (both primary), and put the files I needed to flash while on ubuntu.
Then I flashed the orange-nbh on ezterry's 2708 radio post, rebooted.
After flashing, went into fastboot and did fastboot erase [system, userdata, cache, local, radio, recovery, boot]
Flashed radio, spl, recovery as per instructions
Flashed rom (and kernel if applicable)