Xperia Tablet S Bricked and revived. Service tools obtained. - Sony Tablet S

Hello all. After bricking my Xperia tablet S by the next method: rooted it, then install a soft called as I remember PLay help, or something like that, a soft that helped you make your device look like any other in Google play sao you can install all apps even if they aren't made for your device. everything was ok but when i restarted my tablet it wouldnt pass the sony logo and than black screen.
So I tryed all methods provided within this forum, but nothing worked.
So I decided to sent it to service. they realized it was a soft problem and charged me about 40 $ to repair.
every thing is great now, BUT I have found in the box when I have picked up my tablet from service a 2 gb sd card
i thought that was the sd card used to resoft my tablet, so I inserted the sd card in my tablet and rebooted while holding the vol plus button and it started to say something like: cold-boot linux kernel from sd card. i didnt want to break it again because i didnt have enough power and I restarted my tablet. it works ok.
I want to see what it is on that sd card and share this tool with you, but for this I need help from you to create an image or something like that of this sd card. I have an macbook pro with os x maverick.
Any Ideeas?

Can you upload the files in a zip file?
Sent from my Nexus 4 using Tapatalk

CoolApps said:
Can you upload the files in a zip file?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
my macbook sees the sd card, but it tells me that is not in a recognisable format and wants to format it.

deltaztek said:
my macbook sees the sd card, but it tells me that is not in a recognisable format and wants to format it.
Click to expand...
Click to collapse
If you can, try puting ubuntu on a cd and live boot it on the computer then put in the sdcard and see if it recognizes it
Sent from my C6603 using xda app-developers app

Oh damn, dd it to a file. If you can't do this, I can connect to your computer with teamviewer.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi

I have created a raw copy with Hdd raw copy tool
the image is here. please download until 22 jan 2014
www wetransfer com/downloads/0bf376dc203efb9020b16ad377e5e47820140115102753/0734314e80d6048007785b2d3448fd3020140115102753/8c53e2
replace the spaces in the we transfer link with dots because i have received this error: The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!

deltaztek said:
I have created a raw copy with Hdd raw copy tool
the image is here. please download until 22 jan 2014
www wetransfer com/downloads/0bf376dc203efb9020b16ad377e5e47820140115102753/0734314e80d6048007785b2d3448fd3020140115102753/8c53e2
replace the spaces in the we transfer link with dots because i have received this error: The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Click to expand...
Click to collapse
I wrote the image to my sd card and it is containing 3 partitions. But it is not working for tablet s. Can you explain how can you able to boot the tablet from that card?
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi

smgdev said:
I wrote the image to my sd card and it is containing 3 partitions. But it is not working for tablet s. Can you explain how can you able to boot the tablet from that card?
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I have Sony Xperia Tablet S, which is the next generation of Sony Tablet S.
I have inserted the sd card and tried to boot but nothing happens. I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works.
I apparently can't do nothing with it besides being stuck on screen with this text: Cold-boot Linux.kernel from sd-card.

Wow !
deltaztek thanks for sharing this with us , i think this maybe will be the solution to many bricked devices.
Cheers
Vatis

Damn, this is cool stuff! Just what we needed, service to forgot recovery SD card inside debricked device! Let's see if we can learn how to use this, too bad I am having so little time nowadays.
Btw. what do you mean "I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works." ?
Do you mean that you cannot anymore access recovery, with or without recovery SD-card?
- What happens without SD-card, does your tablet boot normally
- Without SD-card, what happens if you try to go to recovery when booting by Power+Vol?
- With SD-card what happens when you boot normally?
- With SD-card what happens when you try to get to recovery?
I will download image, but my tab is not with me this weekend, damn...
Do NOT let your OSX format the card This is great great stuff.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
Oh and is the SD card itself ordinary generic SD card or is it some kind of Sony's special card or something?

jappaj said:
Damn, this is cool stuff! Just what we needed, service to forgot recovery SD card inside debricked device! Let's see if we can learn how to use this, too bad I am having so little time nowadays.
Btw. what do you mean "I can no longer acces the menu with Power+Vol UP or with Power +Vol UP+Vol Down, which I could before the service did the firmware upgrade. that is why is important this sd card, to see what it contains and how it works." ?
Do you mean that you cannot anymore access recovery, with or without recovery SD-card?
- What happens without SD-card, does your tablet boot normally
- Without SD-card, what happens if you try to go to recovery when booting by Power+Vol?
- With SD-card what happens when you boot normally?
- With SD-card what happens when you try to get to recovery?
I will download image, but my tab is not with me this weekend, damn...
Do NOT let your OSX format the card This is great great stuff.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
Oh and is the SD card itself ordinary generic SD card or is it some kind of Sony's special card or something?
Click to expand...
Click to collapse
Ok here is the strange thing...
When i connect the tab on my pc inside recovery i can not connect with ADB , BUT when i am on cold-boot and connect the tab on pc then showing that discovered a sony device then i dont have drivers but i install ADB test drive 2013 , then i can connect with ADB, any ideas? i try to shell but i am getting error :
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- exec '/system/bin/sh' failed: Permission denied (13) -
anything else i can try?
Cheers

Please explain how device works when this SD card is inside What happens when you boot normally this SD card inside, what happens if you boot Power-Vol ? When this cold boot appears, what did you do?
Next week I can get my tab back and can try this by myself...

jappaj said:
Please explain how device works when this SD card is inside What happens when you boot normally this SD card inside, what happens if you boot Power-Vol ? When this cold boot appears, what did you do?
Next week I can get my tab back and can try this by myself...
Click to expand...
Click to collapse
Ok here is the deal :
After you burn the .img on the sd card the windows stops see the sd card due to the format , so i have to boot linux to see whats is inside sd card, but some people reported 3 partitions .... on uper posts.
Anyway when you boot the tablet with the SD card inside either you try to go to recovery automatically booting from sd card and writing on tablet : Cold-booting linux. kernel from sd card , but nothing happens , now if you remove the sd card and try to boot to recovery wokring as before. If you boot to recovery and after put the sd card can read the sd card from recovery but there is nothing to flash.
Any ideas?
Edit : Can you see mate whats on sd card after burning the .img ? Whats so big for 1.8 gb ?

Hmh. Sound like me that said SD do not contain zip file to flash from the recovery, instead tablet recognizes it as some kind of special Sony's maintenance card an boots directly Linux kernel from the card. If I am correct, this way you can recover device even if recovery itself has been corrupted.
But if there is nothing happening after "Cold-booting linux. kernel from sd card", it could be that some extra gear is required. In example serial cable through which you can run shell commands or perhaps ordinary USB cable but some kind of special software would be needed to upload new images to the device. This is just a quess though.
Need to check out that img and what's inside after I have some time. Let's hope it is not encrypted and all files inside can be read...

jappaj said:
Hmh. Sound like me that said SD do not contain zip file to flash from the recovery, instead tablet recognizes it as some kind of special Sony's maintenance card an boots directly Linux kernel from the card. If I am correct, this way you can recover device even if recovery itself has been corrupted.
But if there is nothing happening after "Cold-booting linux. kernel from sd card", it could be that some extra gear is required. In example serial cable through which you can run shell commands or perhaps ordinary USB cable but some kind of special software would be needed to upload new images to the device. This is just a quess though.
Need to check out that img and what's inside after I have some time. Let's hope it is not encrypted and all files inside can be read...
Click to expand...
Click to collapse
Filer are not encrypted and image contains 3 partitions, one of them contains a full system rot filesystem, and second one contains something similiar to first and third is empty.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi

deltaztek said:
Hello all. After bricking my Xperia tablet S by the next method: rooted it, then install a soft called as I remember PLay help, or something like that, a soft that helped you make your device look like any other in Google play sao you can install all apps even if they aren't made for your device. everything was ok but when i restarted my tablet it wouldnt pass the sony logo and than black screen.
So I tryed all methods provided within this forum, but nothing worked.
So I decided to sent it to service. they realized it was a soft problem and charged me about 40 $ to repair.
every thing is great now, BUT I have found in the box when I have picked up my tablet from service a 2 gb sd card
i thought that was the sd card used to resoft my tablet, so I inserted the sd card in my tablet and rebooted while holding the vol plus button and it started to say something like: cold-boot linux kernel from sd card. i didnt want to break it again because i didnt have enough power and I restarted my tablet. it works ok.
I want to see what it is on that sd card and share this tool with you, but for this I need help from you to create an image or something like that of this sd card. I have an macbook pro with os x maverick.
Any Ideeas?
Click to expand...
Click to collapse
Very very interesting Thank you very much deltaztek for sharing!
It might bring some capabilities, downloading, will take a look
Shame I've got only Tab S, maybe it could be modded to work on 1st Tab S also?
Unfortunately I suspect, that it will work only on Xperia Tab, because of other boot maybe etc.
br
condi
------------------------------
ok, everybody who wants to take a look into partitions in windows,
there is an easy way.
1) download win32diskimager, write img to some SD card.
2) download linux reader, run it
3) voila - all the files accessible
-------------------------------
guys? some maybe stupid idea, but I havent seen that diagnostic card running on device.
if its native linux runned, with adb shell not accessible, but with svold.fstab content:
## SVold 1.0
#######################
## Regular device mount
##
## Format: edev_mount <label> <mount_point> <dtype> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## dtype - Device type
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_monitor sdcard2 /mnt/sdcard2 sd auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
edev_mount usbdisk1 /mnt/usbdisk1 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk2 /mnt/usbdisk2 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk3 /mnt/usbdisk3 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk4 /mnt/usbdisk4 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk5 /mnt/usbdisk5 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk6 /mnt/usbdisk6 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk7 /mnt/usbdisk7 usb auto /devices/platform/tegra-ehci
edev_mount usbdisk8 /mnt/usbdisk8 usb auto /devices/platform/tegra-ehci
Click to expand...
Click to collapse
where all the usb devices should be mounted,
so you could connect usb keyboard via otg host cable,
and with it have access and control on linux command prompt?
anybody here could try?
------------------------
build.prop content:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=txs03_351-eng 4.0.3 IML74K eng.t-yanagawa.20120618.223335 test-keys
ro.build.version.incremental=txs03servicediag.eng.t-yanagawa.20120618.223335
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012ĺą´ 6ćśˆ 18ć—Ą ćśˆć›ść—Ą 22:36:32 JST
ro.build.date.utc=1340026592
ro.build.type=eng
ro.build.user=t-yanagawa
ro.build.host=t-yanagawa-laptop
ro.build.tags=test-keys
ro.product.model=Sony Tablet S_2
ro.product.brand=Sony
ro.product.name=txs03_351
ro.product.device=txs03
ro.product.board=txs03
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 is obsolete; use ro.product.device
ro.build.product=txs03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=txs03_351-eng 4.0.3 IML74K eng.t-yanagawa.20120618.223335 test-keys
ro.build.fingerprint=Sony/txs03_351/txs03:4.0.3/IML74K/eng.t-yanagawa.20120618.223335:eng/test-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite = 1
##NFC
#debug.nfc.fw_download=false
#debug.nfc.se=false
windowsmgr.max_events_per_sec=135
ro.tether.denied=true
ro.sony.sound.enabled=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=txs03_351
ro.sony.sku.base=txs03_351
ro.sony.build.id=TID0010000
ro.sony.build.incremental=120618223
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
keyguard.no_require_sim=1
ro.sony.wan.dispMenuNwTyp=true
rild.libpath=/system/lib/libhuawei-ril.so
ro.kernel.gps.data=/dev/ttyUSB3
ro.kernel.gps.ctl=/dev/ttyUSB4
ro.sony.wan.sar.enable=yes
ro.sony.wifisleep=0
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-sony
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
Click to expand...
Click to collapse
incremental value looks nice
ro.build.version.incremental=txs03servicediag.eng.t-yanagawa.20120618.223335

condi said:
Very very interesting Thank you very much deltaztek for sharing!
It might bring some capabilities, downloading, will take a look
Shame I've got only Tab S, maybe it could be modded to work on 1st Tab S also?
Unfortunately I suspect, that it will work only on Xperia Tab, because of other boot maybe etc.
br
condi
------------------------------
ok, everybody who wants to take a look into partitions in windows,
there is an easy way.
1) download win32diskimager, write img to some SD card.
2) download linux reader, run it
3) voila - all the files accessible
-------------------------------
guys? some maybe stupid idea, but I havent seen that diagnostic card running on device.
if its native linux runned, with adb shell not accessible, but with svold.fstab content:
where all the usb devices should be mounted,
so you could connect usb keyboard via otg host cable,
and with it have access and control on linux command prompt?
anybody here could try?
Click to expand...
Click to collapse
Amazing idea, i have the cable and i can try it tommorow, i will let you know
Cheers
Vatis

