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
Related
I wiped my system because there was something wrong with the hero theme i was running. i booted back up and after i booted into the phone, i cant boot into the home screen, it boots for some reason into lock 2.0 and i didnt choose that as a default, why is it doing this? im running the dude's cupcake beta 12 and app2sd
Don't know...Never heard that occur before. I suggest a reflash of the ROM or even a e2fsck of the filesystems.
i hate when this stuff happens at work where my computer blocks me from plugging in something to the usb port so i have to wait until i leave
alritewhadeva said:
Don't know...Never heard that occur before. I suggest a reflash of the ROM or even a e2fsck of the filesystems.
Click to expand...
Click to collapse
e2sfck? whats that?
Checking of EXT filesystems...Do you have cyanogen's latest recovery? 1.3.1?
no, i couldnt figure out how to install it, but i believe i put it in the appropriate place on the sd card to install it, can i put it up through the recovery console?
Depends, did you download the .zip version, or the .img version? If you have the .zip .. Go to recovery console and:
Code:
mount /sdcard
cd /sdcard
mv cm-recovery-1.3.1-signed.zip update.zip
recovery
Then you can try flashing it. CM Recovery also lets you mount your phone via USB, so if you need to reflash and don't have an image on your phone, drop to the recovery and run
Code:
ums_enable
Copy file to your card, eject on the PC
ums_disable
recovery
If you downloaded the .img version of the recovery, I'm not sure that it can be flashed without getting into the main OS. What happens when you try to unlock Lock 2.0? You didn't really say..
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
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!
Ok so last night when i flashed ace42's hero everything was going ok wasnt a slow hero but i wanted to go back to super D. My dumbasz forgot to nandroid and when i try to flash an rom it stays on the 1st splash screen i could acces recovery and bootloader so its not a hard brick. Ive tried every thing form reflashing the radio and spl to the bootloader and back. Shoooot i even tried using DREAIMG.Nbh and the stock cupcake but still nothing nada. Any ideas what could be wrong? Im using amons recovery 1.6.2 btw
did you try wiping? Usually after you do a nandroid/switchrom/bart it's best to wipe before you flash.
Try This:
Code:
Wipe Data/Factory Reset
Wipe Dalvik Cache
Wipe Ext Partition
Repair EXT
Flash New Rom
See if that doesn't help.
....
nolimit78 said:
did you try wiping? Usually after you do a nandroid/switchrom/bart it's best to wipe before you flash.
Try This:
Code:
Wipe Data/Factory Reset
Wipe Dalvik Cache
Wipe Ext Partition
Repair EXT
Flash New Rom
See if that doesn't help.
Click to expand...
Click to collapse
Yes ive tried all that sadly no success=/ it says error wipe ext via console or repair ext via console im looost
Go to recovery
Console, format your sdcard and repartition
then put the update file
and flash the rom.
Ugh
peshal said:
Go to recovery
Console, format your sdcard and repartition
then put the update file
and flash the rom.
Click to expand...
Click to collapse
Ive tried all of that itll hang on the g1 screen for hours
Alex530 said:
Ive tried all of that itll hang on the g1 screen for hours
Click to expand...
Click to collapse
Can you fastboot the phone? If you can do that then I recommend flashing through fastboot a boot and system image of what was previously working.
Just a thought, but did you try flashing the HTC recovery first?
I just had this same problem. I did a complete wipe. then flashed DRC83_base_defanged.zip (found here: http://www.mediafire.com/?nymkxjmndzd)when it was done flashing I flashed cyanogens latest with no reboot in between. I am now back up and running.
Backup the contents of your FAT partition on your SDCARD to your computer.
Reformat you SDCARD.
Repartition the SDCARD using Amon_RA's recovery (ext3 or ext4 partiton).
Reboot back into recovery.
Wipe your data/dalvik-cache.
Restore all of your FAT content originally saved from your SDCARD.
flash the DRC83_base_defanged.zip and then CM rom immediately following.
plug your device into your computer (if it's not there already) and use ddms or adb shell logcat to get a logcat and see if it appears to be repeating if your phone doesn't boot then copy the logcat and post it here.
Good luck.
I have been searching the forums for 2 hours trying to figure this out and I cannot find out how. I tried following the tutorials on the forums here on how to partition the SD card but none of the settings that were listed are not on my recovery. But I still tried it anyways. Here is the list of options on my recovery
Reboot system now
Nandroid v2.2 backup
Nandroid v2.2 restore
Apply sdcard:update.zip
Apply sdcard:choose zip
Wipe data/factory reset
Wipe SD:ext partition
Wipe SD:dalvik-cache
Part SD:fat32+ext2+swap
Part SDnly fat32
Repair ext filesystem
Convert ext2 to ext3
Fix apk uid mismatches
Fix rotate
USB Mass storage on
USB Mass storage off
The bottom says "Build : RA-heroc-v1.2.3".
Upon reading the tutorials, I decided to try something different. So I wiped ext partion, parted sd fat32 ext2 and swap, then converted ext2 to ext3. Applied PureHero 2.1 and I enabled Apps2SD, move apps to sd, move dalvik cache to sd, enable JIT, and changed dalvik heap to 24mb. It rebooted and none of the applications I downloaded and installed were transferred to the SD.
Before this I applied a rom before wiping and parting and changed the same settings and it wasn't working then either.
I tried using the cmd and located to my android-sdk-windows and tried finding what version of apps2sd I had but it kept aborting. I tried repairing and it kept aborting, I even tried installing and it kept aborting.
I am at a loss here and I am trying to get all of this working.
It is a 2gb card and it is only showing 1.34gb available so I have no idea how to give me the full 2gb like it was before I tried partitioning.
Before I posted this, I applied the program at http://forum.xda-developers.com/showthread.php?t=715116 and that didn't work as well.
Please help.
I'm not sure if it makes a difference, but I would try to upgrade to RA-heroc-v1.6.x, it might be your recovery not partitioning correctly or something. Once you have upgraded, go ahead and wipe everything (data, dalvik, and ext). Flash your ROM. Before you move your dalvik to the sd card you want to make sure you have at least a class 4 sd card. Once your phone is booted up check your internal memory and you should have 90+M out of 159 or so. If you have that then I am pretty sure your ap2sd is working. You can also check to make sure it is working through adb. I don't use the option in recovery to move the apps to sd. Hope this helps, and I hope my information is correct, lol. I still consider myself a noob.
Ok ill do some research on how to update and see what I find. If that don't work then ill come back and keep you updated.
Thanks
EDIT: I have tried updating my Recovery using FlashRec and it isn't backing up my recovery or finding the recovery at all. I am on ubuntu so maybe that might be the problem, idk. Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
puppetmstr said:
Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
Click to expand...
Click to collapse
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
c00ller said:
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
Click to expand...
Click to collapse
Well this is confusing lol. I went into recovery, went into USB mode getting ready to update my recovery option and a screen popped up in ubuntu with the folders app, app-private, dalvik-cache, and lost+found. Apparently I had apps2sd working the entire time... But I nandroid last night back to ZenEXP. Idk if it still works in Pure Hero.
But now that I have apps2sd working, I can flash a new rom and still have my applications right?
EDIT: In Windows 7, it doesn't show the partition anymore for the apps2sd. So im just gonna go ahead and update recovery then repartition everything.
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
c00ller said:
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
Click to expand...
Click to collapse
I cant update the recovery at all. I have tried both ways and it fails.
I tried adb and as soon as i try to use the command "mount -a" it says "no such device". I tried using "mount /sdcard" and it says "Device or resource is busy".
On the Fastboot + adb I can load into fastboot. But when i type "fastboot boot recovery-RA-heroc-v1.6.2-blue.img" it says "cannot load fastboot boot 'recovery-RA-heroc-v1.6.2-blue.img'".
I tried pressing the trackball on fastboot usb and the screen goes black for a second, then i hear a connect noise in the speakers then it shows fastboot for a split second then fastboot usb again.
Also in Fastbot +adb when I use the command "adb shell mount /sdcard" it says "device not found".
EDIT: im also starting to think my adb shell is broken or something lol.
Ok nevermind I got it working. I typed mount /sdcard and it said it was busy but then i used the command "flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-blue.img" then Rebooted into recovery and it says 1.6.2 and its blue. I just hope I did it the right way and didnt **** anything up...
EDIT: Ok well I partitioned it with 64mb swap, 1024mb ext2, converted to ext3, and loaded up PureHero 2.1. How do I know if it is working? I have my DConfig options set to move dalvik and apps to sd, with JIT enabled. Do I just install an app and see if the internal memory lowers or stays the same? How do I access the apps folder through USB mode?
This is how to tell if you have A2SD working
http://forum.xda-developers.com/showpost.php?p=6848245&postcount=80