Related
Sorry, to post my quetion here, but I'm not allowed yet to post over at the development part...
I was trying to flash ICS via the S.onyTablet.S v2.7 [ALLinONE], probably I did something terribly wrong.
Now when I start up my Tablet S the SONY logo comes up and then the tablet blanks and powers off.
I'm able to start the recovery.
I'm able to approach via ADB.
I'm getting error messages when trying to flash the different ROM's I found in the thread: "S.onyTablet.S v2.7 [ALLinONE] - new: ICS ROOT!.. more inside "
I think I made the mistake of not doing the things in the right order, but I saw others having this problem, but not the solution for this problem.
Hoping anyone can help me, almost a week with no tablet...!
Thanks in advance!
Flash this. It will revert you to 3.2.1 r2 US, which is rootable. If it errors, pull the recovery log with "adb pull /tmp/recovery.log" and post it here.
quiqsilver said:
Flash this. It will revert you to 3.2.1 r2 US, which is rootable. If it errors, pull the recovery log with "adb pull /tmp/recovery.log" and post it here.
Click to expand...
Click to collapse
Flashing gives the error: Prohibit update as a result of checking version or base sku
Recovery.log:
Starting recovery on Thu May 3 08:28:52 2012
framebuffer: fd 4 (1280 x 800)
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 /vsd ext4 /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
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=THMASU0035
ro.build.display.id=THMASU0035
ro.build.version.incremental=0035.002
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2.1
ro.build.date=Fri Nov 4 17:35:39 JST 2011
ro.build.date.utc=1320395739
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_002
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=nbx03_011-user 3.2.1 THMASU0035 0035.002 test-keys
ro.build.fingerprint=Sony/nbx03_002/nbx03:3.2.1/THMASU0035/0035.002:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r3
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_011
ro.sony.sku.base=nbx03_011
ro.sony.build.id=THMASU0115300
ro.sony.build.incremental=111104028
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.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
prev version[111201033] is larger than post version[111201009]
Erohibit update as a result of checking version or base sku
Installation aborted.
Starting recovery on Thu May 3 08:59:13 2012
framebuffer: fd 4 (1280 x 800)
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 /vsd ext4 /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
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=THMASU0035
ro.build.display.id=THMASU0035
ro.build.version.incremental=0035.002
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2.1
ro.build.date=Fri Nov 4 17:35:39 JST 2011
ro.build.date.utc=1320395739
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_002
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=nbx03_011-user 3.2.1 THMASU0035 0035.002 test-keys
ro.build.fingerprint=Sony/nbx03_002/nbx03:3.2.1/THMASU0035/0035.002:user/test-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r3
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_011
ro.sony.sku.base=nbx03_011
ro.sony.build.id=THMASU0115300
ro.sony.build.incremental=111104028
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.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx03_001-ota-0042.001.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
prev version[111201033] is larger than post version[111201009]
Erohibit update as a result of checking version or base sku
Installation aborted.
-Fedde- said:
ro.sony.build.incremental=111104028
...
prev version[111201033] is larger than post version[111201009]
Click to expand...
Click to collapse
Have you tried "Reset to factory settings?" Your tablet still has 3.2.1, so you haven't flashed ICS. The "previous version" value is one from 3.2.1 r2, strangely. I would expect it to match ro.sony.build.incremental or be reduced to 111104048. What version is your recovery? It's listed at the top of the screen "Android system recovery..."
I'm not going to be able to help you further until later. Hopefully someone else can assist in the meantime.
Code:
[SIZE="1"]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 /vsd ext4 /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[/SIZE]
This looks like you have a fully bricked device i had the same and had it repaired
Maby there is a way but i'm affraid that there is nothing you can do with flashing etc,
YF,
Mahaco.
Mahaco said:
Code:
[SIZE="1"]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 /vsd ext4 /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[/SIZE]
This looks like you have a fully bricked device i had the same and had it repaired
Maby there is a way but i'm affraid that there is nothing you can do with flashing etc,
YF,
Mahaco.
Click to expand...
Click to collapse
What was the same?
quiqsilver said:
What was the same?
Click to expand...
Click to collapse
Al the zero's like there isn't anything on the tablet anymore,
Maby thats normal but I also had the same result with starting,
First the Sony Mark appears and then it just shuts down, i also could get it the
recovery, also did a recovery.log pull and it was nothing more then emptyness,
i was affraid to send it back because of my warranty, but probaly it was so
empty that they didn't even could see any tracks of self development or whatever,
Probaly the AiO tool made diffrent changes to some sort of values that the software
didn't understand and believe me i tryed everything, but i messed it up with region changer,
which was resolved by Condi "Our Android Brain"
quiqsilver said:
Have you tried "Reset to factory settings?" Your tablet still has 3.2.1, so you haven't flashed ICS. The previous version value is one from 3.2.1 r2, strangely. What version is your recovery? It's listed at the top of the screen "Android system recovery..."
I'm not going to be able to help you further until later. Hopefully someone else can assist in the meantime.
Click to expand...
Click to collapse
Thanks so far!
"Reset to factory settings" has been done.
my recovery version is: " Android system recovery (Rev.10)<3e> "
Mahaco said:
Al the zero's like there isn't anything on the tablet anymore,
Maby thats normal but I also had the same result with starting,
First the Sony Mark appears and then it just shuts down, i also could get it the
recovery, also did a recovery.log pull and it was nothing more then emptyness,
i was affraid to send it back because of my warranty, but probaly it was so
empty that they didn't even could see any tracks of self development or whatever,
Probaly the AiO tool made diffrent changes to some sort of values that the software
didn't understand and believe me i tryed everything, but i messed it up with region changer,
which was resolved by Condi "Our Android Brain"
Click to expand...
Click to collapse
That list of mounts is normal. It doesn't mean everything is empty.
quiqsilver said:
That list of mounts is normal. It doesn't mean everything is empty.
Click to expand...
Click to collapse
Right xD thats quite a noob action "feeling new again"
But then again, it did excactly the same things starting up/Sony Mark appears
and Boom, Nothing more then a black screen, i can get in recovery but thats it
everything i do i get the same result, Not able to do anything failed failed failed
etc. Hopeless, so i had to send it back for repair,
-Fedde- said:
Thanks so far!
"Reset to factory settings" has been done.
my recovery version is: " Android system recovery (Rev.10)<3e> "
Click to expand...
Click to collapse
Since your ro.sony.build.incremental is so high, the only thing that you can flash is probably ICS for whatever region your tablet currently has. Try to flash again. You don't need to use hack_recovery, just signed-nbx03_001-ota-0042.001.zip. After it fails, "adb pull /tmp/region.prop" and post it. It may not even be there.
quiqsilver said:
Since your ro.sony.build.incremental is so high, the only thing that you can flash is probably ICS for whatever region your tablet currently has. Try to flash again. You don't need to use hack_recovery, just signed-nbx03_001-ota-0042.001.zip. After it fails, "adb pull /tmp/region.prop" and post it. It may not even be there.
Click to expand...
Click to collapse
Indeed... remote object '/tmp/region.prop' does not exist
-Fedde- said:
Indeed... remote object '/tmp/region.prop' does not exist
Click to expand...
Click to collapse
Anyone, any idea?
Please... or should I just send it back?
-Fedde- said:
Anyone, any idea?
Please... or should I just send it back?
Click to expand...
Click to collapse
Look at condi's thread:
8. I've bricked my device! What can I do? - As long as your 'region.zip' file is not damaged, then for 99% your tab can be fixed. Firstable try to flash this 3.2.1r2 firmware. In most cases it works. If it will fail then: 1. Boot into RECOVERY; 2. Try to flash the update again - it will fail - thats ok; 3. Wait for 2-3min to get adb available; 4. Use 'adb pull /tmp'; 5. Post your recovery.log and region.prop files.
Wat in jouw geval ook zo is, je moet hem terug sturen maar voordat je dat doet moet je nog eenmaal fabrieks herstel doen dat zorgt ervoor dat alle logs van je laatste poging verdwijnt zoals het proberen te flashen. Daarna stuur je hem op je kan hem bij een plaatselijke gecertificeerd bedrijf brengen zij zullen hem door sturen naar sony bijvoorbeeld een media markt of een andere electronics shop. Met de reden : ik heb geprobeert de tablet terug te zetten naar fabrieks instellingen maar nadat hij klaar was startte de tablet niet meer op.
Succes.
-Fedde- said:
Anyone, any idea?
Please... or should I just send it back?
Click to expand...
Click to collapse
It's likely that your only options are to flash the original, unrooted, unrootable ICS update for whatever region your device has (this may require waiting for ICS to be released for that region) or seeking service from Sony. I'm guessing that its region is not currently US, but the US ICS update is available here. If you want root, I would simply send it to Sony and hope it comes back with a rootable build.
It's also possible that your region.zip is empty, which would explain the brick. If this is the case, you will be unable to flash any update and your tablet will require service from Sony regardless. If you attempt to flash the US ICS update I linked and it fails, you can pull the recovery log again to see if region.zip is the issue. If region.zip is valid, you could just wait for the ICS update in your region to recover, as previously mentioned.
Thanks for your answers!
Off to the store and sending it back to Sony.
It good to hear that you made your choice Sony is really quick so it wont take long,
Please tell us if you'll gett your tablet back, if you have check your kernel version and if its below 9 you can do all steps from the beginning,
Finally!
And not due to Sony..., I got a new tablet!
The store where I bought my tablet, agreed with me that Sony was taking to much time, and they supplied me a new one!
So now I'm off again, but waiting till after my holidays for any rooting and otherwise tricky updating... ;-)
Hopefully a good vacation will teach me how to read and take time to do the things step by step.
Verstuurd van mijn Sony Tablet S met Tapatalk
Can someone test CWM and report.
mount: mounting /dev/block/mmcblk0p10 on /system failed: Device or resource busy
run_program: child exited with status 255
---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------
Starting recovery on Sun Oct 14 11:46:06 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /cache ext4 /dev/block/mmcblk0p12 (null) 0
2 /data ext4 /dev/block/mmcblk0p11 (null) 0
3 /system ext4 /dev/block/mmcblk0p10 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p14 (null) 0
5 /boot emmc /dev/block/mmcblk0p9 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.setupwizard.mode=DISABLED
persist.sys.usb.config=mtp,adb
drm.service.enabled=true
ro.semc.sim.bip.enabled=true
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.semc.version.sw=1254-4233
ro.semc.version.sw_revision=6.1.B.0.544
ro.semc.version.sw_variant=GENERIC
ro.semc.version.sw_type=user
ro.factorytest=0
ro.serialno=CB511ZDGA2
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=s1
ro.hardware=st-ericsson
ro.revision=0
ro.crypto.state=unsupported
persist.chargemon.active=1
persist.sys.profiler_ms=0
persist.sys.language=de
persist.sys.country=AT
persist.sys.localevar=
persist.sys.timezone=Europe/Vienna
persist.sys.boot.sound.volume=0
init.svc.tad=stopped
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
I:Trying /dev/block/mmcblk0p14 on LUN file /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
I:Successfully shared /dev/block/mmcblk0p14 on LUN file /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
Starting recovery on Sun Oct 14 11:46:36 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /cache ext4 /dev/block/mmcblk0p12 (null) 0
2 /data ext4 /dev/block/mmcblk0p11 (null) 0
3 /system ext4 /dev/block/mmcblk0p10 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p14 (null) 0
5 /boot emmc /dev/block/mmcblk0p9 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.setupwizard.mode=DISABLED
persist.sys.usb.config=mtp,adb
drm.service.enabled=true
ro.semc.sim.bip.enabled=true
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.semc.version.sw=1254-4233
ro.semc.version.sw_revision=6.1.B.0.544
ro.semc.version.sw_variant=GENERIC
ro.semc.version.sw_type=user
ro.factorytest=0
ro.serialno=CB511ZDGA2
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=s1
ro.hardware=st-ericsson
ro.revision=0
ro.crypto.state=unsupported
persist.chargemon.active=1
persist.sys.profiler_ms=0
persist.sys.language=de
persist.sys.country=AT
persist.sys.localevar=
persist.sys.timezone=Europe/Vienna
persist.sys.boot.sound.volume=0
init.svc.tad=stopped
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
SD Card space free: 9301MB
Backing up boot image...
Backing up system...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Can't mount /system!
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
XperianPro said:
I need partition blocks with you can see by executing mount in terminal.
Could you guys upload pics of output.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Hi XperianPro,
first of all congratulations on making working CWM for Xperia U ICS :good: Fantastic job!
I can hardly wait to see one for Xperia P. If any one can do it, I'm sure you can :good:
Here is output of mount in terminal:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p10 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /modemfs ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data/idd ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/vold/179:14 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:14 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.wyse.pocketcloudfull-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
Output is also in attach and is from ICS of course
If you need anything else please don't hesitate to ask. I'll test what ever you want
Thank you very much in advance!
Best regards!
I will post test build in next few hours,thanks for reports.
Sent from my ST25i using xda app-developers app
Alpha uploaded.
XperianPro said:
Alpha uploaded.
Click to expand...
Click to collapse
Will test it right away...
seky0405 said:
Will test it right away...
Click to expand...
Click to collapse
Super.
Sent from my ST25i using xda app-developers app
Installation went fine but can not boot in recovery, any suggestion?
I even try with x-parts and when phone reboot I continuously press volume down button and phone vibrate once and continue with normal booting...
How can I help to debug this?
seky0405 said:
Installation went fine but can not boot in recovery, any suggestion?
I even try with x-parts and when phone reboot I continuously press volume down button and phone vibrate once and continue with normal booting...
How can I help to debug this?
Click to expand...
Click to collapse
Can you point me to recovery that boots but for locked bootloader.
Sent from my ST25i using xda app-developers app
XperianPro said:
Can you point me to recovery that boots but for locked bootloader.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Sure Here it is in attach... Looking forward to test another version
seky0405 said:
Sure Here it is in attach... Looking forward to test another version
Click to expand...
Click to collapse
Next version will in next one or two hour or tommorow.
Sent from my ST25i using xda app-developers app
XperianPro said:
Next version will in next one or two hour or tommorow.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
OK Looking forward to test it Thank you very much for your hard work :good:
the Phone vibrate,but doest boot in the Recovery
but i think ,you will manage that
Epic thread, I've been waiting to this since I had the phone. I installed the alpha version, it won't work yet, but good luck, I'll be here to test anything.
test
hello and good job for your work
i test it and nothing else happened non of the tap on screen or push the lower button rapidly.
i appreciate for your work and i can test all of the scripts you will make to help you to finish this wonderfull project
keep up and stay tuned
Hi XperianPro,
can we expect another version tonight?
Thank you very much in advance!
Great!
I will wait for someone that certify that it works 100% on Xperia P :fingers-crossed:
Hi XperianPro
Thank you for your work and look forward to the next one : Good:
XperianPro said:
Sorry for waiting but something went wrong during win 8 installation.
I hope you understand,eta will be in next few days.
Click to expand...
Click to collapse
take your time xperianpro we can wait for 10 days and glad to see you again with new windows 8 skins
Any novelty?
Enviado desde mi Xperia P usando Tapatalk 2
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
magiske said:
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Click to expand...
Click to collapse
You need a jb optimized recovery...
Stereo8 said:
You need a jb optimized recovery...
Click to expand...
Click to collapse
Thanks. Now I can get it up and running. Can I downgrade from here ? Would like to be able to restore my backup ??
/Mads
Yes!
Flowed from my HTC branded muffin...
Surely kernel problem
Hahahahha the same here...For that we need RUU JB aways can fix the mess that we make
i have micromax a27 bolt
Its the important problem nw i faced.... pls help meee.....................also i attach a report.log file
I got a error when i select 'UPDATE TOOL' in mobileuncle.......
i select 'check start safe flash update .zip(null package)-' - click next- click start test.....
phone reboot into recovery mode....
" sd card marker not fount
error proccesing ROM mannager script
please verify that you are performing the back uo,restore from rom mannager v4.4.0.0 or higher
please open rom mannager to report issue
before i run mobileuncle i install rom mannager and take a backup by boot into recovery by rom mannager...
i got this error by run mobile uncle and select update tool...and click check test.....
then i delete backup...i uninstall rom mannager.... bt cannot solve this problem
the report log file is here
Starting recovery on Wed May 25 16:49:49 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v6.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk0p1 (null) 0
2 /system yaffs2 system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data yaffs2 userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /fixnv yaffs2 fixnv (null) 0
9 /runtimenv yaffs2 runtimenv (null) 0
10 /backupfixnv yaffs2 backupfixnv (null) 0
11 /productinfo yaffs2 productinfo (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.msms.phone_count=2
persist.sys.sprd.modemreset=1
ro.device.support.wifi=true
ro.device.support.bt=true
ro.device.support.gps=false
ro.device.support.fm=true
ro.device.support.gsensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.cmmb=false
ro.device.support.vt=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=MocorDroid2.3.5
ro.build.display.id=TD206B_HTO_H06A_V1.5
ro.build.version.incremental=W12.20_P20_20120926.181054
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=2012.09.26 18:16:25 CST
ro.build.date.utc=1348654585
ro.build.type=user
ro.build.user=jsm
ro.build.host=jsm-desktop
ro.build.tags=test-keys
ro.product.model=H06A
ro.product.brand=HTO
ro.product.name=H06A
ro.product.device=hsdroid
ro.product.board=sp8810ga
ro.ctl_baseband_ver=ctl_kernel_td206b_hto
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CELLTEL
ro.wifi.channels=
ro.board.platform=sprdbp
ro.build.product=hsdroid
ro.build.description=sprdroid_base-user 2.3.5 MocorDroid2.3.5 W12.20_P20_20120926.181054 test-keys
ro.build.fingerprint=sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P20_20120926.181054:user/test-keys
persist.sys.timezone=Asia/Yekaterinburg
ro.product.carrier=
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.msms.phone_count=2sim
wifi.supplicant_scan_interval=48
android.keylayout.sprd-keypad=/system/usr/keylayout/sprd-keypad.kl
android.keychar.sprd-keypad=/system/usr/keychars/sprd-keypad.kcm
ro.hardware=mtk6515
ro.telephony.default_network=2
ro.sprd.volume_control_icon=1
ro.sf.lcd_density=160
dalvik.vm.heapsize=32m
ro.opengles.version=131072
ro.internalstorage.threshold=95
persist.sys.language=ru
persist.sys.country=RU
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
net.bt.name=Android
net.change=net.tcp.buffersize.edge
ro.calibration=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.revision=0
ro.recvkeys=115,114,116,212
ro.recvkey.up=115
ro.recvkey.down=114
ro.recvkey.enter=116
ro.recvkey.home=212
ro.recvkey.power=116
ro.gpu=mali
net.tcp.buffersize.edge=4093,48000,64000,4096,10240,14336
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
4ae096ee66868ef0541608427b75d756
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
please help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
[Edit] OK so of course I figured it out within 30 minutes of posting this, after being stumped for the last day. Here is what i did if you guys are in the same pickle:
1. I downloaded an app call Root recovery tools, booted into the cm 13 recovery
2. Renamed "openrecovery-twrp-2.8.5.2-acclaim-sdcard.img" into recovery.img
3. Selected sd recovery in the cm 13 recovery- got loaded into twrp 2.8.5.2
4. Installed CM 13
[/Edit]
I rooted, installed MiUi, and resized my nook tablet partition sizes back in 2012 or 2013. Now I'd like to try another ROM but I can't seem to get anything working. I've tried several different things but always end up in my old version of CWM(v5.5.0.4) and get stuck. I need help. Here is the error log
Code:
Starting recovery on Sat Jan 1 07:49:27 2000
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/platform/mmci-omap-hs.1/by-name/boot (null) 0
2 /bootdata vfat /dev/block/platform/mmci-omap-hs.1/by-name/bootdata (null) 0
3 /bootloader emmc /dev/block/platform/mmci-omap-hs.1/by-name/bootloader (null) 0
4 /cache ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache (null) 0
5 /data ext4 /dev/block/platform/mmci-omap-hs.1/by-name/userdata (null) 0
6 /emmc vfat /dev/block/platform/mmci-omap-hs.1/by-name/media (null) 0
7 /recovery emmc /dev/block/platform/mmci-omap-hs.1/by-name/recovery (null) 0
8 /rom vfat /dev/block/platform/mmci-omap-hs.1/by-name/rom (null) 0
9 /system ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system (null) 0
10 /xloader emmc /dev/block/platform/mmci-omap-hs.1/by-name/xloader (null) 0
11 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
12 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=GWK74
ro.build.display.id=IML74K
ro.build.version.incremental=189904
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Wed Jan 11 16:29:38 MST 2012
ro.build.date.utc=1326324578
ro.build.type=userdebug
ro.build.user=bbennett
ro.build.host=homestar.lan
ro.build.tags=test-keys
ro.product.model=NookTablet
ro.product.brand=bn
ro.product.name=acclaim
ro.product.device=acclaim
ro.product.board=acclaim
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=bn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=acclaim
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
ro.build.fingerprint=google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=acclaim
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-NookTablet-KANG
dalvik.vm.lockprof.threshold=500
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.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=acclaim
ro.revision=5
ro.emmc=0
init.svc.resetboot=stopped
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=restarting
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
Back menu button enabled.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Finding update package...
I:Update location: /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Opening update package...
Installing update...
Warning: No file_contextsTarget: Android/cm_acclaim/acclaim:6.0.1/MOB30Z/7c153c46c0:userdebug/test-keyscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directoryabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volumecould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata, assuming f2fsmount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata at /data: No such deviceabout to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
unmount of /data failed; no such volumePatching system image unconditionally...performing update
open "/dev/block/platform/omap/omap_hsmmc.1/by-name/system" failed: No such file or directory
Verifying the updated system image...script aborted: system partition has unexpected contents after OTA update
Target: Android/cm_acclaim/acclaim:6.0.1/MOB30Z/7c153c46c0:userdebug/test-keys
could not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata, assuming f2fs
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
Patching system image unconditionally...
Verifying the updated system image...
system partition has unexpected contents after OTA update
E:Error in /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
(Status 7)
Installation aborted.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
[/HIDE]
Specifically I can't figure out out how:
1. To update CWM on my already rooted tablet?
2. To install the CM 13 ROM? It seems I may have to do it in several steps, first installing an older version of CM?
I managed to install a google play app that lets me boot into the CM 13 recovery but I can't really do anything with it.