My phone died today and decided that it would like to perform a boot loop upon being turned on again. I'm just wondering if there's a way to save all my phone numbers and pictures off of it before using Odin to wipe.
The odin one click will just reformat the /data, /cache , and /system partitions leaving your sdcard alone.master clear I'd what wipes the sdcard. But if you have clockwork recovery you can go to mounts and storage and mount usb storage and copy it all to your computer before you odin
you might be able to mount usb storage with stock recovery as well, idk I never run stock so am unfamiliar with its options. Check though.
+1 to what studacris said. Using odin won't delete files. As far as phone numbers go, I would just sync them with google contacts.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
If u have data backed up in recovery, I would recommend formatting boot and system partitions, and restoring only those partitions under advanced restore options. Worth a try before u went ahead with a cleanup process. This could help u get ur phone up so u can backup ur contacts.
Like people said above, pics would be on SD card and would be safe.
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 got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Venrun said:
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Click to expand...
Click to collapse
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Ok. At least I got my biggest problem now.
I think my roblem is wipe data/factory reset does not do job it is supposed to do.
I still see folders and files in internal memory after factory reset. I think that is why install aborts and crashes even after successful install.
I think my problem is that wipe data/factory reset does not do its job
It gives me message it is formatting data cache and stuff. And last day they gave me data wipe complete. But the problem is, in internal memory, I can still see old folders and old files.
I think he should be gone if it is formatted. Where do I get the meaning of factory reset wrong?
Its not what is wrong with me. And how can I make factory reset work
And second question is that I tried to install B&N original operating system from cwm-based recovery. I tried a few different versions of
nookHDplus-factory-2.1.1-plain-stock.zip
However it always fail to install. Install aborted for some reason.
Thanks. It seem helpful.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Venrun said:
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Click to expand...
Click to collapse
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
thanks
leapinlar said:
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
Click to expand...
Click to collapse
trying it. hope it works.
did not work
for about deleting internal data, I went to 'mounts and storage'. used 'format /sdcard' and 'format/ data and/ data/media (/sdcard), but still has stuff in internal memory.
and to my surprise , I have been using CWM-6028. so far. I thought its name was 'NookHDplus-bootable'.
hell. stupid me.
Anyhow, CWM-6028 has been giving me troule
so, I would try other versions.
So far, I have done
1. made boot sd by burning image.
2. copy 'NookHDplus-factory-2.1.0-plain-stock' files and other versions.
3. Insert SD in device and boot CWM.
4. choose zip from sdcard.
5. install factory plain stock.
then I get message 'Failed to retouch 'system/lib/libemoji.so' (WTF is libemoji? and it is always this same file.)
E: error in sdard/nookHDplus-factort-2.2.1-plain-stock.zip(status7)
Installation aborted.
hell. And I tried every factory zip.
Am I doing something wrong?
Failed tp retouch '/system/lib/libemoji' is error message I get
Everytime I tried to install factory stock.
I tried every version of stock files. And I tried all CWM. And even tried TWRP, but it is always the same message what the hell is that emoji?
And what can I do with it?
What frustrates me the most is the fact that it installed 99% in a minute without trouble and stays there 410 minutes until it fails to install. It's driving me crazy
Does CM makes Factory reset by power button and home button does not work either.
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
It is possible you have a bricked emmc. When bricked it looks like it is writing but is really read only and nothing takes. If you still have media files after a successful format data and datamedia then it is bricked. Probably best to get rid of it. You can buy a refurbished unit very cheaply these days.
Sent from my SM-T707V using XDA Premium HD app
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
Assuming that your EMMC is shot, you can try running off SD card this no-emmc version of CM11 ROM: https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/. It's best to use a card with fast randomized block read/write (which is what Class 4 cards are typically best at).
Thanks guys. By the way, what is emmc?
Is it part of CM software?
Does not sounds like hardware.
If I had factory resetted a day earlier, I would not have had problems.
Well. That is the way it is.
I finally kind of got nook working. I am running it on SD card now.
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
digixmax said:
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
Click to expand...
Click to collapse
Thanks a lot. That sounds I can do it.
how you did it
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Please tell how you made SD card work.
thanks.
rkgarg2000 said:
Please tell how you made SD card work.
thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Please confirm if my problem has any other solution
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting. Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
thanks.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Click to expand...
Click to collapse
rkgarg2000 said:
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting.
Click to expand...
Click to collapse
Does it boot-loop to recovery?
If so, see http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for potential causes and solutions.
Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
...
Click to expand...
Click to collapse
CWM v6.0.4.6 is not compatible with CM10.x, you need to flash back to the CWM version you previously used.