Getting past N7000 LM5 bootloop without wiping - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting
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
Related
[SOFTBRICK]
I did not flash my phone before, I was using samsung original ICS rom all these while until 2 days ago I decided to flash it with cyanogen nightly build cm-10.1-20130123-NIGHTLY-n7000.zip. I used CWM.zip(I think is a touch version) recovery to update my phone. I did not do a backup. My phone managed to show the cyanogen logo after that with a turning wheel but it just stuck there for 10min. I then realized I have to clear /data, /cache, and the dalvik cache. did so in recovery mode, but now it no longer showing the turning wheel, instead just stuck at the samsung n7000 text logo screen. I then used odin to flash the phone with a malaysian original rom I downloaded from the hotfile.com (http://forum.xda-developers.com/showthread.php?t=1424997). Now it fall into a restart cycle, still stuck at the samsung text logo screen, just that it restart after around 20sec. I then boot into recovery mode(This time I'm using recovery-clockwork-6.0.1.2-n7000.zip) and clear /data, /cache, and the dalvik cache, but no avail. I dont think I bricked it yet since I still manage to go in to the download mode and recovery mode. but no matter what I flash it always stuck at the samsung n7000 text logo screen. Can someone further guide me what should I do? Thanks. (I'm very calm btw)
Flash a gingerbread rom with Odin.. After that go to recovery and Wipe/factory Reset... Do not flash anything else.. Just the stock rom and use stock recovery.. Do not use custom kernels nor cwm or anything else.. Everything stock Tapatalking on my n7000
msedek said: Flash a gingerbread rom with Odin.. After that go to recovery and Wipe/factory Reset... Do not flash anything else.. Just the stock rom and use stock recovery.. Do not use custom kernels nor cwm or anything else.. Everything stock Tapatalking on my n7000 Click to expand... Click to collapse Hi msdek. I just flashed it with a GB rom(N7000DXKL3_N7000OLBKL2_XME to be exact). right after finish, I got this on my screen: Code: -- Copying Media fies... -- Wiping cahce... Formatting /cache... Cache wipe complete. -- Updating application... E:failed to mount /data (Unknown Error : 0) E:install_application_for_customer: Can't mount /data your storage not prepared yet. please use UI menu for format and reboot actions. copy Application failed. -- Applying Multi-CSC... Installing Multi-CSC Copied the packages. Copied the default_wallpaper file. Copied the power on/off animation files. Applied the CSC-code 'XME'. Successfully applied multi-CSC. UPDATE: still the same. stuck at the GT-N7000 text screen (instead of few ten seconds, this time is for few minutes) before it auto restart and repeat the process again.
choongyouqi said: Hi msdek. I just flashed it with a GB. right after finish, I got this on my screen: Code: -- Copying Media fies... -- Wiping cahce... Formatting /cache... Cache wipe complete. -- Updating application... E:failed to mount /data (Unknown Error : 0) E:install_application_for_customer: Can't mount /data your storage not prepared yet. please use UI menu for format and reboot actions. copy Application failed. -- Applying Multi-CSC... Installing Multi-CSC Copied the packages. Copied the default_wallpaper file. Copied the power on/off animation files. Applied the CSC-code 'XME'. Successfully applied multi-CSC. UPDATE: still the same. stucked at the GT-N7000 text screen for few minutes then auto restart. Click to expand... Click to collapse Try flashing and wiping again.
Seems like somehow some partition it's corrupted..... Re download a different gb rom make sure it's stock.. And flash again then wipe.. If that does not works, we could discuss another solutions Tapatalking on my n7000
I flashed with GB N7000DXKL3_N7000OLBKL2_XME rom the first time. I followed the latest advices, I downloaded N7000DXKK1_N7000OLBKJ6_XME (which is an earlier GB version to the former 1 I mention). This time, there's no error prompt after flashing. I then boot into recovery mode and wipe data/factory reset it. Everything looks ok, I then restart the phone. Again, it stuck at the samsung galaxy note GT-N7000 text logo screen for 6min before it reboot itself and continue the cycle. I boot into recovery mode and clear cache and try my luck again, and still the same. Hmm..
Once try flashing the same rom you flashed last. But this time use a PIT file too. http://d-h.st/FVh Choose in odin where it says PIT and then also make sure repartition is ticked.
nokiamodeln91 said: Once try flashing the same rom you flashed last. But this time use a PIT file too. Choose in odin where it says PIT and then also make sure repartition is ticked. Click to expand... Click to collapse Hi Nokia, did as per your suggestion. flashed N7000DXKK1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 together with Q1_20110914_16GB.pit. Screenshot: dl.dropbox.com/u/6893697/odin_flash_pit.png It rebooted itself after flashing and showing all the installations, then it rebooted itself again stuck at the GT-N7000 text logo screen for 1min and reboot itself again, then I waited for 6min at the same GT-N7000 text logo screen and the phone rebooted itself again..
choongyouqi said: Hi Nokia, did as per your suggestion. flashed N7000DXKK1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 together with Q1_20110914_16GB.pit. Screenshot: dl.dropbox.com/u/6893697/odin_flash_pit.png It rebooted itself after flashing and showing all the installations, then it rebooted itself again stuck at the GT-N7000 text logo screen for 1min and reboot itself again, then I waited for 6min at the same GT-N7000 text logo screen and the phone rebooted itself again.. Click to expand... Click to collapse Did you wipe? Bootloops will occur if you do not wipe.
warfareonly said: Did you wipe? Bootloops will occur if you do not wipe. Click to expand... Click to collapse I wiped for the earlier flash, not the current. but both are the exact same rom. Anyway, I just did a wipe cache, then select wipe data/factory reset, and reboot the phone again. Still the same. stuck for 6min and reboot. I understand usually full wipe/first boot we have to wait longer for the booting, but am I suppose to wait at the N7000 screen for few minutes or there is another screen to wait?(perhaps the boot animation screen with colorful samsung logo) Another question is, is wipe data/factory reset consist of wipe cache? (if that so probably I dont need to do twice everytime) Thanks.
Do you have warranty? If you have I advice you to take it for repairs, if not then Get abbys kernel.. Flash it via Odin (Odin version) and go recovery (red cwm) once there perform all kind of wipes and formats(don't touch efs partition) then reboot Tapatalking on my n7000
my warranty expired on 2nd Jan. will flashing the abyss kernel void anything (I heard there's a counter or something in our device)? if that so, could anything be done before attempt flashing the device with abyss kernel? Currently I managed to access adb shell while in the recovery mode and able to su root. do you think any information inside is helpful to understand my current problem? here's a df -h Code: Filesystem Size Used Available Use% Mounted on tmpfs 404.1M 76.0K 404.0M 0% /dev /dev/block/mmcblk0p9 838.6M 811.7M 26.9M 97% /system /dev/block/mmcblk0p7 196.8M 4.2M 192.6M 2% /cache /dev/block/mmcblk1p1 7.4G 3.0G 4.4G 41% /sdcard
As your warranty expired there's nothing to worry about... It will only increase a binary counter Wich you can easily reset later once you boot to android.. Tapatalking on my n7000
I flashed it with abyss kernel. it comes with cwm 5.8.1.5. used that to wipe everything. still the same...
One more try. Can you copy kingdroid v8 rom in your external sd card (using some other means). Install it via abyss kernel. Good luck. (kd8 is my personal choice, tho other custom roms are equally good, read kingdroid thread fully) Sent from my GT-N7000 using xda premium
I just tried the kingdroid v8 rom. it hanged while installing/tweaking "EXT4 performance tweak" at 40% and after few minutes the device restarted itself. Come to think about it, now I got a question: My device always auto restart itself when I perform "wipe data/factory reset" every time. I wonder now, is this normal? or actually it's wiping half way and it hit some exceptions and the device restarted itself?
In recovery, go to mounts and storage and choose format/system, data and cache. Any of there commands getting stuck? Of not then try to install a custom rom again.
nokiamodeln91 said: In recovery, go to mounts and storage and choose format/system, data and cache. Any of there commands getting stuck? Of not then try to install a custom rom again. Click to expand... Click to collapse hmm... formating /cache and /system take immediate effect. formatting /data take unusual amount of time (around 6-8min) but eventually it shows "Done." and I assume is successful too.
choongyouqi said: hmm... formating /cache and /system take immediate effect. formatting /data take unusual amount of time (around 6-8min) but eventually it shows "Done." and I assume is successful too. Click to expand... Click to collapse Did you install the rom again after formats? What's the situation now? Same?
I'm getting worried.. Because looks like EMMC it's partially bricked.. Might need to run the pit file method to scan for bad sectors Tapatalking on my n7000
[Q] Is my internal storage dead?
I am trying to get my Son's Captivate back up and running.. while it has no phone service, he uses it all day long. It was running Cyanogen Mod 10 .. he sat it down to eat.. when he came back the screen was black with the buttons lit up and no response. He did a battery pull to restart it and it came back looping Error to mount /SDcard and a count down. I got it into recovery and am not able to mount /data or /emmc. And it is failing to install a ROM from zip. I tried using "I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click" and it runs through the process.. flashing Kernal, Modem, FactoryFS, DBDataFS and CACHE successfully.. then the device reboots and goes through a few things on screen, and fails on Formatting /data ( E:format_volume: rfs format failed on /dev/block/mmcblk0p2 ) but everything else says success. Hitting "reboot system now" says that it cant copy the log because of failure to mount /emmc.. then reboots to the same recovery and does the copy of Media and Appling Multi-CSC (their spelling mistake not mine) over again. Flashing back to a CWM 6 recovery and still no mounting of /data or /emmc. And it just boots right into the recovery. I tried --repartition with Heimdall and it said it uploaded the S1JE4.pit fine. Same things.. So is there anything I can to to test the internal storage to KNOW if it is faulty or is there anything else I can do? I would really like to get this thing working again for my little dude.. he is so sad as all heck to not have his Android Buddy. :crying:
Seems likely internal sd may be dead, particularly if someone ran ICS on it at some point. If you have an external sd card, at least 8GB, this thread may help- http://forum.xda-developers.com/showthread.php?p=21439417 you could use cm10.1 instead of the ICS rom mentioned in the thread. Sent via Monty Pythons Flying Circus
[Q][SOLVED][HELP] /system, /data not mounting
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
[Q] GT-P1000 Stuck in bootloop
Hello All, Long time lurker, first time poster (and, as usual, asking for help) I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop. At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756 However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above : Code: <3>[ 4.802004] mmc0: error -110 whilst initialising MMC card (Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk) Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.) I guess what I am asking for is: a) Is there a way to recover from this without a complete device wipe? b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and c) If so, is there a way to retrieve all this data to a PC prior to wiping? I have also attached the adb logcat file recorded during the bootloop. Thanks All!!
Resolved I guess this forum is not quite as alive as some of the others, which makes sense considering the age of this device. In any case here is a quick summary of what I went thru to successfully get the device working again. (and I still have all my pics/videos ) a) Answer to my first question below - After a loooot of googling, I couldn't figure out a way to recover without a wipe. b) Answer to my second question - You will NOT lose data on your internal SD card when you do a wipe from (stock) recovery. c) Answer to third question - There may be, but I was unable to figure it out. I'm fairly certain you can mount the internal SD manually from ADB if you have root and attempt to pull your files to your PC, but my device didn't have a rooted kernel, so I couldn't quite get this done. Anyway, my other issue was that my Stock recovery was unresponsive as well. On selecting the wipe option for example, the screen would clear itself of all text and just display the Android w/ Exclamation background. I attempted to flash CWM recovery based on the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2430190 However, I ended up with a corrupt screen when attempting to access this new recovery. (Don't know - May be because of improper rooting?) I was able to successfully restore the device by flashing the stock recovery and ROM based on this thread http://forum.xda-developers.com/showthread.php?t=1133590 ,following the instructions for un-softbricking . When I booted into recovery and attempted to wipe/factory reset, I got an error. Code: rfs format failed on /dev/block/stl10 There was an additional step I had to take, which is clarified further below in the same thread. http://forum.xda-developers.com/showthread.php?p=27979493#post27979493 , which is to flash dbdata as well. Doing this let me successfully wipe the device, which in turn let me finally get out of the damn bootloop. Anyway, I hope all this helps someone. Thanks for being a great resource as usual XDA! :good: Dagrat3One said: Hello All, Long time lurker, first time poster (and, as usual, asking for help) I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop. At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756 However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above : Code: <3>[ 4.802004] mmc0: error -110 whilst initialising MMC card (Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk) Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.) I guess what I am asking for is: a) Is there a way to recover from this without a complete device wipe? b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and c) If so, is there a way to retrieve all this data to a PC prior to wiping? I have also attached the adb logcat file recorded during the bootloop. Thanks All!! Click to expand... Click to collapse
Hi, guys.......new to the process....rooted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!
[HELP PLEASE] NEED HELP WITH make_ext4fs
Hello. So i have a S3 LTE with possibly(?) an insane eMMC. Long story short: phone bought back in dec 2012. Changed battery twice. Last battery started acting up, lost all power, next thing i know phone is in permanent bootloop. Odin won't repartition the phone (idk why) nor can it flash a full firmware, getting stuck on SYSYEM flash, but can flsh recoveries. After fiddling around with recoveries, i finally flashed TWRP. What i found out : /cache, /system, /data, /sdcard and /tombstones couldn't be mounted (invalid argument). After wiping everything with make_ext4fs, everything works fine, except for /tombstones, which can't be mounted. What i have seen from the logs is that twrp doesn't wipe /tombstones as well, so there was no way of getting it to work. Full story here http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-bootloop-mount-data-sdcard-t3379377 WHAT MY PROBLEM IS: I need somebody to tell me the parameters for make_ext4fs in order to wipe /tombstones as well, as it seemed to work flawlessly with the other folders. UPDATE: I managed to wipe /dev/block/mmcblk0p11, which mounts in /tombstones. used rm -fr, then mkdir for the tombstones folder. Everything mounts just fine now. Will reflash and post an update. UPDATE 2: Phone still won't work with odin. i flashed amcha with twrp. Boots just fine, but 10 seconds after boot finishes, phone freezes and won't respond to button presses. Any ideas?