I loaded jacheroskivr1.5 last night and everything was fine(even the leds were working) all of a sudden it cuts off, it takes a few minutes for it to come back on if at all, then it freezes so i wiped the phone now its bootloopin..
wtf happened and wtf do i do?
Did you re flash the rom after? Maybe try repartitioning your sd or atleast wiping your ext2/3.
I can't because im at work right now, but i don't understand what actually happened. It was working fine all day and then it just started cutting off on its own, not even resetting but just cutting off all together.
I don't think i should've wiped it..
so f'n tired of repartitioning my sd card casue with all the music/photos/vids its takes up to an hour for me to transfer it all back from my back up...
So repartition, and flash rom again.. got it.
Yea I have no idea why it went screwy on you but my guess to fix it would be wipe, repartition, then flash. Someone else here with more knowledge might know why it happened to begin with.
Coopaman said:
I loaded jacheroskivr1.5 last night and everything was fine(even the leds were working) all of a sudden it cuts off, it takes a few minutes for it to come back on if at all, then it freezes so i wiped the phone now its bootloopin..
wtf happened and wtf do i do?
Click to expand...
Click to collapse
Don't wipe on hero, ever. It will always give you a bootloop.
Here's what I do if I find myself in a bootloop.
Wipe the EXT2/3 partition from console
(press enter)
#
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# rm -rf /system/sd/*
# reboot recovery
wipe in recovery
repair ext partitions (twice if the first time fails)
reflash.
Always fixes any problems I have.
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
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
Hey,
I have an i9000 (Obvious) which, I put in the freezer (please don't ask me why). So, the problem is I had put it at a Live OC of 120% and opened antutu benchmark and put it in the freezer. I know that my phone hangs if I open some heavy apps at 120%. So, that is what happened with the phone while benchmarking. So I had to force shutdown and when I turned it on, it first showed me the error of "Process System is not responding". I clicked on wait. Well, the Status Bar wouldn't turn on and I assumed that the System UI was retarded at the moment. So I factory reset and flashed ROMs multiple times. BUT, I lost access to /data and /system. So I tried restoring, and it did Restore but didn't work, same stuff happened.
So, Ultimately I flashed Stock ROM and tried flashing another ROM again but no. No access to /data or /system. I did this multiple times until I realised I have access to /system and /data and am able to mount them via the CF-ROOT Kernel and that the Stock ROM works fine. Please help!
EDIT: I just forgot to format /system and /data before switching from GB to KK
This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.
**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999