Have a Note 3, rooted, flashed Jedi Elite about 3 months ago, works like a champ.
Randomly today during normal usage, phone froze, reset, then gives me this message
"Device memory damaged - the data partition has been corrupted. You need to reset your device to factory defaults. This will erase all the data on your device"
Tried that, didn't change anything (booted right back to the same screen), Went into the bootloader, wiped the cache, no change, tried a factory reset from there, no change, tried 're-rooting' it (a suggestion online), root worked, no change ( still booting to the same screen )
Help! Can't find any help online, in desperate need of guidance.
doctorc501 said:
Have a Note 3, rooted, flashed Jedi Elite about 3 months ago, works like a champ.
Randomly today during normal usage, phone froze, reset, then gives me this message
"Device memory damaged - the data partition has been corrupted. You need to reset your device to factory defaults. This will erase all the data on your device"
Tried that, didn't change anything (booted right back to the same screen), Went into the bootloader, wiped the cache, no change, tried a factory reset from there, no change, tried 're-rooting' it (a suggestion online), root worked, no change ( still booting to the same screen )
Help! Can't find any help online, in desperate need of guidance.
Click to expand...
Click to collapse
if you have no choice, I would recommend flashing through ODIN the new firmware, or which ever firmware you have installed on your phone..
goto recovery,, wipe system, data, cache, dalvik cache, then ODIN your firmware.. this way you will have a fresh clean install, see what happens after that,
544
mdiaz33685 said:
if you have no choice, I would recommend flashing through ODIN the new firmware, or which ever firmware you have installed on your phone..
goto recovery,, wipe system, data, cache, dalvik cache, then ODIN your firmware.. this way you will have a fresh clean install, see what happens after that,
Click to expand...
Click to collapse
Tried, everything seemed to go well, but on boot up after flashing the ROM, same screen about corruption of memory.
Seems like I might want to try the re-partition option, which requires a pit file, but can't find the right file (SM-N900T)
doctorc501 said:
Tried, everything seemed to go well, but on boot up after flashing the ROM, same screen about corruption of memory.
Seems like I might want to try the re-partition option, which requires a pit file, but can't find the right file (SM-N900T)
Click to expand...
Click to collapse
After boot up of the stock ROM it still said that?
If you Odin the stock room boot into the stock recovery and factory reset. You can also do this in the settings menu under storage. This will wipe your phone
Sent from my SM-N900T using XDA Premium 4 mobile app
Related
Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
SlimJ87D said:
Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
Click to expand...
Click to collapse
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
BWolf56 said:
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
Click to expand...
Click to collapse
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Could Fix Permissions fix the problem? It seems that the phone boots up to the home screen. While loading files, something at this point is causing it to bootloop. It will freeze after a few seconds and then reboot and repeat the problem.
Something is definitely conflicting within the first 30 seconds of booting up to the home screen. Any ideas?
SlimJ87D said:
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Click to expand...
Click to collapse
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
BWolf56 said:
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
Click to expand...
Click to collapse
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
SlimJ87D said:
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
Click to expand...
Click to collapse
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
BWolf56 said:
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
Click to expand...
Click to collapse
Thanks. Yes she's using an external SD card. I will have to get a hold of her phone and see what's going on. The first time it happened was because we upgraded to Jellybean. it happened right after so I don't think it was a rogue app. This time she just pulled her phone out of her purse and noticed it boot looping. Something sounds wrong with her phone... I think we might need to send it back for warranty repair.
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Now that I put fresh rom and cleared everything her phone was working. But the moment I rooted the phone itboddly didn't come with SU, so upon installing SU nothing could access SU for some odd reason. So I found out you need a SU for Jelly Bean, upon installing this version of SU is when everything went to he'll and the same boot loop came back.
Sent from my GT-I9300 using xda app-developers app
SlimJ87D said:
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Click to expand...
Click to collapse
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Alexandre-P said:
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Click to expand...
Click to collapse
Perhaps, I will try and fix the problem again. We just got back from a movie. Thank you.
if everything doesn't work
here's what you should do
first go look for AT&T 4.1.1 stock rom
download ODIN
go to recovery by vol up + power + home
clear cache, data and dalvik
flash stock rom thru odin.
that should fix soft brick
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Some how I have screwed up my partitions. I was able to Odin to stock lollipop and I can get into download and recovery. However I cannot flash anything at all at this point. In TWRP when I try to flash a custom ROM, Kernel or even the lastest TWRP version, all that happens is recovery restarts. This all started when I tried to flash SlimLP ROM. It flashed fine but would only bootloop when I tried to start phone. So I wiped everything and reflashed lollipop AllianceROM. The phone started okay but I got some error message about the UID. I noticed right away that ALL my text messages which should have been wiped were intact. The phone was running really, really slow and I had continual issues installing apps from the Playstore and TiBu. I decided to try another ROM and again wiped everything, flashed and rebooted. Again text messages were intact. I believe it's my system and/or data partition that is messed up but I am not sure. I'm not knowledgable about any of this so I really need some help here.
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
tx_dbs_tx said:
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
Click to expand...
Click to collapse
samep said:
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
Click to expand...
Click to collapse
Thank you both. I did just what you guys suggested and it worked out! Thank you again!
Ok I have T999L 16GB.
Phone working fine. Did hard reset because they hadn't been used in a while and wanted to start fresh.
After reboot, phone stuck in "T-Mobile 4G LTE" bootloop forever. Tried again, same thing.
Did Odin flash of latest ROM for that device (per what I could find?)
T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar
same thing, no result. Downloaded the PIT file for that phone, did another odin flash of the ROM above, but checked "re-partition" and pointed to the PIT file. Successful flashing, device rebooted. Same thing endless bootloop.
Not really sure what to do now, any ideas?
@DocHoliday77 possibly as one of the resident experts 'round these parts...
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
audit13 said:
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
Click to expand...
Click to collapse
worth a try, will report back.
edit: @audit13 - Worked like a boss, did the odin with repartition PIT file, but deselected auto-restart, went into recovery after flashed and wiped factory reset plus cache, rebooted, and BAM, got into the set up screen.
Thanks for your help.
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
audit13 said:
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
Click to expand...
Click to collapse
Yeah sure seems to be that way, glad that's all it was. I know the PIT mapping with the ROM must have helped too, but flashing in stock recovery after that cleared it up for writing to the new partitions like you said.
Coming from a Nexus 6 this was pretty annoying, I am used to using fastboot to do everything, I don't see a Samsung device in my future.
Same thing can happen with a nexus 4 and nexus 5 in that I still have to perform a full wipe in stock recovery if the phone was running a custom rom. Don't have a nexus 6 or 6p to play with
Samsung phones don't have a fastboot mode. The closest thing would be their download mode.