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.

Stuck on g1 logo

I followed the unlockr guide and did everything and now I am stuck on the g1 screen. I checked my radio and spl are the right number. I wiped everything then re-partitioned then re-updated it with the lastest rom and still stuck. Can anyone give me advice?

If you can get into recovery of bootloader than you aren't bricked.

I know it isn't bricked but it is still temporarily useless. I really want a custom ROM and I wish I knew why this thing was messing up.

You could always reflash using the .nbh file then go through the steps again =]

start from step 1 again

The only thing I could think of is when I updated the .spl I didn't wipe. Whenever I booted into the recovery (before using amon ra's, just the stock recovery) I didn't wipe the system before updating .spl. Whenever I wiped and tried to update .spl it would give me an error (I think the E:signature (5 files)). Anyways I will retry! Thanks for your help!

Custom Roms will not boot! Please Help.

Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic

JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.

I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.

Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!

JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away

[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)

[Q] Updated to CM from Stock Need Help Restoring

I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.

Jeklund said:
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Click to expand...
Click to collapse
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.

ImSoBored said:
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
Click to expand...
Click to collapse
Agreed... reboot into recovery and clear cache and dalvik cache and then reboot.

So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.

Jeklund said:
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Click to expand...
Click to collapse
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.

ImSoBored said:
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
Click to expand...
Click to collapse
That did it, for some reason I had this thought in my head I had to flash cwm right away and clear stuff that way. Once odin finished I went in recovery and wiped data and cache through the stock recovery and it booted right up. Thanks for the help really appreciate it.