Database Develop

Installing Cyanogen

Ive tried installing Cyanogen about 10 times on my G1 and it always ends up the same no matter what guide i use. Ive tried so many different "stable" versions of Cyanogen i dont even know where to begin. I downgrade to RC29 fine, Install the radio update, and gain root access. Then i boot into the Home+Power menu and install Cyanogen through the Alt+S install prompt. Then the phone reboots and either hangs at the G1 screen or loads to the Cyanogen (Blue text) Android screen and hangs there and the screen eventually goes black.
Another time i installed a more recent version of Cyanogen, After about 5 minutes of sitting at the android screen it would load, but all the applications would instantly crash and i would have no choice but to turn the phone off. Does anyone have any idea what im doing wrong. Ive been searching every android forum for the past 4 days and cant seem to find a solution to solve this problem.

I don't know if this will work since you don't have a Cyanogen ROM to begin with, but you might try the Cyanogen updater app in the market. It is unbelievably easy and does everything for you from downloading the rom to rebooting into recovery and automatically flashing it.

Did you partition you sd? I am pretty sure any cyan mod requires a fat32 and ext2 oartition for the auto apps2sd.

crpercodani said:
Did you partition you sd? I am pretty sure any cyan mod requires a fat32 and ext2 oartition for the auto apps2sd.
Click to expand...
Click to collapse
Nah, it works fine without an ext2 partition, once you create one it will copy your apps over and set it up on boot. It does seem to have issues when the partitioning isn't right though. I've found doing partitioning in recovery console most reliable.

I have the same problem and to me it DOes have issue when the partitioning isnt right cuz I failed the partition... in console it just didnt work, and now everytime I try to reinstall the rom it turn black after the blue android logo...and from there Im stuck, I just dont know what to do to make it work...

have you tried checking the md5sum to see if you got a bad download. i got one once and nothing would work

MD5 sum matches up fine. Is there anything else i should be adding to this procedure?
http://forum.xda-developers.com/showthread.php?t=548924
I do this guide word for word and end up with that black screen i was describing before every time.
Install CyanogenMOD 4.0.1 (Stable), Right after that section of the guide when i reboot my phone, i get the black screen after the android logo sits for about 5-10 minutes and i cant continue with the guide any further although im assuming the other guides after this are optional.

have you tried the latest 4.0.4 rom?

Yessir i have. Ive tried 4.0.2 and older versions as well. No luck just different problems.

Can we install another rom other than cyanogen on the cyanogen recovery? cuz if so ill try to install a rom that dont have app2sd just to see...
Ive find my problem now my cyanogen work...it was my sd card that is not well partitioned even tough I reformated it to fat32 it just wont work..so after installin the cyanogen rom i just removed the sd card and it worked fine...so I guess ill go buy a already partitioned sdcard cuz im havin problem with theses...

I can't believe that no one has said this to the op but did you wipe before flashing

yea wiped... but now how to I proceed? I need an sd card...
If I partition my sd card outside of the cellphone and put it in, will cynogen rom will recognize that app2sd is possible or I will need to reinstall the rom?

I was suggesting wiping to the op mesh, forken, yes you can partion the card outside the phone as long as you have a fat32 partion on there since it is the only file type that the phone will recongize as a non operating storage place for your roms and other files

partitioning is so simple, just use console and follow the guides. Make sure you know what size your card is and you will be fine. You can't buy a partitioned sd card so your gonna have to figure it out.
once in recovery goto console
hit enter after each line
parted /dev/block/mmcblk0
print (this will give you your sd size in mb)
mkpartfs primary fat32 0 xxxx (xxxx is the size you get in print MINUS 512)
mkpartfs primary ext2 xxxx xxxx (first xxxx is the size of your sd MINUS 512, like we just did. 2ND xxxx is the full size of your sd)
then goto recovery and click fix/repair ext filesystems.

well yes you can buy a pre partion, theres a android website where you can buy pre partition sd card anyway you like it...
the problem is that my sd card is bugged now I think I need to fix it before trying to partition it again...cuz it wrongly partitioned..