vatis24 said:
Amazing idea, i have the cable and i can try it tommorow, i will let you know
Cheers
Vatis
Click to expand...
Click to collapse
Waiting for results
-------------------------
interesting .sh files inside /xbin/..
chkbootloader.sh:
Code:
#!/system/xbin/busyboxbin/sh
if [ "$1" == "" ]; then
echo COMMAND NOT FOUND
echo Result:NG
exit 1
else
hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" >/dev/null
if [ $? -ne 0 ]; then
echo Cannot get Bootloader version
echo Result:NG
exit 1
fi
BL_1=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f6`
BL_2=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f7`
BL_3=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f8`
BL_4=`hd -c 4200 /dev/block/mmcblk0p8 | /system/xbin/busyboxbin/grep "5f 42 4c" | /system/xbin/busyboxbin/cut -d " " -f9`
BOOTLOADER=$BL_1$BL_2$BL_3$BL_4
echo Value, 0x$BOOTLOADER
if [ $BOOTLOADER -eq $1 ]; then
echo Result:eek:K
exit 0
else
echo Result:NG
exit 1
fi
fi
exit 0
diaginit.sh:
Code:
#!/system/xbin/busyboxbin/ash
/system/xbin/busyboxbin/awk '/^[a-z]/{sub(/=/," "); print "setprop "$1" \""$2"\""}' /system/build.prop > /tmp/setprop.sh
/system/bin/sh /tmp/setprop.sh
rm /tmp/setprop.sh
mount -r -w -t ext2 /dev/block/mmcblk0p1 /configs
mount -r -w -t ext4 /dev/block/mmcblk0p5 /cache
mount -r -t ext4 /dev/block/mmcblk0p10 /log
/system/xbin/busyboxbin/awk '/^[a-z]/{sub(/=/," "); print "setprop "$1" \""$2"\""}' /configs/local.prop | /system/xbin/busyboxbin/grep "bdaddr" > /tmp/setlocalprop.sh
/system/bin/sh /tmp/setlocalprop.sh
rm /tmp/setlocalprop.sh
setprop vold.decrypt trigger_restart_framework
export PS1="# "
That diag.init probably is being started on boot with service mode,
or should be initiated manually via running with shell.
Oh and there is SU binary already there
-----------------------
im thinking is it worth to replace system partition with nbx03 1st gen Tab S,
maybe we could use it on our devices also
-------------------------
there are some parametrs set in /property/ <<<<<<<<<< we could try to add "persist.service.adb.enable"
in order to get adb working

My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
---------- Post added at 11:21 PM ---------- Previous post was at 11:11 PM ----------
vatis24 said:
My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
Click to expand...
Click to collapse
Keyboard not working , i mean getting power but nothing happens, maybe a usb drive to usb port? with update zip ? just saying , any ideas?
Vatis

vatis24 said:
My wife going to sleep now i will test now the keyboard via usb on tablet i will revert very soon!!!
---------- Post added at 11:21 PM ---------- Previous post was at 11:11 PM ----------
Keyboard not working , i mean getting power but nothing happens, maybe a usb drive to usb port? with update zip ? just saying , any ideas?
Vatis
Click to expand...
Click to collapse
could you make a short video how this service mode looks?

Related

Help: Boot Loop on 2.1ROM

Hi all,
I currently facing boot looping on all 2.1 roms.
I.ve done a full wipe.
I've tried re partition my sd card but it's useless.
I've tried remove sd card & reboot (checking is my card cause the prob)
I was only able to flash those 1.5 rom.
My sd info @ siggy below.
go in recovery wipe phone then flash rom?
flash to the googlebits after flashing the rom?
Do a FULL wipe.
If you're using an 2.0+ ROM, you NEED a 2.6.29+ kernel.
i have done all the wipe. i have try to flash gbit after the rom or after reboot & flash. & kernal is in a rom which made by dev right?
You probably do something wrong
1. Wipe data/dalvik/ext
2. Flash ROM
3. Reboot
and now should work...
Maybe Radio issue??
Which ROM did You tried?
Sustanon said:
You probably do something wrong
1. Wipe data/dalvik/ext
2. Flash ROM
3. Reboot
and now should work...
Maybe Radio issue??
Which ROM did You tried?
Click to expand...
Click to collapse
im a flashaholic i know how to flash a rom as u see i able to flash 1.5 rom but not 2.1 rom. but previously i could flash 2.1 rom till recently i can't. & radio is lastest if im not wrong... i've try those current 2.1 on xda now.
and what does logcat say about the bootloop?
Was trying to flash aHerov0.3
i do run
adb logcat
./sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
so i use the move recovery log to sd & got this:
Starting recovery on Mon Mar 1 14:42:19 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
Build : RA-hero-v1.5.3.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405
ro.build.version.incremental=eng.u70000.20090827.103405
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Thu Aug 27 10:35:04 CST 2009
ro.build.date.utc=1251340504
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X02
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=hero
ro.product.board=hero
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=hero
ro.build.description=2.73.405.5 146733 CL#61267 release-keys
ro.build.changelist=61267
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.com.google.locationfeatures=1
persist.service.mount.playsnd=0
settings.display.autobacklight=1
settings.display.brightness=102
ro.ril.def.agps.mode=2
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-hero-v1.5.3.1
ro.factorytest=0
ro.serialno=HT99CL900166
ro.bootmode=recovery_manual
ro.baseband=6.35.09.26
ro.carrier=HTC-Australia
ro.bootloader=1.76.2007
ro.hardware=hero
ro.revision=128
ro.cid=HTC__023
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
I:Set boot command ""
Move recovery.log to SD
Press HOME to confirm,
any other key to abort.
Moving : .
Click to expand...
Click to collapse
help help
recovery.log only helps if you have problems with with the recovery. either add adb to ahero or get another rom where it works...
what do you mean add adb to ahero? i though adb on my pc work on android device?
i'v tried
kagudroid
ahero
vanillain
ckdroid
openeclair
chpoubs
hero21
villain
but none is working for me...
sorry i meant add logcat to ahero, not adb. of course adb is on the pc.
Code:
[email protected]:~$ adb shell ls -l /system/bin/logcat
-rwxr-xr-x 1 0 2000 9736 Aug 1 2008 /system/bin/logcat
kendong2 said:
sorry i meant add logcat to ahero, not adb. of course adb is on the pc.
Code:
[email protected]:~$ adb shell ls -l /system/bin/logcat
-rwxr-xr-x 1 0 2000 9736 Aug 1 2008 /system/bin/logcat
Click to expand...
Click to collapse
adb shell ls -l/system/bin/logcat-rwxr-xr-x <<< likdis?
that should show you how it *should* look...
i downloaded ahero (took forever...). it actually contains logcat (would be stupid to leave it out anyway), not sure why you get that error. here is what you do, make sure to follow the steps exactly:
0: obviously boot to recovery.
1: make sure your update.zip is correct, redownload when in doubt.
2: go through wipes 1&3 (data and ext), reboot again to recovery.
3: flash the rom.
4. "adb pull /tmp/recovery.log ."
5. reboot and start logcat. you can do this: "adb logcat > logcat.txt", then the output will be redirected to logcat.txt. if it loops and you recognise the loop (i.e. the bootanimation starting from the beginning) let it loop twice, then cancel logcat with ctrl-c. if you don't see the loop wait 3 to 5 minutes, then cancel.
6. zip that recovery.log and logcat.txt and put it here.
let's hope that works.
still dont understand from step 4 onward =.=" sorry for being a dumb
Code:
adb pull <remote> <local>
copies a file from your phone to your pc. the file on your phone is obviously /tmp/recovery.log, the period "." at the end stands for the current directory (probably something like c:\androidsdk\tools if you are on win). you can also use
Code:
adb pull /tmp/recovery.log c:\recovery.log
same goes for pushing
Code:
adb push <local> <remote>
local is your pc, remote your phone.
adb logcat gives you the log output of your phone. there is a lot of data going through, so might wanna redirect that into a file with the ">" sign:
Code:
adb logcat > file.xyz
again pay attention for the path, if you don't specify it the current directory is used. when in doubt use the full path:
Code:
adb logcat > c:\file.xyz
now try again, and if you still have problems please be more specific what your problem is. say what works and what doesn't, and if there are error messages quote them here. and what operating system are you using on your pc?
Here: logcat&recovery.rar
e.japonica said:
Here: logcat&recovery.rar
Click to expand...
Click to collapse
do you have an ext4 partition on your sdcard? if so repartition to ext2 or ext3 (ext2 if you ask me), since we don't have the kernel sources we can not add ext4 support to the kernel used in 2.1.
if you don't have an ext4 partition then repartition aswell, the problem is with the ext partition:
Code:
I//system/bin/sh( 44): mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
edit: saw your signature now... could've thought of that earlier
but now you see how easy it is once you supply the correct information. if you had attached that logcat to your first post you've had the answer in the second post...
edit2: you might wanna leave out that swap partition. not sure how different roms react to that, and it wasn't there in the original setup (as in when it left htc's factory).
so i should make my ext partition to 2/3?
and swap = 0?
actually i didn't know the use of swap as i just following guide. as for ext partition i only know is for the a2sd
Thanks Kendong you help me out again! you'r very nice

[Howto] App2sd Step by Step

This new Turial is not from me credits go to tot31
I'm writing the how to my own way, hope this will more helpful..
How To : App2sd on Xperia X10i mini
Pre Installation.
I'm assuming that you have just fresh install 2.1/1.6 firmware and root your phone before you start the procedure. This is how I did with my phone.
1. Reinstall 2.1 firmware by using Sony Ericsson Update Service.
2. Root the phone by using SuperOneClick ( http://d01.megashares.com/dl/1xcuTic/Super...4-ShortFuse.zip ). More info on SuperOneClick, go here -> http://forum.xda-developers.com/showthread.php?t=803682
Note : Please disable any anti virus especially Kaspersky as it will give false virus alarm and will delete one of the file.
Step 1 : Preparing your micro SD Card.
Please refer to this link ( http://forum.xda-developers.com/wiki/index...rd_partitioning ) on how to prepare your micro sd card. For better performance I would advise that you use a Class 10 card instead of the original card that comes with the phone because the card is only Class 2 card. For more infomation on speed class rating of sd card please go here -> http://en.wikipedia.org/wiki/Secure_Digital
An excerpt taken from wikipedia :-
The following are the ratings of some currently available cards:
* Class 0 - These cards do not specify performance, which includes all legacy cards prior to class specifications.
* Class 2 - Minimum of 2 MB/s performance. Lowest speed for SDHC cards.
* Class 4 - Minimum of 4 MB/s performance.
* Class 6 - Minimum of 6 MB/s performance.
* Class 10 - Minimum of 10 MB/s performance.
Note : The recommended maximum size of ext2 partition is 1.4GB. I've tried 3GB before and ended up with unstable system and eventually crash the phone. So if you're really greedy since you've bought a 16GB or 32GB card to partition the ext2 more than the recommended size and if your phone is unstable, you've been warn.
Step 2 : Download the related files.
1. App2sd : see attachment
2. adb shell : see attachment
Step 3 : Enabling USB Debugging mode on you phone.
Go to Settings -> Applications -> Development -> USB Debugging (check this option).
Step 4 : Installing App2sd.
Create a folder name adb in your pc and extract all the files from adb.zip into this folder.
Connect your phone to your pc and mount the sd card. Extract all the file from app2sd2.1.zip to the root of your sd card. Make sure to unmount the sd card before continue the next step.
In your pc open up a dos terminal box by typing cmd in the Search programs and files box.
Type
cd /adb
then type
adb shell
then type
sh /sdcard/app2sd.sh
you'll be presented by this screen...
+________________________________+
|********************************|
|*Welcome To wolfilein's App2sd *|
|*installing script *|
|********************************|
+--------------------------------+
~this version should be go on any device ~
+___________________+
|********************|
|* Menu *|
|* *|
|*[0] install app2sd*|
|*[1] remove app2sd *|
|*[2] exit *|
|********************|
+--------------------+
[0]
now just press the enter key & wait.
Important : Make sure to set your phone screen timeout to the max because Superuser will ask for your permission to allow this script to run. If your screen goes blank, you can't see this prompt and the installation will fail.
after a while you'll get this..
busybox is /system/bin/busybox
rm failed for /etc/mount_sd.sh, No such file or directory
+________________________________+
|********************************|
| finished going reboot now |
|********************************|
+--------------------------------+
Don't worry, actually it does not fail. I also got the same message and I also thought it failed but when install all the apps and check using Minitool Partition Wizard and Linux Reader for windows, all my applications are installed into my card (see my previous post with screenshot).
The Explanation
If you look through the app2sd.sh script, command rm /etc/mount_sd.sh means remove/delete the mount_sd.sh file from /etc folder, since that file does not exist in the fresh install phone, it gives this error message but continue with other commands..
rm /etc/mount_sd.sh
mv /system/bin/sh /system/bin/sh_bak
cat /sdcard/sh.sh > /system/bin/sh
chmod 777 /system/bin/sh
busybox cp /sdcard/mount_sd.sh /etc/mount_sd.sh
echo "
+________________________________+
|********************************|
| finished going reboot now |
|********************************|
+--------------------------------+
"
sleep 1
reboot
Finally after a reboot, your phone is ready with app2sd. From now on when you install any applications it will save into your sd card.
Disclaimer : Do this at your own risk. I will not responsible if any injuries or damage occur to you or your phone
wolfilein said:
/!\Warning this is for testing only/!\
¯¯ ¯¯
here is the script that "should work on the x10 minni"
i hadn't one so i can't say if it works
install is verry easy just
first make a second ext2 fomratted patition on the sdcard
extract the zip in the root of your sd-card
open an adb shell
and type in
sh /sdcard/app2sd.sh
then press just enter and app2sd will be installed
yout phone will reboot and then say me if it give errors
wolfilein
Click to expand...
Click to collapse
it says the folder do not exist
when said it this??
does the actually work?
i have an idea
can anyone of you guys ceck out wat habens if you add a bootscript to
/system/drm/DxDrm/init_drm.rc
/system/etc/hw_config.sh
anyone check this please
just a question.... do it "should work on the x10 minni PRO" ?? ( device with phisycal qwerty) ?
Sorry for my bad english !!
init.rc
what if i enter contents of drm.sh to init.rc?
check please this out!!
in the init.rc it seems the pregram must be a service
wolfilein said:
i have an idea
can anyone of you guys ceck out wat habens if you add a bootscript to
/system/drm/DxDrm/init_drm.rc
/system/etc/hw_config.sh
anyone check this please
Click to expand...
Click to collapse
init.rc
i'm not comfy editing init.rc.
I'm gonna try Autostart application from market first.
are you ignoring me ??
and you the autostartapp can't start before it's loaded on boot that means that you must first load the apps
hwconfig.sh
there is no hwconfig.sh in etc folder.
2 thing create one
and check if it excuted
and
check this file
/system/drm/DxDrm/init_drm.rc
wolfilein said:
2 thing create one
and check if it excuted
and
check this file
/system/drm/DxDrm/init_drm.rc
Click to expand...
Click to collapse
added code to init_drm.rc
did not work.
trying hw_config.sh
i will try to edit the init.rc
if i succes i will say it
no luck with hw_config.sh
so ive edit my script and i will upload it now on both
x10 an x10 minni this script should work on every android phone
so now your script is good also for x10 mini pro ??
simple way apps2sd
First, you have to make two partitions on your sdcard - Fat32 and ext2 (ext3)
Second, Mount ext2(ext3) on your device
Third, ln -s /system/app/xxx.apk \sdcard\ ext partition\ way you want\xxx.apk
Caution - never try to remove sdcard after this operation - very dangerious for the health of your device.
your way is not so good
and yes it !should! work now buti cannot test it
garbage
MasterKira said:
so now your script is good also for x10 mini pro ??
Click to expand...
Click to collapse
not really, this time it froze my phone on bootup at the SE logo.
I fear i might have to reflash n lose all my settings!

[HOWTO] Ubuntu on Folio 100

I'm sorry it took so long, I got lots of stuff to deal with. Good things are worth waiting for (i heard)
First off: You are responsible for any of your actions! Changes that are needed to boot Ubuntu on your folio will void your warranty!
Special Thanks goes to DerArtem for posting his Kernels, Weeds2000 for eMail support, topogigi for wifi hacking and last but not least the Ubuntu-Touch Team on IRC that made it possible for me to tweak the touchscreen driver.
However, the system you are about to create is not fully functional, there are still things missing (a working sound driver for example). Its nice to play with it anyway
Heres a quick walk-through:
We will flash a kernel to the toshiba folio tablet which makes it possible to boot from an sdcard or USB-stick (You have to choose one, we need at least 2GB, I'd recommend 4GB so you can install fancy stuff like OpenOffice etc.).
We will then create a root filesystem with rootstock, which will hold our Ubuntu system (similar to your hard drive-Ubuntu).
Finally, we have to tweak that filesystem and change passwords, copy wifi driver etc.
Then we're able to boot a beautiful Ubuntu.
Things you will need:
- A Computer running Linux (Debian / Ubuntu would be great. If you're not running Linux on your computer, running it on the folio would make absolutely no sense. Please don't ask, I don't know how to install it in Windows.)
- The files i added to this post
- A SD-Card, 2-4 GB should be fine.
- optional: A second SD-card, 128MB would be enough (for flashing)
- A USB hub (If you want to boot from USB AND use a keyboard.
- Some time... =)
The first thing you should do is flash one of the update.zip files; choose update-sdmmc.zip (this will boot your folio from sdcard) or update-usb.zip (this will boot from a usb pen drive), open it and unpack the content to a sdcard (This has to be a SDcard, we're gonna flash our device from there.)
Backup all your data on your folio (I'm serious! It'll be gone!) and turn it off.
Put the SDcard in its slot and turn the folio back on. Press + hold both power and volume up.
Follow instructions to do a system update (If you've never done this before you shouldn't start now =) )
When it reboots, your folio will show some funny black and white linux text stuff and hang somewhere. Congratulations! You just bricked your tablet. Now lets see how we can fix it... Turn it off (Keep power pressed for about 5 seconds) and take out the sdcard, put it in your PC.
It's getting messy now, so grab a beer and let's go:
Open a Terminal on your linux computer.
Code:
#echo "Hello world!"
If your console says "Hello World" you got it. Awesome! =)
Code:
#sudo apt-get install rootstock gparted
This will install rootstock, the tool we're gonna need to create our filesystem, as well as gparted, a tool for partitioning our flash drive. You can also install rootstock-gtk, the graphical version. Try it if you like:
Code:
#sudo apt-get install rootstock-gtk
I heard that ubuntu-netbook won't work because there are drivers missing, would somebody try that and report please?
If your beer is already empty when this is done, you need a faster computer. Tell your wife the guys at xda-developers told you so
Back to the terminal:
Code:
#sudo rootstock -f MyCoolHostName -l myCoolUserName -p myCoolPassword --seed xubuntu-desktop -i 2G --notarball
This will create our filesystem with a user called "myCoolUserName" and (theoretically) his password "myCoolPassword" and install a basic xubuntu-desktop. I had to change the password manually because it didn't work this way... We'll do that later.
Rootstock will download lots of packages (You could also set it up with "--seed ubuntu-desktop", then youll download even more packages or "--seed ubuntu-minimal" or kubuntu... I still didnt find a list of seeds online :-/
The creating will take quite some time, get another beer.
When this is done, you'll get a file like this : "qemu-armel-201104112120.img". We will now mount this image: (make sure the directory /mnt/ does exist and is empty:
Code:
#ls -la /mnt )
Code:
#sudo su
(its simpler to be root for now)
Code:
#mount -o loop qemu-armel-201104112120.img /mnt/
(You are aware that your filename is different, are you? Try this:
Code:
# mount -o loop qemu-armel-*TAB*
and your terminal will automatically fill in your filename. Awesome linux, huh? =)
)
Code:
#cd /mnt/etc/
#mv fstab fstab.bak
#echo "proc /proc proc defaults 0 0" > fstab
#echo "dev /dev tmpfs rw 0 0" >> fstab
Note that the first time we create a file called fstab (echo asdf > fstab), then we add one line to this file (echo asdfasdf >> fstab)
Now we need to copy our wifi-driver over. Remember I told you to write down the directory you put them in? =)
Code:
#cp /home/YourUserName/Desktop/FolioStuff/firmware /mnt/lib/firmware
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK.
Code:
#cd /
#chroot /mnt/
#passwd myCoolUserName
#passwd
#exit
That's it, we're out of the chroot.
It's now time to prepare the SDcard (The steps are the same for a USB Flash drive, I think you'll figure them out.)
Find out how your SDcard can be accessed (You should still be root):
Code:
# fdisk -l
In my card reader, it's "/dev/mmcblk0", it could also be "/dev/sdb1" in your computer.
Now there are two possibilities:
1. You know what youre doing. Then it's easy: You wipe the only partition (or, if there are more than one, the first partition) on your sdcard and format it with ext3:
Code:
#mkfs.ext3 /dev/mmcblk0p1
Note: The device is called /dev/mmcblk0, the partition itself /dev/mmcblk0p1 (Partition 1)
2. You are not sure about this. No problem, start gparted: (as root!)
Code:
#gparted
In the upper right corner, select your flash drive, delete all partitions and create one formatted with ext3. Close gparted.
Mount your freshly created partition somewhere (i chose /mnt2/):
Code:
#mkdir /mnt2/
Code:
#mount /dev/mmcblk0p1 /mnt2
We can now copy our filesystem over. Make sure you use exactly the same flags (rfp for recursive, force, preserve (attributes))
Code:
#cp -rfp /mnt/* /mnt2/
OK, that could work. Unmount the sdcard:
Code:
#umount /mnt2/
Put it in your folio and cross your fingers.
Wifi drivers will be up soon...
It's recommend to add build-essentials to your rootstock image too..
Because then you can easily build the wireless lan drivers on your devices..
Maybe I'll post a howto this afternoon!
Is this Ubuntu really usable (for daily work) with the folio 100 (touch, response speed, ecc.)?
Thanks.
Yup, it's usable for everyday work. It's quite fast on the Folio 100, I've been pretty impressed when I tested it a few weeks ago.
Thanks ph84
It seems most difficult than expected but, great job !
Only i have 1 question, bricking the tablet sounds dangerous... is possible break out the tablet and get a rock?
Thanksss!!!!!
if ubuntu is installed on sd, does that mean that we can dual boot foliomod from nand and ubuntu from sd/usb?
Hm... I'm using Ubuntu 11.04 and I'm getting this error at the end of the rootfs creation :
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
umount2: Dispositivo o risorsa occupata
umount: /tmp/tmp.zaZ1j1Tgt6/tmpmount/proc: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Dispositivo o risorsa occupata
Click to expand...
Click to collapse
Do you have any idea where I can find the log?
And this procedure will build in the tablet a dual boot? Or dualboot is another procedure?
what is the *.rar????
No it's for singleboot only...
You can only start Ubuntu installed on SD-Card/USB-Stick with this procedure...
I don't know wether the boot-partition is locked when you are booting ubuntu/android..
If not it should be possible to build some applications to flash the boot-partition on the running system to change from ubuntu to android
When I do the rootstock step,I got this error!!!Please help!!!
I: Base system installed successfully.
I: First stage install done
I: Using Chroot for installer
Adding 'local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
Generating locales...
en_GB.UTF-8... done
Generation complete.
Generating locales...
en_US.UTF-8... done
Generation complete.
/bin/installer: line 53: syntax error near unexpected token `+'
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
I: A logfile was saved as //rootstock-201104140706.log
I: Done
Click to expand...
Click to collapse
Could you upload an *.img for us in this forum?
or a databank,etc?
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
sony_tornado said:
what is the *.rar????
Click to expand...
Click to collapse
Nvm, I was talking crap...
schnudergof said:
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
Click to expand...
Click to collapse
Just try rootstock without the parameters on --seed..
Maybe it will work..
You wont have a Desktop Enviroment like Gnome or something but you wont need that for installing the wireless drivers...
And after installing wireless drivers you can install ubuntu-desktop or something with apt-get!
Ok, I have been looking at rootstock, and if you install rootstock-gtk and than click on tasksel there is a whole list of seeds to chose from. I Think im going to try build the netbook build.
On a side note:
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK
Click to expand...
Click to collapse
with chroot your only changing the root of your file system, your not running anything from there.
But its its in no way a complaint to your awesome guide! Thanks and keep up the good work!
shidima_101 said:
with chroot your only changing the root of your file system, your not running anything from there.
Click to expand...
Click to collapse
Thats right but when you change your root shell to the rootstock-fs you can also use sudo apt-get update/install and install it into the rootfs!
ph84 said:
Meanwhile, open another terminal. (This is linux! We're gonna multitask since our computer is capable of handling that!) Go to where you stored the attached files, for example
Code:
#cd /home/YourUserName/Desktop/FolioStuff
and unpack them:
Code:
#rar x *.rar
Click to expand...
Click to collapse
Where/what is the "attached files"?
Thanks
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
°EraZoR° said:
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
Click to expand...
Click to collapse
The files I found are only *.zip for update bootloader. Where is *.rar file?
Thanks

[Q] XTS (SGPT1211) brick - stuck on Sony Logo

Hi All,
first of all, I'm very sorry should ask dump questions but I am totally lost here. Have been trying for two months to get my tablet to work and tried thorugh all of your helpful tipps but nothing seems to work, so I would very very much appreciate any help!!
The situation: I have a Xperia Tablet S from the US, SGPT1211, which just shows the Sony Logo when turned on. I can access the Android recovery menu and have tried (several times) to install the JB R2 and R3 files from SD card (i used the US versions from here: http://forum.xda-developers.com/showthread.php?p=26882207).
The Updates start but at about 20%, they would just stop and says "Installation Aborted"
Also, I have tried to use @condi Unbricker (http://forum.xda-developers.com/showthread.php?t=2642436). It does install on my SD Card, but if I start the device using the SD card, it still hangs and the Sony Logo and does not show booting cold.
If there is anyone here, please please please help! @stifilz
(I bought the tablet while studying in the US and living in Europe now. Sony Europe won't look at it - not even for money...)
davhenry said:
Hi All,
first of all, I'm very sorry should ask dump questions but I am totally lost here. Have been trying for two months to get my tablet to work and tried thorugh all of your helpful tipps but nothing seems to work, so I would very very much appreciate any help!!
The situation: I have a Xperia Tablet S from the US, SGPT1211, which just shows the Sony Logo when turned on. I can access the Android recovery menu and have tried (several times) to install the JB R2 and R3 files from SD card (i used the US versions from here: http://forum.xda-developers.com/showthread.php?p=26882207).
The Updates start but at about 20%, they would just stop and says "Installation Aborted"
Also, I have tried to use @condi Unbricker (http://forum.xda-developers.com/showthread.php?t=2642436). It does install on my SD Card, but if I start the device using the SD card, it still hangs and the Sony Logo and does not show booting cold.
If there is anyone here, please please please help! @stifilz
(I bought the tablet while studying in the US and living in Europe now. Sony Europe won't look at it - not even for money...)
Click to expand...
Click to collapse
Hi, i am in the same situation that you and the same tablet, i tried too with Sony Unbricker program but never work for me even with 3 different SD Cards 2, 8, 16 GB and differents class 4, 6, 10 respective.
I found the original post about unbrick the tablet http://forum.xda-developers.com/showthread.php?t=2610791 but doesnt have any idea what to do because i am not a linux advanced user and low level's programming :crying:
Recovery log
Hi again @davhenry, i am posting the recovery log of my tablet maybe we are having the same problem that me. You could post your recovery log for compare, thanks
I would appreciate any help or any clue @condi, @stifilz
Starting recovery on Mon Apr 21 01:42:48 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
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 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d3b65d827f602
ro.boot.commchip_id=0
ro.boot.bootloader=0x00000009
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=0x00000009
ro.hardware=txs03
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TJDSU0177
ro.build.display.id=TJDSU0177
ro.build.version.incremental=131023017
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Wed Oct 23 08:43:49 JST 2013
ro.build.date.utc=1382485429
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
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=txs03
ro.build.description=SYS_052-user 4.1.1 TJDSU0177 131023017 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.1.1/TJDSU0177/131023017:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
debug.nfc.fw_download=false
debug.nfc.se=false
ro.ril.wake_lock_timeout=200000
ro.streaming.video.drs=true
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.irremote.devicefile=/dev/ttySIR0
ro.sony.display.release=release3
ro.sony.autovolume.threshold=10
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
ro.carrier=unknown
drm.service.enabled=true
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.sony.wifisleep=0
ro.sf.lcd_density=160
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.1_r4
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
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.cradle.settings=true
ro.sony.hdmi.settings=true
ro.sony.cabc.settings=true
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
init.svc.ueventd=running
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
rassegan said:
Hi again @davhenry, i am posting the recovery log of my tablet maybe we are having the same problem that me. You could post your recovery log for compare, thanks
I would appreciate any help or any clue @condi, @stifilz
Starting recovery on Mon Apr 21 01:42:48 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
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 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d3b65d827f602
ro.boot.commchip_id=0
ro.boot.bootloader=0x00000009
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=0x00000009
ro.hardware=txs03
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TJDSU0177
ro.build.display.id=TJDSU0177
ro.build.version.incremental=131023017
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Wed Oct 23 08:43:49 JST 2013
ro.build.date.utc=1382485429
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
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=txs03
ro.build.description=SYS_052-user 4.1.1 TJDSU0177 131023017 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.1.1/TJDSU0177/131023017:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
debug.nfc.fw_download=false
debug.nfc.se=false
ro.ril.wake_lock_timeout=200000
ro.streaming.video.drs=true
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.irremote.devicefile=/dev/ttySIR0
ro.sony.display.release=release3
ro.sony.autovolume.threshold=10
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
ro.carrier=unknown
drm.service.enabled=true
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.sony.wifisleep=0
ro.sf.lcd_density=160
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.1_r4
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
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.cradle.settings=true
ro.sony.hdmi.settings=true
ro.sony.cabc.settings=true
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
init.svc.ueventd=running
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
Click to expand...
Click to collapse
Unbricker is only for Xperia Tablet S not Sony Tablet S. I am partly in the same boat, although my one does run (honeycomb) lol. Anyway can you both please try the install your original update (i.e. to suit your region) twice in a row and then pull the recovery log. If you need help with this please see my FAQ thread in my signature.
Thanks
Its Works!!!
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
@rassegan
Thanks for your tips! However, I'm having some trouble following your advice: when using WIN32DiskImager to unpack the unbrick.zip onto my SD Card, I can no longer access the SD Card as it says it uses an unknown Data System.
Additionally, where did you unpack the OTA Software? directly onto the SD Card or rather on my desktop and then the SD Card? And could you detail the DOS unpacking using desklunvr.exe?
Sorry for asking so many questions, it would be so so so great if you had some additional comments!
@stifilz Thanks for your help, was abroad for a cpl of days and will try to pull the log file which I couldn't work out so far
@stifilz I'm having trouble to actually access my XTS via ADB. I follwed all your steps here (http://forum.xda-developers.com/showthread.php?p=30099315#post30099315) and installed a billion of drivers. I do see my tablet in the device manager als Android Device, however, it won't show if I enter "adb devices". Instead, the list is empty.
Anyone an indea what I'm doing wrong here?
Many thanks!!
davhenry said:
@rassegan
Thanks for your tips! However, I'm having some trouble following your advice: when using WIN32DiskImager to unpack the unbrick.zip onto my SD Card, I can no longer access the SD Card as it says it uses an unknown Data System.
Additionally, where did you unpack the OTA Software? directly onto the SD Card or rather on my desktop and then the SD Card? And could you detail the DOS unpacking using desklunvr.exe?
Sorry for asking so many questions, it would be so so so great if you had some additional comments!
@stifilz Thanks for your help, was abroad for a cpl of days and will try to pull the log file which I couldn't work out so far
Click to expand...
Click to collapse
Hi @davhenry, well i unzipped the file unbrick.zip in the same folder UNBRICK_DATA so you should be have a image file of 1.5 or 1.6 GB this image you would use at moment to copy in the SD CARD with the WIN32DiskImager
---------- Post added at 08:11 PM ---------- Previous post was at 07:51 PM ----------
davhenry said:
@stifilz I'm having trouble to actually access my XTS via ADB. I follwed all your steps here (http://forum.xda-developers.com/showthread.php?p=30099315#post30099315) and installed a billion of drivers. I do see my tablet in the device manager als Android Device, however, it won't show if I enter "adb devices". Instead, the list is empty.
Anyone an indea what I'm doing wrong here?
Many thanks!!
Click to expand...
Click to collapse
Hey again, i had the same problem, follow this thread i use the method A in my Windows 8.1 and download the zip file and unzip
Once time you unzipped the folder find the file android_winusb.inf and add this lines under the sony products
;SONY Sony Xperia Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_06AC&MI_01 (Verify if your PID is same as me )
Copy this line in GoogleNT_X86 and GoogleNT_amd64 and save the file
Update the drivers manually in the device manager
OMG guys, it worked!!!
I didnt do anything differet, for some reason it worked though. I am so grateful, thank you so so muc @stifilz and @rassegan!!
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
Hi..
Firstly, I'd like to apologize in advance for my bad english..
My Xperia Tablet S is an SGPT131A1 (Asia model)
Rooted and got it bricked few weeks ago..
Got panicked and recklessly did a full wipe..
Still stuck on Sony logo..
Thanks God I found Condi's post..
Gave it a try, and still did not work..
Still stuck on Sony logo..
There are several questions I'd like to ask you @rassegan
1. How do you copy the unbrick.img to the SD card? I tried using the Win32DiskImager as you mentioned above, but my SD card ended up having 0 byte of free space. Thus, the unbricker program cannot copy the rest of the file.
2. Eventually I formatted my SD card and skip part 3 instead. Followed Condi's unbricker program, chose option 6, and followed the instruction, but it did not succeeded to copy the files onto my SD card. Here's the screen capture of @condi 's program showing the error.
View attachment 2844352
Is there something wrong? Or did I miss some step?
Any help will be much appreciated..
Thanks in advance
If I do step 3 Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
how I can use S.onyXT.S [UNBRICKER] v1.0 after and does step 6 again if first partition have ony 71 MB????
{
"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"
}
all time is there error
but when I tried automatic process with S.onyXT.S [UNBRICKER] v1.0 fr4om 1 - 7 not works I never had ''COLD -booting '' message
I have only if I manually use Win32DiskImager and add unbrick.zip to sd card ( 8GB )
but how long will this process take?
I running long time and no change
PLEASE HELP HOW To recover back
davhenry said:
OMG guys, it worked!!!
I didnt do anything differet, for some reason it worked though. I am so grateful, thank you so so muc @stifilz and @rassegan!!
Click to expand...
Click to collapse
What you did MR can you help me please
I cant have cold boot anyhow from
S.onyXT.S [UNBRICKER] v1.0
ON the end I have xperia tablet S SGPT1211 back to live btw is R6A for all who will experiment as I did
on the beginning I Have 2 tablets SGPT1211 and will be using as multi -functional remote control
because I set up already first tablet to fully remote control functionality a I want copy data from one to second tablet
but I delete APPDATA from second one and whole unit after factory restore doesn't have all APP
and manually installed remote control APP crashed all time
I decide to recovery by sony tablet Flasher but I choose R5A which was for first tablet S gen - STUPID BOY
tablet has been unresponsive etc
I tried UNBRICER but not work!!!
on the end I copied UNBRICK DATA by win32diskimg to 8GB SD
after cold boot I run @condi's unbricker program from point 7 and after 30 min approx xperia tablet S SGPT1211 (R6A) return back to live
BUT not all APP installed
now I using Sony tablet flasher 3 @condi and choosing fw 4.0.3 1a for R6B and will see what happens.
hopefully this info will help someone to unbrick his device
after update 4.0.3 by @condi still missing some application
when install app ''remote control'' manually not working crashes all time
tabled cant see external SD card!!! as well dock USB !!!
I going to try 1b 4.1.1 and I hope will be back with all APK from factory
can anyone tell me how reinstall back to factory SGPT 1211US/S
urgas said:
I going to try 1b 4.1.1 and I hope will be back with all APK from factoryS
Click to expand...
Click to collapse
than with trouble reinstalled finally back to factory
how to:
use @condi S.onyXT.S [UNBRICKER] v1.0 and download all 2 files by choosing 1 for US(use for you correct version)
-unbrick data.zip
-update.zip
this program will unpack to the 3 files:
-image.img
-hiden.img
-unbrick.img
after download Win32DiskImager from here http://sourceforge.net/projects/win32diskimager/files/latest/download
take any SD card and upload unbrick.img to SD card by Win32DiskImager
when is done be sure all ABD driver installed and tablet is visible in device manager OK!!! when install drivers disable Microsoft signing driver enforcement!!!
add SD card to tablet and start tablet
cold boot info have show at top left corner
start @condi S.onyXT.S [UNBRICKER] v1.0 and choose 7
press enter and connect tablet to PC
!!!process will take approx 30min!!! be patience
-on the end error appears in @condi program don't worry
-restart tablet manually by holding power button
-boot to android
-some APP will missing
after do full restore by recovery console :
-off tablet by holding power button
-push and hold volume + and pres power button once
-count to 9 and release volume button
-recovery console appears and do factory restore
after is tablet finally back and working jeeeeeee :laugh::laugh::laugh:
what simple process I panicking last week haha
urgas said:
than with trouble reinstalled finally back to factory
how to:
use @condi S.onyXT.S [UNBRICKER] v1.0 and download all 2 files by choosing 1 for US(use for you correct version)
-unbrick data.zip
-update.zip
this program will unpack to the 3 files:
-image.img
-hiden.img
-unbrick.img
after download Win32DiskImager from here http://sourceforge.net/projects/win32diskimager/files/latest/download
take any SD card and upload unbrick.img to SD card by Win32DiskImager
when is done be sure all ABD driver installed and tablet is visible in device manager OK!!! when install drivers disable Microsoft signing driver enforcement!!!
add SD cart to tablet and start tablet
cold boot info have show at top left corner
start @condi S.onyXT.S [UNBRICKER] v1.0 and choose 7
press enter and connect tablet to PC
!!!process will take approx 30min!!! be patience
on the end error appears in program dont worry
restart tablet manually
let the boot to android
some APP will missing
after do full restore by recovery console :
off tablet
push and hold volume + and one power button once
count to 9 and release volume button
recovery console appears and do factory restore
after is tablet finally back and working jeeeeeee :laugh::laugh::laugh:
what simple process I did panicking last week haha
Click to expand...
Click to collapse
Ok regarding your english "restore" =reset
What generation tab do you have
Your english is just terrible if your going to do a guide like you have plz correct your grammer and your confusing words
I appreciate that english might not be your first language but your posts are confusing and will not be much help to people
Sent from my SGPT12 using XDA Free mobile app
xts unbrick
rassegan said:
Hey guys @davhenry @stifilz i could finally recover my Sony Xperia Tablet S following these steps and the Sony's Unbricker Software 1.0 by @condi
1) Unzip the software and make a new folder called "UNBRICK_DATA"
2) Download manually the files unbrick.zip and the correct OTA Software of your tablet
3) Unzip the unbrick.zip file and copy in the SD Card with Win32DiskImager
4) Rename your OTA Software ( Example: signed-txs03_201-ota-131023018.zip) to update.zip
5) Copy this file in the folder "files" in the program
6) Open and DOS Console in Windows and descrypt the file using desklunvr.exe. Example : desklunvr.exe update.zip
7) Make 2 image files with the recently file generate (update_deslunvr)
7za.exe x update_desklunvr.zip system.img
7za.exe x update_desklunvr.zip hidden.img
8) Copy the new images files and update_desklunvr in UNBRICK_DATA (these last file i did just in case )
9) Run Condi´s Program and make sure you go to the step 6 and just follow the instructions
The tablet reboot 2 times at the beginning looks like not working because get stuck in sony logo but turn off and turn on again and then ITS WORKSS !!! :laugh:
Good luck guys
Click to expand...
Click to collapse
Hi everybody thanks for this great topic
i try to follow this procedure but cannot find the files "unbrick.zip" you mentioned.
searched for a while with no success.
thanks for your help. :good:
Where the heck did you find all those files you mention?
Yes it works again
My Sony xperia s tablet sgpt1211 works again, thanks @condi
It wasn't easy but this is how it worked for me
1. download @condi unbricker program 
 @condi Unbricker (http://forum.xda-developers.com/show....php?t=2642436)
2. Run using option 3 (I have an eu no 3g tablet)
it will create all the files you need in a folder named unbrick_data
the software will probably fail at the step to create the sd card - no worries
3. dowload Win32DiskImager and write a copy of the unbrick.img file to the SD Card with the Win32DiskImager software.
4. Run @condi unbricker program and use option 7
after you put the sd card in the tablet just press the start button only and it should display the cold booting text on the sony logo page so you know something is working.
5. be patient and let the @condi software work through each step - some take up to one hour to complete.
6. If you get an error message from the @condi software you have to resolve the problem it won't work if an error occurs. You need to stop and go back through the steps again.
Keep trying it does work if you can solve all the hiccups.
Thanks again @condi
gordo588 said:
My Sony xperia s tablet sgpt1211 works again, thanks @condi
It wasn't easy but this is how it worked for me
1. download @condi unbricker program
@condi Unbricker (http://forum.xda-developers.com/show....php?t=2642436)
2. Run using option 3 (I have an eu no 3g tablet)
it will create all the files you need in a folder named unbrick_data
the software will probably fail at the step to create the sd card - no worries
3. dowload Win32DiskImager and write a copy of the unbrick.img file to the SD Card with the Win32DiskImager software.
4. Run @condi unbricker program and use option 7
after you put the sd card in the tablet just press the start button only and it should display the cold booting text on the sony logo page so you know something is working.
5. be patient and let the @condi software work through each step - some take up to one hour to complete.
6. If you get an error message from the @condi software you have to resolve the problem it won't work if an error occurs. You need to stop and go back through the steps again.
Keep trying it does work if you can solve all the hiccups.
Thanks again @condi
Click to expand...
Click to collapse
after root
Now my sony xperia tablet s open in this screen
ples. help my

[Tutorial] Blu Studio 5.0 LTE -Y530Q- Root Method

I have been searching for a way to root my Blu Studio 5.0 LTE - which doesn't seem Vulnerable to framaroot.
after 3 days of non stop searching and trying the basic one-clicks as well as trying a number of commands through terminal I have finally found one to root my device. Here is a bit of information on my device.
Model #: Studio 5.0LTE
Android Version: 4.3
Baseband Version: TBW599010_9520_LTE_V0104
ROM: Original Factory Shipped 4.3 - Will backup then unroot - update and see if it still works then post back
I am fairly new to posting to xda, but I have been using XDA since htc google G1 came out... and haven't used anything but androids for myself since... so thank you all and hopefully someone will be able to use this method that i found...
Note: I am not developer of the software that is used in this posting - and I am not responsible for any damage or warranty status that my be negated as a result of the use of this tutorial! This tutorial has possibility to brick your phone, which neither myself nor providers of the root software are responsible .
Note2: I have contacted Shuame about posting their software on alternate site and they have not responded - if they request me to though, I will remove file and post link.
First of all let me just inform you that this will remove the Messaging app from your phone - I haven't hacked the file to see what commands it's running but from what I can tell is they have exploited the sms app and in process of root the app is removed.
You will need - Blue drivers which you can download here - attached
{You can install the sdk and drivers with installer or unpack the exe and using computer management install the drivers within the folder.View attachment ADB-Driver-v1.4.2.zip
Then you can download the installation file for the one click type root method - virus free - attached below cause im not allowed to post links yet - but install the program - chinese mostly translated but follow few steps to install then after its rooted you will see it say on screen rooted and give you options.
Then you can either download from play store or from attached APK for messaging.View attachment 3156953
There you go - root can be checked with any software - I am still working on what cwm will work and will update - hope this helps!
Thanks a lot Great Work :good::good::good:
That saved me a lot of time. It worked perfectly. although I would like to add a few points
1. For me it didn't delete the messaging app so it was great
2. after rooting, I installed supersu from play store, restarted and then deleted the kinguser app
3. installed adfree to remove ads
4. In my case, the genius root didn't seem to work the first time since the phone was in MTP setting. As soon as I changed USB setting to storage the program worked
I have link to some custom roms for this phone from a different forum, let me find the links again and I will update.
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Ok found the links
well seems like I cant post any links until , I have 10 posts ..
but it is there on google plus
It would be great if you can make something out of these links .
---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------
FYI: This phone is a clone of k-touvh touch3 and there is a custom rom for the other phone. Not sure about the recovery or CWm
memory swap
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
vsmartguy said:
Thanks a lot Great Work :good::good::good:
That saved me a lot of time. It worked perfectly. although I would like to add a few points
1. For me it didn't delete the messaging app so it was great
2. after rooting, I installed supersu from play store, restarted and then deleted the kinguser app
3. installed adfree to remove ads
4. In my case, the genius root didn't seem to work the first time since the phone was in MTP setting. As soon as I changed USB setting to storage the program worked
I have link to some custom roms for this phone from a different forum, let me find the links again and I will update.
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Ok found the links
well seems like I cant post any links until , I have 10 posts ..
but it is there on google plus
It would be great if you can make something out of these links .
---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------
FYI: This phone is a clone of k-touvh touch3 and there is a custom rom for the other phone. Not sure about the recovery or CWm
Click to expand...
Click to collapse
You know, I heard that on the blu lte google+ page but I also heard that the roms were not completely working right. Something about the GPS doesn't quite work right when doing that, but I'm still looking as well
compary said:
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
Click to expand...
Click to collapse
I didn't have to do anything with the swapping of memory... i'm not sure what you mean, but I was able to install xposed and at least fix some of the lame inabilities of this ROM - including apps to sd
I think user "company" is talking about the fact that on other devices with 4GB or lower ROM space, developers have figured out a way swap sd card with internal sd card so now you have a lot more space to install apps. For example Lg f6 forum has large thread about this. Obviously it needs a rooted phone to get the swap to work.
---------- Post added at 11:33 PM ---------- Previous post was at 11:07 PM ----------
compary said:
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
Click to expand...
Click to collapse
I tried using the script on LG F6 forum but it didn't work. spent quite sometime to do debugging and this is what I have figured out
1. Internal naming of disk space is different between the phones
2. Also the block space assigned in my case was different
This is the 11extsd2internals script for LG F6 ( you need to follow all the previous steps like installing unitinit.apk , smanager etc)
sleep 2
mount -o remount,rw /
mkdir -p /data/internal_sd
mount -o bind /storage/sdcard0 /data/internal_sd
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /storage/sdcard0
mount -o bind /data/internal_sd /storage/external_SD
I think if we change it to this, it might work. Although I am not going to try this out untill I have CWM recovery for this device ( added comments).
#######################
# Warning this is untested , try at your own risk
sleep 2
# this will remount all the partitions again with read write permission
mount -o remount,rw /
# create an empty temp directory to link the internal sd card to it
mkdir -p /data/internal_sd
#mount old-dir new-dir. Bind the original space to the temp directory
mount -o bind /storage/emulated/legacy /data/internal_sd
# Now read the SD card ( I got 179:66 when I put a 64GB sd card). Read both vfat and exfat
mount -t vfat -o umask=0000 /dev/block/vold/179:66 /storage/emulated/legacy
mount -t exfat -o umask=0000 /dev/block/vold/179:66 /storage/emulated/legacy
# Once we have mounted the sd card , swap the internal memory to external memory
if mount | grep vold/179:66; then
mount -o bind /data/internal_sd /storage/external_SD
fi
chown system /data/media/0
#############################
As I said, This is untested and I am not going to try it out for the time being but if someone want to use this and update if this works
vold fs
# Copyright (c) 2012, The Linux Foundation. All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are # met: # * Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # * Redistributions in binary form must reproduce the above # copyright notice, this list of conditions and the following # disclaimer in the documentation and/or other materials provided # with the distribution. # * Neither the name of The Linux Foundation nor the names of its # contributors may be used to endorse or promote products derived # from this software without specific prior written permission. # # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
This is all it shows
I don't think we can make changes to vold.fs to fix the low memory issue.
It has to be done through either ROM support or making fixes to the init script as I posted.
Anyways if someone can figure out a way to put recovery CWM or TWRP on this phone , I can start playing around with the storage fixes.
I've tried all kinds of root and nothing is working. I'm on V10_generic for the build number. Any other root options? also please an os x or linux root option as i don't have a windows machine. I hope we can find something soon. thanks y'all
blu studio 5.0 lte y530q
I can not flash the mobile blu studio 5.0 lte y530q, Help me find firmware for it and for firmware custom recovery, turns off radio module and the extremely hot processor.
Thank you in advance for your help.
droidkeyboardfan12 said:
I've tried all kinds of root and nothing is working. I'm on V10_generic for the build number. Any other root options? also please an os x or linux root option as i don't have a windows machine. I hope we can find something soon. thanks y'all
Click to expand...
Click to collapse
Yep. King Root Dot net, v.4.6.2....
can you help me with the QCN file for BLU Y530Q please
tomelich said:
can you help me with the QCN file for BLU Y530Q please
Click to expand...
Click to collapse
I did not fix this phone model and threw it away, sorry, I can't help you at all.

Categories

Resources