Database Develop

Need help system not reconizing SdCard

Yes I've done a search however if I was mistake in missing this already being done I'm sorry.
1st. I did the whole apps to Sd and that worked. However my phone later in the day wouldn't stop looping so i wiped then updated again.
The issue : After wiping the system and re-flashing with jf1.51 adp, I start the whole apps2sd again. I reformat SD again. I type in the whole "cp /sdcard/init.rc /data/ cp /sdcard/a2sd.sh /data/ Then reboot" While its rebooting it gets stuck at the Android logo. This will stay here for 20min.(yes I've timed it). So i take out the SD and it will start just fine. I then restart the phone with another SD this time not the class 6 but a 16 gig and it yet again starts fine. What could be the issue?
Thank you. Like I've said if this was already discussed as my issue I'm sorry I did look.

What can u post the outputs for the following commands
Code:
df
And
ls -l /data

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

Getting past N7000 LM5 bootloop without wiping

My Galaxy Note N7000 was on the Jelly Bean 4.1.2 LM5 (HK) firmware with "PhilZ-cwm6-ZSLM5-OZS-4.35-signed.zip" installed.
Phone internal memory was repartitioned to 10.9GB for /system and 2 GB for /data since I store most of my files on the microSD card anyway.
The phone was working nicely although I did experience a boot loop problem when I first flashed it because I changed the phone ID with Titanium Backup, so I did a wipe to get out of the boot loop.
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Searched around xda and it seems that everyone's solution is to wipe the phone to factory default.
The problem was that I haven't backed up my phone for quite a while and I wasn't willing to wipe the phone again and lose all of my data if I can avoid it. :crying:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
I am now flashing the new UBLSF and PhilZ new kernel with bootloop fix, I hope that gets rid of the bootloop problem for good.
This seems similar to the problem and solution posted here : http://forum.xda-developers.com/showthread.php?t=2040107
Hope my experience is useful to others who experience similar problem

Thank you. Really helpful.
Enviado desde mi BlackBerry Runtime for Android Apps usando Tapatalk 2

this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop

zerenx said:
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Click to expand...
Click to collapse
I did that too, then I fixed data partition, yet since that incident. It happens several times that I find my phone shut (even though the battery is full), then the phone is boot looping. I can't understand the reason for this.

Hi, yesterday my phone suddenly restart few times before stuck at the samsung boot animation. Until today my GNote unable to get pass the boot animation. Is there any way to fix this without data wipe because I didn't expect this would happen so I haven't backup my data yet. I'm using samsung latest official Jelly Bean. Non rooted. Last activity before it happen, playing games & update few apps in play store. This is the first time I post in this forum. Sorry if there's any mistake I've made.

Can you connect your phone to the PC? And try to use the phone while keeping it plugged in to charge. How old is your battery? If you can conncet to the PC, you can take a copy of your data.

I can copy files from sdcard. But not from internal storage. And I actually need to backup my sms, call log, etc.. which need to able to boot the phone. battery is almost 1 year already.

Can you use the phone while keeping it plugged in? There must be an issue with some app, maybe after updating it, any app you suspect?

I no longer can use the phone since it stuck at samsung boot animation there. And I can't really remember which apps I was updating.

thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
FYI:
i WAS able to mount /data with cwm utility. but when i tried e2fsck -n, it threw a lot of complaints, so i did it again with a -y, and it rebooted fine.
i also tried browsing around /data with Aroma from CWM. some data/* i could view, but it froze when i tried to look in the delvik folder.
is there a more convenient utility to fsck the whole system everything?
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?

gnormal said:
thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
Click to expand...
Click to collapse
Glad that helps.
At my device, the /data partition is always located at the /dev/block/mmcblk0p10 so I didn't think it was necessary to mention it. Of course, if you repartition your device then the block might change but I guess you should be advanced enough when you've been playing with the partition.
gnormal said:
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?
Click to expand...
Click to collapse
UBLSF refers to official Samsung firmware Jelly Bean 4.1.2 for Trinidad and Tobago (N7000UBLSF_N7000UUBLSF_TTT).
But no, even that firmware isn't immune to the bootloop, I still experienced one bootloop with UBLSF firmware.
Thankfully I have this thread so I was able to recover my data intact in just a few moments, would've forgot the steps without this thread. :laugh:

It works!
zerenx said:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
Hope my experience is useful to others who experience similar problem
Click to expand...
Click to collapse
I thank you from the bottom of my heart! You saved my data!
I was experiencing problems with the Note (rooted, CWM recovery, Philz kernel) and space on the internal memory, so I wiped the Cache and Dalvik partitions (I've done that many a times to be casual about it). The phone restarted thereafter, but went dead all of a sudden, forcing me to do a hard reset. It went into a boot loop, and I could not revive it.
Luckily, I found this thread, and after looking through various other links, I was able to download ADB (without the SDK). Somehow, I could not get ADB to see the device in the download mode (vol down + middle button + power), but it was visible in the recovery mode (vol up + power + middle). [Edit: I ended up taking the necessary steps in Recovery mode after all].
I had been able to mount /data from CWM Touch recovery, but when I tried to backup, the process had been exiting on reaching the /data folder. So I checked the unmounted volume as you had indicated, and it did find some errors! I checked all the other unmounted volumes for good measure, and they turned out to have no errors. (Actually, as I didn't know which block device referred to each of them, I checked with the 'mount' command both before and after mounting/unmounting them from Touch recovery )
The phone restarted after fixing the /data partition, booted up, but hanged after mounting the memory cards and establishing a connection. I had to do a few hard and soft restarts after that, but nothing has been corrupted. It is stable right now on airplane mode, and I'm backing up data via KIES. I think I'll do a factory reset later and restart from scratch.
In summation, your trick worked, and it should be recommended as the first thing one tries. Thanks again!

I have this problem
terminator_5505 said:
this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop
Click to expand...
Click to collapse
Hi !
I have this problem with my Note and couldn't find a topic explaining how to get out of this loop (in this particular case).
Do you know one or what to do?
I'm JB (I don't know my baseband but it's the official one I got OTA in France, couldn't find it on sammobile). I didn't do anything since the update a few month ago.
I still have the download mode and the recovery menu
Can I wipe securely on JB?

I have retired my original Note N7000 and moved on to Note 3 N9005, so my memory might be a bit rusty.
If you have all original firmware on your Note, I think it would be safer to first flash in PhilZ's safe kernel (http://forum.xda-developers.com/showthread.php?t=1901191) on the device before wiping to avoid the brick bug.
You can then do the wipe from the recovery menu.
If you have some data you need to recover from the device, maybe you can give the method described in the original post to check for filesystem errors and have your Note out of the bootloop.
Good luck.

thanks a lot Mannn :good:
you just save me from reinstalling from scratch

[Q] Is my internal storage dead?

I am trying to get my Son's Captivate back up and running.. while it has no phone service, he uses it all day long. It was running Cyanogen Mod 10 .. he sat it down to eat.. when he came back the screen was black with the buttons lit up and no response.
He did a battery pull to restart it and it came back looping Error to mount /SDcard and a count down.
I got it into recovery and am not able to mount /data or /emmc. And it is failing to install a ROM from zip.
I tried using "I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click" and it runs through the process.. flashing Kernal, Modem, FactoryFS, DBDataFS and CACHE successfully.. then the device reboots and goes through a few things on screen, and fails on Formatting /data ( E:format_volume: rfs format failed on /dev/block/mmcblk0p2 ) but everything else says success. Hitting "reboot system now" says that it cant copy the log because of failure to mount /emmc.. then reboots to the same recovery and does the copy of Media and Appling Multi-CSC (their spelling mistake not mine) over again.
Flashing back to a CWM 6 recovery and still no mounting of /data or /emmc. And it just boots right into the recovery.
I tried --repartition with Heimdall and it said it uploaded the S1JE4.pit fine. Same things..
So is there anything I can to to test the internal storage to KNOW if it is faulty or is there anything else I can do?
I would really like to get this thing working again for my little dude.. he is so sad as all heck to not have his Android Buddy. :crying:

Seems likely internal sd may be dead, particularly if someone ran ICS on it at some point. If you have an external sd card, at least 8GB, this thread may help-
http://forum.xda-developers.com/showthread.php?p=21439417
you could use cm10.1 instead of the ICS rom mentioned in the thread.
Sent via Monty Pythons Flying Circus

[HELP PLEASE] NEED HELP WITH make_ext4fs

Hello. So i have a S3 LTE with possibly(?) an insane eMMC. Long story short: phone bought back in dec 2012. Changed battery twice. Last battery started acting up, lost all power, next thing i know phone is in permanent bootloop. Odin won't repartition the phone (idk why) nor can it flash a full firmware, getting stuck on SYSYEM flash, but can flsh recoveries. After fiddling around with recoveries, i finally flashed TWRP. What i found out : /cache, /system, /data, /sdcard and /tombstones couldn't be mounted (invalid argument). After wiping everything with make_ext4fs, everything works fine, except for /tombstones, which can't be mounted. What i have seen from the logs is that twrp doesn't wipe /tombstones as well, so there was no way of getting it to work.
Full story here http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-bootloop-mount-data-sdcard-t3379377
WHAT MY PROBLEM IS:
I need somebody to tell me the parameters for make_ext4fs in order to wipe /tombstones as well, as it seemed to work flawlessly with the other folders.
UPDATE: I managed to wipe /dev/block/mmcblk0p11, which mounts in /tombstones. used rm -fr, then mkdir for the tombstones folder. Everything mounts just fine now. Will reflash and post an update.
UPDATE 2: Phone still won't work with odin. i flashed amcha with twrp. Boots just fine, but 10 seconds after boot finishes, phone freezes and won't respond to button presses. Any ideas?