Database Info

o3d goes into recovery mode every time it boots

Hi guys, i'm in desperate need of your help. i think my precious o3d might have been screwed.
first let me tell you what i did. as you know the internal sd card of o3d is 5gb or so and it fills up very quickly. this internal sd card is mounted as /sdcard. i have a class 10 16gb micro sd card and when i insert it, its automatically mounted as /sdcard/_ExternalSD. The applications or games, especially the ones that have external data folders which are like 1gb in size insists to be installed on /sdcard. You can't move those data folders to _ExternalSD, because then the apps doesn't work.
Then i came across this topic:
http://forum.xda-developers.com/showthread.php?t=1189701
As you can see that was exactly what i needed. I had CWM 5.0.2.0 installed so i downloaded the first .zip then copied all of the files and folders excluding the _ExternalSD folder to the external sd card then rebooted into recovery. From there i flashed the zip and rebooted again. phone booted up and all was ok and it worked. now the phone sees the external sd card as the internal one and the internal sd card was mounted as /sdcard/_ExternalSD. I then formatted the internal sd card from the settings menu because i already copied all of the stuff there to the external card. It worked fine and the internal card is formatted. After that i decided to get a nandroid backup so i opened the rom toolbox program. From the menus i selected the backup option, gave it a name, clicked ok. the phone rebooted into cwm recovery screen but nothing happened. then i noticed something was not right because there was some error lines under the cwm menus saying "E:can't mount CACHE:recovery/command" etc. Then i selected the reboot phone option but the phone rebooted right back into the CWM recovery again!! At that point i knew that i was @#?^ed.
Anyways i researched a lot and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1156549
i did exactly what he said and it worked, i mean it flashed nicely. then i rebooted the phone but it booted into the recovery again!!! But this time the CWM recovery was gone and i believe this is the stock recovery screen. I can browse the menu of it and make selections but the phone boots into the recovery every time it reboots.
The recovery screen looks like this:
http://farm8.staticflickr.com/7010/6654644033_b616bc0635_z.jpg
Then i flashed the phone to the latest official firmware V21A_00, it flashed nicely but it still boots right into the recovery everytime.
Then i installed the Android SDK and tried to push the original vold.fstab file to the system using the adb command line tool but it doesn't see the phone. I think adb works only when the system boots up normally, not in the recovery mode.
I don't know if there's a way to install the CWM from the stock recovery somehow. If you know how, please tell. The CWM has more options.
I don't know what else i can do. It started to look ridiculous. If there are any experts cool enough to help please do so. I'll be waiting. Thank you...
Edit:
I also tried this:
http://forum.xda-developers.com/show....php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit 2:
I also posted on the official LG Mobile forum here:
http://www.lgforum.com/forum/boards...d-goes-into-recovery-mode-every-time-it-boots
Fingers crossed

Quite a post!
From all your post there is no mention that you formated and did a factory reset after 21a flash.
Can you please try that if you haven't?
Sent from my LG-P920 using xda premium

thank you for the reply!
i tried all 4 wipe options on the recovery screen then rebooted. it's the same, i'm back at the good old recovery again

Did you try with the external sd card out?
This is strange, usually a kdz flash coupled with a format fixes the problem.
Some how it still can't find the internal SD card.
I don't have further recommendations. Sorry
Sent from my LG-P920 using xda premium

yes i tried with the external sd card out. it didn't work..

vpamir said:
yes i tried with the external sd card out. it didn't work..
Click to expand...
Click to collapse
Hopefully someone else on this forum can suggest a way for you to unbrick.
your problem is although you have reset your phone, somehow it can't find a partition to boot from.
or
somehow the KDZ flashing is not totally successful.
good luck

If only there could be a way to be able to use the adb command from the Android SDK then i might be able to restore the vold.fstab file to its original, if the problem is that at all. Maybe then it'll work. To be able to flash the CWM Recovery again somehow might be a good thing too because it has more options like flashing .zip format roms but i have no idea how. Does anyone know if the stock recovery can flash some specifically named file to the system, does it have that kind of functionality? I'm desperate, please share your thoughts.

.............anyone?

