Related
The option to format my SD Card is GONE from the recovery menu, here's what happened.
1. i9000M running Froyo JPM approx. 3 days, no lagfix, rooted, lots of apps, SD card almost full.
2. Took phone out of pocket - Black screen of death, bottom buttons light up on touch.
3. Reboot into ClockWorkMod Recovery - unmount and remount everything. Reboot, and nothing. Wipe cache, reboot, nothing. Wipe data/restore to factory, reboot, AHA!, see 4.
4. Phone starts, immediately starts force closing like none other.. so, reboot into recovery.
5. Try restoring a Nandroid backup.. everything is swell, but it finds an error: can not restore android_system.img ... oh boy
6. Go back into recovery.. can NOT get to ClockworkMod Recovery, when I try to apply the update.zip, ERROR: no such file exists
Note: at this point I am not getting any errors when I enter recovery mode related to mounting, sdcard - nothing.
7. Try wiping/resetting again. Nothing.
8. Try flashing back to UGJH2 (stock Bell), nothing.
In the end, I still have no errors in recovery, and the option to format my SD card is gone..
Is this the same SD card issue as everyone else, or did I unmount my SD card somehow in step 3?
you sound like this case
http://forum.xda-developers.com/showthread.php?t=822580
so when you re-flashed back to JH2
did you get any error message?
which method did you use to flash back to JH2 ?
EDIT4: Well I had to NVFlash my phone and flash the LG stock rom, and it worked, but I lost all my data, o well I'm so happy now
It all begins when I first flashed CM7.1 stable for the first time, I had initial problems with the browser not downloading files to my internal sdcard, but I think I fixed that by editing vold.fstab and build.prop files following some guide I found on the internet. Everything was good but I was unable to flash vorkkernel because when I did, It would not boot. To fix that I recovered a back up, I think:cyclops:? months went by and I was happy with my CM7.1, but I still wanted vorkkernel for the voodoo sound. I end up just flashing cm-7-20120902-NIGHTLY and was able to flash vorkkernel sucessfully. I again ran into the browser problem + it also duplicated corrupt copies of all my music files into the sdcard again and again, and tried my best to once again figure out how to properly edit vold.fstab and build.prop, with many unsuccessful attempts, I end up making my internal SDCard unreadable, so I tried to revert the files back to their original by looking in the rom zip and using those files. It did work somewhat, I was able to read my exeternal sd card, but the internal couldn't mount, I was so fed up. I was gonna reflash cm-7-20120902-NIGHTLY so I rebooted into recovery and then I decided not too so I tried to reboot, but I got stuck in a boot loop (phone always booted into CMW recovery mode) with an error
E:can't mount cache/recovery/command
E:can't mount cache/recovery/log
E:can't open cache/recovery/log
E:can't mount cache/recovery/last_log
E:can't open cache/recovery/last_log
I'm unable to get into internal sdcard where my backup is located, however I am able to access external sdcard. I am also unable to wipe cache, I tried to flash cm-7-20120902-NIGHTLY (wipe data/factory reset, wipe divik cache, install zip) again but it doesn't do anything. I have also formatted /sytem with success but unable to format /data and /cache of course.
I'm not really concerned too much about the data on phone, I can get all of it back except some pictures and video I don't value too much. So wiping everything is an option, but would waste a bunch of my time if I didn't have to, but I'm not sure how to do it because I can't find a stock rom for fido (I am aware of the stock roms posted here on this site, but mine is dead). I actually am no longer with fido and don't use this phone as a cell phone anymore, so do I really need the offical stock fido rom or can I download the european one? I
Sorry I have googled this for about 8 hours before posting here and I can't find any clear cut solutions, all I find is similar problems and outdated links.
EDIT1: Cannot boot into S/W mode screen just goes black and shuts off
EDIT2: Found a old backup in my computer that I had transferred to my SDCARD which doesn't work because it says MD5 mismatch!
EDIT3: Was able to restore backup but now it says error formatting /data (I also can't mount /data /cache /emmc, but can only mount /system
and /sdcard)
Thanks
UPDATE
I Can't boot into S/W mode, I take out battery, hold vol down button, then plug phone. What happens is the white logo boots, then goes black and shuts off. I'm running out of options...
PeterSK said:
I Can't boot into S/W mode, I take out battery, hold vol down button, then plug phone. What happens is the white logo boots, then goes black and shuts off.
Click to expand...
Click to collapse
Try this.. if u have a custom ROM installed.. plug the phone in>reboot phone from power menu> as soon as phone turns off press and hold volume down.. this worked for me before.. hope it helps.. remember only if on a custom ROM
Sent from my LG-P990 using xda app-developers app
darenb4 said:
Try this.. if u have a custom ROM installed.. plug the phone in>reboot phone from power menu> as soon as phone turns off press and hold volume down.. this worked for me before.. hope it helps.. remember only if on a custom ROM
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I can't load my rom I'm stuck in a CWM boot loop. I have tried rebooting from there but the phone never really shuts off.
PeterSK said:
I can't load my rom I'm stuck in a CWM boot loop. I have tried rebooting from there but the phone never really shuts off.
Click to expand...
Click to collapse
Yep nv flash would be the answer lol.. glad u got it sorted
Sent from my LG-P990 using xda app-developers app
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
(For reference, I have a MAG2GA FW v6 dated 10/2012) -- yes, I have access to CWM and ADB
Had verygreen's CM11 (1-18, eMMC install) on my HD+ and it was working without any major issues -- came back home one day and the screen was frozen. Did a power + N button reboot, and now the CM logo on boot spins incredibly slowly (completely hanging at several points). After a few minutes it will either bootloop or get into CM11 -- if it does make it into CM11, the system will be very unresponsive and eventually reboot on its own [no matter what I select].
Booted into eMMC CWM 6.0.4.6, formatted /system, /data and /cache and reinstalled CM11 1-18 + PA GAPPS. On reboot, I see the exact same behavior (slow/freezing CM logo, eventual bootloop). When it does sometimes make it back into CM, I see my widgets / wallpaper for a brief moment before it bootloops again, implying that my format/wipe in CWM did nothing...?
I then booted into bokbokan's CM10.1 I had on a MicroSD lying around -- I installed the eMMC brick check app from there (which checked out fine, including a test on the full 16gb). I'm trying to do an ADB push now of leapinlar's NookHDplus-factory-2.2.0-plain-stock.zip so I can install it and try to get it replaced under warranty but it either [tried both SD-based CWM and eMMC-based CWM] :
1 - hangs forever (implying some issue with my internal storage)
2 - says transfer complete, but when I navigate to /sdcard/0/ I don't see it
3 - the one occasion I did manage to transfer stock back over and the system could actually see it, I got a '"Failed to retouch '/system/lib/libemoji.so'" error when installing (and yes, I'm formatting /system every time)
In additional, the eMMC CWM behaves very erratically, sometimes taking over a minute to navigate through folders or respond to a volume button click. Pretty sure my internal storage is damaged somehow.
It seems like no matter what I do in CWM, my HD+ continues to try to reboot back into my old CM11 installation. Any thoughts or ideas on what I can do next?
Edit: Okay, so using a 4GB SD card image, I tried to erase /system, /data and /cache and flash cm 10.1 and twrp just to see if anything would stick. Removed the SD after flash, reboot, and the system goes right back into CM11 boot loop. Trying to reboot into TWRP brings 6.0.4.6 back up -- looks like nothing I'm doing will stick. Brought up ADB shell and ran "mke2fs -T ext4 /dev/block/mmcblk0p8" to wipe system, still reboots back into CM11 no matter what I flash in SD CWM.
226 68565523
I have the same issue, but on my HTC One S. My eMMC chip: MAG2GA.
Looks like its TRIM brick.
I can't wipe or install other rom, and recovery allways say "E:/can't mount /data"
My system works well, but after reboot the system returns to its previous state and all new data (SMS, calls, files) delete.
All it happens after 27 January after installing nightly update for CM11
Leapinlar has the knowledge and info on fixing the partitions. Might be just refreshing them up might fix it. Trim bug can also cause physical damage... don't know which that could be here if its it.
I've played a few minutes with the 29th(?) nightly and had not received this problem though that build had quite a few issues for me. So Korshun could be on to something.
Just swapped it instead -- seems like physical TRIM damage, given that nothing I changed [even writing 0s to disk] would stick.
After my succesfull CM 13 install attempt and 1 day of use, when I turned it off and turned it on again, it would boot normaly, the CM 13 logo keeped pulsating, but after some seconds, it suddenly stopped pulsating and crashed. Is there a way to solve this, or do I just flash my backup (before CM 13 install)? Preferrably, I wanted to keep my apps.
Did you change anything on system partition? If you haven't done anything then it's hard to say that it can be fixed without a data wipe, but you can try to wipe system, cache and dalvik-cache partitions then flash CM and Gapps.
I wiped the system, cache and dalvik-cache, flashed CM and Gapps. It then booted into CM 13, the logo appeared for a few seconds, it showed the "aindroid is starting - optimizing app (2 of 19)" screen, it went all the way through the 19 apps and then it turned off, I rebooted it and it did the same logo crash thing.
UPDATE: it seems that on the logo crash, technically the device is still turned on, cuz' i leaved on that state for a while without pulling off the battery (the only way to get off that "state"), pulled off the battery, rebooted into TWRP and the battery had decreased
So the problem is probably in data partition. Unless you have a clue to what to erase using recovery"s file manager, adb (if it's enabled) or a previous backup then I think you will have to wipe data. With adb you can try to use logs to search for the cause.
PS: do you have a microSD inserted in your phone? Did you try booting without it?
After I runned some tests, apparently the cause of all this was the microSD that I formatted to be an Adopted Storage. It crashed whenever I put it on the device. Now just gotta find a way to format the microSD for me to get it back (Already on my way, any help would be appreciated).
Here's the correct tool to format a SD card:
https://www.sdcard.org/downloads/formatter_4/
Don't use fast format, use the configuration that tests the whole card memory.