Really you can buy pre partion cards, I think I just found my next scheme to make money since I can use the partion editor in ubuntu in 3 minutes so there is 60 minutes in an hour, so that's 20 cards an hour and I am lazy so 5 cards a day. How much is the mark up on these pre partion cards, I can out do them by 50 cents, make a link to my website for them in my sig and prob make a little profit, yay, go ignorance and laziness

ahah ill post it...
Do you know if I can fix a wrongly partitioned sd card... with just trying to partition it correctly? or I need to fix it first?

Sure, wipe it completely clean, it's called reformating. Make new partions, whichever way you are using for partion does not seem to be working for you so I would suggest trying to find another way, try googling gparted like I told you before to do and give that a try

just format the card to FAT32. You don't need an ext partition to run cyanogen, you just need it if you want apps2sd. And do a low level (not quick) format.

ive tried to reformat to fat32 and it does the same thing...

Cant get past the G1 Screen

Hi everyone,
I just recently bought an Unlocked g1 and tried to Load JacHero ROM on it .
the guide i was following was this
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&message.id=13411#M13411
Briefly
I unrooted frst and then install Android 1.6 Rooted version. and then set the recovery image by using the flash_image to cm-recovery-1.4.img. Then i copied and successfully installed the Hero ROM. it was working great and perfectly. after a few days i wanted to go back to Rooted Android 1.6. I repeated the same steps. i had a working copy of Android 1.6 Dev Phone . by updati9ng to JF - 1.5. It was working a .ok. then i wanted to partition my meme card. I waent into Terminal. Set the flash-Image again. Rebooted to recovery mode. went into console. then i ran gparted. and partitioned my 2 gb (1873 MB) card.
here are the commands i ran
mkpartfs primary fat32 0 1297
mkpartfs primary ext2 1297 1809
mkpartfs primary linux-swap 1809 1873
then i did upgarde_fs
but after this step my G1 is stuck at the G1 Logo. I cannot go into recovery mode or fastmode . ?? If anyone can point me to what should I do. ??
I tried unbricking processes as when i googled. but that too requires me to go to recovery mode . Waiting anxiously..

do you have access to the bootloader? (with phone powered off, press and hold camera button+power button till the splash screen is displayed) If you can access that, I would poke around the threads for more info, your phone is not bricked. Otherwise, you may have a new paperweight

Sounds obvious, but have you tried removing or replacing the sdcard and booting into recovery? You brick your phone by partitioning an sdcard, but i suppose the card could be corrupted and preventing startup.. i dont know, im clutching at straws.
To my knowledge the only way to fully brick a g1 is the infamous spl.

I cant access boot loader ...
maybe my method for reverting back to Android 1.6 wasn't correct.
the complete steps for installing Stock 1.6 -> JacHERO -> Android 1.6 Rooted were as below
after i got JacHERO installed i did the following, I installed DREAMimg.nbh again.
ww.androidctivity.com/root/root.apk automatically downloaded the SPL and Radio and i installed them after rebooting. after that i downloaded the JV v1.5 ADP and installed it .. worked perfectly. next i thought (maybe i made a mistake) that im going to partition the sd card by following the method
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&message.id=13411#M13411
and gave the following commands.
mkpartfs primary fat32 0 1297
mkpartfs primary ext2 1297 1809
mkpartfs primary linux-swap 1809-1873
and then quit and upgrade_fs
and then rebooted it. it got stuck. then i thought maybee the partition tabel is incorrect so i formatted on XP ,but it didnt work, it doesnt even run without a SDCARD. only problem is i cant get into END + HOME or END + CAMERA mode.

