Sony Tablet S Brick - Sony Tablet S

I guess I terribly messed up my tablet when trying to replace SuperUser with SuperSU.
Doesn't start anymore, recovery is reachable but I can't do anything with Condi's tools, it's just "waiting for device".
adb devices gives me the tablet in recovery mode.
Here's the recovery log, I really hope somebody can help me, I'm done with my knowledge...
Code:
Starting recovery on Thu Jul 25 17:23:42 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
E:Fail to read boot logo flag
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
stat /dev/block/mmcblk0p5 try 1: No such file or directory
stat /dev/block/mmcblk0p5 try 2: No such file or directory
stat /dev/block/mmcblk0p5 try 3: No such file or directory
stat /dev/block/mmcblk0p5 try 4: No such file or directory
stat /dev/block/mmcblk0p5 try 5: No such file or directory
stat /dev/block/mmcblk0p5 try 6: No such file or directory
stat /dev/block/mmcblk0p5 try 7: No such file or directory
stat /dev/block/mmcblk0p5 try 8: No such file or directory
stat /dev/block/mmcblk0p5 try 9: No such file or directory
stat /dev/block/mmcblk0p5 try 10: No such file or directory
failed to stat /dev/block/mmcblk0p5
E:Can't open /dev/block/mmcblk0p5
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
stat /dev/block/mmcblk0p5 try 1: No such file or directory
stat /dev/block/mmcblk0p5 try 2: No such file or directory
stat /dev/block/mmcblk0p5 try 3: No such file or directory
stat /dev/block/mmcblk0p5 try 4: No such file or directory
stat /dev/block/mmcblk0p5 try 5: No such file or directory
stat /dev/block/mmcblk0p5 try 6: No such file or directory
stat /dev/block/mmcblk0p5 try 7: No such file or directory
stat /dev/block/mmcblk0p5 try 8: No such file or directory
stat /dev/block/mmcblk0p5 try 9: No such file or directory
stat /dev/block/mmcblk0p5 try 10: No such file or directory
failed to stat /dev/block/mmcblk0p5
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410039
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 03:50:59 JST 2012
ro.build.date.utc=1333997459
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build5
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=SYS_017-user 4.0.3 TISU0077 120410039 test-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0077/120410039:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
drm.service.enabled=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
W:Can't unlink /cache/recovery/command

---