I am sorry to say that but there is no solution for this problem yet. I have done the exact thing that you do and tried every single solution with no luck. The only way is to send it to lg repair service. My solution was to replace the mainboard.
Dostum gecmis olsun malesef tek cozum yolu anakarti degistirmek. Uzaman sayilirim android konusunda bosuna ugrasmayasin diye soyluyorum. LG servisi bile anca anakarti degistirerek cozum sunabildi. Temel problem internal karti formatlamis olman. Partititon table'i bozuyor bu islem malesef ve bu yuzden hicbir yontem ise yaramiyor.
Gecmis olsun tekrar...

so you say that the main problem was to format the internal sd card? well if formatting the internal sd card bricks the phone then why the hell is there an option to format it in the settings menu?

well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.

crime_of_heart said:
well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.
Click to expand...
Click to collapse
so you did exactly the same thing as me right? i mean you applied the swap fix then formatted the internal sd?
replacing the motherboard to fix this seems to be a bit nonsense to me to be honest. what does the partition table have anything to do with the motherboard?
if only there would be a .kdz format custom rom which factory resets the internal sd card during the flash process and maybe fixes the bootloader somehow, that might be the solution.

yes i did the same and the only solution was to replace the motherboard. we need a sowftware that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.

crime_of_heart said:
yes i did the same and the only solution was to replace the motherboard. we need a software that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.
Click to expand...
Click to collapse
i don't know what the emmc is, i need to do research on that. but i still think that replacing the motherboard won't solve this issue because it seems non relevant to me. i messed up with the vold.fstab file. but after that it worked fine. i mean the internal and external cards swapped just fine. only after i decided to make a nandroid backup using rom toolbox all hell broke loose. i plan to wait a couple of days before turning the phone to LG service. i believe someone will come up with an idea.
yardım etmeye çalıştığın için teşekkür ederim bu arada

Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!

Marcovecchio said:
Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!
Click to expand...
Click to collapse
Great news! But now i need to find a way to install the new CWM. Just as you said i believe what i need is to find or make a .kdz update which includes this new CWM.
What do you think?

I know this is possible, at least for the Galaxy Ace: I have a ZIP file for this device with a custom recovery image, flashable in stock recovery!
To make one for the Optimus 3D, I need to know the following:
- How can I obtain the .IMG of the new recovery? I have found some temp files in clockworkmod folder in my sdcard. The creation date of one of them matches the exact moment I upgraded my recovery, and the file size also matches a recovery image: 5.54MB. Is it the recovery image? Can I just rename it to recovery.img? How can I extract it to ensure it´s ok?
- After I get the recovery image, I can use the Galaxy Ace ZIP as the base to build the O3D zip file. Any help on what do I have to change to make it work correctly?

I also tried this:
http://forum.xda-developers.com/showthread.php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit: I'm 99% sure that this isn't a hardware related problem. And LG's software not being able to turn the phone to stock is totally [email protected]#$%!

On some "unbrick your optimus 3d" threads i came across this image:
http://attachments.xda-developers.com/attachment.php?attachmentid=667470&d=1311752328
i tried all methods around here but not once i came across a screen like it. weird...

well i give up guys. so much technical [email protected] going on and no one seems to understand this device enough. i'll turn it to the LG Repair Service today. Thank you everyone for your help...

SD card issues

Hi,
I have a Samsung nexus S GT-19020
I had some issues booting recently so I decided to root it and put on cyanogenmod, I'm now having issues with the SD card. I can mount the card fine and view the contents however when I delete files or add them they reappear/disappear when I remount the SD card. Does anyone have any idea on what this might be? I've used adb shell to mount it and remove the files to no avail so I've ended up with a phone that can't save anything!
Thanks in advance,
Mrpinksss

First things first, make a backup. Copy any and all important files off of the phone and onto the computer, and it would be wise to copy the entire /sdcard even if there is stuff you don't think you need. If there are specific files/settings you are unsure how to backup manually feel free to ask, these may be located in /system or /data. Furthermore, i would recommend making a backup of your /efs folder (at least copy the entire folder and save it somewhere safe on the computer - be sure to get all hidden files starting with a DOT [.]), just in case if you havn't done so already.
Once this is done and anything left to worry about is behind us, try formatting the /sdcard via clockworkmod and see if that does anything. If not, post again and i'll think of some new things to try

yeah everything is backed up, I've tried to format with clockwork multiple times now with no luck. I've also tried formatting with fdisk with no luck either

Start over from the beginning and lock/unlock your bootloader which will erase/format everything. After you have everything backed up, of course, as previously mentioned.

