Database Info

Galaxy TAb 7.7 brick, please help

Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!

same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!

TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!

davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!

Where did you find the PIT file ? You may just destoried the partition. God bless you!

matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days

If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..

suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....

Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!

suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!

davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.

Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..

davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?

白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.

The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?

I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.

Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?

Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).

davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.

please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!

A700 bricked, what can I do?

Hello,
I have a problem.
Device bootloader unlocked, CWM Recovery v5.5.0.4 installed.
I tried to flash Acer_AV043_A700_1.025.00_EMEA_CUS1.
I thought that this firmware a zip file, then need to flash with CWM.
After nandroid backup start wipe data/factory reset and tablet hanged.
Then I reboot it and see nothing, just "Acer".
When with CWM restore my backup, system wrote something abought "MD5".
What can I do? Help me please!!! and sorry for my english.

Can you wipe cache and davlik cache?
Or try this:
While off hold volume+ button (one dot) and power button and then toggle the rotation switch on and off a few times.

For now I'm not at home. Will try and right away write.

nurbek05 said:
For now I'm not at home. Will try and right away write.
Click to expand...
Click to collapse
More than likely bricked. Best send it in for service.
As best as I can tell, you have to use the exact same rom version to go back to original.
Also, it seems CWM "may" have an issue restoring recovery backups. It's possible the data partition gets corrupted on restore, with possible system partition as with one other user. Hanging at the "wiping/formatting data seems to be a problem.
The MD5 is the checksum, which verifies the recovery backup is the same.
Remember, this is new territory, and a lot of this is untested.
MD

Itchiee said:
Can you wipe cache and davlik cache?
Or try this:
While off hold volume+ button (one dot) and power button and then toggle the rotation switch on and off a few times.
Click to expand...
Click to collapse
Hanged

nurbek05 said:
Hanged
Click to expand...
Click to collapse
Turn it in for service.
Your partitions are all destroyed. Data, System, and so it seems cache.
You can try getting a full rom, naming it to update.zip, and try installing using Vol + and PWR. this will of course wipe out you CWM and install a stock bootloader, but you already know it doesn't work anyhow.
If you can find the exact same rom it came shipped with, it might work.
Unfortunately, not a lot of roms to choose from right now, and asking for a certain version rom probably won't get many answers. Seems certain tabs require certain factory roms to run.
If your authorized Acer repair center is local, they may not charge you much for installing the correct service rom. Maybe.
70x Development is new. And these things happen, so expect it.
MD

Thank you, but I try.
Can you give me system.img?

nurbek05 said:
Thank you, but I try.
Can you give me system.img?
Click to expand...
Click to collapse
I don't have a system.img for your 700.
But, in the Dev forum, they have several full stock roms for download in the "ROMS" thread.
No, I do not know if they will work for you.
Sorry I can not be of much more help.
MD

seems we can only wait for NVflash
nurbek05 said:
Thank you, but I try.
Can you give me system.img?
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.

If Acer A700 have Tegra3 then it have Secure Boot Key like Asus TF201?
http ://androidroot.mobi/2012/01/15/an-analysis-of-prime-security/

no way to nvflash
nurbek05 said:
If Acer A700 have Tegra3 then it have Secure Boot Key like Asus TF201?
http ://androidroot.mobi/2012/01/15/an-analysis-of-prime-security/
Click to expand...
Click to collapse
the asus has blocked the nvflash in tf201,and there isn't any method to flash a device of tegra3 via nvflash...
seems there is much time for us to wait

Any news abought nvflash?
In my town I more than sure that nobody can repair my A700.
Service is not good. But I can send it to capital where maybe repair.
Maybe need wait for nvflash or ROM which be compatibility with A700.

s
nurbek05 said:
Any news abought nvflash?
In my town I more than sure that nobody can repair my A700.
Service is not good. But I can send it to capital where maybe repair.
Maybe need wait for nvflash or ROM which be compatibility with A700.
Click to expand...
Click to collapse
same situation as mine....im in china and the device is not for sale publicly,i got it from a special way.seems there is noe one can repair the device all over the country,i should wait for the device on sale...

SD Card boot
I have exact the same problem.
Has anyone tried to boot from SD card?
Webitu

nurbek05 said:
Hello,
I have a problem.
Device bootloader unlocked, CWM Recovery v5.5.0.4 installed.
I tried to flash Acer_AV043_A700_1.025.00_EMEA_CUS1.
I thought that this firmware a zip file, then need to flash with CWM.
After nandroid backup start wipe data/factory reset and tablet hanged.
Then I reboot it and see nothing, just "Acer".
When with CWM restore my backup, system wrote something abought "MD5".
What can I do? Help me please!!! and sorry for my english.
Click to expand...
Click to collapse
Has yes to unbrick?you try to obtain a unbrick test of a500 to a700
http://forum.xda-developers.com/showpost.php?p=23584356&postcount=39
http://forum.xda-developers.com/showpost.php?p=23584356&postcount=39

DO NOT even think about running an A500 RUUs rom on your tablet.^^^^^^^^^^^^^^
Sure way to brick any device.
What you can do, is send lots of contacts to Acer, and demand the SBK (secure bootloader key). Then you can start thinking about NVFlash.
MD