lynx_hanan said:
I cant access boot loader ...
maybe my method for reverting back to Android 1.6 wasn't correct.
the complete steps for installing Stock 1.6 -> JacHERO -> Android 1.6 Rooted were as below
after i got JacHERO installed i did the following, I installed DREAMimg.nbh again.
ww.androidctivity.com/root/root.apk automatically downloaded the SPL and Radio and i installed them after rebooting. after that i downloaded the JV v1.5 ADP and installed it .. worked perfectly. next i thought (maybe i made a mistake) that im going to partition the sd card by following the method
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&message.id=13411#M13411
and gave the following commands.
mkpartfs primary fat32 0 1297
mkpartfs primary ext2 1297 1809
mkpartfs primary linux-swap 1809-1873
and then quit and upgrade_fs
and then rebooted it. it got stuck. then i thought maybee the partition tabel is incorrect so i formatted on XP ,but it didnt work, it doesnt even run without a SDCARD. only problem is i cant get into END + HOME or END + CAMERA mode.
Click to expand...
Click to collapse
If you were doing all those steps every time, it's entirely possible you've ended up flashing an old radio with the new spl, in which case, you're bricked. Once you had the rooted recovery image installed, there was no need to ever mess with spl's and radios again.
If you really can't get into recovery, then there's nothing you can do to fix it. Another brick in a very large pile. Sorry.

Yeah but i had successfully reverted back to Android 1.6 (though not the proper was as you just told ). I had a working roooted 1.6 which i was using for quite some time. It wasnt hanging when i rebooted. ? .. it was after all this that i decided to Partition the sdcard. what you are saying is correct but i feel result of that should have been instantaneous ????? when i did reboot recovery from terminal and went into console and did these steps it actually happened

lynx_hanan said:
Yeah but i had successfully reverted back to Android 1.6 (though not the proper was as you just told ). I had a working roooted 1.6 which i was using for quite some time. It wasnt hanging when i rebooted. ? .. it was after all this that i decided to Partition the sdcard. what you are saying is correct but i feel result of that should have been instantaneous ????? when i did reboot recovery from terminal and went into console and did these steps it actually happened
Click to expand...
Click to collapse
Well if that's the case I can't explain it.. If you went straight into the recovery console from a working installation and didn't flash anything before using parted, I have no idea how you could've bricked..
You could try installing the android SDK on your pc, run ddms from the tools folder, then connect your phone by usb and check the logs to see if anything is happening. If you get an output in the logs, post it here and we might be able to suggest something.. If there's no output at all then you are probably bricked.

@goldenarmzz .. its not being detected. i think its bricked. .. Thanks for the cooperation guys.
BTW is there anyway i could seel this or make some money for my new fone maybe get it repaired or something. Its not in warranty.????

Problems after apps to SD EXT2 format

Hi
I have some problems with my Dream now after an format fore EXT2 so I can use apps to sd.
I have CyanogenMod 4.0.4
Iv'e used an guide and console for formating my SD card 8gb class 6.
I've made an 7.2gb fat32
700mb ext2
50mb linux swap
After that I converted the ext2 to ext4, checked everything with print and it was ok.
Than when I've rebootet my phone it woudnt start up, it came to the android in blue, and that blinked some and than the screen went black.
So my plan was to upgrade the 4.0.4 to 4.2.5 anyway so I did that.
My phone was an 32B so I used the HTC_ADP_1.6_DRC83_rooted_base.zip
Everything went great with that, but when I tried restarting the problem was still there...
Dont know what to do know?
Remove the ext4 partition?

Try restoring your memory card to original and then try to partition it again.

Ive tried to restore my memory card, no help.
Ive tried to boot the phone with no memorycard, still no go...
Dont know what to try anymore..

1) Format the entire card as fat32
2) add other partitions
3) Wipe from recovery
4) Flash your rom
Also this sub forum is for development, which this clearly isn't.

Ok sry i thought this was the place to ask with this.
I got the phone booting up with 4.2.5 and it worked great.
All my programs waws gone so I need to install them again, but no worry.
So I now tried to format the memorycard again, looks like it didnt work again and im at my problem again...
Now it hangs on the T-mobile screen, so I guess out with the battery and try an reboot before I start all over again...
Maby I'm not supposed to have programs on my SD?

make sure you partition properly.
fat>ext>swap
you can install amon_RA's recovery and let that partition your card for you