so I tried fastboot with the stock ice cream ROM 4.0.2 which seemed to work but it won't boot and just gets stuck at the Google logo. I also locked the bootloader but when I try and unlock it I get a
FAILED (remote: Erase Fail)
thanks for your help so far!

Sounds like a busted SDCard. These are known for giving up, often quite randomly and with no warning. It is a hardware issue and generally needs Samsung to sort out the issue for you - it should be covered by warranty so long as it is still within the warranty period.

MrPinksss said:
so I tried fastboot with the stock ice cream ROM 4.0.2 which seemed to work but it won't boot and just gets stuck at the Google logo. I also locked the bootloader but when I try and unlock it I get a
FAILED (remote: Erase Fail)
thanks for your help so far!
Click to expand...
Click to collapse
Crapola, that sucks. Hmmm...
I did a search for that error message and lots of stuff came up on xda and elsewhere and i think harbb is right, your hw might be borked. Lame-o....

Well at least I got it locked and back to a stock ROM, shall take it into Vodafone.
Many thanks!

[Q] Ooops - Tab's funked. Help!

P6800 running Zeta
I was browsing facebook the other night when... shaboom - everything froze. No biggie I thought, I'll just do a little reset (I was getting a few FCs here and there anyway lately) and I'll be good to go...
NOPE. It started bootlooping at the initial Samsung Galaxy Tab 7.7 screen. I'm able to enter CWM recovery and even wipe the cache and flash ZIP files, but when I try to wipe data/factory reset, wipe the Dalvik cache or restore a Nandroid backupI get a System Error. It doesn't look good.
Is there a way to fix my seemingly funked /system without losing all my internal SD card data (where my Titanium backups reside) or to recover it before a full Odin flash?

Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop

Do you dare to wipe the system folder and follow by flashing another ROM?
Sent from my GT-P6800 using xda app-developers app

iena said:
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Click to expand...
Click to collapse
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data

Thread moved to Q & A section, post in the relevant section next time.

edan1979 said:
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Click to expand...
Click to collapse
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.

yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294

iena said:
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
Click to expand...
Click to collapse
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.

edan1979 said:
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
Click to expand...
Click to collapse
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.

Just reading the 1st post of the ZETA rom thread.
He says he is using stock Kernel.
He says every 5 lines, that you should full wipe...
without giving any sort of warning that it will eventually brick your device.

friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
Tried that one, but it won't mount unfortunately. The external will no problem, but when I try with the internal it just... well it does nothing. It's a bummer cause all my most recent backups are on the internal. Any other way of retrieving my data short of extracting the chip?
Giving it back to Samsung sounds like the best option, but I'm worried cause it has a custom ROM and it's rooted. Anyone has experience doing that?
Also I thought full wipes were good, but you're saying they eventually brick the device? How come? I thought having a custom recovery meant it would be virtually impossible to brick my device... and the weird thing is that it happened during normal usage, not while flashing.
Anyway, my priority is obviously to get my tab working again, but retrieving my internal data is second highest. Isn't there a flashable ZIP that would copy the contents of the internal SD into an external SD card? Surely this has happened to someone before me?
Thanks for all the answers, really appreciated!

bruce16878 said:
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Click to expand...
Click to collapse
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.

Oh I see, Thanks for the explanation. Learn something new today.
Sent from my LT18i using xda app-developers app

friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
edan1979 said:
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Click to expand...
Click to collapse
Gotcha! Will try that one and post result - thanks!

how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there

JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
Thanks for that. I haven't tried anything yet as I'm away till Weds, but I will then and let you know. So you're saying by flashing stock HC via Odin and wiping/resetting everything through stock recovery I won't lose my internal storage data?

