Hello,
I have samsung galaxy note after brick (I had to use pit's to help with brick). Everyhing seems to be okay on gingerbread (sometimes some few secs lags) but when I upgrade to stock xxlsz its freezing. Its freezing very often. Now I was adding google account and phone screen went black and nothing happens. Its connected to the pc and I can access storage but when I disconnect it and connect it I can hear in pc sound that its connected but I cant access memory anymore. Very ofter phone just displays the app that I was using and no touch or button reaction, even when I connect or disconnect charger. So i hold power button till it turn of and turn it on again then its mainly stucking on samsung screen and then reboot and its like that for loooong time. When i remove battery for 5 mins or maybe even less its botting up again but phone is wiped. I mean its asking for everyhing as I would do full data wipe.
I was checking I think every possible stock rom.
I also found this but Im not that good and I dont know what to do with it.
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showthread.php?t=1667886
Any help would be very, very appreciated.
Thank you.
You have a bricked note with reduced memory. So the freezes are consequence of this. Nothing to solve. You'll have to replace the mainboard for a real solution.
Ok, but I still have 8GB of memory so it should be enough I think so.
If I need to replace mainboard can someone tell me where can I buy it and where is it cheapest?
Daxidov said:
Ok, but I still have 8GB of memory so it should be enough I think so.
If I need to replace mainboard can someone tell me where can I buy it and where is it cheapest?
Click to expand...
Click to collapse
Only way: Samsung Service Center. The mainboards aren't available in the "free" market.
And 8GB isn't enough for JB Roms and even with the slim CM/AOSP ones you'll get the freezes.
Ok,
So if 8GB isnt enough why have I around 6GB free space for my files? Is there any way I can repartition it so system would have whole 8GB and there wouldnt be any lags?
the freezing is mainly because the OS could be still accessing the bad blocks.. run the scanner again to get new start and end and see it you can get a new pit to cover up those
nokiamodeln91 said:
the freezing is mainly because the OS could be still accessing the bad blocks.. run the scanner again to get new start and end and see it you can get a new pit to cover up those
Click to expand...
Click to collapse
Ok.
Can you tell me how can I do this test? And what software need I to use?
Thx
head over to HG42s thread and use the scanners he provided there.. tutorial also there
nokiamodeln91 said:
head over to HG42s thread and use the scanners he provided there.. tutorial also there
Click to expand...
Click to collapse
When I use this on stock PIT using CWM I got brick between 863MiB = 930MB and 3072MiB = 3222MB but when I use same script and do the scan using CMD I get brick between 1023MiB = 1073MB and 15028MiB = 15759MB
When I use the same method but on modified PIT (brick between 00281MB and 03770MB FACTORYFS moved by 03328MiB) using CWM I got brick between 22 = 24MB and 4354 = 4566MB
After I use PIT brick between 00281MB and 03233-MB FACTORYFS moved by 02816MiB which schould be okay Im formating /cach /system /data and Im unable to format /emmc (Error mounting /emmc).
I really dont know what the problem is with.
On stock PIT Im not able to format /data and /emmc with which I got Error mounting /emmc
At last I have used this and its stucked at FACTORYFS nearly at the end.
I have tried to use PIT brick between 00281 and 12092-MB FACTORYFS moved by 11264MiB but even after this Im unable to mount /emmc. I can instal rom but its freezing whole the time.
Any ideas?
First, let it be known that I'm an idiot. I'm not new to the scene but I did some really noobish things and I've really screwed myself into a corner. So, first the background info. I have a Samsung Galaxy S Captivate, on Rogers (Canada), and I was running CM 10.2 (if I remember correctly). I set an alarm at night and woke up the next day to a recovery loop. I tried a number of ways to recover and reflash and one by one they failed, and piece by piece, I unmounted, erased and formatted everything (I know, I know). So I've got to an interesting point and I'm not sure what to do next as most method seem inaccessible. So, here's the list of broken things (that originally worked but I broke):
- No recovery/no ability to boot to recovery. All attempts cycle a boot loop.
- no internal sdcard. Can't see it or mount it. I've tricked my phone into thinking the external is the internal. This however, means I can't download anything or even copy anything to my phone. No cloud or internet files.
- no usb. I can connect and it recognizes it, but there's no sdcard (so it thinks) so there's no connection made.
- no download mode. Here's where it gets funny. I managed to flash a stock kernel with odin (YAY!) but I flashed an AT&T version and guess what? No download mode anymore. I've tried numerous combinations. I haven't yet tried a jig which is what I'm assuming everyone will say I have to do. I have no idea what I'm doing from there.
- almost unusable phone. I can't even make calls as the SIM is meant for Rogers, not AT&T
- my bank account. I'm short on cash so I can't just go and buy a new fancy phone even though I really, really want to.
I seem to be the prime example of what not to do and I brought it all upon myself. However, I've heard that as long as the phone turns on, there's hope. My goal is to get back to a CM firmware (or something else if you hate it) and maybe recover from the damage I've caused. So, am I screwed?
tl;dr Everything is broken and I'm stupid and desperate. :good:
Jig... to get into Download mode.
Then flash an Odin Stock firmware for Rogers here... http://forum.xda-developers.com/showthread.php?p=18371028 Post #4.
But not sure how that will work out for ya since ur internal memory is messed up.
---------- Post added at 12:18 PM ---------- Previous post was at 12:08 PM ----------
If all fails and u don't mind spending some money when ya can...check out mobiletechvideos.com for the repair.
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Val D. said:
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Click to expand...
Click to collapse
It's using the external as the internal right now. If I remove the external and try to boot, it will show the boot logo and shut down. Seems like the jig is the next step.
So I have tried my first bit of rooting and modding with this phone. Though I have decided to go back to stock 5.1. I am having one problem though. When I go to storage in my setting it only shows 23GB available. I have a 64GB model so I'm sure it just some backups or something left from switching to and from CM12. I am wondering how do I get this space back? I cant find it by just plugging my phone into the computer. I have also installed an app that lets me look at my phones SD but still cant find the backups. Does anyone have a solution for me. Thanks for any help.
Would factory reset option on the phone reclaim the space?
Need to use a command in fastboot.
fastboot format userdata
You will lose everything on the phone like pictures, songs etc.
But its like doing a full factory reset. This happened on the last update to many people.
Easy fix.
You can also try doing a factory reset from within Settings. Not sure if that still works the same though.
That worked. Thanks for the help
I have seem to have found the issue and solution to this problem that many of us have been experiencing. If you have encountered issues like myself, there is a thread dedicated to the description of this problem; MAJOR LAG, RANDOM REBOOTS, the phone won't boot up and goes into a screen where you read:
----Mmc_failed failed boot---
After searching for about a month, it seems to be an internal SD issue. Many have reported to having these issues after they root, others upgrading to the non reversible DOK2 FIRMWARE. Others were stock with out root and had this issue as well.
**THE PARTITION OF THE INTERNAL SD CARD IS CORRUPTED**
Could be corrupted files, that stick to the phone EVEN AFTER ODIN FLASHING STOCK MANY TIMES.
(I Odin 5 times back to back to fix and the partition was still corrupted)
People thought "well, if Odin doesn't work, it's a hardware issue" I thought that myself, and it was not.
My friends, I have found something that has worked for me and would like to share with you guys. I hope this fixes your device like it did mine. I've been so close to throwing this Note 4 against the wall, running it over with my car, or smashing it with a hammer. I had no way to return my device as many have suggested to do because I left T-mobile a while back. Plus, rooting my phone voided my warranty. Yada, yada, yada, let's get into it.
*Since the internal partition to the SD card is messing up, we need to repair it.
**In order for this to work, you will need to be ROOTED.
*Download an app called "AParted SD Card Partition." Hope I don't violate any rules, but here is the link to it on Google Play.
https://play.google.com/store/apps/details?id=com.sylkat.AParted
Once the app gains root access, you will be brought to the main screen. Click the tab that says tools. Once that screen pops up, you will see
Part 1 FS: fat32 . Size 31914 MB
Part 2
Part 3
Part 4
Please note that the size to Part 1 may be a different number. That is what mine read.
*You will now click Part 1
*After doing so, at the bottom where it says create, click it and replace it with REPAIR.
*Hit apply, and you're all set.
*Turn off phone, pull battery out for 10 seconds, as well as external SD card and Sim. (They hold small amounts of electric current which may prevent the phone to do a proper boot) I usually hold both volume buttons, power button, home button, and pull the s spen out for 10 seconds simultaneously, then put it all back together and boot up.
*******Also, I used the app to delete the partition, and creating it again to avoid problems from a faulty repair. So if you want to do that, click Part 1. Instead of repair, click delete. Once done, click Part 1 again, then click create. Hit the Fat32, and start it. Once it's created, you shouldn't have issues. In case you're worried, pictures and videos will not be erased.******
I HAVE NO AFFILIATION WITH THE DEVELOPER, BUT HE SAVED MY DEVICE WITH THIS APP. PLEASE, PLEASE, PLEASE DON'T FORGET TO THANK HIM AND HIT THE LIKE BUTTON IF THIS WORKED FOR YOU AS WELL. LEAVE COMMENTS AND QUESTIONS BELOW, AND IF YOU SEE PEOPLE TALKING ABOUT THE PROBLEM IN OTHER THREADS, RE- DIRECT THEM TO THIS THREAD.
This is what I got when repairing the partition. You should have a message as well.
um... if they can't start up the device, how are they going to download it from the play store and install to run it? Thanks!
Are you able to go into DOWNLOAD MODE AND FLASH FIRMWARE? I had the Mmc_failed screen and my phone would not turn on until I took everything out the phone; battery, both cards and s pen, then hold all the buttons down.
Try this to reboot like I described up at top.
Turn the phone off. Pull the battery out, s pen out, SD card and SIM CARD.
PRESS AND HOLD ALL HARDWARE BUTTONS FOR 10 SECONDS WITH EVERYTHING OUT THE PHONE. I CLICK ALL THE BUTTONS SEVERAL TIMES TO GET ANY ELECTRIC CURRENT OUT THE PHONE. IT WON'T BOOT UP IF YOU DON'T DO THAT. I'm assuming it messes with the boot up process. Anyways, Re assemble and boot. When I was having this mmc_failed crap, it would take several times doing these steps so that the phone could boot. Don't get frustrated and try again until it boots up. Sometimes it would sit on the NOTE 4 screen, other times it would boot up to the Android logo with the mmc_failed screen. It takes several attempts since the PARTITIONS TO THE SD CARD ARE CORRUPTED. IF YOU ARE ABLE TO ODIN FLASH FIRMWARE, FLASH THE FIRMWARE TO HELP YOU BOOT UP. FLASH TWRP, THEN ROM, then you will have root.
If you still get the mmc_ boot after repairing it, erase the partition, and create it again. I updated the guide on top on how to do that. Haven't had a single hiccup or Mmc_failed bs since then. Good luck guys.
Please report back if it worked for you.
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
mtran1977 said:
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No problem. Save everything important from your sd card and formatt it. That also helps. Try booting up your phone without your sd card. You know what mmc is? An sd card. Google it. Ive seen corrupt sd cards prevent phones from booting up.
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
What does it fix??
I tried using this application and the first partition that came up was a 61240 Mb partition. I thought it has to be my external SD card. Then i pulled out the external sd card and ran this application again. This time it did not find any partition.
Is this what its suppose to do? If not can you post a screenshot of your partition list.
Thanks
thiennvbk said:
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
Click to expand...
Click to collapse
After flashing TWRP AND THE COOKED ROM, TURN OFF THE PHONE. TAKE THE BATTERY OUT....SIM CARD OUT...TAKE THE SD CARD OUT AND THE S PEN PUT.
THEN WITH ALL THAT OUT, PRESS AND HOLD POWER FOR 20 SECONDS. THEN TRY TURNING ON THE PHONE. HAD THE SAME ISSUE AND IT TURNED ON AFTER A FEW TRIES.
U may need tp try to do that a few times until you get it to power on.
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
It does not fix internal SD
Willy318is said:
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
Click to expand...
Click to collapse
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
rajatkuthiala said:
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
Click to expand...
Click to collapse
So all of this lengthy post and RED Promises are all BS?
I thought so !
Willy318is said:
So all of this lengthy post and RED Promises are all BS?
I thought so !
Click to expand...
Click to collapse
I am still waiting @notufatjesus to reply.
---------- Post added at 03:09 PM ---------- Previous post was at 02:37 PM ----------
I was wondering, could this issue be related to eMMC like they had on earlier galaxy series. These symptoms are pretty much similar.
created new thread with real solution
Ashwin Prabhunerurkar said:
created new thread with real solution
Click to expand...
Click to collapse
I have the same problem and also hope have a way to repair this error. Now very difficult to use the phone.lol
Mine works fine
@dannygoround
My hopes went up then got nuked as I read the comments lol
TL : DR - My phone won't boot because of low disk space, how can I free up memory?
Greetings,
Project FI purchased Moto X4 running BONE STOCK and absolutely ZERO CUSTOMIZATION. If I can get access to my pics taken via the camera I'm ok with wiping the phone and starting over. Screenshots folder access would be cool too but not life necessary... Wait there has to be a way to make a dump of all this data somehow, somewhere right?
Last night I was on 15% or less battery life and less than 100mb's of disk space left. (i know, i know, i'm a dummy head)
I heard about PLEX running no problem on mobile Browser and decided to test it out and sure enough it worked fine. Was test streaming a few movies out when my PHONE DIED. I thought, oh man, thats probably not the best since it died and it was low on space but yeah I threw it on the charger and went to bed....
This morning, I confirmed it was charged 100% but when I turn it on, the phone will not boot past the AndroidOne screen. Left it there for 40mins and no change, AndroidOne displays and the rainbow colored bars at bottom are frozen(don't scroll) and screen flashes off/on every 30 secs to that same AndroidOne screen.
However I can boot into Bootloader with no issues, and into Recovery mode as well, but there is not a WIPE CACHE option on this device... Obviously the Wipe data/factory reset option is there...
BUT BEFORE WE GET TO THAT POINT, WHaT GIVES? Anyone have any ideas?
few ?'s
#1 - In the Bootloader menu, What is this RESTART BOOTLOADER option for, what does it do?
#2 - Is there any way I can free up some space from Bootloader/Recovery as I'm pretty sure thats the cause of this problem I'm having. I was intending to do that today actually, was going to dump all my pics from the phone to a computer. ..
#3 - Is there any way I can see if my pic's backed up somewhere? New to the Google ecosystem...
#4 - Is there any way I can read or access the phones data via a computer, then perhaps I can delete a few pics to free up memory or better yet, wipe app caches to clear up memory instantly? PERHAPS even command line ????
Any and all other inputs and suggestions greatly appreciated before I take that step of wiping the device(which assumes I can start over with a working phone by doing that but not a guarantee).
Please ADVISE
much appreciated!
oNe
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
jhedfors said:
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
Click to expand...
Click to collapse
Thanks for the reply, so Google says I have backup turned off but my photos are in the timeline.. SO I just manually downloaded them all as a backup/pre-caution.
any other suggestions before I attempt the WIPE data/factory reset option from Bootloader > Recovery?
I can boot up fine into Bootloader and Recovery.
I can access the logs via . Bootloader > Recovery > View Recovery Logs
last line states the following: I:[libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt
please advise,
oNe
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Sean Price said:
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Click to expand...
Click to collapse
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
johnjingle said:
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
Click to expand...
Click to collapse
gotcha.. so basically 32gb's is the new 8gb
moving forward I'll try to stick to 64gb phone's and up..
oNe