Hi.
Ive sendt my phone back to originale software, and than upgraded again, and it seems like it's 4.2.5 and the ext partition that is the problem.
If I change SD card to one without the ext partition it's no problem to start after an whipe..
I've tried reinstalling 4.2.5 but no luck, maby I shall trie an ext3 insted of ext4?
Yes have followed the guide on the pratition, and Fat32, EXT than swap

[SOLVED; broken SD] ADP1 will not boot with any ext partition present on SD

Hi all,
A couple of days ago i decided to give my phone a completely fresh start, looking back i wish i never did. Here's my problem:
As soon as i create any ext partition on my SD card the phone will not boot past the splash screen. When i remove the partition all is well but i really love APPS2SD so this is not an option for me.
Here's some more info on my setup;
ADP1 (PVT 32B ENG S-OFF)
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Running the latest cyanogen's recovery
Here's what i already tried (i know its a long read but please hang in there);
I formatted the SD card using a HTC Magic (as stated on cyanogens wiki that formatting on android 1.6 is preferred). Put signed-dream_devphone_userdebug-ota-14721.zip and update-cm-4.2.13-signed.zip on the SD and followed instruction to flash both in correct sequence. This works flawlessly, booting up with no issues at all. I then turned the phone off and put the microSD in my PC.
I then proceeded to shrink the FAT32 partition (Ubuntu GParted) to make room for the ext partition but not created this partition just yet for testing purposes. Put the SD card back in the phone and i boots up like a dream (no pun intended) running smooth as ever so the shrunk partition is still working great! Once again turned the phone off and put the SD back in my PC to create the ext partition and that's where the problems begin; as soon as ANY ext partition is present (i tried ext2, ext3 and ext4) the phone will not get past the splash screen!!
As soon as i remove this ext partition all works great once again! So then i figured i'd probably have to flash everything from scratch with the ext partition present but this gives me the same results every single time with ext2/3/4 partition present. I even gave Amon-RA's recovery a try with this same process, and even tried to create the partitions using that. No luck, same results every single time.
Now in the past i always used APPS2SD with a ext2 partition without any problems but now i am unable to just get it back to work!
I have a feeling that something goes all messed up somewhere in creating the ext partition but i just cant put my finger on it where, i've ben on this for 3 days now so any input would be very much appreciated!

maarten82 said:
Hi all,
A couple of days ago i decided to give my phone a completely fresh start, looking back i wish i never did. Here's my problem:
As soon as i create any ext partition on my SD card the phone will not boot past the splash screen. When i remove the partition all is well but i really love APPS2SD so this is not an option for me.
Here's some more info on my setup;
ADP1 (PVT 32B ENG S-OFF)
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Running the latest cyanogen's recovery
Here's what i already tried (i know its a long read but please hang in there);
I formatted the SD card using a HTC Magic (as stated on cyanogens wiki that formatting on android 1.6 is preferred). Put signed-dream_devphone_userdebug-ota-14721.zip and update-cm-4.2.13-signed.zip on the SD and followed instruction to flash both in correct sequence. This works flawlessly, booting up with no issues at all. I then turned the phone off and put the microSD in my PC.
I then proceeded to shrink the FAT32 partition (Ubuntu GParted) to make room for the ext partition but not created this partition just yet for testing purposes. Put the SD card back in the phone and i boots up like a dream (no pun intended) running smooth as ever so the shrunk partition is still working great! Once again turned the phone off and put the SD back in my PC to create the ext partition and that's where the problems begin; as soon as ANY ext partition is present (i tried ext2, ext3 and ext4) the phone will not get past the splash screen!!
As soon as i remove this ext partition all works great once again! So then i figured i'd probably have to flash everything from scratch with the ext partition present but this gives me the same results every single time with ext2/3/4 partition present. I even gave Amon-RA's recovery a try with this same process, and even tried to create the partitions using that. No luck, same results every single time.
Now in the past i always used APPS2SD with a ext2 partition without any problems but now i am unable to just get it back to work!
I have a feeling that something goes all messed up somewhere in creating the ext partition but i just cant put my finger on it where, i've ben on this for 3 days now so any input would be very much appreciated!
Click to expand...
Click to collapse
Your sd could be going bad.
Which version of Amon_Ra are you using?Try repartitioning your sdcard and try another rom like Super-D thats much faster and see where that gets you.

