Hi everyone,
I'm living in China and last year, I bought a chinese Sony tablet S. Never, I might use google tools. For long weeks, I try to find help on several forums.
I have installed ADB and followed step by step the "prerooted ICS tutorial" and the "china device tutorial" from AIO v 6.5.
Always, I get a satus 7 error, when I'd like to install a custom ROM, in recovery.
I've copied below this error message:
assert failed: file_getprop ("system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_011/nbx03:3.2.1/THMASU0035/0035.001:user/release-keys"
file_getprop ("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_001/nbx03:3.2.1/THMAS0042/0042.001:user/release-keys"
E:Error in /tmp/desklunvr/desklunvr.zip (status 7)
ADB seems to have no problem, it works.
In fact, one time, I succeeded to install the GooglePlay by following the "china device tutorial"; it worked until I have updated system, as it was proposed.
So, I have reset to factory settings. But since, I can't install the rom any more.
Thanks a lot for your help!
Matthieu
About my tablet:
SGPT 111 CN/S
Android version: 4.0.3 R5a
Kernel version: 2.6.39.4 [email protected]#1
Build number: TISU0243410
AIO would not work with a non rooted and r5a device. Root your device, apply backdoor patch and flash a original US ota.
Sent from my Sony Tablet S using Tapatalk
Thanks for you reply.
In fact, I'm a really beginner. What do you mean with "apply backdoor patch". Already, I rooted my tablet by the way of AIO tools. I thought that it worked with R5A device.
Please, do you know a good tutorial that could help me? I have spent many hours, tried several ways.
Matthieu
The aio tool in there you will see a menu section three subsection 4 I think rescue backdoor
Its in the tool it lowers the build number to trick the device in to thinking there is a update available
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
When you say custom rom what are you using there is no way to put anything other than offical albeit rooted sony firware sony encrypt their tablets unless you have the offical sony codes or a tablet with an unlocked bootloader which I highly doubt
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
When I said “custom rom”, in fact it was ICS firmwares (I tried to install US R5A and R1A). Here, you can have a look on steps succeded (it seems…).
I’m following the CHINA DEVICE TUTORIAL! v0.4:
1) Root device using option no.1,
2) Run tweaks&mods - and apply Rescue-Backdoor function,
3) Run region changer and choose US region,
4) Download US ICS R1A FIRMWARE (R5A for me - signed-nbx03_001-ota-121116036)
5) Copy it to external SD.
Every time, the 6th step doesn’t work and I get a “status 7 error”
6) Run v5.3 AiO – go to 'Custom Rom' submenu, choose 'Decrypt Update' function, (1- create “decrypted update.zip”)
In order to give you more information, I let you have a look on my PC/tablet settings. Please see below and my attachments.
ADB is working.
Build.prop
(I’m French, so I tried to manually change the two following lines)
ro.product.locale.language=fr
ro.product.locale.region=FR
I’ve also changed ro.build.version.incremental=121116035
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0143
ro.build.display.id=TISU0143
ro.build.version.incremental=121116035
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Nov 16 07:18:05 JST 2012
ro.build.date.utc=1353017885
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build10
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_008
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=fr
ro.product.locale.region=FR
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_008-user 4.0.3 TISU0143 121116035 release-keys
ro.build.fingerprint=Sony/SYS_008/nbx03:4.0.3/TISU0143/121116035:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.display.release=release5a
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.autovolume.threshold=10
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
ro.semc.xloud.supported=true
ro.somc.clearphase.supported=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=1
ro.sony.ols.eula=0
Thanks a lot for helping me.
bye
Matthieu
Ok I would skip 6 and flash the rom/ota from the sd card boot the tablet in to recovery the select apply update from sd card
have you tried the flasher that might do the trick
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
Hi,
Which flasher do you mean?
As you proposed, I've just tried to skip step 1 in "CUSTOM ROM AND FLASHING SUBMENU", then I've tried directly step 5 in this menu "Flash signed zip [straight from recovery]" from recovery mode. (Before I've downloaded "hack_recovery" and "firmwares for ICS R1A/R5A" on SD external card).
In recovery mode, each time, I get Status 7 error message when I use "hack_recovery", and when I try to update ICS R1a or ICS R5A, I get this error message
"E;Prohibit update as a result of checking version or base sku
Installation aborted"
What do you think about that?
Bye.
Matthieu
desarcanes said:
Hi,
Which flasher do you mean?
As you proposed, I've just tried to skip step 1 in "CUSTOM ROM AND FLASHING SUBMENU", then I've tried directly step 5 in this menu "Flash signed zip [straight from recovery]" from recovery mode. (Before I've downloaded "hack_recovery" and "firmwares for ICS R1A/R5A" on SD external card).
In recovery mode, each time, I get Status 7 error message when I use "hack_recovery", and when I try to update ICS R1a or ICS R5A, I get this error message
"E;Prohibit update as a result of checking version or base sku
Installation aborted"
What do you think about that?
Bye.
Matthieu
Click to expand...
Click to collapse
No you didnt under stand im not talking about the custom rom section tweaks and mods section rescue backdoor it will lower your SKU which is why its not allowing you to install a new firmware the one your trying to flash is the same as whats installed therefore it gives an error
Run the rescue backdoor
Put rom/ota on sd card
Boot in to recovery
Apply update from sd card
And it should work
root again And apply rescue backdoor patch again if your device boots after all this you will get a notification of and update
This is a false positive sort of it means the patch has worked and the base sku has been lowered
You can switch the update notification off with the aio tool under the rescue backdoor option
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
dex9mm said:
No you didnt under stand im not talking about the custom rom section tweaks and mods section rescue backdoor it will lower your SKU which is why its not allowing you to install a new firmware the one your trying to flash is the same as whats installed therefore it gives an error
Run the rescue backdoor
Put rom/ota on sd card
Boot in to recovery
Apply update from sd card
And it should work
root again And apply rescue backdoor patch again if your device boots after all this you will get a notification of and update
This is a false positive sort of it means the patch has worked and the base sku has been lowered
You can switch the update notification off with the aio tool under the rescue backdoor option
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
Click to expand...
Click to collapse
Champagne!!
It's working... I have got now a french sony tablet S.
By the way of recovery, I installed french firmware for ICS R5A.
Unfortunately, there is a new problem. It's always updating, automatically... I mean, everytime, at starting. First, it's for a french update, but when I shut down and I restart, it's a chinese update, and all disappear (google tools). I can't access Google Play anymore.
Do you think it's possible to fix it?
I have tried to disable OTA system updates, as you proposed.
Matthieu
Ok so you need to look at the posts threads on dual system you now really only have half of a rom there seems to be two system partions so on one side you have china the other fr I think flashing the rom again will work but in not certain
Gald to hear your making progress
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
Hi,
In fact, I've forgiven during severals months... But I've tried again last days.
Finally, after several nights I've got my final solution. I've installed Jelly Bean by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=2050126
Now, it works very well! I'm using an Astrill VPN; I may normally access to the Google play store, even with the strong censorship in China. My apps are in french and I can discover how to really use a tablet...
Thanks a lot for your help. :good:
Matthieu
dex9mm said:
Ok so you need to look at the posts threads on dual system you now really only have half of a rom there seems to be two system partions so on one side you have china the other fr I think flashing the rom again will work but in not certain
Gald to hear your making progress
hit thanks if I helped
sent from rooted xts thanks djrbliss and condi
Click to expand...
Click to collapse
Related
I have read through various threads and couldnt find it but i know someone who was able to get me the original official Rogers i717r Firmware for people who want to revert Back to Stock, Unrooted, Like brand new.
PHONE: I717RUXLA2
PHONE:I717RUXLA2
CSC: I717RRWCLA2
Build info jan 6 2012
This firmware is to be Used with ODIN only. This is test by me personally running Rogers i717r Samsung NOTE
1, RWC_signed_Q1_USA_1221.pit (3.89 KB) PIT FILE
http://www.multiupload.nl/GUEL1DIAMF
2. ABOOT_SGH-I717R_I717RUXLA2_user_CL875155_REV00.tar.md5 (1.54 MB) BOOTLOADER FILE http://www.multiupload.nl/XSP4X7SU5O
3. PLATFORM_KERNEL_AMSS_SGH i717R_I717RUXLA2_user_CL875155_REV00.tar.zip (536 MB) PDA FILE UNZIP IT FIRST New Link http://www.multiupload.nl/U72CE005WL
4. I717RUXLA2_phone_secure_Q1_ROGERS_REV_00_CL870799.tar.md5 (26.09 MB) PHONE FILE
http://www.multiupload.nl/0KV4DII0X1
5. SGH-I717R-CSC-RWCLA2.tar.md5 (9.19 MB) CSC FILE http://www.multiupload.nl/3EZMLXNY08
All the above files are in order. Just plug them in ODIN and put your phone in download mode by holding Volume down and power button. Get the Green Guy and your are set. press start.
Enjoy.
Say Thanks if you like it. and If anyone need Samsung firmware i can help. PM me.
Thanks! keeping these bookmarked for future reference
Must be a U.S. thing as I haven't been able to connect to multiupload in quite some time now.
Yea maybe its hard to find free provider that will let you upload over 200 mb file
Hi,
I have an ICS ROM, Can I downgrade to GB?
Also, How can I root the device after installing the stock rogers ROM? without flash the counter(if it possible)
Thank you very much.
Delete double post
djkid said:
Yea maybe its hard to find free provider that will let you upload over 200 mb file
Click to expand...
Click to collapse
I understand. I appreciate it. I just used a proxy server to get by multiupload's IP blocking.
dajj said:
Hi,
I have an ICS ROM, Can I downgrade to GB?
Also, How can I root the device after installing the stock rogers ROM? without flash the counter(if it possible)
Thank you very much.
Click to expand...
Click to collapse
i believe you can downgrade using the the rom givin and flash a different kernal that wont increase counter. quick search "flash counter reset roger" in this forum. and root wise there are alot of them. i personally havent found anything that i found stable on my phone. so i am staying away from it. until i do more research. sorry cant be help there.
Hey guys
I rooted my Note and after few reboots my phone stocked on splash screen with logo Rogers. If i understood right I had a problem with new ROM.
Then I flashed my phone via Odin using pda-odin-rogers-stock-system-boot.tar. rebooted and I thought my phone works fine but I have new problem- phone doesnt see sim card. After I flashed modem via CWM using Rogers-Modem-CWM.zip but still have the same problem- NO SIM card...
I did it following this thread : http://forum.xda-developers.com/showthread.php?t=1630843
Finally I tried your files.After file #3 I got message on my phone:
-Veryfing Internal MMC block... checking confirmation-check(0)
Not need checksum confirmation already executed!!!...
Deleting CryprionMeta Data
#MANUAL MODE # and green robot with exclamation mark
an options on the top of the screen
-reboot
-applying update from sd card
-wipedata/factory reset
-wipe cache partitiontest redbend
Button power didnt work, just volume UP or Down.
Do you know what it was?
I just took down battery and then did next steps 4 ,5... pretty sure something was not correct... and to take down battery is could be straight way to brick phone.
However my phone turned on as new but I still have the same problem- phone doesnt see sim card.
Maybe some of you know what to do or any ideas how to solve this problem?
Thank you
How can I get i717r firmware after flashing a custom ROM to get Rogers Live on my device. It says "device not compatible", and I see i717 instead of rogers model i717R
andronikal659 said:
How can I get i717r firmware after flashing a custom ROM to get Rogers Live on my device. It says "device not compatible", and I see i717 instead of rogers model i717R
Click to expand...
Click to collapse
Have you tried editing the build.prop?
Agoattamer said:
Have you tried editing the build.prop?
Click to expand...
Click to collapse
I don't know how to do that yet. :$ do you have a link for tutorial? Thanks.
No I don't have a link. It is just something you learn to do. Most that install custom ROMs do so to get away from these branded apps like Rogers Live. All build.prop files are different. Some give you different IDs and some define how and what your phone will do in certain situations.
What Rogers Live looks for I am uncertain. Possibly others will know better. And if you are not careful what you change in this file your phone may not boot or run without errors. The build.prop can be found on a rooted phone in the system folder. I use root explorer to edit mine but you may find build.prop editors on google play to do this for you. Below is part of the gingerbread build.prop from this thread. You will see all the instances of I717R in red.
ro.build.host=SEP-65
ro.build.tags=release-keys
ro.product.model=SGH-I717R
ro.product.brand=samsung
ro.product.name=SGH-I717R
ro.product.device=SGH-I717R
ro.product.board=MSM8660_SURF
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I717RUXLA2
ro.build.hidden_ver=I717RUXLA2
ro.build.changelist=875155
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I717R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I717R-user 2.3.6 GINGERBREAD 248 release-keys
ro.build.fingerprint=samsung/SGH-I717R/SGH-I717R:2.3.6/GINGERBREAD/248:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I717RUXLA2
ro.build.hidden_ver=I717RUXLA2
ro.build.changelist=875155
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Try changing your build.prop to show these instances as I717R instead of I717 and change region to CA and see how Rogers Live functions now. It may or may not work for you. Make sure you do some investigating on changing your build.prop first.
Agoattamer said:
No I don't have a link. It is just something you learn to do. Most that install custom ROMs do so to get away from these branded apps like Rogers Live. All build.prop files are different. Some give you different IDs and some define how and what your phone will do in certain situations.
What Rogers Live looks for I am uncertain. Possibly others will know better. And if you are not careful what you change in this file your phone may not boot or run without errors. The build.prop can be found on a rooted phone in the system folder. I use root explorer to edit mine but you may find build.prop editors on google play to do this for you. Below is part of the gingerbread build.prop from this thread. You will see all the instances of I717R in red.
ro.build.host=SEP-65
ro.build.tags=release-keys
ro.product.model=SGH-I717R
ro.product.brand=samsung
ro.product.name=SGH-I717R
ro.product.device=SGH-I717R
ro.product.board=MSM8660_SURF
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I717RUXLA2
ro.build.hidden_ver=I717RUXLA2
ro.build.changelist=875155
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I717R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I717R-user 2.3.6 GINGERBREAD 248 release-keys
ro.build.fingerprint=samsung/SGH-I717R/SGH-I717R:2.3.6/GINGERBREAD/248:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I717RUXLA2
ro.build.hidden_ver=I717RUXLA2
ro.build.changelist=875155
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Try changing your build.prop to show these instances as I717R instead of I717 and change region to CA and see how Rogers Live functions now. It may or may not work for you. Make sure you do some investigating on changing your build.prop first.
Click to expand...
Click to collapse
Thank you very much. That was a very detailed explanation. I appreciate you giving the time to help me out. I'll try to do some research on google first before modifying anything there, I'm not comfortable yet as I'm afraid my device will not boot. I love this community.
currently running a custom ROM and noticed the signal quality was not as good as the stock rogers. Is it possible to flash the stock radio to get the same signal quality back? and does anyone have a link to said radio .tar?
allan_esp said:
currently running a custom ROM and noticed the signal quality was not as good as the stock rogers. Is it possible to flash the stock radio to get the same signal quality back? and does anyone have a link to said radio .tar?
Click to expand...
Click to collapse
Isn't there one in the first post??
FrolToronto said:
Hey guys
I rooted my Note and after few reboots my phone stocked on splash screen with logo Rogers. If i understood right I had a problem with new ROM.
Then I flashed my phone via Odin using pda-odin-rogers-stock-system-boot.tar. rebooted and I thought my phone works fine but I have new problem- phone doesnt see sim card. After I flashed modem via CWM using Rogers-Modem-CWM.zip but still have the same problem- NO SIM card...
I did it following this thread : http://forum.xda-developers.com/showthread.php?t=1630843
Finally I tried your files.After file #3 I got message on my phone:
-Veryfing Internal MMC block... checking confirmation-check(0)
Not need checksum confirmation already executed!!!...
Deleting CryprionMeta Data
#MANUAL MODE # and green robot with exclamation mark
an options on the top of the screen
-reboot
-applying update from sd card
-wipedata/factory reset
-wipe cache partitiontest redbend
Button power didnt work, just volume UP or Down.
Do you know what it was?
I just took down battery and then did next steps 4 ,5... pretty sure something was not correct... and to take down battery is could be straight way to brick phone.
However my phone turned on as new but I still have the same problem- phone doesnt see sim card.
Maybe some of you know what to do or any ideas how to solve this problem?
Thank you
Click to expand...
Click to collapse
Use the little house button as enter button
---------- Post added at 08:28 PM ---------- Previous post was at 07:38 PM ----------
bit of guessing but it all worked out!!
awsome work!!
I see a few already flashed this.....and I have a little inquiry. Does this (the huge file in the OP specially) also flash the stock rogers kernel (UXLA2)?
I know that there is a CWM version of the stock kernel but just wanna make sure.
thanks......i think if you have an app that reads kernel info (like CPUSpy), the kernel info should have a PREEMPT date or something. According to the system files, the date should be January 6, 20XX (if what i believe is right). thanks again.
This is the same file that Samsung uses for CAnada rogers note
Sent from my SGH-I717R using Tapatalk 2
Works perfectly
Just wanted to say that after downloading all the files and plugging them into odin in order, I just booted my Note into Download mode and pressed Start in odin. After 3 minutes, my phone was back to Rogers stock! Thank you so much!!
The Sony Tablet FAQ Thread
Why this thread, I am sick of repeating myself LOL
Why trust me?? I have been through a fair bit of crap with this tablet (Original Tablet S)....
Bricked after messing with build.prop (BIG NO NO) sent to Sony repair....
Well it was sort of repaired the second partition was not quite right. I could not update if I wanted to.
Tried to fix using Flasher but did not have enough room to deflate files = semi-brick
Managed to install 3.2 HoneyComb but the non rootable version so I am stuck.
First thing. HoneyComb 3.2 with kernel 10 maybe rootable by flashing updates. 3.2.1 (big difference) kernel 10 IS NOT ROOTABLE.
However ICS is now rootable, thanks to the 'adb restore' loophole in ICS.
JB is also rootable thanks to the motochopper exploit.
Both are compiled in All in One tools by condi
Next thing some HOUSEKEEPING
Install drivers here @ Sony
or On XDA here thanks to BluechipJ
and driver for R5a recovery thanks to andyabc THEN:
Options:
a. install Android SDK
b. download zip attached to this post
Best thing to do is create a folder on main drive such as C:/ADB
Next we want to 'link' the adb.exe file so it can be opened without having to be in that folder.
Goto My Computer > Properties > Enviroment Variables > Select Path then edit > Scroll to the end of textbox and add ;C:\ADB
Note the entries are seperated by ;
Now you can open cmd: Windows Key + R, type cmd then enter. Or windows key, type cmd, then enter.
Lots of ways to do that.
Then type 'adb devices' without ' ' it should come up with a device listed
When you have that working shut down tablet. Hold vol+ and turn on tab (still holding vol+) this should boot into recovery.
Once again 'adb devices' and now it should say blahblahblah recovery
If that went well then adb is set up and you won't any problems rooting
FAQ
Q. Can I install a cutom rom?
A. NO! You can not, there is no such development for Sony and Xperia Tablet S'. If you want development try Sony Tablet Z.
Q. But, why not?
A. Bootloader is locked down tight and because both Sony and Xperia Tablet S are developed by Sony VAIO not Sony Mobile. The VAIO team knows nothing about Android compared to Mobile team.
Q. I am a noob, how do I install (flash) these update zips that everyone is talking about?
A. Good question, firstly go to here for current files or here for my 4Shared older zips.
Then copy file(s) to sd card, turn off tab, insert SD card, hold VOL UP and turn tablet on by pressing POWER button
but keep holding VOL UP until recovery menu, then use UP and DOWN keys to navigate and POWER button to select.
Recovery Menu > Update System From SD Card > signed-...............
Q. Arrrgh I think I am bricked!
A. Ok firstly calm down and DO NOT factory reset if you haven't already. Next try the step above (installing zip) twice in a row, any zip will do and then use the command adb pull /tmp/recovery.log
Once the file is pulled please rename it from .log to .txt and create a new thread and add attach the file to it and don't forget to tag me "@stifilz" so I see it.
Q. I unistalled an app and need a copy!
A. Don't be lazy.... First of all you should have an update.zip for your region. If not see question 1 for the links (or my signature).
Once you have the file use desklunvr.exe thanks to robin. You can simply drag the zip onto the .exe file and it will output a decrypted zip.
Next you will need to extract the zip using your favourite zip program (I use 7-zip from http://7-zip.org)
After this you will see a bunch of files. You can use ext2explore.exe to open system.img. (See attached) NB: Hidden.img is just that hidden, it CAN NOT be accessed.
In ext2explore you can open the img you want and then navigate the file you want and right click and select save.
Q. Can I root Jelly Bean in Xperia Tab?
A. Yes you can!!! See here.
Q. WAIT!!! Xperia S has JB... WTF.. Do we get JB for Sony Tab?
A. NO. It seems Sony is being dumb and not going to give us JB.
Q. How do I root ICS or JB? Easiest AIO Method
A. To do it the easy way follow this post here for the AIO tool.
Q. How do I root ICS? Manual Method
A. Try to use AIO first, it is the most effectve. To do it manually follow this post here for step by step instructions.
Q. How do I root ICS? Above is not working... Semi-Auto Method
A. Try to use AIO first, it is the most effectve. To do it semi-auto go here and download the latest zip. ( I used 13)
Q. I have a non US Tab S can I flash down to HC?
A. Kind of. Use region changer to change to US region. Download this. And then either
flash normally and then root tablet using HC method (see post #2).
Q. I have a new Xperia Tab S can I flash down to HC?
A. At this stage NO, HC was not released with this Tablet (that I know of) and there is no way to 'fake' as old Tablet atm (to go down to HC).
Q. I have a new Xperia Tab S can I change region?
A. At this stage NO, although it would not be hard to implement this into condi's AIO tool.
Q. I have 4.0.3R5 rooted and want to downgrade to something else
A. When you install R5 OTA or flash normal file the recovery is 'upgraded' you will not be able to use AIO to pre-root future updates nor flash them. You can still root using the ICS method (if it is still current for the update. You can however flash either ICS or ICS R1A by lowering your incremental and manually flashing through recovery. Or see below for condi's amazing solution.
Q. I want 4.0.3R5 rooted and don't want the stupid new recovery
A. See this post here.
-- Now with double flash (flashes both system0 & system1)
UPDATE: Now you can also use FLASHER
Q. My region is not US?
A. Then you may be out of luck. But check here to see if we have a 3.2.1 for your region:
Click Here or PM Me.
Q. AIO still isn't working 100%?
A. Please dowload the attached file ADB v1.0.31, extract and replace the files in the "files" directory.
This has helped a user at post #4 with AIO. This is somewhat obsolete.
Well that was a short FAQ but will add more questions as I think of them, or they pop up.
Please feel free to ask any questions here and I will try answer and post to OP.
Thanks
Stifilz
OLD FAQ Outdated v2
Q. GRRRR I CAN’T ROOT MY TABLET
A. Not really a question so go to next.
Q. Why can’t I root my tablet?
A. That’s more like a question. There can be many reasons for this. Most likely you have R5A / R6A/B or Jelly bean.
Q. How can I root HC?
A. See post #2 or update to ICS and see below.
Q. Can I root ICS, R1a, R5? Or R4, R5, R6 in Xperia Tab
A. YES see below.
Q. Can I root ICS R6a/b in Xperia Tab?
A. NO you can not, however there is a work around to keep root upgrading from R6. See here.
Q. Can I root ICS R5a in Tablet S/P?
A. No you can not however if you have R1a or lower and have not flashed anything higher then see here.
-- Now with double flash (flashes both system0 & system1)
Q. I now have 3.2.1R2 and want to upgrade to ICS?
A. Don't not accept any Over The Air (OTA) updates as this WILL UNROOT your Tab. Instead go here and download the 4.0.3 or 4.0.3R1A / R2A
Then use AIO tool to pre-root and install; follow here.
OR You can use root method above to root ICS.
Q. I have 4.0.3 rooted and want to upgrade to 4.0.3R1A / R2A?
A. Same as above.
Q. I have 4.0.3R1A /R2A rooted and want to upgrade to 4.0.3R5?
A. Same as above except change to US region (only region with release 5 at the mo)
OLD FAQ Outdated v1
Q. GRRRR I CAN’T ROOT MY TABLET
A. Not really a question so go to next.
Q. Why can’t I root my tablet?
A. That’s more like a question. There can be many reasons for this. Most likely you have ICS 4.0.3 installed. Settings > About Tablet > Android Version
i.e. 4.0.3 (release 1a)
Q. But I don’t have ICS 4.0.3 Installed, I have HoneyComb!!!!
A. Ok, do you have 3.2 or 3.2.1. Settings > About Tablet > Android Version
i.e. 3.2.1R2
3.2 maybe able to ROOT see below.
Q. I have 3.2.1!
A. Do you have 0035 (R1) or 0042 (R2)?
What is the build number? Settings > About Tablet > Build Number
If you have 0035 3.2.1 then see “Q.My tablet is 3.2.1 build 0035” below.
Q. I have 3.2.1R2 (0042) and still can not root!
A. Ok what is you kernel build? Settings > About Tablet > Kernel Version
i.e. “2.6.39.4 [email protected] #1” is what we call kernel 5
Generally build 10 is not rootable, but in some cases neither is 9 or 8. You MUST wait until another root method is discovered.
Q. I don’t have 3.2.1, I have 3.2?
A. What is the build number? Settings > About Tablet > Build Number
You may be able to save you TAB yet, see below.
Q. My tablet is 3.2 build 11000.
A. If you are US region. Flip over tablet check model SGPT111US/S or SGPT112US/S or
Open a file explorer, navigate to /system/build.prop look for
“ro.sony.sku.base=nbx03_001” is US region.
NB Some users have been able to skip 0035 and flash 0042. If you are having trouble with 0042 then flash 0035 first : )
Then flash this: 3.2.1 build 0035
http://www.mediafire.com/?cti11ejoxpxx4cm
Then flash file in next question.
Q. My tablet is 3.2.1 build 0035 (R1)
A. If you are US region. Flip over tablet check model SGPT111US/S or SGPT112US/S or
Open a file explorer, navigate to /system/build.prop look for
“ro.sony.sku.base=nbx03_001” is US region.
Then flash this: 3.2.1 build 0042
http://www.4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
OR
http://www.4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Q. But I am a noob, how do I flash these?
A. Good question, firstly copy file(s) to sd card, turn off tab, insert SD card, hold VOL UP and turn tablet on by pressing POWER button
but keep holding VOL UP until recovery menu, then use UP and DOWN keys to navigate and POWER button to select.
Recovery Menu > Update System From SD Card > signed-nbx03...............
Q. My region is not US?
A. Then you may be out of luck. But check here to see if we have a 3.2.1 for your region:
Click Here
wise man
Wise idea with all the new wooters like myself ....
Thanks
Thanks for the thread. I followed your instructions in the ALLinONE thread and that was helpful!
Two extra things I experienced when rooting my tablet:
1. I somehow skipped 0035 and directly updated from 11000 to 0042. No problem with that.
2. With 0042, I still had problem with ALLinONE (4.0, 4.1, whatever version) froze after launching adb [AiO froze after "daemon started successfully"]. No root process performed. It turned out that the adb files come with AiO seem to be outdated. I updated my SDK tools to rev 20 just this afternoon. The new adb.exe (under android-sdk\platform-tools\) is able to recognize the device when the adb.exe w/ AiO cannot. Copied adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll to \files\ solved the problem with a successful rooting.
Now challenging pre-rooted ICS! Fingers crossed....
[Updated] after 3 or 4 rounds of failed, now i'm officially on rooted ics!! The most confusing part for me was after signing the decrypted update file and flash custom_update_signed.zip.
Here's how it finally worked for me:
1) install busybox;
2) when in the recovery model: run install.zip [it wouldn't fail] -> run _hack_recovery.zip [this one failed!!] -> run the new install.zip [it was the old custom_updated_signed].
ps: i'm not allowed to post in the dev forum yet so can't add to the original AiO thread. @@
Perfect for all the questionnaires out there
Sent from my Sony Tablet S using xda premium
House keeping added....
How to set up adb properly
Stifilz
andyabc said:
Perfect for all the questionnaires out there
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
Not all...
I read all of the posts (forumSony Tablet S how to root) but do not had any sucess to root my Sony P. I finally found out that it is not possible to root the device with ICS 4.0.3 ....
After I bought my Sony it was running 3.2.1, but I updated it to ICS 4.0.3 and then tried to root (found this forum to late). Can I downgrade the software? I would like to ask if there is a solution to root an ICS 4.0.3 (release 2)???
dimatrixxx said:
Not all...
I read all of the posts (forumSony Tablet S how to root) but do not had any sucess to root my Sony P. I finally found out that it is not possible to root the device with ICS 4.0.3 ....
After I bought my Sony it was running 3.2.1, but I updated it to ICS 4.0.3 and then tried to root (found this forum to late). Can I downgrade the software? I would like to ask if there is a solution to root an ICS 4.0.3 (release 2)???
Click to expand...
Click to collapse
You can not downgrade and it has not been found possible to root any version of ics.
Sent from my ADR6425LVW using xda app-developers app
cslingerland said:
You can not downgrade and it has not been found possible to root any version of ics.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Thanx for information. I have to wait until some one will find a solution:crying:
This may seem a bit strange - I rooted my Nook Color to get the full Android system. What will I get if I root my Sony S? For example, will I get my Windows 7 machine to recognize my Sony S (and sd card) with a letter instead of just Sony S? I did look through many of the discussions and couldn't find the answer - if this is the wrong place, please let me know where to look.
Found answer in wikipedia!
oh....no......,my tablet Kernel Version is 2.6.36.3 [email protected] #1,it can not be root in this time.how long can solve it?????? http://forum.xda-developers.com/images/smilies/frown.gif
[email protected] said:
oh....no......,my tablet Kernel Version is 2.6.36.3 [email protected] #1,it can not be root in this time.how long can solve it?????? http://forum.xda-developers.com/images/smilies/frown.gif
Click to expand...
Click to collapse
Which version of Android do you have? If you have anything less than HC 3.2.1 (release2), you may be able to pre-root and update to ICS.
my tablet is 3.2.1(release2),how to do?thanks
[email protected] said:
my tablet is 3.2.1(release2),how to do?thanks
Click to expand...
Click to collapse
That is a shame. You cannot root Android version 3.2.1 (release2) with Kernel version 2.6.36.3 [email protected] #1. If you would have had Android version 3.2 with Kernel version 2.6.36.3 [email protected] #1, you could have updated to and rooted Android version 3.2.1 (release2) with Kernel version 2.6.36.3 [email protected] #1 and then pre-rooted and updated to Android version 4.0.3.
Cat McGowan said:
That is a shame. You cannot root Android version 3.2.1 (release2) with Kernel version 2.6.36.3 [email protected] #1. If you would have had Android version 3.2 with Kernel version 2.6.36.3 [email protected] #1, you could have updated to and rooted Android version 3.2.1 (release2) with Kernel version 2.6.36.3 [email protected] #1 and then pre-rooted and updated to Android version 4.0.3.
Click to expand...
Click to collapse
it is bad news for me!!!!so,it means i am nothing to do now?
[email protected] said:
it is bad news for me!!!!so,it means i am nothing to do now?
Click to expand...
Click to collapse
Correct. There is nothing you can do now. Your only hope is that someone will discover and post an exploit that can root the unrootable versions of Android or better yet, discover a way to unlock the tablet's bootloader.
Cat McGowan said:
Correct. There is nothing you can do now. Your only hope is that someone will discover and post an exploit that can root the unrootable versions of Android or better yet, discover a way to unlock the tablet's bootloader.
Click to expand...
Click to collapse
thanks for your answer.
Cat McGowan said:
Correct. There is nothing you can do now. Your only hope is that someone will discover and post an exploit that can root the unrootable versions of Android or better yet, discover a way to unlock the tablet's bootloader.
Click to expand...
Click to collapse
sorry,i forgot to tell you,my tablet is chinese version,somebody say chinese tablets are different,bulid 10#1 can be root.is it really?
[email protected] said:
sorry,i forgot to tell you,my tablet is chinese version,somebody say chinese tablets are different,bulid 10#1 can be root.is it really?
Click to expand...
Click to collapse
Meaning that Chinese tab can be unrootable from kernel 8 and up. Unlike most regions where 10 is no good. If the AIO tool gives you the red screen then you will have to wait for another exploit like alot of us
Stifilz
Hello,
i just want to root my tablet, then i noticed i have firmware 3.2 with kernel #10.
As i know I need a OTA update 3.2.1 with a different kernel than #10
My problem ist to get the update for my region, I'm from austria.
Pleace can anyone provide me such an OTA update or just give me a link to it.
It would be verry kind of you.
Best Regards
Benjo
Hi guys
I've prepared ready-to-flash nbx03 fw.
What's the difference between stock and that one?
Features:
prerooted,
'rescue-backdoored'
init.d added
write permissions for ext-sdcard enabled,
replaced locked recovery with one from R1A!
So you will have newest R5A with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5A disables shell in recovery - means no more functions
like flashing custom, decrypting etc!
Requirements:
no R5/R5A flashed before, because of recovery locked down.
(= will not work on downgraded from R5/R5A devices)
root
newest AiO
How-to?:
download fw and rename it as 'custom_update_signed.zip',
put custom_update_signed.zip on root of your extSD,
run AiO - choose '3' & '4' - Flash signed zip, choose automatic.
just sit, wait and enjoy
PS. wipe is not required, but recommended.
If after wipe or reboot your device will boot to old firmware (which is still on 2nd /system partition),
then you should use v2 doubleFLASH custom zip - which updates both /system0&1 partitions when flashing
This prevents from such problems!
You can flash 1st regular version of custom zip, or directly v2 with doubleFLASH
Easy as hell
Download:
NEW R5A with 3G! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip
NEW R5A with 3G!:
custom_prerooted_R5A_nbx03_016-ota-121116077.zip
NEW R5A WiFi only! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip
old R5 WiFi only custom_prerooted_nbx03_001-ota-120914044_by_condi.zip
-----------------------
mirror on Google Drive
-----------------------
br
condi
condi said:
Hi guys
I've prepared ready-to-flash US nbx03_001-ota-120914044.
What's the difference between stock and that one?
Features:
prerooted,
'rescue-backdoored'
init.d added
write permissions for ext-sdcard enabled,
replaced locked recovery with one from R1!
So you will have newest R5 with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5 disables shell in recovery - means no more functions
like flashing custom, decrypting etc!
Requirements:
R1 firmware currently on device,
no R5 flashed before, because of recovery locked down.
(= will not work on downgraded from R5 devices)
root
AiO
How-to?:
download fw and rename it as 'custom_update_signed.zip',
put custom_update_signed.zip on root of your extSD,
run AiO - choose '3' & '4' - Flash signed zip.
just sit, wait and enjoy
Easy as hell
br
condi
----uploading...
Click to expand...
Click to collapse
Great work once again!!!!
Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE
YOU ARE A TREASURE TO THIS COMMUNITY
Stifilz
stifilz said:
Great work once again!!!!
Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE
YOU ARE A TREASURE TO THIS COMMUNITY
Stifilz
Click to expand...
Click to collapse
im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !
condi
condi said:
im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !
condi
Click to expand...
Click to collapse
You SIR are toooooooooooo modest.
So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself
Well time will tell and we WILL get there! LOL
Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?
I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?
That would be TOPS.
Thanks again
Stifilz
stifilz said:
You SIR are toooooooooooo modest.
So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself
Well time will tell and we WILL get there! LOL
Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?
I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?
That would be TOPS.
Thanks again
Stifilz
Click to expand...
Click to collapse
have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.
br
condi said:
have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.
br
Click to expand...
Click to collapse
Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL
Stifilz
stifilz said:
Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL
Stifilz
Click to expand...
Click to collapse
check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!
btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??
br
condi said:
check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!
btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??
br
Click to expand...
Click to collapse
Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.
Still got this error.
Code:
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.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
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" || getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?
When tabs are returned to Sony they come back as 3.2!!
Stifilz
stifilz said:
Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.
Still got this error.
Code:
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.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
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" || getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?
When tabs are returned to Sony they come back as 3.2!!
Stifilz
Click to expand...
Click to collapse
check /datapp/vendor/vendor0&1/vendor.prop for nbx values
So if we have R5 then we shouldn't even bother with this?
condi said:
check /datapp/vendor/vendor0&1/vendor.prop for nbx values
Click to expand...
Click to collapse
Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.
Copy system image...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx-3"3.2/THMAS11001/11001.003:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys"
Click to expand...
Click to collapse
[email protected] said:
So if we have R5 then we shouldn't even bother with this?
Click to expand...
Click to collapse
Correct because we have already lost adb shell in recovery.... so can't flash modded roms like this one.
Stifilz
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
Ultimate Chicken said:
Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.
Click to expand...
Click to collapse
Don't worry about that, that was condi and I trying to figure something out. Didn't work BTW.
As in first post you need to be on R1A/R2A. US is the only region with R5 out atm. Apparently the other regions are due out mid DEC....
Stifilz
Must be doing something wrong....
Hi,
I'm trying to flash a UK 4.0.3 R1a tablet with the details in this thread.
The tablet was rooted via the b1nry method (when that method was first discovered).
All appears to work OK but then I get a failed assert.
Told the device to do a full wipe, then rooted using the AiO5.2 - this worked fine.
Then attempted the flash again, still no joy, same error message.
What am I doing wrong ? Should I changed the tablet to US region before attempting the flash ?
Thanks
Ian
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
In answer to my own query - no that doesn't help either, the error this time coming much sooner (whilst verifying update package) :-
Erohibit update as a result of checking version or base sku
Attached should be a pic of the actual error I receive...if that helps at all..
ianfretwell said:
Attached should be a pic of the actual error I receive...if that helps at all..
Click to expand...
Click to collapse
That error is 100000% ok.
Use 'adb devices' and tell me if there is device there - im pretty sure that there will be none.
Probably you have not installed drivers for adb in recovery (yes it needs to be installed aside from regular drivers in normal boot. So enter device manager and there should be new device without driver. You will have to install it manually.
Oh and if you have changed region to US, then go to AiO\files directory and delete _hack_recovery.zip.
Condi - many thanks, you were, of course, absolutely correct and the flash has now succeeded !!
Apologies for being the noob!!
Ian.
condi said:
I've prepared ready-to-flash US nbx03_001-ota-120914044.
So you will have newest R5A with still adb shell enabled in recovery!
Click to expand...
Click to collapse
Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.
I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.
Cat McGowan said:
Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.
Click to expand...
Click to collapse
biablo said:
I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.
Click to expand...
Click to collapse
yes, just a typo, my bad ive lost count with all that incrementals lol
wifi only rom, right?
Hello,
I don't know much of updating firmware besides the OTA like on mobile phones , a fully automatic proces so please have patience with my problem. This forum seems the major source of tablet s knowledge so I hope for a positive result.
Sometime ago I bought a Sony Tablet S from a friend, I never used it a lot until recently.
I problaly had it before it was officialy released now that I think of it.
but I have a major problem it seems like it was a engineering sample of some kind.
I cant update through settings etc. I get many error on youtube app and while browsing I don''t do much else on it yet.
These are the settings it runs on shown under settings:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
On the back there is a label stating its not for sale /made in china
S1 V0A0 PVT
A1TWS-002
I tried running the comdi AIO and got error message thats its unrootable.
I think I had all requirements in order like adb devices listed in cmd, usb debugging on tablet,mtp driver..
Is there anything that I can do to update this table to ICS maybe?
F.
Try updating all your apps btw does psxperia work on your device?
Sent from my Sony Tablet S using xda app-developers app
fcbvenlo said:
Hello,
I don't know much of updating firmware besides the OTA like on mobile phones , a fully automatic proces so please have patience with my problem. This forum seems the major source of tablet s knowledge so I hope for a positive result.
Sometime ago I bought a Sony Tablet S from a friend, I never used it a lot until recently.
I problaly had it before it was officialy released now that I think of it.
but I have a major problem it seems like it was a engineering sample of some kind.
I cant update through settings etc. I get many error on youtube app and while browsing I don''t do much else on it yet.
These are the settings it runs on shown under settings:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
On the back there is a label stating its not for sale /made in china
S1 V0A0 PVT
A1TWS-002
I tried running the comdi AIO and got error message thats its unrootable.
I think I had all requirements in order like adb devices listed in cmd, usb debugging on tablet,mtp driver..
Is there anything that I can do to update this table to ICS maybe?
F.
Click to expand...
Click to collapse
3.0.1? My was 3.2.1, back to factory!!!
fcbvenlo said:
Hello,
I don't know much of updating firmware besides the OTA like on mobile phones , a fully automatic proces so please have patience with my problem. This forum seems the major source of tablet s knowledge so I hope for a positive result.
Sometime ago I bought a Sony Tablet S from a friend, I never used it a lot until recently.
I problaly had it before it was officialy released now that I think of it.
but I have a major problem it seems like it was a engineering sample of some kind.
I cant update through settings etc. I get many error on youtube app and while browsing I don''t do much else on it yet.
These are the settings it runs on shown under settings:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
On the back there is a label stating its not for sale /made in china
S1 V0A0 PVT
A1TWS-002
I tried running the comdi AIO and got error message thats its unrootable.
I think I had all requirements in order like adb devices listed in cmd, usb debugging on tablet,mtp driver..
Is there anything that I can do to update this table to ICS maybe?
F.
Click to expand...
Click to collapse
from what region/country is your device?
Hi Guys,
As I said its a engineering pvt sample.
On outside:
S1 V0A0 PVT
A1TWS-002 <- TW I guess Taiwan?
In Android about devide:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
I have it now with Dutch language settings.
I have no psxperia as far as I can see, or should I download that?
But please what should be my first step in trying to update this thing to atleast a android verison that can run google play..because it shuts down on 3.01..I mean root whatever it takes.
You want photos?
F.
fcbvenlo said:
Hi Guys,
As I said its a engineering pvt sample.
On outside:
S1 V0A0 PVT
A1TWS-002 <- TW I guess Taiwan?
In Android about devide:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
I have it now with Dutch language settings.
I have no psxperia as far as I can see, or should I download that?
But please what should be my first step in trying to update this thing to atleast a android verison that can run google play..because it shuts down on 3.01..I mean root whatever it takes.
You want photos?
F.
Click to expand...
Click to collapse
post here your /system/build.prop content
condi said:
post here your /system/build.prop content
Click to expand...
Click to collapse
Hi Condi
I put the values in a txt file.
Hope it is what you need.
Othewise please explain.
F.
fcbvenlo said:
Hi Condi
I put the values in a txt file.
Hope it is what you need.
Othewise please explain.
F.
Click to expand...
Click to collapse
1st try this: http://www.4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
normal flash update via recovery.
if you will get some error - just after flash use adb pull /tmp/recovery.log
and post it here.
Hey Condi,
That file is curropted tried downloading twice winrar cant open..
F.
fcbvenlo said:
Hey Condi,
That file is curropted tried downloading twice winrar cant open..
F.
Click to expand...
Click to collapse
The file is not corrupt; instead, it is encrypted. The zip file is to be used as-is. Do not try to extract its contents using WinRAR, 7zip, etc.
Cat McGowan said:
The file is not corrupt; instead, it is encrypted. The zip file is to be used as-is. Do not try to extract its contents using WinRAR, 7zip, etc.
Click to expand...
Click to collapse
Hi
OK i succesfully opened recovery console and loaded the image on the sd.
But then below errors:
Finding update package
Desllunvr update package
Opening update package
Verifyng update package
E: failed to verify whole-file signature
E: signature verification failed
Instalation aborted
I cant pull like you stated because device isnt found in adb when I reboot to go into recovery console..if its shut down its gone from pc..when the tablet boots into android its found again in adb..
I appreciate the help.
The errors are msot sure my mistakes I am doing this 1st time.
I am not sure adb is correct installed.
F.
fcbvenlo said:
Hi
OK i succesfully opened recovery console and loaded the image on the sd.
But then below errors:
Finding update package
Desllunvr update package
Opening update package
Verifyng update package
E: failed to verify whole-file signature
E: signature verification failed
Instalation aborted
I cant pull like you stated because device isnt found in adb when I reboot to go into recovery console..if its shut down its gone from pc..when the tablet boots into android its found again in adb..
I appreciate the help.
The errors are msot sure my mistakes I am doing this 1st time.
I am not sure adb is correct installed.
F.
Click to expand...
Click to collapse
Drivers need to be installed separately for recovery. Look in device manager. If you cant get that to work after boot get the /cache/recovery/last_log (I think)
fcbvenlo said:
Hi Guys,
As I said its a engineering pvt sample.
On outside:
S1 V0A0 PVT
A1TWS-002 <- TW I guess Taiwan?
In Android about devide:
Modelnummer NBX03
Android-versie 3.01
Kernel-versie 2.6.36.3 [email protected] #1
Build-nummer FF0.82.021100001
I have it now with Dutch language settings.
I have no psxperia as far as I can see, or should I download that?
But please what should be my first step in trying to update this thing to atleast a android verison that can run google play..because it shuts down on 3.01..I mean root whatever it takes.
You want photos?
F.
Click to expand...
Click to collapse
Psxperia is a PlayStation emulator made frombthe crash bandicoot app its awesome im trying to get it working on ics
Sent from my LT28i using xda app-developers app
I recently received a developer preview device, Acer A3-30, running Lollipop. Previous tablets I have worked with are already rooted or rootable however this is a new tablet that isn't in production yet. I have tried installing ChainFire SuperSu.zip through fastboot but had no luck. I received an error of permission denied. I am currently setting up a machine to build a custom recovery but have never done so. I only have one of these devices to try any of this on and for my apps to work I have to have a rooted device. Is there anything I can do? I have already tried with Framaroot, CF-autoroot, kingo root, Impactor and a few other one click root methods.
Any advise?
If it helps, here is the build.prop for the device:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22C
ro.build.display.id=Acer_AV0L0_A3-A30_0.000.42_WW_GEN1
ro.build.version.incremental=1423546392
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.1
ro.build.date=Tue Feb 10 13:34:11 CST 2015
ro.build.date.utc=1423546451
ro.build.type=user
ro.build.user=pandora
ro.build.host=pandora08
ro.build.tags=release-keys
ro.build.sku=WW_GEN1
ro.product.model=A3-A30
ro.product.brand=acer
ro.product.name=a3a30_ww_gen1
ro.product.device=omega
ro.product.board=baytrail
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.id=Omega
ro.product.cpu.abi=x86
ro.product.cpu.abi2=armeabi-v7a
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Acer
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=omega
Rsek said:
I recently received a developer preview device, Acer A3-30, running Lollipop. Previous tablets I have worked with are already rooted or rootable however this is a new tablet that isn't in production yet. I have tried installing ChainFire SuperSu.zip through fastboot but had no luck. I received an error of permission denied. I am currently setting up a machine to build a custom recovery but have never done so. I only have one of these devices to try any of this on and for my apps to work I have to have a rooted device. Is there anything I can do? I have already tried with Framaroot, CF-autoroot, kingo root, Impactor and a few other one click root methods.
Any advise?
Click to expand...
Click to collapse
I am looking for root solutions of Acer A3-A30, too.
May I ask if anybody can advise? Thanks in advance for the help!
Gary Chan said:
I am looking for root solutions of Acer A3-A30, too.
May I ask if anybody can advise? Thanks in advance for the help!
Click to expand...
Click to collapse
I bought an A3-A30 last week, and found the root process very easy using the Intel Temp Recovery method.
I now have root, I do not want a custom rom as this is as close to Vanilla Android as it gets without a NEXUS badge. All you need is a SuperSU.zip and Intel Temp Recovery.
Edit: URL for instructions: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Options that work fro the Lollipop Acer A3-A30 are
CWM Recovery
Method T4
CraigsBar said:
I bought an A3-A30 last week, and found the root process very easy using the Intel Temp Recovery method.
I now have root, I do not want a custom rom as this is as close to Vanilla Android as it gets without a NEXUS badge. All you need is a SuperSU.zip and Intel Temp Recovery.
Edit: URL for instructions: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Options that work fro the Lollipop Acer A3-A30 are
CWM Recovery
Method T4
Click to expand...
Click to collapse
Thanks! It works! :good:
One thing to remind is that the SuperSU.zip needs to be put into SD card because the internal storage space is not mounted in recovery.
Has anyone found a way to install custom roms on the A3-A30 yet or away to make cwm permanent
Narrowing down my original question...I keep getting DEVICE STATUS: UNKNOWN when I run the launcher in the Intel Temp Recovery process. Why is my a3-a30 not being recognized? I don't see any errors on my pc's Device Manager....
Hi, just tried this method on my Acer Iconia A3-A30 but not working for me.
I get into FASTBOOT MODE but it comes up with an error in blue text: E:No valid installer medium found.
Any ideas please?