Nice, this will do perfectly...I did found this... http://forum.xda-developers.com/showthread.php?t=1022273
Sent from my C6603 using xda app-developers app
Sent from my Nexus 4 using Tapatalk
Nice, this will do perfectly...I did found this... http://forum.xda-developers.com/showthread.php?t=1022273
Sent from my C6603 using xda app-developers app
Actually I know how to use nvflash but communication between tablet and nvflash is secured by secure boot key (sbk, --sbk parameter). We need to know that. Only way to get sbk , Find a sony tablet s developer and ask him/her for sbk and make a black deal.I did found this... http://forum.xda-developers.com/showthread.php?t=1022273
Sent from my C6603 using xda app-developers app
Is it the same for all tablets or does every tablet have a different key? And if anyone asks him/her also ask how to enter APX without deleting the bootloader...Actually I know how to use nvflash but communication between tablet and nvflash is secured by secure boot key (sbk, --sbk parameter). We need to know that. Only way to get sbk , Find a sony tablet s developer and ask him/her for sbk and make a black deal.
All the tablets' (except 3g versions(maybe 3g is also same)) sbk should be same. We can get some guns and break into Sony maybe.Is it the same for all tablets or does every tablet have a different key? And if anyone asks him/her also ask how to enter APX without deleting the bootloader...
I know, I know. LolAll the tablets' (except 3g versions(maybe 3g is also same)) sbk should be same. We can get some guns and break into Sony maybe.
And you don't need to delete bootloader to access apx mode. Remember, The meme is wrong.@CoolApps
Actually it must be a booting problem caused by interruptng ota flash or edited partitions etc..I know, I know. Lol
So is it some bootloader corruption?
Sent from my Nexus 4 using Tapatalk
While flashing the OTA it does do a few things such as writing to the staging folder.Actually it must be a booting problem caused by interruptng ota flash or edited partitions etc..
Now hard-bricking your device is a good thing? XDJust tried to use Droid X Bootstrap and bricked my devise it's a bad news,
but System Information on my Mac said:
APX:
Product ID:0x7420
Vendor ID:0x0955 (NVIDIA)
Version: 1.04
Speed:Up to 480 Mb/sec
Manufacturer:NVIDIA Corp.
Location ID:0xfa210000 / 8
Current Available (mA):100
Current Required (mA):32
It's a good news 8)
Yeah, cause I wanted to examine apx mode. Unfortunately there is no nvflash for OSX.Now hard-bricking your device is a good thing? XD
This is what I was talking about in the discussion. +1Yeah, cause I wanted to examine apx mode. Unfortunately there is no nvflash for OSX.
Finally I tried to push and hold reset button and tablet boots normally.
Yeah, same happened to me actually, gone to apx first time but then, it booted normally.This is what I was talking about in the discussion. +1
Sent from my Nexus 4 using Tapatalk
Ive made a little progress using wheelie. I wouldnt call it progress at all really, but got something other than just the nv error in nvflash. Using wheelie it will also give me this:
C:\>wheelie --sbkv2 --bl ebtblob.bin --bct gtablet.bct --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'ebtblob.bin'.
Using BCT: 'gtablet.bct'.
----------------------------------------
[=] Chip UID: 0x310871825619870615
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
The Chip UID stays the same no matter what I change, so Im pretty sure its mine. Ive gotten another number as well in the early stages of using wheelie, but i cannot get it to give it back to me no matter what i do. I'm not sure if it gave me that number because of file I used or what. But here it is any way.:
Chip UID: 0x450704740bfe397
Ive read that back in the days you were able to get the sbk out of the acer tablets using the uid number with some formula. That formula wont work on this UID because it requires splitting it in to 4 sections. It is a 18 digit number and cannot be split in to 4. So, thats where I'm stuck.
Just thought I post it here, dont know where else to post it. Thanks.
So I followed the process on http://unlockbootloader.sonymobile.com/instructionsI had a choice between this tab and the Galaxy Tab 3, beginning to regret my choice...
Bump
If accessing Fastboot was that easy, then the device would be unlocked like over a year ago. :/So I followed the process on http://unlockbootloader.sonymobile.com/instructions
I got sent an unlock code but I get no response from fastboot.exe -i 0x0fce oem unlock 0x<I inserted the KEY>.
In fact I can't get my device to boot in fastboot mode. I've tried apps, I've tried the holding down buttons and inserting into USB but nothing works so far.
Anybody have any further ideas?
There is no fastboot mode to enter actually on STS actually.If accessing Fastboot was that easy, then the device would be unlocked like over a year ago. :/
Sent from my Nexus 4 using Tapatalk
Interesting, I wonder how Sony got in and written the file system...There is no fastboot mode to enter actually on STS actually.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
They have got replaceble memory modules. They can reflash the whole system or there is nvflash apx interface..Interesting, I wonder how Sony got in and written the file system...
Sent from my Nexus 7 2013 using Tapatalk