Ace42 said:
Your sd could be going bad.
Which version of Amon_Ra are you using?Try repartitioning your sdcard and try another rom like Super-D thats much faster and see where that gets you.
Click to expand...
Click to collapse
Thank you for the very fast reply!
I'ver tried repartitioning multiple times with different partition sizes and i used the latest of Amon_RA's work (dream v1.5.2).
I will give Super-D a try just for kicks..
And before i forget, i also tried flashing with the defanged DRC83 base and older versions of cyanogens just to make sure without any luck. I also always double-check the MD5sums on all the files that get on my phone!

Ace42 said:
Your sd could be going bad.
Click to expand...
Click to collapse
Well my friend, your first hunch appears to be correct! I've done some small experiments with the card - copying large files back/forth and checking integrity - and it appears that the card is indeed messed up! That's just one of those things i never seem to come up with myself!
I just came back from the store to buy a new cheap card, and even tho its only a class 2 everything formatted and installed without any problems including the APPS2SD! So i guess ill have to order myself a new card, bummer those things only last a year and a half as it appears, i guess ill just have to keep the receipt and get myself a new one under warranty every now and then......
Thanks a million for pointing me in the right direction!

maarten82 said:
Well my friend, your first hunch appears to be correct! I've done some small experiments with the card - copying large files back/forth and checking integrity - and it appears that the card is indeed messed up! That's just one of those things i never seem to come up with myself!
I just came back from the store to buy a new cheap card, and even tho its only a class 2 everything formatted and installed without any problems including the APPS2SD! So i guess ill have to order myself a new card, bummer those things only last a year and a half as it appears, i guess ill just have to keep the receipt and get myself a new one under warranty every now and then......
Thanks a million for pointing me in the right direction!
Click to expand...
Click to collapse
I had that happen to my 8Gb, had it for about a year i think.

did you use 1.6 or did you format from Amon? Also, is i possible not to load "signed-dream_devphone_userdebug-ota-14721.zip". And just go download everything again from the market? Someone said I don't need that file? Where they trying to brick me?

surfereddie said:
did you use 1.6 or did you format from Amon? Also, is i possible not to load "signed-dream_devphone_userdebug-ota-14721.zip". And just go download everything again from the market? Someone said I don't need that file? Where they trying to brick me?
Click to expand...
Click to collapse
I just formatted the card in a cardreader using Gparted, a FAT32 partition for the whole size of the card minus space for the EXT and swap partition (in my case 512+32Mb resp.). Don't know if it is mandatory but i also flagged the FAT32 boot and lba and it works brilliant for me!
I indeed used the devphone OTA update, but only do this is you have a ADP1... I guess you could probably mess up a normal G1 with that rom. Just follow instructions! Pick the correct 1.6 base rom for your phone (either defanged or the devphone version), flash it and without a reboot flash the latest cyanogens rom over the base, its all explained quite idiot-proof on cyanogens wiki.

error: /dev/block/mmcblk0: unrecognised disk label

This error (error: /dev/block/mmcblk0: unrecognised disk label) is plaguing my life and I don't know how to get around it. I have scoured the net for two days and I only find other people asking about the error with no real solutions offered.
Basically, I am trying to set up my 16gb SD to work on my rooted G1 recently flashed to CyanogenMod 5.0.7-test2. I have tried running with all three current recovery builds (the RA build flat out states it doesn't work with apps2sd so I have gone with Cyanogen's 1.4)
Using parted in console and following all of the standard partition steps (found all over the web) I was previously able to get the three partitions set up with RA's recovery 1.6.2, however the apps2sd didn't work and no one seemed to have a work around to get it to work, so I started from scratch.
Now with Cyanogen's 1.4 recovery, I can't get the ext2 partition in at all. I get the above error every time. What am I doing wrong? What can I do to get this working? Please help as I know there are dozens of others with this issue and I have seen no solutions for Android. (Did find something on a Linux forum, but waaaayyyy over my head.)
Thanks,
JS

