Related
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
hey guys, i have a smiple question, I am running Cyanogen7rc2 with data2ext applied. Now if i wiped data and it formatted everything, and i format sd card and sd-ext, i get this "(bad) installition aborted" when ever i flash that rom. Can anyone explain this to me in greater detail?
1st what version are you running??? If your able to nand back to when you had data2ext working do so. 2nd if you wipe sd-ext more than likely you'll end up in a boot loop. Also if you just wipe everything and flashed the rom without flashing the data2ext zip right after you might receive that msg. After you restore a nand always reflash the data2ext zip. If your rom is functioning fine and you want to update to a new one. Reboot into recovery make a nand+ext backup then flash the data2ext zip and reboot. Then reboot back into recovery and to keep all of your data just wipe cache & dev-cache then flash the rom then the data2ext zip and reboot. If your rom is running fine and you wanna do a fresh install do the same process of making a nand+ext backup then reboot. Then go back into recovery and wiped data,cache,dev-cache. "Don't wipe sd-ext". Then flash the rom & right after flash the data2ext zip and reboot. You will have to setup the data2ext again threw terminal or adb. This is what I do no guarantee it will work for you if your running cwm but it should. The reason I say this is because I'm running data2ext ext2 gf's mod and I'm using Ra1.7. Hope this helps. Also you might want to redownload the rom as it might be a bad dl.
Root/Hack_Mod-Always*
laie1472 said:
1st what version are you running??? If your able to nand back to when you had data2ext working do so. 2nd if you wipe sd-ext more than likely you'll end up in a boot loop. Also if you just wipe everything and flashed the rom without flashing the data2ext zip right after you might receive that msg. After you restore a nand always reflash the data2ext zip. If your rom is functioning fine and you want to update to a new one. Reboot into recovery make a nand+ext backup then flash the data2ext zip and reboot. Then reboot back into recovery and to keep all of your data just wipe cache & dev-cache then flash the rom then the data2ext zip and reboot. If your rom is running fine and you wanna do a fresh install do the same process of making a nand+ext backup then reboot. Then go back into recovery and wiped data,cache,dev-cache. "Don't wipe sd-ext". Then flash the rom & right after flash the data2ext zip and reboot. You will have to setup the data2ext again threw terminal or adb. This is what I do no guarantee it will work for you if your running cwm but it should. The reason I say this is because I'm running data2ext ext2 gf's mod and I'm using Ra1.7. Hope this helps. Also you might want to redownload the rom as it might be a bad dl.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
That was a ginormous explation! thanks!
Im running dataext4 v4.
So let me get this straight, if i wipe data data/factory reset it wipes the partion off the sd card, or no?
coffeehandle said:
That was a ginormous explation! thanks!
Im running dataext4 v4.
So let me get this straight, if i wipe data data/factory reset it wipes the partion off the sd card, or no?
Click to expand...
Click to collapse
Na not wipe it out as in making the partition disappear it just removes the link you had to it threw data2ext. Because you wiped all of the data from it. Your partition remains but the link is removed. Data2ext ext4 or ext2 wont carry over if you wipe data.
Root/Hack_Mod-Always*
You might want to consider data2ext ext2 "IMO" It performs better. I've read a lot of posts about users having problems with ext4. Its a know fact ext2 can cause data loss if you do a battery pull or improper shut down. But I've been using it for quite some time and I've done batter pulls galore and have lost no data just had to boot into recovery and wipe cache & dev-cache and reflash the data2ext zip and I was good. Also if your not s-off I recommend it when using data2ext and just in general.
Root/Hack_Mod-Always*
laie1472 said:
You might want to consider data2ext ext2 "IMO" It performs better. I've read a lot of posts about users having problems with ext4. Its a know fact ext2 can cause data loss if you do a battery pull or improper shut down. But I've been using it for quite some time and I've done batter pulls galore and have lost no data just had to boot into recovery and wipe cache & dev-cache and reflash the data2ext zip and I was good. Also if your not s-off I recommend it when using data2ext and just in general.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
L I thought it was the other way around ext2 was the one that could lose data if you pulled battery
Yea I caught that and edited my post look up lol
Root/Hack_Mod-Always*
laie1472 said:
Yea I caught that and edited my post look up lol
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
You sly one lol,you get my pm?
Nope no go. Strange. I guess I have to figure out how to contact a admit. Never did it.
Root/Hack_Mod-Always*
laie1472 said:
Nope no go. Strange. I guess I have to figure out how to contact a admit. Never did it.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
ok thanks ill do the data2ext2 and try that out.
So one last thing and im all good. the only way you can erase those partions is if you format the sd card, through a computer program?
ah man now im stuck, i nand back to a stock back up i had, then formatted my sd card through my computer
then went to recovery to flash CM7rc2 and i still get this (bad)installition aborted. do i need to re enable the data2ext in my stock rom, then flash CM7.
You can threw a computer program or threw your recovery.
Root/Hack_Mod-Always*
laie1472 said:
You can threw a computer program or threw your recovery.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
did you read my edit? i did just that in my nand stock rom, and it did the same thing
coffeehandle said:
did you read my edit? i did just that in my nand stock rom, and it did the same thing
Click to expand...
Click to collapse
Backup all of your data.
After you format threw your pc then format it threw your recovery. Then re partition your sd to 1024 ext2 or 1024 ext4 0swap and the rest fat. Then place all of your data back on your sd. Then wipe data, cache,dev-cache and sd-ext. Then flash your rom of choice followed by the data2ext zip and reboot. When you reboot you will have to resetup data2ext threw terminal or adb.
Root/Hack_Mod-Always*
laie1472 said:
Backup all of your data.
After you format threw your pc then format it threw your recovery. Then re partition your sd to 1024 ext2 or 1024 ext4 0swap and the rest fat. Then place all of your data back on your sd. Then wipe data, cache,dev-cache and sd-ext. Then flash your rom of choice followed by the data2ext zip and reboot. When you reboot you will have to resetup data2ext threw terminal or adb.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
cheers to you man, hope this works. so as long as i dont run that command in adb it wont push the data over to the ext, though it is always partioned?
Yup your right. Even if you flash the data2ext zip it wont activate until you tell it to.
Root/Hack_Mod-Always*
Pardon my noob language, but thanks friend it got me up n running
A no prob. Glad you got it. If you need anything else just shoot me a pm.
Root/Hack_Mod-Always*
ok. so i was running medroid 6.1 on my nexus fine, then i went to go update it to medroidmodremix 1.2.1 and i wiped dalvic cache but not user data.. first it would not even turn on, then i booted into recovery and i fully wiped everything cache, dalvic, system data, user data etc.. then i got boot loops on the medroid boot logo. it would restart after 10 mins and boot loop again. i then booted into recovery and deleted everything and wiped dalvic cache and updated to medroid 1.3. and it still is boot looping..
please help
ps: it gets pass the x logo but loops at the medroid logo and reboots.
Normally, it would reboot three times at the X logo after wiping dalvik since it has to move it back to sd-ext, but since it's looping at the medroid logo, something else is amiss.
My first guess would be that you might have to repartition your sdcard. There shouldn't be any problems with your hboot partition scheme as it would have looped at the X logo if that was the problem.
Thanks for the reply.
and im kinda a n00b at this stuff.. How would I partition my sd card. I tried doing it with the recovery in my nexus but it always fails.. im running windows 7.
harjnijh said:
and im kinda a n00b at this stuff.. How would I partition my sd card. I tried doing it with the recovery in my nexus but it always fails.. im running windows 7.
Click to expand...
Click to collapse
Do like this:
1. Download and flash 4ext recovery. It's pretty much the only recovery to actually make good partitions.
2. Boot into the recovery.
3. Mount USB storage and connect your phone to your PC
4. Copy-paste everything from your sdcard to your PC
5. Unmount the USB storage and enter the partition menu and partition to ext2. Choose 512mb for the first partition, 0mb for swap and 0mb for the second partition and leave the rest for fat (or fat 32)
6. Now mount USB storage again and this time copy-paste everything back to your sdcard.
That should do it.
Oh, and download and install this .apk to automatically download 4ext recovery and future versions of it. It's the free and somewhat limited version. There is a paid version in the market for all features.
http://www.4ext.net/get.php?apk
how do i flash 4ext recovery when my nexus doesnt turn on?
how do i flash 4ext recovery my nexus doesnt get past medroid logo.
harjnijh said:
how do i flash 4ext recovery my nexus doesnt get past medroid logo.
Click to expand...
Click to collapse
Ah, worry not! Simply reboot your phone into fastboot mode and plug your phone to your computer. Make sure you have ADB set up correctly and fastboot drivers installed.
Then go to the folder where you have a fastboot.exe and shift-right click and select open command windowd here. Then make sure you have your recovery in that folder and the type:
fastboot flash recovery name-of-recovery.img
fastboot reboot-bootloader
where to download
where can i download the recovery from. 4ext is a .apk. please provide link
harjnijh said:
where can i download the recovery from. 4ext is a .apk. please provide link
Click to expand...
Click to collapse
http://nexusone-medroid-ics.googlecode.com/files/4ext-recovery-RC3.img
thanks man !!!
thanks man you the best!!!!!!!!
it worked!!
harjnijh said:
thanks man you the best!!!!!!!!
it worked!!
Click to expand...
Click to collapse
You're very welcome!
I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?
iFeelYouJohanna said:
I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?
Click to expand...
Click to collapse
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method
Viper The Ripper said:
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method
Click to expand...
Click to collapse
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.
Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.
iFeelYouJohanna said:
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.
Click to expand...
Click to collapse
Try doing wipes after odin flashing
Viper The Ripper said:
Try doing wipes after odin flashing
Click to expand...
Click to collapse
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Edit- ok I noticed my sd card wasn't being detected so I removed it and rebooted and everything seems to be fine :/
Can a faulty sd card slow down/ make your phone become unresponsive?
iFeelYouJohanna said:
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Click to expand...
Click to collapse
And dalvik cache?
nikwen said:
And dalvik cache?
Click to expand...
Click to collapse
Yeah root it and flash cwm and then wipe dalvik cache if not try to flash a custom stock rom after odin fashing e.i. rooted and cwm installed after odin flash
Viper The Ripper said:
Yeah root it and flash cwm and then wipe dalvik cache
Click to expand...
Click to collapse
And afterwards do that: (also use a fresh downloaded CWM)
nikwen said:
Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.
Click to expand...
Click to collapse
Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.
Is it detecting the card in CWM? If so, you could format it that way.
I got a miniSD card adapter with my phone? Did you not?
iFeelYouJohanna said:
Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.
Click to expand...
Click to collapse
so your Sd card was corrupted, use a micro sd reader
Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format
iFeelYouJohanna said:
Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format
Click to expand...
Click to collapse
Great. :good:
Hello.
first I want to apologize for my, sometimes, bad English!
Second, i want to apologize for my novice touch in this topic!
The story:
I've been using SweetRom for a while, but tonight i wanted to try another rom.
I loaded up SuperBean(not really relevant to this story) on a microSD.
Rebooted my phone into recovery
Philz Touch 5
I choose "Wipe Data/Factory Reset" and then "Clean to install a new rom"
Then i tried to "install zip"
"Choose zip from sdcard"
But then i get: E:Can't Mount /sdcard/
I've tried to format the sdcard, exfat, fat, fat32, ntsf but nothing worked, still the same error.
I can access the internal storage and i can boot into download.
I thought that maybe i'll try to install the newest Philz but when in download mode
my computer wont recognize my phone (i'm using Windows 8)
i'm stuck! please help me out!
I've searched everywhere for answers but i can't find any!
What are my options?
Boot into Philz recovery again and go to mounts and storage and mount USB. Then connect it to pc. Check if the any drive shows up. Then move the new rom to the internal storage.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
Boot into Philz recovery again and go to mounts and storage and mount USB. Then connect it to pc. Check if the any drive shows up. Then move the new rom to the internal storage.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Thank you so much!
It took a while for my computer to find my phone, but it worked!
Cool. There's another way to express thanks.
There's is a thanks button and press it for the guy who helped you.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
Boot into Philz recovery again and go to mounts and storage and mount USB. Then connect it to pc. Check if the any drive shows up. Then move the new rom to the internal storage.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
what DOES the "clean to install a new rom" option do anyway?
explorer-10 said:
what DOES the "clean to install a new rom" option do anyway?
Click to expand...
Click to collapse
It does a full wipe. Basically it formats: cache, /system, /preload, /data
XxPixX said:
It does a full wipe. Basically it formats: cache, /system, /preload, /data
Click to expand...
Click to collapse
is /preload equivalent to /dalvik-cache? but then what's the point of format /data/factory restore if "clean to install new rom" is present?
No. It's different. Preload is a separate partition and dalvik-cache is in data partition.
The option you mentioned only exists in Philz recovery not in standard cwms
explorer-10 said:
what DOES the "clean to install a new rom" option do anyway?
Click to expand...
Click to collapse
XxPixX said:
It does a full wipe. Basically it formats: cache, /system, /preload, /data
Click to expand...
Click to collapse
explorer-10 said:
is /preload equivalent to /dalvik-cache? but then what's the point of format /data/factory restore if "clean to install new rom" is present?
Click to expand...
Click to collapse
nokiamodeln91 said:
No. It's different. Preload is a separate partition and dalvik-cache is in data partition.
The option you mentioned only exists in Philz recovery not in standard cwms
Click to expand...
Click to collapse
So, to be clear, is it necessary or advisable to do any of 'Wipe Data/Factory Reset', 'Wipe Cache Partition' and 'Wipe Dalvik Cache'? Or is 'Clean to Install a New ROM' merely an amalgam of the above (plus added formats?)?
Thanks
It's usually not necessary but it is ALWAYS advised to format /data /preload /system and cache before flashing a new ROM. If you don't do those wipes then you can sometimes end in a bootloop, random force closes, battery and performance issues et cetera. Basically if yoou want to flash a new ROM (unless it is an update to your current ROM) then always do a full wipe,
If you are just updating your ROM (ex. updating one nightly to another) then you just have to flash the ROM in recovery and wipe cache, dalvik cache (in advanced)
.
XxPixX said:
It's usually not necessary but it is ALWAYS advised to format /data /preload /system and cache before flashing a new ROM. If you don't do those wipes then you can sometimes end in a bootloop, random force closes, battery and performance issues et cetera. Basically if yoou want to flash a new ROM (unless it is an update to your current ROM) then always do a full wipe,
If you are just updating your ROM (ex. updating one nightly to another) then you just have to flash the ROM in recovery and wipe cache, dalvik cache (in advanced)
.
Click to expand...
Click to collapse
Thanks very much for that - much appreciated.
I've read elsewhere that many seem to recommend wiping cache and dalvik after they've flashed a ROM? Is this something you'd advise and, if so, why (or not!)?
Many thanks
largeruk said:
Thanks very much for that - much appreciated.
I've read elsewhere that many seem to recommend wiping cache and dalvik after they've flashed a ROM? Is this something you'd advise and, if so, why (or not!)?
Many thanks
Click to expand...
Click to collapse
If you're updating then yes, it's enough that you flash the ROM and then wipe cache and dalvik cache.
If you're reflashing from start then you should first do a full wipe, flash the ROM, gapps, su and that is all. No need to wipe the cache or dalvik cache again
XxPixX said:
If you're updating then yes, it's enough that you flash the ROM and then wipe cache and dalvik cache.
If you're reflashing from start then you should first do a full wipe, flash the ROM, gapps, su and that is all. No need to wipe the cache or dalvik cache again
Click to expand...
Click to collapse
Ah right. So if you're flashing a new ROM - then clean install is all that's necessary. If upgrading to a newer version of existing ROM, then it's better to wipe cache and dalvik post-install? Why? What does it do and how does it help?
Cheers
reset before installing zip, now no super su ... cannot mount usb
Hi,
The title says it all. I have been reading and searching. Many similar stories. I apologise if this is in the wrong place but this is very similar to my problem.
I have a galaxy i9505 trying to install a DjeMBeY ROM from TWRP.
I factory reset and wiped cache's BEFORE I flashed the .zip file so then had no .zip file to flash!
Also have erased my system backup and the USB WILL NOT SEEM TO MOUNT to copy it back onto the card.
I have read and read I am very struck.
I am not familiar with all the processes yet. Please help.
i recommend going to here
Similar prob
nokiamodeln91 said:
Boot into Philz recovery again and go to mounts and storage and mount USB. Then connect it to pc. Check if the any drive shows up. Then move the new rom to the internal storage.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, thanks for the advised. i have a similar prob. I dont have a sd card (external) and i just had installed xtrestolite 2.1 in my exynos S5 smg900h but google play services kept crashing so i decided to wipe clean to install new rom instead of just regular wipe data. i wanted to flash again xtrestolite but i did not know that the rom i had inthe internal memory of the phone was gonna be erased as well (i know iknow dumb me ) so now i cant get pass recovery, i dont know if download mode will work as i did not activate usb debug after i installed xtrestolite. if a go to mount usb nothing happens............. i dont know what to do ..
luislaperika said:
Hi, thanks for the advised. i have a similar prob. I dont have a sd card (external) and i just had installed xtrestolite 2.1 in my exynos S5 smg900h but google play services kept crashing so i decided to wipe clean to install new rom instead of just regular wipe data. i wanted to flash again xtrestolite but i did not know that the rom i had inthe internal memory of the phone was gonna be erased as well (i know iknow dumb me ) so now i cant get pass recovery, i dont know if download mode will work as i did not activate usb debug after i installed xtrestolite. if a go to mount usb nothing happens............. i dont know what to do ..
Click to expand...
Click to collapse
You can go with the download mode and install a stock ROM or use the 'adb sideload " feature of cwm recovery to install the zip of your ROM if you have it saved on your PC.
nokiamodeln91 said:
You can go with the download mode and install a stock ROM or use the 'adb sideload " feature of cwm recovery to install the zip of your ROM if you have it saved on your PC.
Click to expand...
Click to collapse
Thanks! i went with download mode, then installed a stock rom, i had to root again and flash philz touch and install xtrestolite and now everything is ok!