Related
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
So I was backing up a rom in TWRP recovery when the phone randomly rebooted. I went back to recovery to see if I could do a backup and now I can't mount the /data directory at all. Whatever I try to do when accessing the directory, it says unable to mount. I tried using the file explorer and it shows an empty directory. Other screens show internal storage as 0mb. I've also tried using CWM but same, can't mount data. I already wiped /system so I can't reboot, and I can't install a rom w/o access to /data (same thing when doing adb sideload).
Any ideas how to get this fixed?
Thanks!
EDIT: Somehow right when I posted this question, I got access to /data again... -_-
EDIT2: Same problem again, tried side loading a rom and can't access data anymore
Same problem again, tried side loading a rom and can't access data anymore... any ideas?!?
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Sammy321 said:
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Click to expand...
Click to collapse
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
bitdomo said:
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
Click to expand...
Click to collapse
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Sammy321 said:
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Click to expand...
Click to collapse
Download AIO-toolkit from the developement forum. Install itt, and install nvflash drivers with it.
At the main screen select option 2, and then select option 2 again. Follow teh instructions on the screen, and select TWRP 2.5.0.0 to be installed, or cwm 5.0.2.8, both have working mass storage.
(6.0.3.1 has broken massstorage and adb interface. I think you installed cwm 6.0.3.1 through rom manager, if it that true you are on old bootloader.)
bitdomo said:
(6.0.3.1 has broken massstorage and adb interface.
Click to expand...
Click to collapse
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Sammy321 said:
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Click to expand...
Click to collapse
Can you try twrp 2.5.0.0?
bitdomo said:
Can you try twrp 2.5.0.0?
Click to expand...
Click to collapse
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Sammy321 said:
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Click to expand...
Click to collapse
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
bitdomo said:
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
Click to expand...
Click to collapse
YES! I thought factory reset would delete the internal SD, so I didn't even consider that, but it worked like a charm! Thank you so much for caring and helping! You just made my week! :highfive:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
N0he said:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
Click to expand...
Click to collapse
+1 on this, I am seeing the exact same behavior. After running a while there seems to start cascading failures of apps. Browser stopped, google play most common, MTP host stops...
TWRP hangs on the splash screen , Ive tried all (3) 3.0.2. variants.... I am running the NDE63P 7.1 build...
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
N0he said:
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?).
Click to expand...
Click to collapse
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
N0he said:
Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Click to expand...
Click to collapse
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
mikeataol said:
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
Click to expand...
Click to collapse
Yes, all these recoveries clear the boot count, but only after they finish booting. When TWRP doesn't finish a full boot, the system is still marked for recovery.
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
amaces said:
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
The rom boots and runs normally from emmc, no signs anywhere that there is corruption, except subtle hints... (change settings on an app, clear data and cache on an app, and on the successful reboot into the rom those changes don't seem to have stuck.
mikeataol said:
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
Click to expand...
Click to collapse
Right, CWM is one of the recoveries on the SD card. No recovery that supports F2FS and wants to access /data will work at this point; it just happens that CWM can skip that step.
@amaces and as you suggested, booting cwm from the card
reformatting userdata (make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata )
allowed TWRP to work again just ducky.....
Thank you for taking your time to help me!
amaces said:
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
amaces said:
Sounds like your userdata partitions got corrupted; F2FS?
Click to expand...
Click to collapse
I did not know what F2FS is, but from googling, I assume it is something the user would have to manually set, which did not happen in my case.
amaces said:
Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
Click to expand...
Click to collapse
Is it possible to do so without access to recovery? Can you give me some directions to where I can get the info to be able to do so? Any good posts on that, or any keyword I could research around? Would fastboot work? I'm not too sure where to start.
amaces said:
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
Click to expand...
Click to collapse
From what I have seen in the forums, I assumed having a "rescue microSD card" would make flashing ROMs fairly save, but I guess I'll stick to stable builds from now on then. But then again, doing stupid stuff does make me learn new things, and I was willing to risk bricking my tablet.
Anyways, thank you for helping me and for all your work to keep the Nooks alive!
N0he said:
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
Click to expand...
Click to collapse
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
mikeataol said:
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
Click to expand...
Click to collapse
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
I was able to do this while stuck on a TWRP splash screen
this will reset your file system back to ext4, (and wipe it) . if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
the NBD90Z 161019 build is working very well for me....
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
So, it never presents the external recovery menu, where you could select CWM before? You might need to format and re-build that SD card if that's the case.
mikeataol said:
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
Click to expand...
Click to collapse
Yes, do try this even with the eMMC recovery; ADB should be working, and you might be able format userdata if it was ext4 before. With some F2FS corruption, it's less likely to work, since it'll say /data is in use, and you can't unmount it.
mikeataol said:
if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
Click to expand...
Click to collapse
I think you should stick to ext4 while testing these issues. I did notice more corruption with F2FS on the new kernel, but didn't have time to investigate yet.
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
N0he said:
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
Click to expand...
Click to collapse
I think you should format it mkfs.ext2 then, ....
that should allow you to boot into the internal recovery and then convert it to ext4
Thank you both for taking your time to help me!
I'm going to summarize what I did to get my tablet back to working:
1. Having the tablet shut down because of low battery seems to have been the reason why I could boot from the microSD card again. So what can be done in that situation is to boot into the emmc recovery (which gets stuck at the splash screen) and then just leave it on until it shuts itself off. Then charge it up again and try to boot into the microSD card. Worked for me.
2. To then actually fix the problem, make sure to have CWM on the microSD card. There are at least two ways to get the tablet to work again:
- Boot into CWM, then connect to a pc with adb, reformat with adb shell using "make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata" (didn't work for me, as it couldn't find make_ext4fs)
- Boot into CWM, install stock recovery, use it to factory reset the tablet, boot into stock ROM once to make sure, boot into CWM, flash all your stuff.
I have my magisk.zip in my sdcard/download but it's not showing on twrp (Internal storage 0 MB)... I tried wiping cache and data but it failed... I made sure that "Install ZIP" is selected. I'm using this twrp (color is orange instead of blue).
I'm using SM-J730F (used to be SM-J730F/DS but because of bootloop I had to install SM-J730F firmware, everything seems to work as it should).
I successfully rooted my other android phone but it's a lot more complicated for this model...
Is there any solution for this problem?
Edit 1: I tried with this solution by "format data" and then copy magisk.zip to sdcard/download, formating worked (Internal storage was't 0MB anymore) but when I connected with PC and opened my mobile folder was completely empty... It was empty before and after formating when accessing mobile folder on PC while on twrp (access was allowed the first time system booted) but in home screen mobile files can be accessed on PC. I'm starting to hate SM-J730F...
Edit 2: This solution worked (I can transfer files directly from my PC while on twrp) but my whole OS got wiped as well and had to flash it with odin... Which returned me to square one (no twrp)...
Well, i had same problem, got around it by flashing twrp in adb
markoscekic said:
Well, i had same problem, got around it by flashing twrp in adb
Click to expand...
Click to collapse
I just installed this kernel
Dragonknigh said:
I just installed this kernel
Click to expand...
Click to collapse
try to install via Magisk Manager app
Dragonknigh said:
I have my magisk.zip in my sdcard/download but it's not showing on twrp (Internal storage 0 MB)... I tried wiping cache and data but it failed... I made sure that "Install ZIP" is selected. I'm using this twrp (color is orange instead of blue).
I'm using SM-J730F (used to be SM-J730F/DS but because of bootloop I had to install SM-J730F firmware, everything seems to work as it should).
I successfully rooted my other android phone but it's a lot more complicated for this model...
Is there any solution for this problem?
Edit 1: I tried with this solution by "format data" and then copy magisk.zip to sdcard/download, formating worked (Internal storage was't 0MB anymore) but when I connected with PC and opened my mobile folder was completely empty... It was empty before and after formating when accessing mobile folder on PC while on twrp (access was allowed the first time system booted) but in home screen mobile files can be accessed on PC. I'm starting to hate SM-J730F...
Edit 2: This solution worked (I can transfer files directly from my PC while on twrp) but my whole OS got wiped as well and had to flash it with odin... Which returned me to square one (no twrp)...
Click to expand...
Click to collapse
Same problem, fixed! flowing this link
https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
Just save my day!
I fixed this by removing i.e. the password that locks my device i.e. no password
ADB Sideload