after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?

after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?
I did not. At what point would I do that? This is what I did, (where would the "P(#)" go?
Boot into recovery (Power Button + Home)
Go to console and hit Enter
Type ‘Parted /dev/block/mmcblk0’
Type ‘print’ to check existing partitions and storage size
If any partitions exist remove by typing ‘rm 1’ for first, ‘rm 2’ for second…
For new partitions it will be total 16384 (16GB) minus 96mb for swap minus 500mb for ext3 (15788, 16288, 16384)
Type ‘mkpartfs primary fat32 0 15776’
Type ‘mkpartfs primary ext2 15776 16288’
Type ‘mkpartfs primary swap-linux 16288 16384’
Type 'print' to see changes
Type 'quit' to leave parted
Type upgrade_fs to move ext2 to ext3
Reboot
I have this working flawlessly on my 2GB card, so it must be a hardware issue.

Just_s said:
after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?
I did not. At what point would I do that? This is what I did, (where would the "P(#)" go?
Boot into recovery (Power Button + Home)
Go to console and hit Enter
Type ‘Parted /dev/block/mmcblk0’
Type ‘print’ to check existing partitions and storage size
If any partitions exist remove by typing ‘rm 1’ for first, ‘rm 2’ for second…
For new partitions it will be total 16384 (16GB) minus 96mb for swap minus 500mb for ext3 (15788, 16288, 16384)
Type ‘mkpartfs primary fat32 0 15776’
Type ‘mkpartfs primary ext2 15776 16288’
Type ‘mkpartfs primary swap-linux 16288 16384’
Type 'print' to see changes
Type 'quit' to leave parted
Type upgrade_fs to move ext2 to ext3
Reboot
I have this working flawlessly on my 2GB card, so it must be a hardware issue.
Click to expand...
Click to collapse
why don't you just use amon_ras recovery to partition sdcard.
also, cyanogen's recovery will be updated way less than amon_ras - if it's ever updated again. either do amon_ras or clockwork.

why don't you just use amon_ras recovery to partition sdcard
I actually started with AmonRa's and I love it, but it says it is not compatible with apps2sd which is pretty much the main reason I got an Android phone, so tat was out for me. I posted about a half dozen queries on other sites asking if anyone could tell me how to get apps2sd working if I was running AmonRa 1.6.2 and I received no responses. If you know how that could work, I would be extremely elated and grateful!!
Ideally, I would get to run CyanogenMod 5.0.7test2 on my G1 running Amon Ra recover 1.6.2 with my 16GB card and all of my apps stored on the card via apps2sd. But I couldn't get it to work.
Right now, I have CyanogenMod 5.0.7test2 on my G1 running CM recover 1.4 with my 2GB card and all of my apps stored on the card via apps2sd and it is working flawlessly, just not much room left for media files.
BTW, I appreciate the advice, I haven't had much luck in any of the forums.

apps2sd has nothing to do with the recovery image, apps2sd has to do with the ROM itself. When you hear that, it's because cyanogen moved the place for apps2sd or something, which honestly changed nothing as long as you still partition your sdcard. It technically DID, but that's more under-the-hood. You just can't wipe ext partition, which you can do with a simple adb command. I personally don't know it as I've never used apps2sd.
Cyanogen's recovery is pretty old, and like I said, he probably won't update it. Also, don't worry about not being able to wipe your ext partition. Amon_RA will roll an update around soon enough to fix this and you won't have to type the code in yourself anymore. Well, maybe. I'm not him so I can't promise you that, but I'm sure he will.

Did you solve it?
Did you figure out how to get around the unrecognized disk label problem?

i had the same problem, for me was helpfully
format sd card and partition again in cwm