I was just about to buy one of these tablets and now i read this quite upsetting info. There is no nvflash? Thats the suck for sure. Any word on it?
Anyone know if the tf700 has nvflash ability?

Unable To Mount SD Card via TWRP

I have had my Nexus S 4g rooted for sometime and have flashed many roms, so I'm not a complete nooby... but for some reason I'm stumped right now.
I woke up this morning to my phone in the TWRP recovery thing and I just tried to restart my phone but it wouldn't boot up so I figured I would just restore to a previous ROM and all of my backups were just gone. This is the error I have: error opening /sdcard/TWRP/BACKUPS/randomcharacters
But that was way at the bottom, above it I see all these notifications saying that nothing is mounting... so I go and wipe all my stuff to try to re-install the ROM I already had because it had been working very nice and it was just gone. Couldn't find it at all so I figure ok... let's just mount it and put the ROM on my phone... but when I try that my computer tells me that I need to insert a disk into the removable disc.
So right now I really have no clue what to do and I can't use the one click stock since I can't get to my phone to turn on USB debugging.
Any help?
Sorry if this has been answered elsewhere but I was unable to find anything similar.

And I have tried unrooting using this site:
nexusshacks. com/nexus-s-4g-hacks/how-to-unroot-nexus-s-4g/
However, it doesn't work after "fastboot flash system system.img"

And when I go look at the log thing in TWRP I get this:
*Verifying filesystems...
*Verifying partition sizes...
E: Unable to mount /system
(x20 with different things!)
E:failed to mount /sdcard (No such file or directory)
Gah! Have no idea how this happened!!

getliketie said:
And when I go look at the log thing in TWRP I get this:
*Verifying filesystems...
*Verifying partition sizes...
E: Unable to mount /system
(x20 with different things!)
E:failed to mount /sdcard (No such file or directory)
Gah! Have no idea how this happened!!
Click to expand...
Click to collapse
Can you go into fastboot? I would try to fastboot flash recovery, flash CWM and start from there. If it still wouldn't work i would presume that either your NAND went bad or that somehow the partitions got screwed... I do remember something similar happening to me on my wife's SGS and the solution was a Odin flash of a stock ROM to restore the partitions.

DeuXGod said:
Can you go into fastboot? I would try to fastboot flash recovery, flash CWM and start from there. If it still wouldn't work i would presume that either your NAND went bad or that somehow the partitions got screwed... I do remember something similar happening to me on my wife's SGS and the solution was a Odin flash of a stock ROM to restore the partitions.
Click to expand...
Click to collapse
I can go into fastboot! That is the mode I'm in.
I am currently trying to unroot my device using the unroot guide from nexusshacks. com but I get a forever hang time when it is writing my system.
So I just flashed CWM but I am no sure what to do from here! I tried mounting sd card and usb but neither worked. However, I did see an option to format my sd card. Should I do that directly from CWM? And in the advanced menu I see an option to partition my sd card.
At this point I just want to have my phone back in working condition.

You can try to format the SD card, but i think it won't work... If it doesn't work try to search for Odin and the files to restore to stock ROM, maybe it can fix the partitions... The SD card partition option in CWM i never used, so i'm not sure what it does in this case.

So I tried the Odin and I'm still stuck in the writing system stage... I have no idea what to do at this point.

getliketie said:
So I tried the Odin and I'm still stuck in the writing system stage... I have no idea what to do at this point.
Click to expand...
Click to collapse
Seems your NAND reach its end. There's allot of topics regarding that problem with the Nexus S and every single one of them ended up with the OP sending the phone to Samsung or getting a new phone...

E:Failed to mount EFS ( Invalid Argument)

Hello friends, when I flash Combination file, or stock file , my phone boots and hang at start up logo, while I restart to recovery I see this error (E:Failed to mount efs, Invalid Argument)?
Can anyone help?

What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.

TheRealKeyserSoze said:
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
Click to expand...
Click to collapse
This steps does not work, I need EFS for A8 2018.

I'm having the same problem, I've tried everything. z3x, Odin , won't even let me flash from sd card. Won't load into Oreo just keeps rebooting. I can get into recovery but does nothing as well as boot loader. I did have a utility im pretty sure was made by FACTORY BINARY that was it's own little OS with a bunch of little tools. I have a sm-a530w flashed with boot loader 4 ugggg. If anyone can help find that utility that will wipe the whole thing and let me flash from scratch that would be awesome. I've tryed miracle, Uni-Android, samsung tools 29.5 and flashing with odin. Lets me flash factory FIRMWARE but still error's out on the "Failed to mount EFS" HELPPLEASE

A quick suggestion you probably tried, but i've had failure at boot in the past after returning to stock via odin if i used home_csc. So, if you haven't already tried, use just csc. No home. On home it does system.img until the end, no user_data . Not sure at all what the deal is but it's all i can suggest. Get 'er goin'!

:Failed to mount EFS
Yes I think I tried that, but at this point, I try again. Any more suggestions would be greatly appreciated. An A8 in mint shape just hurts LOL.

Unable to keep flashed recovery or rom. Device restores everything after reboot

I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz

FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.

niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk

I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.