fix_permissions/Repair Ext - G1 Q&A, Help & Troubleshooting

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

Related

Hero to cyanogen ( half brick here... )

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!

G1 fails at flashing and reboots

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

Why would my hero be completely stable on 1.6, but reboot frequently on any 2.1 rom?

I am extremely frustrated at this point so I have decided to make a thread.
My hero has been a good phone and runs 1.5/1.6 roms without any problems, and has for 6+ months. However, as soon as the 2.1 leaks came around, I was eager to try them. NONE of them will work. I have tried 6 or 7 different versions. My phone will shut off very frequently, which essentially makes it unusable.
Has anyone else experienced this and was able to fix it, or otherwise have any advice for me?
Any help would be greatly appreciated.
pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?
spiritcrusher33 said:
pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?
Click to expand...
Click to collapse
Haha. Yeah man, factory reset + dalvik cache wipe. Would a bad SD card cause something like this?
sounds like you didn't properly wipe... once you wipe EVERYTHING.. (after a nandroid).. you shouldn't have problems installing any ROM whether it be 1.5, 1.6, 2.1, 4.2 (coming to the htc hero6 in 2013)
edit: you mentioned factory reset... are u doing the factory reset thats installed in the settings menu or are you wiping everything from recovery?
Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.
roadster92 said:
Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.
Click to expand...
Click to collapse
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
what recovery rom are u running? and no wiping the ext partition is not wiping your SD card... just the partition you created..
dont wipe the battery but wipe the sd ext.
the sd ext only wipes what apps you have installed when you partition your sd card. it doesn't remove music, picutres, etc...
splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
The one I am using now is overclock. But the previous one that I used is "recovery-RA-heroc-v1.6.2-blue.img"
You might have the older version. Battery Stat Wipe is just reference for me every time I using a new ROM to see how the battery life is.
As mentioned above, wipe EXT partition will not wipe any pictures or data on the FAT32 of the SD card.
im having a similar issues i cant get my phone to stop restarting. ive wiped everything you can even repartitioned and it sill does it.
are we doing somehting wrong?
i have a thread i started not seeing this one.
http://forum.xda-developers.com/showthread.php?t=684727
check the hardware
As someone suggested, please be sure to rollback to 1.6 to rule out a hardware problem.
I have a battery -- one of four in rotation -- that consistently reboots the phone after it draws down to 80% or so. This is probably the battery that I misplaced and didn't use for a few months. Before I pinned the problem down to this particular battery, I thought 2.1 was haywire, rebooting all the time. Once I pulled the battery out of rotation 2.1 became relatively stable again.

darchdroid apps2sd + wipe phone, what happens?

I've never bothered with apps2sd previously, but since I've been running darchdroid the last few weeks I've set up his native version and have been loving it.
Now that dd2.7 is out and MMS is fixed, I tried to flash over but it didn't fix the issue. Release notes say I may have to wipe to get it to work. Ok no problem.
What happens to my apps2sd stuff when I wipe my phone? Will I be able to just flash dd2.7 as per usual and everything is good to go?
If I choose to wipe everything (including ext4), will I have to repartition my card again or will my current partitions hold from when I partitioned them the first time?
I ran a few searches but couldn't come up with any good answers to my questions.
I appreciate your help,
-b
blampars said:
What happens to my apps2sd stuff when I wipe my phone? Will I be able to just flash dd2.7 as per usual and everything is good to go?
Click to expand...
Click to collapse
If you do a wipe, you'll want to wipe ext and cache as well. I suggest Titanium Backup or something like that for your apps.
blampars said:
If I choose to wipe everything (including ext4), will I have to repartition my card again or will my current partitions hold from when I partitioned them the first time?
Click to expand...
Click to collapse
Partitions won't change unless you re-format your SD card. Nothing on the FAT partition will be touched.
awesome, thanks for clearing things up for me.
Much appreciated.

Flashing trouble

Okay, i've been having a problem where my device gets stuck at the g1 screen after i flash ANY rom, i've given each rom i've attempted to flash up to 10 minutes each, i have to resort to a battery pull and nan restore to get my phone working again, i've tried flashing roms on two different cards, both with the same horrible end. I've tried reformatting, repairing partition, and wipe wipe wipeing, but nothing seems to work. Any ideas?
my specs:
OS: im running cyanogen's donut (which i have a nan backup of)
SD: 4gb class 6
Radio: latest
SPL: Danger
Recovery: Amon_RA's
Ext3: 1000mb
swap: 32mb
what rom are you tryna flash ill help you out.?
for example if you want the new cm508 t4 then u gotta download the following in the listed order:
1. download & install the newest radio for your device
2. download & install the danger( aka deathspl )\
3. download & install the latest version of cyanogen for your device.
that easy bro. HERE is a gide a friend of mine put together for me and its acurate and current. although there are nomore file links so u have to search google or xda search for the needed files.
good luck.
Requested to be moved to Q&A because this is NOT Development.
okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash
xStuntmanEdx said:
okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash
Click to expand...
Click to collapse
Why can't you wipe?
Do a fresh nandroid/bart backup of your current working system.
Backup your SDCARD FAT partition to your computer.
Reformat your SDCARD (completely, no ext partition or swap partition)
Make sure you have Amon_Ra 1.7.0 recovery installed
Restart your device in recovery.
Wipe data and dalvik-cache.
Repartition your sdcard
Convert ext2 to ext3
Convert ext3 to ext4 (optional)
Mount SDCARD from Recovery onto your computer.
Re-download your the rom that you want to install and gapps if applicable and place them on the root of your sdcard.
Safely remove the device from your computer
Unmount the SDCARD from the phone (may need a reboot)
Flash your desired rom (don't reboot yet)
Find ddms.bat in the tools folder with the AndroidSDK and run it.
Click logcat
Reboot your device and let it SIT and watch the logcat.
If it seems to stop for a long period of time highlight the lines at the bottom and save the file to your desktop. Open it to confirm that you have the log in your text file.
Upload it to pastebin and post the link in this thread for others to help you further.

Categories

Resources