that's what i experienced..but i could not guarantee that it will be the same for your device
i noticed that because old folder are not deleted when i rebooted, but i haven't checked if the system folders are cleared
to have a clean reflash i also format/sdcard on recovery..but don't do this on stocl ICS recovery since you might risk increasing the damage
try to format via odin the Honeycomb fw first [don't put PIT file neither enable Repartion, just normal flash]
then force it to enter recovery mode when it bootloops after reset
you might fix your device this way if it has softbrick
just resort to using PIT/repartition as your last option

Again I would not recommend repartition when tab still under warranty. Repartition the last resort only if the tab is without warranty after failing all other alternatives.

JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck

al128 said:
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
Click to expand...
Click to collapse
Ok I'm gonna do it. There are dozens of versions of HC for the 6800 though, can I just pick any or do I need to find out what it was running out of the box? Mine came from Singapore.

[Q] nexus s strange brick

Hello there guys i got an issue on my nexus s i9023 and am describing you the situation fast.
Nexus running good custom rom matrix kernel etc and one day i was in need to remove battery cause of a small stuck.
after that moment the nexus booted on android staying there on the main screen playing the live wallpaper and then poof reboot and the same forever till the battery is of..
i tried wiping everything even sd card at last but it seems that i cant touch it at all.the sd card coudnt be deleted.(i had it encrypted before throught the phone)
i tried formating my sd card from home pc and i got ''format complete'' but when i opened again cwm everything was still there on sd. old forders old everything..cant restore from nandroid too.
do you have any idea whats the matter or some command to use to fix it?
i really need help there i cant afford bying one new..:highfive:

what ROM?

ej8989 said:
what ROM?
Click to expand...
Click to collapse
AOKP Build 5 Milestone 1 Jelly Bean

have you tried flashing another rom in cwm recovery?

ej8989 said:
have you tried flashing another rom in cwm recovery?
Click to expand...
Click to collapse
i tried flashing another rom both throuth the cwm and command promt from my pc...
cant understand whats really happened..but i think there is a problem in the sd(cause of that i cant erase it)

remake partition
try remake partition
for windows
run -> diskpart can remake partition for your nexus s
command sequence: select disk, select partition, delete partition, create partition primary
for linux
terminal -> fdisk

am gonna try it at once...
I found my disk of nexus s but it seems that i can handle partition...
it saying when i type ''list partition'' only one partition the one of nexus s..
the i command select partition=1
and the respond is no partition is found..am i doing something wrong?

yeah am sure now i just check select partition of another disk on my computer and is ok...
the system doesnt letting me to touch partition

here is the picture of cmd while giving commands...dunno what am doing wrong.
i achived to select other partition from other disk and it was fine but not on nexus.

image
wertytemplar said:
here is the picture of cmd while giving commands...dunno what am doing wrong.
i achived to select other partition from other disk and it was fine but not on nexus.
Click to expand...
Click to collapse
image size is too small to recognize.
when you select partition, diskpart displays what?

first i select disk example ''select disk 2''
''disk 2 is now selected''
then i press ''list partition'' so i can see how many partitions there are there (there is only one)
then ''select partition 1''
''there is no partition selected''

dl. dropbox. com/ s /m3uvqik9gk27tst/ I9023_XEN_I9023XXKD1_.zip ?dl=1
remove spaces
download above and flash using Odin in download mode
if u can get in fastboot

uxmanz said:
dl. dropbox. com/ s /m3uvqik9gk27tst/ I9023_XEN_I9023XXKD1_.zip ?dl=1
remove spaces
download above and flash using Odin in download mode
if u can get in fastboot
Click to expand...
Click to collapse
your link is invalid...
what this does?

i cant really find a way to format the memory...so bad that is intergrated....
anyone else help me please?

i have PM you some links and read,...please follow the steps

couldnt fix it.... odin doesnt seem to be responding with my nexus cause of pdanet couldnt be installed on my device...
am almost sure that there is a problem on the memory...

I'd first trying using Diskpart, and if that doesn't work, try flashing Stock using the command prompt. Like I mean full stock and with everything erased and whatnot. There's a guide somewhere in the forum's if you search for it.
Give that a try and let me know.
Regards,
Bomboholic

Bomboholic said:
I'd first trying using Diskpart, and if that doesn't work, try flashing Stock using the command prompt. Like I mean full stock and with everything erased and whatnot. There's a guide somewhere in the forum's if you search for it.
Give that a try and let me know.
Regards,
Bomboholic
Click to expand...
Click to collapse
i have tried many thinks till now....it doesnt seem like i can fix it really.
the only way to give command and take some feedback is from bootloader...
example(fastboot flash recovery.img)
(fastboot flash system.img) etc
when am trying to copy-paste something on sd (after mount it from cwm) its lost when i go back to mobile...
thank you for your time reading all these bro!:good:

Are you seeking to save the current data on your storage or you can afford losing it?

have you tried to format sdcard from cwm?...,..
if u can mount scdard from usb to computer ,.. u can use any partition software or even windows disk manager to format sdcard,...have u tried?

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.