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.
Related
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
How could I in Odin insert a PIT file to remap my filesystem.
Is there one for the TMO S4 or could I simply use one from the gt9505?
Stoowyguy said:
How could I in Odin insert a PIT file to remap my filesystem.
Is there one for the TMO S4 or could I simply use one from the gt9505?
Click to expand...
Click to collapse
You don't.
Remapping the file system is not a current mod and is not recommended to try. One of the 95xx variants had a remapped PIT file done to add a little bit of usable space. (You can't use that one. It will break your 919 device) The risk was high and the benefit was low. It's just so cheap and easy to buy a 32 or 64 GB external SD card that accomplishes the same thing.
I guess basically what I'm trying to achieve is for my phone to be able to install custom roms again. Randomly one day I was unable to install any, for it would just install a few apks from each CustomRom installation zip.
I've tried reinstalling stock and it doesn't fix my issue that most likely lies in the file system of my phone.
Stoowyguy said:
I guess basically what I'm trying to achieve is for my phone to be able to install custom roms again. Randomly one day I was unable to install any, for it would just install a few apks from each CustomRom installation zip.
I've tried reinstalling stock and it doesn't fix my issue that most likely lies in the file system of my phone.
Click to expand...
Click to collapse
That is weird. Did you try to reflash back to stock using Odin? Or by flashing a nandroid of a stock ROM?
If using Odin to flash a stock image doesn't work I'm not sure a pit file would help. The stock .tar image for Odin contains the proper PIT file. So it's getting the PIT file anyway.
I'll try again..
I've tried coming back from Odin many times but I've noticed Odin is pretty sketchy because honestly most of the time oI get FAIL status near the end of stock installation but I keep going until it passes and I've tried going back from NAND. I was going to see this phone because no one on XDA nor me could figure out this tricky issue. Someone pm'd me claiming he has the same issue and I told him I haven't solved it yet. I think tomorrow I'm going to maybe try stock install and then wipe data factory reset after and then boot and then go back to download mode and install recovery and try install wicked or maybe gpe. Btw the last ROM I was running was Gpe by Kot49h danvd I think the name is
I'm The Second Person Who Claimed it Wasn't work
Sent from my SGH-M919 using Tapatalk
Hi, I have been trying to flash a new ROM to my Note II.
It was on Official Stock 4.3 ROM and I flashed succesfully another 4.3 ROM based on stock with some Note 3 features using Philipz Touch.
Then I switch Philipz to TWRP in order to install DN3 V4 ROM and I made the wipes and format /data and I start flashing the ROM, and since that moment It stucks on the first screen.
When I try to flash a stock 4.3 ROM using Odin, It seems to flash correctly, but when I try to boot, it stucks again.
I can enter to recovery and download mode, I can install some ROMS using TWRP but when it finishes it shows "Unable to mount /data" and if I try to boot, It always stucks on fisrt screen.
I hope you can help me.
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Still the same
biokiller said:
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Click to expand...
Click to collapse
I really appreciate your help, but I can't fix the problem yet.
With CWM I can't make a factory reset, when I try to make it, it restarts the phone and it stuks on the first screen.
I have flashed stock ROMS with odin and it says PASS but when the phone boots It always stucks on the first screen.
Fear not.
I am fairly confident this will work, but read the whole post first
You tick erase all nand as well as the usual two options. Then boot into recovery (should give warnings about unmountable /data) and wipe data / factory reset. Then reboot and it should work / odin a stock rom as normal.
If that doesnt work / or instead you get the correct pit file and flash it as well as the rom and have four options ticked: pit, erase all nand + normal two.
If someone gave me their phone with the same symptoms as yours and said: fix it right now that's what I'd do. I'd also warn them I really need to do more research before doing this and using these two options in odin could brick the phone forever.
I hope this gives you lines of inquiry. I found many mixed messages with the erase nand option, most said nothing of merit except don't do it, some said you must wipe data first (which u can't), some said exactly what I've repeated, some say a pit is enough, others had many steps and files ive never heard of to solve the same issue. There is a large thread in the S3 forum about this, even got mentioned on xda proper. My brief cookie crumbs journey did not return any note 2 threads.
Remember one thing, before using odin, double check every detail. Battery, cable being used, files being used (right ones, md5s), right options ticked, computer is in good health, internet is off, Kies is not running. (I'm sure ive missed some)
Solved
I install again the stock kit Kat firmware and the problem was the same, but this time I boot stock recovery and there I made factory reset and that's it. Problem solved and Note boot normally.
Thanks for your help
With or without erase nand in odin?
No, I just flashed normally as all the stock firmwares
I see, thought you'd rule that out. Disappointing really. Glad ur sorted anyway. Remeber wiping data is important when changing roms, even if it's not always absolutely necessary.
Did you try TWRP or Philztouch ? Did you flash 4.3 stock rom?
Sent from my GT-N7100 using Tapatalk
I had a stock 4.3 based rom on my t999l that has had a 4.3 modem since i got it and updated it... I had phils touch recovery on it... I like purple. So my bluetooth microphone starts having issues in things like utter and I begin trying different ROMs. Unfortunately I tried a liquidsmooth 5.0 based rom andi find that bluetooth and wifi won't turn on. I used a motorized wheelchair for mobility so bluetooth is a necessity. Saif ROM was using an att kernel but i did not read the thread like i should have . So when the bt and wifi failed i just went back to the recovery and selected clean to install new rom and found me a 4.42 tw based rom and tried to install that back. Before the 5.0 attempt I could install anything and get boot. Now, no matter what I install it freezes at the ROMs splash boot image whatever that may be. I have tried odin which claims to succeed but even odin based firmware doesnt rewrite the cache partition. Have tried getting a pit file for the t999l to no avail after an odin. The recovery no longer finds the internal sd card which seems to be the issue since that seems to also be where the cache is stored. What can I do to get my phone back to functional?
For future reference, we got it sorted. flashed stock UVUBNC1 with Heimdall using this PIT and it would get to the 4G LTE logo and sit there... replaced CWM Recovery 6.0.4.5 with Heimdall again, and it could never mount or format /data but when I chose the option under mounts and storage to format /data and media together, it worked. On next reboot we got the T-Mobile bell sound along with the 4G logo for the first time, and it finished booting. Internal SD card was obliterated but that was apparently necessary.
mark9121 said:
I had a stock 4.3 based rom on my t999l that has had a 4.3 modem since i got it and updated it... I had phils touch recovery on it... I like purple. So my bluetooth microphone starts having issues in things like utter and I begin trying different ROMs. Unfortunately I tried a liquidsmooth 5.0 based rom andi find that bluetooth and wifi won't turn on. I used a motorized wheelchair for mobility so bluetooth is a necessity. Saif ROM was using an att kernel but i did not read the thread like i should have . So when the bt and wifi failed i just went back to the recovery and selected clean to install new rom and found me a 4.42 tw based rom and tried to install that back. Before the 5.0 attempt I could install anything and get boot. Now, no matter what I install it freezes at the ROMs splash boot image whatever that may be. I have tried odin which claims to succeed but even odin based firmware doesnt rewrite the cache partition. Have tried getting a pit file for the t999l to no avail after an odin. The recovery no longer finds the internal sd card which seems to be the issue since that seems to also be where the cache is stored. What can I do to get my phone back to functional?
Click to expand...
Click to collapse
the option said /sdcard in parathensis next to /data/media so it appeared to simply format the internal sd card which then allowed /data to mount and the rom could actually work.
I woke up the other day with my phone stuck at the Galaxy Note II bootup screen.
Great!
So I've been trying for days to solve this issue that's driving me insane.
I'm running TWRP 2.8.0.0
It starts and can't mount any of the partitions. Attempting to mount internal storage or SD card is impossible, it says it has 0 bytes.
Obviously something corrupted something. But now I can't get anything working.
I can't format from withing TWRP, it fails.
Tried using KIES emergency firmware update, but its supposed to show a list of devices that need emergency update, it never shows up.
I was able to flash a stock rom with Odin. Except for that it doesn't repartition the device's internal storage and it never is able to boot into the new ROM. If I check TWRP after installing with Odin, it shows that all the devices are still unmountable.
So I flashed the new TWRP 2.8.6.0 with Odin. Except when I boot back into Odin it shows 2.8.0.0 still.
Anyone have any ideas? I've been phoneless for a week now!
changoland said:
I woke up the other day with my phone stuck at the Galaxy Note II bootup screen.
Great!
So I've been trying for days to solve this issue that's driving me insane.
I'm running TWRP 2.8.0.0
It starts and can't mount any of the partitions. Attempting to mount internal storage or SD card is impossible, it says it has 0 bytes.
Obviously something corrupted something. But now I can't get anything working.
I can't format from withing TWRP, it fails.
Tried using KIES emergency firmware update, but its supposed to show a list of devices that need emergency update, it never shows up.
I was able to flash a stock rom with Odin. Except for that it doesn't repartition the device's internal storage and it never is able to boot into the new ROM. If I check TWRP after installing with Odin, it shows that all the devices are still unmountable.
So I flashed the new TWRP 2.8.6.0 with Odin. Except when I boot back into Odin it shows 2.8.0.0 still.
Anyone have any ideas? I've been phoneless for a week now!
Click to expand...
Click to collapse
Have you tried flashing a pit file along with the stock firmware in Odin? That's what I would do in your case. It'll repartition the phone and flash the firmware. Fresh as the day you bought it.
absinthesummer said:
Have you tried flashing a pit file along with the stock firmware in Odin? That's what I would do in your case. It'll repartition the phone and flash the firmware. Fresh as the day you bought it.
Click to expand...
Click to collapse
On your advice I just flashed i317.pit with Stock ROM. Succeeded in flashing in ODIN as well as looking like it rewrote the partitions. However, upon reboot to TWRP, all partitions are still unmountable. Tried flashing pit along with TWRP 2.8.6.0. It remained on 2.8.0.0 when I rebooted into TWRP. Again experienced the same issue and could not mount any partitions. Tried flashing PIT alone and then booting into TWRP. Same.
I've attached a picture too. This inability to mount also prevents me from formatting, factory resetting, loading from external microsd, so on and so forth...
http://i.imgur.com/J5ppODI.jpg
Man I really thought the pit would work! Just 2 days ago I had the unable to mount data error and flashing stock with the pit file worked for me
A few questions-
1. I wonder if that old old old issue of eMMc brick bug is present in your device. The symptoms are very similar from what I remember of it but I do highly doubt that's what's happening.
2. Do you have more info about your device prior to this breakdown? Ie what rom + kernel were you on? were there any hints of anything failing? did you flash anything and if so what was it?
I'm hoping the information might help point us in the right direction. I'll look into something a well, but I'm also hoping that someone else with more experience with this problem will come help. @sawdoctor didn't this happen to your note 2 once also? When mine refused to mount data the other day it wasn't quite as bad as this, so it was an easy fix. Hopefully we can get you sorted.
absinthesummer said:
Man I really thought the pit would work! Just 2 days ago I had the unable to mount data error and flashing stock with the pit file worked for me
A few questions-
1. I wonder if that old old old issue of eMMc brick bug is present in your device. The symptoms are very similar from what I remember of it but I do highly doubt that's what's happening.
2. Do you have more info about your device prior to this breakdown? Ie what rom + kernel were you on? were there any hints of anything failing? did you flash anything and if so what was it?
I'm hoping the information might help point us in the right direction. I'll look into something a well, but I'm also hoping that someone else with more experience with this problem will come help. @sawdoctor didn't this happen to your note 2 once also? When mine refused to mount data the other day it wasn't quite as bad as this, so it was an easy fix. Hopefully we can get you sorted.
Click to expand...
Click to collapse
I had a similar issue when porting a s3lte 4.4.4 base to the n2 I couldn't mount data even odin didn't fix it but I was able to format internal with recovery. A full wipe of everything fixed it. I'd try mskips toolkit, it has an emergency firmware rescue package that you can flash see if it helps. It maybe your internal sd has actually died which I've heard off before
Sent from my SM-N910F using Tapatalk
sawdoctor said:
I had a similar issue when porting a s3lte 4.4.4 base to the n2 I couldn't mount data even odin didn't fix it but I was able to format internal with recovery. A full wipe of everything fixed it. I'd try mskips toolkit, it has an emergency firmware rescue package that you can flash see if it helps. It maybe your internal sd has actually died which I've heard off before
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Thanks for chiming in! Hopefully that'll help him. Yeah memory failure us what I was thinking not brick bug (couldn't think of the right word, thanks)