Hi XDA team,
I got this problem with my T-Mobile I recently installed a custom rom BiffMod 2.1 and the installation was fine. But now when I boot the system enters and it start "Preparing the SD Card" and suddenly the phone shuts down...
Thanks for your help
crossmonk said:
Hi XDA team,
I got this problem with my T-Mobile I recently installed a custom rom BiffMod 2.1 and the installation was fine. But now when I boot the system enters and it start "Preparing the SD Card" and suddenly the phone shuts down...
Thanks for your help
Click to expand...
Click to collapse
I don't know how much I can do to help you, but I have installed almost every rom there is available for the G1 on these forums, lol. You need to make sure your spl and radio are compatible with your rom, then you need to make sure if your going to setup for an ext partition and swap that you do and you switch to using them through the settings. Usually if your spl and radio are the wrong ones it will just boot loop and wont even get to where your at. I would also try formatting data/factory reset in the custom recovery, then clearing cache, then Dalvik cache, and wiping ext partition. Then going into sd partition and repairing it if it was already setup how you need it, then select power off and wait a second and reboot back into recovery. From there download Ohsaka wipe and flash it like you would a rom through the recovery, and then power off once more and reboot back into recovery. Assuming your sd card is not messed up, and your spl and radio are correct flash the rom again and hopefully you should be without errors.
Related
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.
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
Here's the scenario:
Been running CM4.2.15.1 with Amon_RA's recovery v1.6.2 & default(?) SPL.
Nandroid backup.
Wiped data/factory reset.
Tried to flash OpenEclair1.2.2. Got error:
Code:
E: Can't symlink /system/xbin/bb/dirname
E: FAilure at line 73:
symlink /system/xbin/busybox SYSTEM:xbin/bb/dirname
So I wiped again and tried to Nandroid restore.
After "restore," I keep getting stuck on the "T-Mobile G1" screen after waiting 10ish minutes. Any suggestions? Am I not waiting long enough?
Did I "brick" my phone?
Well, you wiped to flash OpenEclair which currently requires the Danger spl (or you can create proper symlinks). Since you wiped and then tried to flash a rom onto your phone which formats the /system partition (here Android resides), I'm thinking you should reflash Cyanogen (after flashing the Htc Recovery of course).
So when I did the factory reset, that means I got rid of the "htc recovery"? The Amon_RA recovery is still working for me though.
EDIT:
So I've wiped again and tried to reflash the CM but again it's still stuck at the "G1" screen. Should I wipe dalvik? I don't understand why my nandroid restore isn't working..
atolar said:
So when I did the factory reset, that means I got rid of the "htc recovery"? The Amon_RA recovery is still working for me though.
EDIT:
So I've wiped again and tried to reflash the CM but again it's still stuck at the "G1" screen. Should I wipe dalvik? I don't understand why my nandroid restore isn't working..
Click to expand...
Click to collapse
The HTC recovery, as in the thing you flashed before you first flashed Cyanogen. I have always done this and I'm pretty sire that Cyanogen does not boot without having flashed the HTC recovery on a new flash (As in coming from another rom)
I can't load my phone to mount my sd card to put those files onto my phone..? I've been flashing roms all the time but I feel like a noob right now.
EDIT:
Oh it's a simple "push". Sorry, freaking out here is all.
EDIT:
successs!! turns out I needed to flash the "base" as described in http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Thank you so much for your help!
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)
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.