Alright, well, I got Haykuro's SPL, and I got a nice hero rom installed, but I figured it was a little too slow for my liking (mostly part of my class 2 SD card I'm sure ) so I decided too go back.
Now thanks to my infinite wisdom (total sarcasm) I have a half bricked phone, on cyans 1.5 recovery, I wiped, repaired ext, and flashed over cyan 4.2.3.1, and now it just hangs on the g1 screen. Did I miss something? I can boot into reovery/fastboot, but I can't seem to get anywhere else.
I searched a little bit, not intensively, so flame me if you feel like it, I probably deserve it. lol
Any help would be greatly appreciated!
Edit 2: I got it flashed to Jesturblurs ROM, IDK how exxactly but anyway, I still want to go back to cyanogen, is there a specific process to do this? Or do I just format everything a flash? I don't want another episode like the one I had when I nearly bricked my phone xD
gotta remove app-s and clear dalvic
you need to format your ext2/3/4 partition.
from recovery you need to go to your console (alt-x) and get into parted.
once in console type
parted /dev/block/mmcblk0
then type
print
this will tell you how much ext2/3/4 partition you have and where it is. You need to WRITE DOWN the start and ending points of that partition. Mine is partitioned in partition 2. To wipe that partition
type
rm 2 (or whatever slot yours is, it SHOULD be 2)
now you have NO ext2/3/4 partition, so we gotta creat it
type
mkpartfs primary ext2 xxxx xxxx (xxxx= the start and ending points you WROTE DOWN)
then type
print (just to be sure everything wrote properly)
if you have all 3 partitions back like normal (almost) we'll exit parted and upgrade the ext2 partition to ext3.
type
quit (this exits parted)
then type
upgrade_fs (this will make your ext2 to ext3)
then type
reboot recovery
then back in recovery,
wipe
repair ext filesystems
wipe (just for good measure)
flash whichever rom you want
if this doesnt work, let me know, we'll try and work around it
you have to flash the htc dev recovery first as well
robkoehler said:
you have to flash the htc dev recovery first as well
Click to expand...
Click to collapse
if this wasnt done, it could cause issues as well.
i assumed it was though, as cyan lays out pretty clear instructions, lol.
sykokenndogg said:
you need to format your ext2/3/4 partition.
from recovery you need to go to your console (alt-x) and get into parted.
once in console type
parted /dev/block/mmcblk0
then type
print
this will tell you how much ext2/3/4 partition you have and where it is. You need to WRITE DOWN the start and ending points of that partition. Mine is partitioned in partition 2. To wipe that partition
type
rm 2 (or whatever slot yours is, it SHOULD be 2)
now you have NO ext2/3/4 partition, so we gotta creat it
type
mkpartfs primary ext2 xxxx xxxx (xxxx= the start and ending points you WROTE DOWN)
then type
print (just to be sure everything wrote properly)
if you have all 3 partitions back like normal (almost) we'll exit parted and upgrade the ext2 partition to ext3.
type
quit (this exits parted)
then type
upgrade_fs (this will make your ext2 to ext3)
then type
reboot recovery
then back in recovery,
wipe
repair ext filesystems
wipe (just for good measure)
flash whichever rom you want
if this doesnt work, let me know, we'll try and work around it
Click to expand...
Click to collapse
Alright, I got my hero rom on there for now, and I think that's because I re-did my SD card this afternoon anyway, just to try random stuff that I research and what not, and your idea sounds pretty solid, I'll try that as soon as cyan makes a new version ( I can't help but love the hero layout ).
Thanks anyway though, appreciate it!
And for robkoehler, I would've done that first, but I'm scared sh*tless because I have Haykuro's SPL and the last thing I want to mess with are radio img's and SPL's for a while, seeing as how easily I could brick it O.O. If you could explain that process in which I won't get bricked, I'll do it and let ya' know.
Thanks for the responses guys
lol, you would be hard pressed to truly "brick" your phone.
thats the bennifit of the recovery image, you really cant.
the spl and most current radio img's are a must if you dont have them, go here;
http://code.google.com/p/sapphire-port-dream/
make sure you flast the radio before the spl, and when you flast the spl, be ready to flash another ROM, because it basically wipes everything clean, you'll have no real rom loaded on your phone.
when your ready to go back to cyan's rom, make sure you READ EVERYTHING and follow his directions to the T. His rom is one of the easier roms to go back and forth to and from, because he makes them that way.
I have everything modded nicely, newest radio/SPL (haykuro's) I was just asking how to go from a hero back down to cyan ( going from cyan to hero was easy as pie ) but the first time I tried, I couldn't use my phone for half the day ( at school no way to access SD card >.> ) I got home and re-flashed hero ( which I'm using for now ) I was just asking if there was an easy way to go back.
From what I've seen so far ( and please correct me if I'm wrong ) is...
Wipe
format ext* partition
Wipe
Flash
Correct? I don't see a need to reflash the radio and what not, but if it's required let me know, thanks!
nope, if you have the most current radio and spl, your good to go!
i think the problem your having is with some hero info still written on your ext partition, which doesnt clear itself, you need to do manually (refer to my above LONG post).
once you clear that ext, rebuild it and upgrade it, you'll have no problem going through the standard procedures to install cyan's rom.
But again, i cannot stress enough, if you do not follow all of cyan's instructions you will continue to have problems. Make sure you flash the stock 1.6 rom so you can get all the google apps cyan cant include anymore as well.
Edit: Got it!
Thanks for all the help guys!
Related
Howdy friends. I recently rooted and installed cyan 4.0.1/teds hero. Everything was going smooth until about 20 min ago. The messaging app kept force closing everytime I would open a thread, so I rebooted. Upon startup, it said my sd card is now damaged. I clicked format, and nothing happened at all. what's the solution? Any help would be appreciated.
i assume your doing auto apps 2 sd with an ext2/3/4 partition? go to recovery and repair ext filesystems. that should fix you up.
I did nothing beyond rooting / cyan / teds hero.
christpuncher said:
I did nothing beyond rooting / cyan / teds hero.
Click to expand...
Click to collapse
k. if you did not partition the sdcard, then take the sdcard out of the g1 (unmount it first in settings), and put it in your pc. try to get the data off of it as best that you can. repartition and format as fat/fat32. put the data back on it, then stick it back in your g1 and see if you can access it, etc.
good luck.
your sd card corrupted, gonna have to reform it, if you install the recovery image from the mytouch that is floating around in the android devolpment forum under new recovery that has an option of reformating your sd card.into 3 partions that would work for you than reflash your rom and theme
here is the link to it. just use in terminal (after putting on root of sdcard also make sure that cyanogen's 1.4 is on the root of your sdcard as well, also for safe keeping have your cm 4.0.x rom on sdcard too)
Code:
su
flash_image recovery /sdcard/recovery-RAv1.2.1G.img
reboot recovery
then once it boots into recovery use the option to format your sdcard into 3 partitions then once it is finished reflash your rom to activate apps2sd, then once it boots up go to the terminal and type
Code:
su
flash_image recovery /sdcard/cm-recovery-1.4.img
that way you will have easily partitioned your sdcard, got apps2sd workning, then return to a recovery image with a recovery console!
I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them
gridlock32404 said:
I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them
Click to expand...
Click to collapse
thats why i included the steps to going back to the 1.4 recovery after using maybe cyanogen will look into this for his next recovery image. i also sent nephron a pm to see if he would like to include it into his partitioning guides
I hope he does make it into 1.5 for us because it just his 1.4 with some great additions and just missing the console
So I partitioned my sd card so i would be able to automatically have apps to sd like the faqs of the cyanogen mods said, but now that i have done the process and partition my sd card 500mb ext, 34mb linux swap, not only has it not worked and the apps are still taking up memory on my phone, it is not noticing the secondary partition in the settings and when i reboot my phone, after the g1 screen and android screen, my phone just goes blank. does anyone have any input? ive wiped and reflashed the rom, now im just clueless. and if it matters, i used Paragon Partition Manager to partition my sd card.
You could re-partition it by using the console in recovery mode.
http://forum.xda-developers.com/showthread.php?t=533731
Look at the 2nd code box and follow it. This is how I did it my first time.
It is really easy.
yea the only thing is it is either saying not found, or error could not stat device dev/block/mmcblk0 no such file or directory. so im stuck i cant even format my card and get back to 8 gigs its sayin 6.06 gigs. ionno im stuck.
Can't you use your partition manager to delete the partitions you made? Then just make 1 partition: fat32, then use the code on the link.
I use paragon Partition mgr. and that is an option to use.
If you partion your card after flashing your rom, then you must reflash your rom for changes to take effect. You have to do that so the system can change the way it runs
Oops sorry, I just reread your first post and saw that I missed that you did reflash. Try going into your recovery console and type ums_enable to mount your card and than try downloading gparted and try to reformat that way, when you are done type ums_disable to unmount. Have you tried taking your sd out when you try to boot up just to see if you can get past, it is possible that your sd corrupted
its ok thank you both, i used the recovery erase all partitions and im gonna read the second box and partition threw the console instead of on the manager.
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
surfereddie said:
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
Click to expand...
Click to collapse
To get it back to just a fat32 partition.... THIS WILL WIPE ALL DATA ON YOUR SDCARD!!!! MAKE A BACKUP OF FAT32 also this will only work with 1.3.1 and up cyanogen recovery image
boot into recovery and go to the recovery console and type
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3 (if you have a linux-swap partition)
print (after the 4th or 5th line there is a number after a line that reads disk size or something and that will be the end value for the next command. Sorry on my g1 now)
mkpartfs primary fat32 0 xxxx(substitue with number above)
quit
reboot recovery
Then reflash your rom. That will clear all partitions of your sdcard and leave you with one whole partition that is fat32.
Ok so i have no clue what to do to get this fixed and what i don't get is i see all these ppl with there G1s and the versions being able to boot without problems. I have done a full format of the SD card. I partition it in parted
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
print (to make sure all went ok)
quit
upgrade_fs
reboot recovery
wipe
repair
apply update.zip
I can do this i dont know how many times and I still get a bootloop. If I flash any build before the ones listed in the title it boots fine. All of Drizzys roms boot fine. I would stay on Drizzys Elite v0.5 if it didn't have the text problems but i need my texting so I hope the new builds fix that. Any ideas how to fix this.
do u have the right spl?
Both my radio and SPL are from here
http://code.google.com/p/sapphire-port-dream/
did you make sure to see that the radio,spl were actually applied, check the versions
it looks like they are. I held the cam and power button and this is what it says
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA100000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
via fastboot and command prompt =
fastboot erase system -w
fastboot erase boot
then use console in recovery mode to format EXT3 partition on SD card
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
In recovery mode "repair ext filesystems"
and then try reflashing rom again!
or just use this command from the console of recovery
mke2fs -j /dev/block/mmcblk0p2
gtrplr71 said:
or just use this command from the console of recovery
mke2fs -j /dev/block/mmcblk0p2
Click to expand...
Click to collapse
lol seems easier that way...
Prod1702 said:
Ok so i have no clue what to do to get this fixed and what i don't get is i see all these ppl with there G1s and the versions being able to boot without problems. I have done a full format of the SD card. I partition it in parted
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
print (to make sure all went ok)
quit
upgrade_fs
reboot recovery
wipe
repair
apply update.zip
I can do this i dont know how many times and I still get a bootloop. If I flash any build before the ones listed in the title it boots fine. All of Drizzys roms boot fine. I would stay on Drizzys Elite v0.5 if it didn't have the text problems but i need my texting so I hope the new builds fix that. Any ideas how to fix this.
Click to expand...
Click to collapse
I can't actually help you with this, but I just wanted to point out that your linux-swap partition should be around ~96MB for the new Hero ROMs to run smoothly.
thanks for the replys guys but that didnt work milesman I still get a bootloop on them. I did find out that i can get JACs 1.6r2b to work but not r2a. So there has to be something that was moved over that makes it so i am having problems booting.
anyone else have any ideas. i am starting to think that there might be some kinda of problem with the build but am not sure what it could be.
wipe your ext3. hero roms need a clear ext3 in order to boot properly.
heres the commands
go to console
hit enter
type this with no quotes "mount -o rw /dev/block/mmcblk0(thats a zero, dont type this) /system/sd hit enter
then type " rm -rf /system/sd/* (yes you need that) hit enter
"reboot recovery"
and that will take you to the recovery screen then apply the update and repair the extensions and your good to go
Oshizzle1991 hmm i dont know how many times i have done this, but like i said. I have formated the whole SD card more then 10 times and repartitioned it so that pretty much wipes my ext3 since the SD car is being formated. Still a no go. I am pretty much giving up right now unless there is something i havent done that wasnt been said in the other posts.
lol might be a dumb question but did you wipe the phone too? you know, alt w? lol. some people forget to do that because they only remember the ext2/3 partitions.
downgrade to RC29/RC7 and start the process over again if you reallllllly want it. That's basically guaranteed to get it to work...
oshizzle1991 yea i have wiped also the commands that milesman has said to use with adb in fastboot erases all data from the phone its self. so that is pretty much wiping everything. I don't really feel like I should have to start the root all over again going back to RC29 since all hero roms work but these newer ones. I am trying JACs 1.8 right now to see if that works but if that doesn't work I think i am going to give up on hero and stick with CM roms.
edit: JACs 1.8 loads fine for me so i don't know what he changed from 1.6r2a and 1.7r2 to 1.8 but all is fine now thanks for all the reapplies. Mod you can close this thread.
ME TOO!!!!!!!
i dont know why, but i had (kind of) the same problem too. all my rooting life, i used JAC's hero roms, then when i tried to use drizzy's or someone else's, it always goes into a bootloop.
Yea i spent hours and hours trying to get them to work. not sure what it is but it seems to be fine now with the 1.8. I am sure it was my erorr somewhere in the line. I have flash roms on my phone over 50 times now and i know how to do all this as if my life depended on it.
Could someone give a brief summary when to use fix_permissions and when to use Repair Ext?
I see it discussed in conjuntion with flashing ROM's sometimes, but it does not seem to be the "standard" (i.e. wipe, format ext, flash...).
Is there a problem with running these on every flash? My sense is that you would run Repair Ext before the Flash and Fix_Permissions after the flash - is that right? Even with Hero Roms or Donut Roms?
qwerty3656 said:
Could someone give a brief summary when to use fix_permissions and when to use Repair Ext?
I see it discussed in conjuntion with flashing ROM's sometimes, but it does not seem to be the "standard" (i.e. wipe, format ext, flash...).
Is there a problem with running these on every flash? My sense is that you would run Repair Ext before the Flash and Fix_Permissions after the flash - is that right? Even with Hero Roms or Donut Roms?
Click to expand...
Click to collapse
fix_permissions is helpful when you're running into a problem where everything is FC'ing on you.
Repair Ext is something I do each time I wipe the partition. It helps keep the integrity of the partition and fixes any problems if there are any. (If it can't repair it'll ask you to type in a command in console(can't remember what it is off the top of my head))
hey, I had Mighty Max's Hero rom installed onto my phone running perfect and I was happy, until today. My phone is randomly rebooting for no reason what so ever. Started yesterday morning with just one reboot and didn't think much of it then when I woke up today it was going crazy and now its just frustrating. So in my frustration I backed up my phone and put a new rom
http://forum.xda-developers.com/showthread.php?t=579674
Now when I flash it goes through everything and then says
Code:
E:Can't chown/mod /system/ (Too many open files)
E:Failure at line 22: set_perm_recursive 0 0 0755 0644
SYSTEM:
Can anyone help me out on this
Specs are in sig.
ok here is what you do, you gotta reformat and repartition your sd card, load a new NON HERO ROM on your sd card, and flash it. that SHOULD do the trick.
i know its a pain in the ass but i have had to do it a couple of times. may i suggest cyanogens rom? its really easy to flash, you just have to flash a .zip before you flash his rom. he has a WIKI. its super easy and pretty stable.
haha oh geeze I did that just before I installed Mighty Max >.<
well, i'll give it a whirl haha.
Thanks for the reply
Edit: It didn't work, I still get errors =/
Did you wipe? Wipe ext?
fix_permissions?
fenixnr said:
Did you wipe? Wipe ext?
fix_permissions?
Click to expand...
Click to collapse
Yes sir, I always do
Wipe Data/Factory
Wipe Ext
Repair Ext
Wipe Data/Factory
install rom
I don't understand why its doing this.
I noticed your using Amon Ra 1.2.3. I was having a problem with the ROM not staying on my phone until I went back to Cyanogen 1.4. Weird any time the phone was plugged in and I rebooted the ROM was gone. Try flashing and after flash unplugging, reboot and get Cyanogen back on there. Just a thought.
Chadzworld said:
I noticed your using Amon Ra 1.2.3. I was having a problem with the ROM not staying on my phone until I went back to Cyanogen 1.4. Weird any time the phone was plugged in and I rebooted the ROM was gone. Try flashing and after flash unplugging, reboot and get Cyanogen back on there. Just a thought.
Click to expand...
Click to collapse
I wasn't able to flash any roms besides a few selected, i wasn't even able to flash Cyanogen's, that even shocked me. It always flashed no matter what.
I reflashed the Mighty Max after thinking that maybe me deleting everything would fix the rom, turns out it doesn't.
When my phone goes idle, it freezes up and restarts from a crash.
I guess its when I get a text, but not all the time though.
CrazyEye said:
I wasn't able to flash any roms besides a few selected, i wasn't even able to flash Cyanogen's, that even shocked me. It always flashed no matter what.
I reflashed the Mighty Max after thinking that maybe me deleting everything would fix the rom, turns out it doesn't.
When my phone goes idle, it freezes up and restarts from a crash.
I guess its when I get a text, but not all the time though.
Click to expand...
Click to collapse
Are you wiping your Ext3 with Amon Ra Recovery 1.2.3? If so, go to recovery drop to console and hit enter, then mkefs2 -j /dev/block/mmcblk0p2 enter. Wait, let it do its thing. Then,
reboot recovery enter. Now flash and proceed to reflash your recovery back to Cyanogen 1.4. If this fails, you may want to go back to RC29. Sounds like alot of work but at least you'll have a functioning phone.
Chadzworld said:
Are you wiping your Ext3 with Amon Ra Recovery 1.2.3? If so, go to recovery drop to console and hit enter, then mkefs2 /dev/block/mmcblk0p2 enter. Wait, let it do its thing. Then,
reboot recovery enter. Now flash and proceed to reflash your recovery back to Cyanogen 1.4. If this fails, you may want to go back to RC29. Sounds like alot of work but at least you'll have a functioning phone.
Click to expand...
Click to collapse
I tried typing the first command and it wouldn't work. Maybe you typo-ed it?
mkefs2?
Can I use this code to do the same?
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# rm -rf /system/sd/*
# reboot recovery
./fastboot erase recovery
./fastboot flash recovery *name of whatever you named the Cyanogen recovery image*
./fastboot reboot
Click to expand...
Click to collapse
The reason I added "*name of whatever you named the Cyanogen recovery image*" is because I tried flashing Amon Ra's 1.2.3 the same way using the default name but Terminal said I couldn't flash, so I just named it "recoveryimage.img."
blackknightavalon said:
The reason I added "*name of whatever you named the Cyanogen recovery image*" is because I tried flashing Amon Ra's 1.2.3 the same way using the default name but Terminal said I couldn't flash, so I just named it "recoveryimage.img."
Click to expand...
Click to collapse
Hmm I did that as well
in console I put
Code:
cd C:\
fastboot flash recovery cm.img (cm.img is what i named the Cyanogen recovery)
fastboot reboot
It still gives me the same error when trying to install most roms, even in the CM rom.
REFLASH THE HAYKURO "DEATH/DANGER" spl!
it'll repartition (also wipe) your phone's internal phone memory if you haven't already done so,
it's usually the cause since some roms are too big and leave residual files
next stop to ensure a clean install is to just do a data/cache wipe from the recovery menu
now you wanna either wipe/format your ext partition or just repartition your entire sd card for the heck of it
then repair ext partition,
then wipe again
then flash flash flash
phamous said:
REFLASH THE HAYKURO "DEATH/DANGER" spl!
it'll repartition (also wipe) your phone's internal phone memory if you haven't already done so,
it's usually the cause since some roms are too big and leave residual files
next stop to ensure a clean install is to just do a data/cache wipe from the recovery menu
now you wanna either wipe/format your ext partition or just repartition your entire sd card for the heck of it
then repair ext partition,
then wipe again
then flash flash flash
Click to expand...
Click to collapse
Is this the death / danger spl?
http://code.google.com/p/sapphire-port-dream/
if it is, I already have it =/
yeah that's the one, but DO IT AGAIN anyways
because it also cleans out the system.
Do I need to flash the radio again as well or just the SPL?
most times when trouble shooting these things, you'd want to repeat steps to ensure that what you're doing and what you have done at the moment aren't causing your problems, only by redo-ing these steps can you validate what's a problem and what's not, and in the process you'll most likely find a solution!
so try repartitioning, wiping, and reflashing the radio and spl, and finally reflashing your rom
just reflash both
radio, then spl
you wanna make sure everything's in good order.
sometimes if all these things don't work, it might just be your sd card has crapped out on you
and its time to get a new one, sd cards and the flash memory on them are limited to however many read and write cycles and if you've been using linux swap on them, then you're using your sd card as RAM pretty much.
phamous said:
just reflash both
radio, then spl
you wanna make sure everything's in good order.
sometimes if all these things don't work, it might just be your sd card has crapped out on you
and its time to get a new one, sd cards and the flash memory on them are limited to however many read and write cycles and if you've been using linux swap on them, then you're using your sd card as RAM pretty much.
Click to expand...
Click to collapse
I haven't been using my SD card as ext for long though.
I did what you said and it still says the same error.
I even went ahead and installed a new recovery through fastboot to Cyanogen.
EDIT:
I brought the phone back to RC33 and rerooted then upgraded recovery CM 1.3 and Haykuro Death SPL and Latest Radio and I still get the error code.....
I'm going to break this phone >:-(
SenseHero writes but doesn't boot, any reason why?
Sorry about that, check my OP post forgot the -j.
Chadzworld said:
Sorry about that, check my OP post forgot the -j.
Click to expand...
Click to collapse
it says
Code:
mkefs2 : not found