Develop Bugs

[Q] crashed and now can't format /data (and other wierdness)

Just got a brand new N7100 today. Do my usual thing as with all my phones, flash CWM, root, flash custom rom (Omega v8.0). Changed kernel to Note2Core (OC, NOT EXTREME VERSION WITHOUT FSYNC), was running for a bit then it rebooted itself.
After reboot, phone won't run, so I go to do a full system wipe. Except now I can't wipe /data. Tried 3 different CWMs including TWRP (TWRP doesn't even start, just shows load screen then reboots).
Flashed stock ROM with ODIN including .PIT but the /data isn't being cleared, I can't clear it in any way. Only way to get the phone working now is stock ROM through ODIN but it boots up with a bunch of messed up stuff and I can't factory reset.
I have tried scanning for EMMC Brickbug but there are no errors. This one has got me stumped, I know my way around recoveries and android etc. but can't for the life of me figure out what I can do to fix this.
Don't really want to send in for warranty as I probably have a flashcounter (I will try to flash a rooted ROM through ODIN and triangleaway..)
Hoping since there's no EMMC brickbug triggered from the scans, that there's some way to fix this. I thought flashing PIT would wipe the /data partition but obviously not.
Any ideas? Would be most appreciated.
Thanks

I'm having the exact same issue on my N7105. It was working fine for days after flashing, then all of a sudden it rebooted and all user apps were gone. When I tried to reinstall from TB, I got an error on each app that it had stopped working.
I tried to reflash the ROM with full wipe, but CWM restarts when it tries to wipe /data.
I'm using this ROM http://forum.xda-developers.com/showthread.php?t=1985200 with Note2Core v2.10.

there is probably an issue with the internal sd card(hardware part).
or maybe you have done something wrong.
try using adb to format it.

I was finally able to format the /data folder by doing a factory reset, now it works in CWM and flashing a ROM doesn't fail when choosing the full wipe installation.
I'm not sure what the problem was. A faulty internal SD card would still be having this problem and incorrect flash method would show problems straight away, not 5 days later, right?

Hi guys,
I have the same issue, anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?

Wtf this is n7100 thread and forum. How can you get 4.0.x on it
Sent From Samsung's Galaxy Note II Using Internet

i think u guys just hardbricked ur n7100..maybe try to go samsung centre..can try ask for warranty

SGS III L710 Unable to Mount /anything

A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!

I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA

You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.

jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.

Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?

prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!

n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.

prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium

Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium

billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.

Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.

n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.

swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app

I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice

Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol

n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.

I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium

Corrupt Partition, PIT file needed, I think?

I am trying to fix my friends phone. I believe the partitions are out of whack. The data partition is displaying an abnormally huge size as you can see in the attach picture. I have tried ODIN back to stock and can actually get 4.2.2 MDL to load but I encounter issues from there. Its highly unstable. I have tried to install several custom roms off from TWRP, CWM, and OUDHS and not a single one boots. I definitely can't make backups since the partition is so huge. I think I PIT file will solve the problem but it seems like PIT file for TMobile variant is available. Is there any way to extract one? Is there any other way I can fix this?

So far I haven't seen a pit file posted for this device anywhere.
And from my knowledge it is not included in the stock firmware files that we would flash from sammobile.com
What happens when you try to format the partitions in the recovery like that.
I had a similar problem before with my s3 and using twrp and formating the partitions was able to fix it in that case.
When you Odin back to MDL and don't root it right away, how does it work then?

When you say format partition in recovery, I assume you mean wiping the partition. Wiping the partition, although it appeared the procedure completed successfully, the size of the partition did not change. Very strange.
As far as ODIN to MDL, the phone does boot into 4.2.2. Its a little quirky but it works. I can always get it back to MDL. Doing any installing from recovery does not work. He may be stuck with a quirky 4.2.2 system.

Samsung Galaxy Tab 3 7.0 (T210) - Can't factory reset ("make_extf4fs failed")

Samsung Galaxy Tab 3 7.0 (T210) - Can't factory reset ("make_extf4fs failed")
Hi all,
I have a Samsung Galaxy Tab 3 7.0 (SM-T210), last week I updated it to Android 4.4.2 Kitkat using Kies.
But now, the tablet loads, starts downloading updates from Google Play, and after one or two minutes it reboots. All modifications I do are lost, even if I turn off Wifi, after reboot it's on again.
I tried to factory reset the device, but it throws a series of errors:
"E:format_volume: make_extf4fs failed on /dev/block/..."
Does anyone know how can I fix this?

zekkerj said:
Hi all,
I have a Samsung Galaxy Tab 3 7.0 (SM-T210), last week I updated it to Android 4.4.2 Kitkat using Kies.
But now, the tablet loads, starts downloading updates from Google Play, and after one or two minutes it reboots. All modifications I do are lost, even if I turn off Wifi, after reboot it's on again.
I tried to factory reset the device, but it throws a series of errors:
"E:format_volume: make_extf4fs failed on /dev/block/..."
Does anyone know how can I fix this?
Click to expand...
Click to collapse
Not sure if this would be along the same problem as yours but something similar once hsppened to me, not google update reboot but not being able to wipe device through twrp. I found that by going to the mount options first and mounting system etc and then go doing the wipe fixed this. You could also try to repair or change file system if that doesnt work or using the format option as well but be sure to backup anything you dont want to lose. All else fails always could reflash stock firmware via odin and choose nand erase all option.

droseofc said:
Not sure if this would be along the same problem as yours but something similar once hsppened to me, not google update reboot but not being able to wipe device through twrp. I found that by going to the mount options first and mounting system etc and then go doing the wipe fixed this. You could also try to repair or change file system if that doesnt work or using the format option as well but be sure to backup anything you dont want to lose. All else fails always could reflash stock firmware via odin and choose nand erase all option.
Click to expand...
Click to collapse
Sorry. I'm somewhat new to some of the terms you used.
1. twrp. Is this an application?
2. mount options. Which mount options?
3. Repair/change file system. Where? How?
I don care about backup, the device is empty. In fact, my intention is exactly wipe it from any previous content, so it can work with 4.4.2.
I tried reflashing it with odin and heimdall, no success.

zekkerj said:
Sorry. I'm somewhat new to some of the terms you used.
1. twrp. Is this an application?
2. mount options. Which mount options?
3. Repair/change file system. Where? How?
I don care about backup, the device is empty. In fact, my intention is exactly wipe it from any previous content, so it can work with 4.4.2.
I tried reflashing it with odin and heimdall, no success.
Click to expand...
Click to collapse
Sorry i assumed you were rooted and had custom recovery without asking. Twrp is a custom recovery you can use when you root a device. If you are not rooted I would download official firmware for your specific device, one option would be sammobile.com and would be good idea to do this over night as generally it takes awhile to download unless you pay for premium. Then unzip file and use odins ap slot for the file inside. U can choose nand erase all if wanted which should wipe before flashing. Im not sure how many official firmwares are available for yours specifically but may not hurt to have a couple or all handy in case one dont work. When you say no success you mean it just does the same thing as it did with kies or it doesnt flash it completely using odin?

droseofc said:
Sorry i assumed you were rooted and had custom recovery without asking. Twrp is a custom recovery you can use when you root a device. If you are not rooted I would download official firmware for your specific device, one option would be sammobile.com and would be good idea to do this over night as generally it takes awhile to download unless you pay for premium. Then unzip file and use odins ap slot for the file inside. U can choose nand erase all if wanted which should wipe before flashing. Im not sure how many official firmwares are available for yours specifically but may not hurt to have a couple or all handy in case one dont work. When you say no success you mean it just does the same thing as it did with kies or it doesnt flash it completely using odin?
Click to expand...
Click to collapse
My tablet was never rooted. I had problems with it, while it had Android 4.1.2. Did a factory reset and it got better, still I couldn't use FOTA update [after downloading the update and restarting, the device was counting to 25% then saying that there was some problem with the update]. So I used Kies and the update finally worked. But after that, the reset-loop started, and since that, nothing that I tried to do to solve the problem worked.
When I tried using odin, it started the flashing process, but it immediatelly fails.

I need help with unremovable bootloop

So it got into bootloop randomly (didn't install anything new), here is everything ive done since:
Reflashed the rom using twrp
reset the whole thing using twrp by deleting everything
reinstalled the custom rom using twrp
reinstalled the stock rom using twrp
reinstalled twrp
reinstalled stock rom using odin
anything else i can do. The problem is that even i i get into twrp it just goes back to bootloop. Any files that you may suggest could you post them here please to save others the trouble of going to sites and finding broken links. Sometimes the phone goes on into setup but eventually goes back to bootloop within a couple of seconds.

Does the phone reboot by itself when in download mode?

audit13 said:
Does the phone reboot by itself when in download mode?
Click to expand...
Click to collapse
NO it doesnt reboot on its own in download mode. i have fixed it recently but back to square 1 due to it having a failed to mount /efs error. Any ideas?

The flash is successful using Odin? If yes, it is possible that the internal memory chip is damaged.

audit13 said:
The flash is successful using Odin? If yes, it is possible that the internal memory chip is damaged.
Click to expand...
Click to collapse
How do i fix it then?
It keepes showing this error:
faile to mount /efs (operation not supported by endpoint)

So the flashes with Odin failed? Tried flashing the latest stock ROM with a pit file in Odin?

audit13 said:
So the flashes with Odin failed? Tried flashing the latest stock ROM with a pit file in Odin?
Click to expand...
Click to collapse
did that after you suggested but still stuck on boot loop ao i installed twrp again and tried to wipe dalvik and cache, i go the failed to mount /efs (operation not supported on transported endpoint) error. I think this is the root of the problem and if i can solve this then i can get up and running again.

Do you think it would be possible to create a clean installation on genymotion of my device (gt n7100) then take a full backup of it and try to install it on my device? (through twrp)

I have just tried doing that but unfortunately my CPU is not compatible with virtualization technologies or some BS like that, is it possible that someone could do it for me and post it or even post a full backup of Samsung note 2 (gt n7100) please?

Sounds like the internal memory chip is damaged. To confirm that it is the memory, you may have to take it to a cell repair shop and have them try to force flash it via jtag.

audit13 said:
Sounds like the internal memory chip is damaged. To confirm that it is the memory, you may have to take it to a cell repair shop and have them try to force flash it via jtag.
Click to expand...
Click to collapse
Would I be able to do that at home? And do you recommend me taking a virtual backup (genymotion) and installing it on my physical device?

You would need to create a JTAG cable. It works be simpler to take it to a cell shop that has the hardware to force flash the phone such as an octopusbox.
Unfortunately, I don't know about restoring a virtual backup.

audit13 said:
Sounds like the internal memory chip is damaged. To confirm that it is the memory, you may have to take it to a cell repair shop and have them try to force flash it via jtag.
Click to expand...
Click to collapse
Is there a way of doing that myself? and do you recommend taking a backup of a virtual device?

If you want to try it yourself, you could Google for a JTAG method for the note 2.
Taking a virtual backup may not help if it can't be restored to the phone.