slinder154 said:
I guess I terribly messed up my tablet when trying to replace SuperUser with SuperSU.
Doesn't start anymore, recovery is reachable but I can't do anything with Condi's tools, it's just "waiting for device".
adb devices gives me the tablet in recovery mode.
Here's the recovery log, I really hope somebody can help me, I'm done with my knowledge...
Code:
Starting recovery on Thu Jul 25 17:23:42 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
E:Fail to read boot logo flag
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
stat /dev/block/mmcblk0p5 try 1: No such file or directory
stat /dev/block/mmcblk0p5 try 2: No such file or directory
stat /dev/block/mmcblk0p5 try 3: No such file or directory
stat /dev/block/mmcblk0p5 try 4: No such file or directory
stat /dev/block/mmcblk0p5 try 5: No such file or directory
stat /dev/block/mmcblk0p5 try 6: No such file or directory
stat /dev/block/mmcblk0p5 try 7: No such file or directory
stat /dev/block/mmcblk0p5 try 8: No such file or directory
stat /dev/block/mmcblk0p5 try 9: No such file or directory
stat /dev/block/mmcblk0p5 try 10: No such file or directory
failed to stat /dev/block/mmcblk0p5
E:Can't open /dev/block/mmcblk0p5
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
stat /dev/block/mmcblk0p5 try 1: No such file or directory
stat /dev/block/mmcblk0p5 try 2: No such file or directory
stat /dev/block/mmcblk0p5 try 3: No such file or directory
stat /dev/block/mmcblk0p5 try 4: No such file or directory
stat /dev/block/mmcblk0p5 try 5: No such file or directory
stat /dev/block/mmcblk0p5 try 6: No such file or directory
stat /dev/block/mmcblk0p5 try 7: No such file or directory
stat /dev/block/mmcblk0p5 try 8: No such file or directory
stat /dev/block/mmcblk0p5 try 9: No such file or directory
stat /dev/block/mmcblk0p5 try 10: No such file or directory
failed to stat /dev/block/mmcblk0p5
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410039
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 03:50:59 JST 2012
ro.build.date.utc=1333997459
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build5
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=SYS_017-user 4.0.3 TISU0077 120410039 test-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0077/120410039:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
drm.service.enabled=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
W:Can't unlink /cache/recovery/command
Click to expand...
Click to collapse
Weird seems cache which is mmcblk0p5 is not mounting for some reason.
First of all DO NOT RESET TO FACTORY SETTINGS
How far do you get trying to boot normal? You get bootloop? If so you should still have shell access and should be able to use flasher.
Do you have rescue back-door installed? AKA lowered incremental? This will allow you to try install another zip
If you have tried the above then try to flash anything the lowest version of android you have.... I have all since R4 if you need BTW.
Remeber do not factory reset you will lose adb access on boot (recovery should still work, but shell is closed in recovery.
Good Luck
Stifilz

---

stifilz said:
Weird seems cache which is mmcblk0p5 is not mounting for some reason.
First of all DO NOT RESET TO FACTORY SETTINGS
How far do you get trying to boot normal? You get bootloop? If so you should still have shell access and should be able to use flasher.
Do you have rescue back-door installed? AKA lowered incremental? This will allow you to try install another zip
If you have tried the above then try to flash anything the lowest version of android you have.... I have all since R4 if you need BTW.
Remeber do not factory reset you will lose adb access on boot (recovery should still work, but shell is closed in recovery.
Good Luck
Stifilz
Click to expand...
Click to collapse
Unfortunately I already resetted some times. It's a really strange behaviour, sometimes the recovery boots normal, sometimes with errors stating "can't mount ...". Also I have different boot behaviour, while it usually doesn't get further than to the Sony logo, it sometimes reaches the boot animation (I think after a fresh wipe). But I never have boot loops, meaning I have to restart it myself.
I think I had rescue backdoor installed, yes. But I cannot flash the R5A, the only time it went that far (it usually freezes at some point) I had the "prohibited update" message.
I guess my tablet is unrecoverable due to the factory reset? (adb devices still works)

---

slinder154 said:
Unfortunately I already resetted some times. It's a really strange behaviour, sometimes the recovery boots normal, sometimes with errors stating "can't mount ...". Also I have different boot behaviour, while it usually doesn't get further than to the Sony logo, it sometimes reaches the boot animation (I think after a fresh wipe). But I never have boot loops, meaning I have to restart it myself.
I think I had rescue backdoor installed, yes. But I cannot flash the R5A, the only time it went that far (it usually freezes at some point) I had the "prohibited update" message.
I guess my tablet is unrecoverable due to the factory reset? (adb devices still works)
Click to expand...
Click to collapse
Maybe you will still have adb on boot. There are two system partitions, perhaps the boot animation partition has adb! If it does then should be an easy fix. Let me know if you have adb outside of recovery and we will sort it out. Also try to flash anything twice in a row without restarting and pull recovery.log

---

Thanks, but no adb there either, I'll have it sent to Sony and see what they'll do...
But thanks for the help so far!
Sent from my Nexus 4 using xda app-developers app

---

Today I get back my tab S from Sony, they didn't change any pieces and they give it to me with HC installed
And all of this for only 800 Mexican pesos (like 63.15 USD) cause I don't have warranty
They must have some kind of zip file or something to recover these tabs cause even my Internal SD Card files are untouched
I tried to flash HC Zips and a lot of ICS versions from stifilz list and I couldn't restore it
Sorry for bad english
Regards!

---

limax182 said:
Today I get back my tab S from Sony, they didn't change any pieces and they give it to me with HC installed
And all of this for only 800 Mexican pesos (like 63.15 USD) cause I don't have warranty
They must have some kind of zip file or something to recover these tabs cause even my Internal SD Card files are untouched
I tried to flash HC Zips and a lot of ICS versions from stifilz list and I couldn't restore it
Sorry for bad english
Regards!
Click to expand...
Click to collapse
Why didn't you have warranty? Was it over the time or did they suppose you are responsible?
Sent from my Nexus 4 using xda app-developers app

---

I bought it in 2011 and they just gave me 1 year of warranty...
I don't think they suppose that I was responsible cause I told them that I was updating to the new release (r5a) and suddenly it didn't boot anymore (trying to have a free repair :fingers-crossed: ) but nope they just charge me the technicall service or something like that, and they said that didn't required to change any pieces
And btw I brick my tab just cause I tried to convert the QuickPic app into a system app with Titanium, and when rebooted it stucks at SONY logo, no adb or recovery with any zip found here.
If I only understand a little better about condi's AIO or Flasher maybe this didn't happen to me but its kind of confusing starting with the language :silly: (It's so easy to repair a Xperia phone but this tab... )
Regards!

---

limax182 said:
Today I get back my tab S from Sony, they didn't change any pieces and they give it to me with HC installed
And all of this for only 800 Mexican pesos (like 63.15 USD) cause I don't have warranty
They must have some kind of zip file or something to recover these tabs cause even my Internal SD Card files are untouched
I tried to flash HC Zips and a lot of ICS versions from stifilz list and I couldn't restore it
Sorry for bad english
Regards!
Click to expand...
Click to collapse
Can you do us a huge favor??????
If you can ROOT it before upgrading to ICS and then look in the file /cache/last_log or something like that. It will tell us the name of the special file so we can try to find it on their servers. Should look like a normal file name with installer instead of ota in it.
Thanks

---

I've got this trying to root with condi's AIO tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read sometime ago about the kernel version that make some Sony Tab S unrootable
This is my "About tablet" section
Model number: Sony Tablet S
Android version: 3.2
Kernel version: 2.6.36.3 [email protected] #1
Build number: 1.10.001100002
Regards!

---

limax182 said:
I've got this trying to root with condi's AIO tool
View attachment 2149091
I read sometime ago about the kernel version that make some Sony Tab S unrootable
This is my "About tablet" section
Model number: Sony Tablet S
Android version: 3.2
Kernel version: 2.6.36.3 [email protected] #1
Build number: 1.10.001100002
Regards!
Click to expand...
Click to collapse
Update tablet to latest version, 4.0.3r5a, then root using Condi's S.onyTablet.S [ALLinONE] Tool.

---

Yeah that's what I was going to do but I wanted to do the instructions that stifilz said about the /cache folder
Can you do us a huge favor??????
If you can ROOT it before upgrading to ICS and then look in the file /cache/last_log or something like that. It will tell us the name of the special file so we can try to find it on their servers. Should look like a normal file name with installer instead of ota in it.
Thanks
Click to expand...
Click to collapse
I tried via ADB but of course permission denied
Regards!

---

limax182 said:
Yeah that's what I was going to do but I wanted to do the instructions that stifilz said about the /cache folder
I tried via ADB but of course permission denied
Regards!
Click to expand...
Click to collapse
Interesting that you are on 11000. Damn, was hoping you we on 0042 and root-able. Oh well nothing we can do. Might as well upgrade to R5a and root.
Thanks for trying,
Stifilz

---

And if I try to flash a zip from your list? Will the cache folder going to be erased?
Also if I upgrade with OTA update, I will not be able to use some AIO tools or flasher??
Cause someday I read something about the adb in recovery mode
Regards!

---

limax182 said:
And if I try to flash a zip from your list? Will the cache folder going to be erased?
Also if I upgrade with OTA update, I will not be able to use some AIO tools or flasher??
Cause someday I read something about the adb in recovery mode
Regards!
Click to expand...
Click to collapse
Cache will show the last update which will change when you flash an update. You won't need flasher as r5a is now rootable using AiO. Best advice install r5a then root and rescue back door with AiO

---

Well looks like I got myself in the same problem than the OP....
SuperUser was getting buggy after I installed Greenify, so I switched to SuperSU a few days back(which did a clean-up/removal of SuperUser, kinda normal as to remove any conflict) everything was fine, tablet S ran smooth...came back home today and realized that the clock was frozen while docking in the cradle...couldn't even turn the tab off, so did a pin reset to reboot it and here we go stuck on Sony Logo...
I was able to get into recovery just fine at the beginning and could see the external SDcard just fine at first (as I was going to flash custom prerooted stock) ...but now when I boot into recovery I get this prompt:
E: Fail to read boot logo flag
E: Can't Open / Dev/block/mmcblk0p5
(No Such file or directory)
E: Failed to Mount /cache (No such file or directory)
E: Can't mount/ cache/recovery/command
E: failed to mount /cache (No such file or directory)
E: failed to mount /cache (No such file or directory)
Don't have access to SDcard anymore, so no zip through recovery...
Was able to reinstall the adb drivers ( I can see it in Device Manager) but got problem with MTP though (no drivers installed for this device)
And I haven't done a factory reset in recovery...so any help from here would great if one got some ideas...Thanks

---

-DM- said:
Well looks like I got myself in the same problem than the OP....
SuperUser was getting buggy after I installed Greenify, so I switched to SuperSU a few days back(which did a clean-up/removal of SuperUser, kinda normal as to remove any conflict) everything was fine, tablet S ran smooth...came back home today and realized that the clock was frozen while docking in the cradle...couldn't even turn the tab off, so did a pin reset to reboot it and here we go stuck on Sony Logo...
I was able to get into recovery just fine at the beginning and could see the external SDcard just fine at first (as I was going to flash custom prerooted stock) ...but now when I boot into recovery I get this prompt:
E: Fail to read boot logo flag
E: Can't Open / Dev/block/mmcblk0p5
(No Such file or directory)
E: Failed to Mount /cache (No such file or directory)
E: Can't mount/ cache/recovery/command
E: failed to mount /cache (No such file or directory)
E: failed to mount /cache (No such file or directory)
Don't have access to SDcard anymore, so no zip through recovery...
Was able to reinstall the adb drivers ( I can see it in Device Manager) but got problem with MTP though (no drivers installed for this device)
And I haven't done a factory reset in recovery...so any help from here would great if one got some ideas...Thanks
Click to expand...
Click to collapse
Try to boot without going into recovery. If you have adb shell access with su then you can use Flasher to fix this. Make sure you have plenty of room on your internal sd (best to use adb pull /sdcard and then delete some big files) you will need lots of room to have the files copied over and then extracted. If that doesn't fix it there will be a way as long as you have adb shell and root! You will be fine
Stifilz

---

stifilz said:
Try to boot without going into recovery. If you have adb shell access with su then you can use Flasher to fix this. Make sure you have plenty of room on your internal sd (best to use adb pull /sdcard and then delete some big files) you will need lots of room to have the files copied over and then extracted. If that doesn't fix it there will be a way as long as you have adb shell and root! You will be fine
Stifilz
Click to expand...
Click to collapse
Thanks for the reply...
If I try to boot without going into recovery , my tablet is not recognized when I plug it into my computer (it just sit at the sony logo, no new hardware found, no MTP...), now if I boot into recovery and plug it in, I do have a connection as Android ADB interface...
I never used adb shell before so I don't know how to really run commands , but I did figure out how to use the cmd prompt and access the adb folder from prompt, I did a "adb devices" command to see a list of devices attached and I get this:
View attachment 2153130
it seems kinda odd that my device is 0123456789ABCDEF ?!?!
Tried "adb pull / sdcard and I get this:
View attachment 2153158
View attachment 2153170
View attachment 2153180
View attachment 2153193
As I said before I never used adb commands, I understand what to do if explained and I never give up so I'm good for next if anything is possible....
edit1: adb shell command return this : exec '/system/bin/sh' failed: No such file or directory (2)
so if I understand this correctly it means that I don't have remote shell access and I'm pretty much screwed...
edit2: after fiddling around with some adb commands, I was able to access my external SD from recovery and tried to update system from SD card, selected custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip (by the way I was on a different firmware before all this thing happened , it was the firmware prior to R5 if I recall properly)...well no go either, as I get a prompt in recovery saying:
--Install /sdcard ...
Finding update package...
Desklunvr update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted

---

-DM- said:
Thanks for the reply...
If I try to boot without going into recovery , my tablet is not recognized when I plug it into my computer (it just sit at the sony logo, no new hardware found, no MTP...), now if I boot into recovery and plug it in, I do have a connection as Android ADB interface...
I never used adb shell before so I don't know how to really run commands , but I did figure out how to use the cmd prompt and access the adb folder from prompt, I did a "adb devices" command to see a list of devices attached and I get this:
View attachment 2153130
it seems kinda odd that my device is 0123456789ABCDEF ?!?!
Tried "adb pull / sdcard and I get this:
View attachment 2153158
View attachment 2153170
View attachment 2153180
View attachment 2153193
As I said before I never used adb commands, I understand what to do if explained and I never give up so I'm good for next if anything is possible....
edit1: adb shell command return this : exec '/system/bin/sh' failed: No such file or directory (2)
so if I understand this correctly it means that I don't have remote shell access and I'm pretty much screwed...
edit2: after fiddling around with some adb commands, I was able to access my external SD from recovery and tried to update system from SD card, selected custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip (by the way I was on a different firmware before all this thing happened , it was the firmware prior to R5 if I recall properly)...well no go either, as I get a prompt in recovery saying:
--Install /sdcard ...
Finding update package...
Desklunvr update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Ok so there is normally no adb shell in recovery since the latest recovery anyway. Also you have no shell on normal boot. You may be ok still. BTW even after factory reset you will have adb in recovery.
Do the following.
Turn tablet off.
Enter recovery.
Try to flash a your normal region zip file. i.e 001 for USA. Do the oldest one you can. Let it fail and try it again.
Then use adb pull /tmp/recovery.log
Post your recovery.log here and we will have a look at it
Stifilz

---

stifilz said:
Ok so there is normally no adb shell in recovery since the latest recovery anyway. Also you have no shell on normal boot. You may be ok still. BTW even after factory reset you will have adb in recovery.
Do the following.
Turn tablet off.
Enter recovery.
Try to flash a your normal region zip file. i.e 001 for USA. Do the oldest one you can. Let it fail and try it again.
Then use adb pull /tmp/recovery.log
Post your recovery.log here and we will have a look at it
Stifilz
Click to expand...
Click to collapse
The problem is that when I get into recovery I don't have access to my external SD card, I always get
E: Fail to read boot logo flag
E: Can't Open / Dev/block/mmcblk0p5
(No Such file or directory)
E: Failed to Mount /cache (No such file or directory)
E: Can't mount/ cache/recovery/command
E: failed to mount /cache (No such file or directory)
E: failed to mount /cache (No such file or directory)
And when that happens, I can't flash anything from the external SD, I was able to get in recovery ONLY A FEW TIMES without the above messages and that's when I saw that I could read the external and then I immediately tried to flash this zip custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip but it gave me the "failed to verify signature" error, I tried a few times with the same results....when I rebooted I was even able to pass the Sony logo to the boot animation and it went into a bootloop...
I haven't been able to access my external SD since it happened those few times back then....and I'm running out of ideas on what to do with my problem right now...
By the way, when you say flash my "normal region zip file. i.e 001 for USA", you mean through recovery right??!?
The latest firmware I was on was ICS Release 1a (I never bothered upgrading higher than that as my tablet was super smooth/fast and my battery life would last forever even with very high usage, plus we had all those problem of non root-able R5a back in the days)...so if I put this firmware (the US ICS Release 5 Incremental
info.update.sony.net/ST002/nbx03_001/contents/0017/signed-nbx03_001-ota-incremental-120914044-from120803000.zip
(upload thanks to stifilz)
4shared.com/zip/MWOYlSmt/signed-nbx03_001-ota-increment.html
FILENAME: signed-nbx03_001-ota-incremental-120914044-from120803000.zip) on my external SD and if I'm able to access it through recovery again can I just flash the zip like that in recovery?!?
I'll download that zip and have it ready on my card just in case I'm able to access my external again....
And one last thing, if I can't do an update system from SD card as I'm unable to access the damn card , what other things could I try (if you have anymore ideas) ?
Thanks again