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
Related
Hi all,
Anyone having the same issues?
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
I'm also having the trouble with the same built (2.73.707.9), when i put the cm-hero-recovery.img on the sdcard, then run flash recovery (sdcard/cm-hero-recovery.img) i cant click on backup to flash custom image button, fastboot boot isnt working for me!. Please if someone can help that would be greatly appreciated.
salmanbodla said:
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
Click to expand...
Click to collapse
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
I am also having the same problem. Flashrec says backup failed but more importantly it says flash failed.
My 2.73.707.9 ROM is straight out of the box so I do not have any recovery image installed. Much appreciated if some clever person can help out. Thanks!
Leechoonhwee said:
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
Click to expand...
Click to collapse
I'm Having the exact same problem with the adb commant prompt.
I tried to close all apps with taskiller and tried to use flashrec again and again without any luck, I can't even click on the flash custom image button, I can only click on backup, and it gives me an error.
Leechoonhwee said:
Hi all,
Anyone having the same issues?
Click to expand...
Click to collapse
I have ticked usb debugging and C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
I have tried flashrec and followed the instructions and it says fail.
It cannot start with back up.
Thanks
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
awsy44 said:
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
Click to expand...
Click to collapse
I have the exactly same Kernel version. Some new discovery
1. Use the drivers from SDK 1.6. Phone in normal mode. Adb devices and fastboot devices can recognise the phone.
2. Fastboot USB mode. Fastboot devices recognise devices while adb returns nothing.
OK, I am running the official new European ROM 2.76.405.5 with the following kernel:
2.6.27-8dd6deee [email protected] )
I don't know how different it is from yours, but some numbers are certainly different. May be that is the reason, but I am afraid I am not sure. So keep trying - you may be lucky!
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
1. Linux version 2.6.27-44690c1a ([email protected]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #739 PREEMPT Thu Aug 27 19:50:51 CST 2009
2. the ROM on my unbranded HK retail version (htc_asia_hk_wwe) is 2.73.721.9 146733 CL#62020 release-keys
Hey roger,
same here, look like the kernel expliot is fixed:
#adb push /tmp/flashrec-1.1.2-20090909/assets/raw/asroot /sqlite_stmt_journals
932 KB/s (81188 bytes in 0.085s)
#adb shell /sqlite_stmt_journals/asroot /sqlite_stmt_journals/abc /system/bin/sh
FAILURE: Didn't get root.
awsy44 said:
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
Click to expand...
Click to collapse
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Heppieboeddah said:
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Click to expand...
Click to collapse
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
awsy44 said:
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
Click to expand...
Click to collapse
Your phone is unlocked in a sense that you can insert any sim card and it works. CID lock means that you cannot flash ROMs other than your region.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Leechoonhwee said:
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Click to expand...
Click to collapse
Then I think the best way to go is to install Modaco rom version 2.2 enhanced - that has Chinese IME in it. About MCR 2.3, people have several complaints, but there is no harm in trying. Oh but the main question is how will you install the recovery image to do all this rooting/flashing since flashrec is the only option available after the upgarde (I suppose!). The new hboot file won't even allow you to "fastboot boot recovery.img". That's a bit of a shame but I am sure cleverer people out there will soon find a hack
As Modaco's boot image "Superboot (for Nexus One)" got no more updates after Android build version GRI40 and we're on GRK39F for some time now; and even though the Superboot GRI40 version gave you root as desired (https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/), that Superboot version also caused some problems with wifi connection and had an outdated su binary, as well as an outdated Superuser.apk.
To cut a long story short, i did it on my own: Bexboot. A boot image - especially for Android GRK39F on passion devices. I compiled it (based on a guide by Modaco himself) from the stock GRK39F source of my own Nexus One. Also it includes the lates Superuser.apk (v3.0.5) and the latest su binary (v3.0).
Here you go: https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
Any feedback highly appreciated.
[UPDATE#1 08.11.2011]:
Please don't use v1 (link above) any longer. Instead use the Bexboot v2.0 (link below). It was rebuilt from a completely clean stock rom, what solves the compatibilty issues, some reported for v1. (Also it includes the latest Superuser.apk (3.0.6), as well as the latest su binary (3.0.3).)
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
[UPDATE#2 11.12.2011]:
As i forgot to pay the invoice for the server where my blog is running on, it is offline since yesterday. :/ Anyway, i uploaded a copy of the zip archive containing all files you need to root your device to http://www.nahklick.de/user/stephan/bexboot.v2.GRK39F_OTA.zip. To get the instructions, follow this link http://www.google.com/search?q="bexboot"+version+2 and use the Google cache to view the original site. Thx
[UPDATE#3 20.02.2012]:
Files and instructions mirrored at request: http://code.google.com/p/bexboot/
i've posted this on my blog aswell. Nice work
http://patrick.oberdorf.net/2011/10/12/nexus-one-root-rechte-mit-stock-rom/
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
zc2 said:
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
Click to expand...
Click to collapse
Hi zc2,
sorry for the long response time, i was on a business trip and didn't had the time to check in. I received a bunch of similar issue reports so i did a factory reset and rebuilt the bootloader from a completely clean stock rom.
First comments confirm that it now also works for persons, that had the same issue like you with v1. So if you're still interested in it, check out the updated release version: https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Hi Bexton, thank you for the response. I actually was able to root my phone using the instructions from the following post:
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
V2 Failed for me
Bexton said:
...use the Bexboot v2.0 (link below)....
Click to expand...
Click to collapse
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Thanks for such a fast reply. I bought the phone in Bangkok. It was a "grey market" item from the Hong Kong market. I am not sure whether my Thai carrier even bothers with such things.
I looked at the link but unfortunately for me, I have only the most primitive understanding of how to deal with the bootloader, etc. So I can't even grasp what aspects of that thread apply to me. I really need step-by-step instructions. So unless I can find someone with more mastery, I guess I will only dream of Cyanogen Mod on my phone.
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Bexton said:
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Click to expand...
Click to collapse
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
efrant said:
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
Click to expand...
Click to collapse
I realize you're trying to clarify. But I don't understand any of the terminology. The only thing I am capable of is following a prescribed procedure. I thought this procedure was going to unlock and root the phone. I guess I was wrong.
I don't have the diagnostic skills to change direction if things don't go in a predictable fashion-- I've only used stock devices up until now and this was my first attempt. I guess the best I can hope for is to make contact with someone more experienced when I am next in the US and have that person assist me. It makes it more difficult because most of what I am finding online is either old (pre-Gingerbread) or it assumes the user has hacked their Nexus One in the past and just needs to bring it up to date.
My goal is to get past the memory problems I am having by installing a custom ROM with a minimal set of apps in phone memory-- and more customizability.
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
davelis828 said:
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
Click to expand...
Click to collapse
No prob. You can use: https://bexton.net/android/n1/recoveries/recovery-clockwork-5.0.2.0-passion.img
If needed, here's the full stock GRK39F: https://bexton.net/android/n1/sys/grk39f/ota.zip and here the update: https://bexton.net/android/n1/sys/grk39f/d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip
o thanx ma! i appreciate your feedback, you did it on both sites aswell
Respect!
Mirror created at request: http://code.google.com/p/bexboot/
I gave superoneclick a go before trying this method. It worked flawlessly.
Sent from my Nexus One using Vodka
Source code availability?
Hi Bexton,
first of all, thanks for your work!
Next, I'd like to replace the Superuser app by Koush' one (https://github.com/koush/Superuser/).
Would it be possible to get the source code of bexboot?
None is available at http://code.google.com/p/bexboot/source/checkout...
Regards,
Patrick.
I already tried everything enabled ADB, everything seems fine, but when i start the root app, everytime it gives me this error
remount failed: operation not permited
failed to copy 'files\su' to '/system/bin/su': Read only file system, what am i doing wrong???
please help me what am i doing wrong i'm on 3.2.1 (release 2) and my kernel is 2.6.36.3 build 8#1 so it's supoused to be exploitable.
Tekkenlord said:
I already tried everything enabled ADB, everything seems fine, but when i start the root app, everytime it gives me this error
remount failed: operation not permited
failed to copy 'files\su' to '/system/bin/su': Read only file system, what am i doing wrong???
please help me what am i doing wrong i'm on 3.2.1 (release 2) and my kernel is 2.6.36.3 build 8#1 so it's supoused to be exploitable.
Click to expand...
Click to collapse
Did you do the Rescue-Backdoor with Condi's AiO Tool
If not then you are getting a red menu and if you already did that
Then maby you could try this:
1. Connect your tab.
2. Enable usb debugging.
3. Open device manager
4. Disable SONY TABLET S
5. Start Condi's 2.7 AiO Tool
6. Choose option 1 for root.
7. Press enter so your device will reboot.
8. look in device manager list and wait until SONY TABLET S re-appears
9. If it appears then you must enable it again and wait for the AiO tool to finish.
YF,
Mahaco.
thanks for answering, no i havent done the rescue back-door, so i should try that first? and then the steps you mention?
but wait don't i need to be rooted first to do the rescue back door?
also when the exploit starts and in the middle of it a meesage in windows apperas saying that it is trying to install MTP USB device and it's unable to install it maybe that's another cause?
pardon my noobinesh but im really getting desperate here.
You were right!!!!! i was disabling the adb device listed NOT the sony tablet S listed i disabled Sony Tablet S and enabled it again in the fist reboot and that did the magic (crazy uh?) thanks so much Mahaco you're a life saver now on to another dumb question now that i'm rooted what? xD
Tekkenlord said:
-Thanks for answering, no i havent done the rescue back-door, so i should try that first? and then the steps you mention?
-But wait don't i need to be rooted first to do the rescue back door?
-Also when the exploit starts and in the middle of it a meesage in windows apperas saying that it is trying to install MTP USB device and it's unable to install it maybe that's another cause?
-Pardon my noobinesh but im really getting desperate here.
-You were right!!!!! i was disabling the adb device listed NOT the sony tablet S
listed i disabled Sony Tablet S and enabled it again in the fist reboot and that did the magic (crazy uh?)
thanks so much Mahaco you're a life saver now on to another dumb question now that i'm rooted what? xD
Click to expand...
Click to collapse
Nice to hear you made it! You gave me a smile for that lol
Okay now try the rescue-backdoor,
Follow these steps carefully, be patient, if you have downloaded the update 3.2.1.r2
then don't install!, This will probaly change your kernal version and you will not able to gain root anymore!
So if you downloaded the update the AiO tool will go on,
if you have finished that, some values are changed and you are able to do the steps from Condi's ICS steps ( In Blue )
i must remind you even how silly it sounds, with switching you External SD from your tab to your pc
then don't forget to put it back before you continue, this wont brick your device but it can cause problems
and you have to re-do all the steps which is quite frustrating if you are stressed about bricking your device,
And last but not least, don't change your region thats not nessesary just follow the steps and you will get true
thanks i will try everything i can, i just wanted to ask what do you mean by if i downloaded the update 3.2.1 r2 you mean if i downloaded it from the internet then i can't do the ICS and rescue-back door thing?
because yes i updated the tablet via internet form an original update, thanks for the patience you have and the help; me i'm a total noob.
Tekkenlord said:
thanks i will try everything i can, i just wanted to ask what do you mean by if i downloaded the update 3.2.1 r2 you mean if i downloaded it from the internet then i can't do the ICS and rescue-back door thing?
because yes i updated the tablet via internet form an original update, thanks for the patience you have and the help; me i'm a total noob.
Click to expand...
Click to collapse
No the AiO tool will atomatic start the download 3.2.1.r2 on your tab nothing more just try the rescue backdoor and you will find out after you have proper driver installed
succes
i'm already in ICS and i can say it's quite nice and all, thanks again mahaco for all the help provided, and with another silly question, how can i gain more access to other apps now that im rooted? i use the condi's tool to install google market place modded or what?
Tekkenlord said:
i'm already in ICS and i can say it's quite nice and all, thanks again mahaco for all the help provided, and with another silly question, how can i gain more access to other apps now that im rooted? i use the condi's tool to install google market place modded or what?
Click to expand...
Click to collapse
Thats something you have to find out on condi's page thats not my part,
I'll PM you about something what you can do with Root access in combination with Rom Tool Box Free,
EDIT>
Be carefull with deleting system apps, there is a high chance that you ruïn your tablet,
so think twice before you uninstall an system app,
Don't try region changer still not supported i think,
I installed the modded version in HC but it didn't worked for me so don't know that
I ordered a Sony Tablet S tablet model SGPT112US/S from Woot.com. I updated and rooted it from its stock Android 3.2 to 4.0.3r1a. Here is my adventure in brief sentences. Keep in mind that I am not telling you what to do, I am just telling you what I did.
Computer running Windows 7 with Android Composite ADB Interface and Sony Tablet S drivers installed.
Links to files used:
Android 3.2.1r2(US) file signed-nbx03_001-ota-0042.001.zip
Android 4.0.3r1a(US) file signed-nbx03_001-ota-120803002.zip
Condi's ALLinONE v4.0 tool file S.onyTablet.S__ALLinONE__v4.0.7z
Android Debug Bridge version 1.0.29 file ADB_v1.0.29.zip
Powered on tablet and did not set up Wi-Fi, accounts, etc.
Went into Settings.
About table read:
- Android version 3.2
- Kernel version 2.6.36.3 [email protected] #1
- Build number 1.10.001100001
Made sure Wi-Fi was turned off.
Turned on (allowed) Unknown sources.
Turned on USB debugging.
Exited Settings.
Opened File Transfer app, went into its settings and selected Do nothing.
Powered off tablet.
Installed SD card in computer.
Copied 3.2.1r2(US) file signed-nbx03_001-ota-0042.001.zip to SD card.
Moved SD card from computer to tablet.
Powered on tablet into recovery mode.
From recovery screen, selected Update system from SD card.
From next screen, selected signed-nbx03_001-ota-0042.001.zip file.
Allowed update to complete.
Tablet rebooted to normal boot.
Went into Settings.
About tablet read:
- Android version 3.2.1 (release2)
- Kernel version 2.6.36.3 [email protected] #1
- Build number THMASU0012400
Exited Settings.
Installed Condi's ALLinONE v4.0 tool.
Added empty file named _offupdates to ALLinONE tool's files directory.
Updated ALLinONE tool's adb files to version 1.0.29.
Connected USB cable between tablet and computer.
Started ALLinONE tool.
From main menu, selected 1 Root device.
Allowed rooting of 3.2.1r2 to complete.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.
Moved SD card from tablet to computer.
Deleted signed-nbx03_001-ota-0042.001.zip file from SD card.
Copied 4.0.3r1a(US) file signed-nbx03_001-ota-120803002.zip to SD card.
Moved SD card from computer to tablet.
Powered on tablet.
Started ALLinONE tool.
From main menu, selected 3 * Custom ROM and Flashing [SUBMENU].
From next menu, selected 1 Create decrypted update.zip [+optional make custom].
Followed ALLinONE prompts.
First problem occurred!
Booted tablet into recovery mode as prompted, but ALLinONE tool stalled at NOW ENTER RECOVERY MODE screen lastly showing 3 dots.
KCCO.
From recovery screen, selected Update system from SD card.
From next screen, selected install.zip file.
Allowed update to complete.
From recovery screen, selected Update system from SD card.
From next screen, selected signed-nbx03_001-ota-120803002.zip file.
Allow update to complete. (Update took several minutes to complete.)
ALLinONE tool continued as expected.
Continued following ALLinONE prompts.
Second problem occurred!
Booted tablet into recovery mode as prompted, but ALLinONE tool stalled at NOW ENTER RECOVERY MODE screen lastly showing 3 dots.
KCCO.
From recovery screen, selected Update system from SD card.
From next screen, selected install.zip file.
Allowed update to complete.
From recovery screen, selected Update system from SD card.
From next screen, selected custom_update_signed.zip file.
Allowed update to complete. (Update took several minutes to complete.)
ALLinONE tool continued as expected.
Tablet rebooted to normal boot.
Went into Settings.
About tablet read:
- Android version 4.0.3 (release1a)
- Kernel version 2.6.39.4 [email protected] #1
- Build number TISU0R0010110
Exited Settings.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.
Booted into recovery mode.
From recovery screen, selected Reset to factory settings.
From next screen, selected Yes -- delete all user data.
Allowed reset to complete.
Tablet rebooted to normal boot.
Set up Wi-Fi, accounts, etc.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.
Successfully updated tablet from stock (unrooted) Android 3.2 to rooted Android 4.0.3r1a.
Wiped sweat off forehead.
Nice post. This will surely help all the Wooters and clear some things up. Glad to see it went well
Stifilz
I too purchased a tablet s from woot and successfully updated to ics using aio4.0. But, i had to manually update the adb driver in device manager while in recovery to resume full auto install during the 3 dots. Apparently it sees the device differently while booted verses in recovery. This was my second attempt, the first ended up with ics and no root. By watching the first video example by bluechip j, i was told not to root when prompted but to add that later. Bad mistake. Luckily i could reflash the 3.2.1 update again and start over. Overall a very trial and error journey through this process. I would have preferred a detailed written procedure but i figured it out in the end. Thanks to everyone involved for all their hard work.
Sent from my DROID RAZR using Tapatalk 2
Good stuff...I could have used this last weekend. Bought my tablet S through Woot as well.
Is that version of ICS you used basically the rooted version of the OTA update? I don't want to lose all the functionality that SONY built in to this thing (the PS games mostly sound pretty cool), but I want to get it rooted while it's still possible (looks like no one has cracked how to root this thing if you take the OTA). I just got mine from woot this afternoon and I'm anxious to get it up and running as a gift for my bf... he's been jealous of my Galaxy Tab 10.1 for a while now
Awesome write-up BTW... I plan to use this for my reference!
agent0014 said:
Is that version of ICS you used basically the rooted version of the OTA update? I don't want to lose all the functionality that SONY built in to this thing (the PS games mostly sound pretty cool), but I want to get it rooted while it's still possible (looks like no one has cracked how to root this thing if you take the OTA). I just got mine from woot this afternoon and I'm anxious to get it up and running as a gift for my bf... he's been jealous of my Galaxy Tab 10.1 for a while now
Awesome write-up BTW... I plan to use this for my reference!
Click to expand...
Click to collapse
Yes the method above using AIO will give you a pre-rooted ICS, same as OTA but with root access. If you update OTA there is currently no way to root and no way to go back. Follow this guide and you can't go wrong!
Stifilz
agent0014 said:
Is that version of ICS you used basically the rooted version of the OTA update?
Click to expand...
Click to collapse
Yes, the ICS file I rooted was the latest OTA update file that a Sony Tablet S (US region) would download from Sony's servers. Links to all of the files used in my update/root can be found in this forum; however, to assist you better, I am going to edit my original post and add links to all of the files.
bart77 said:
I too purchased a tablet s from woot and successfully updated to ics using aio4.0. But, i had to manually update the adb driver in device manager while in recovery to resume full auto install during the 3 dots. Apparently it sees the device differently while booted verses in recovery. This was my second attempt, the first ended up with ics and no root. By watching the first video example by bluechip j, i was told not to root when prompted but to add that later. Bad mistake. Luckily i could reflash the 3.2.1 update again and start over. Overall a very trial and error journey through this process. I would have preferred a detailed written procedure but i figured it out in the end. Thanks to everyone involved for all their hard work.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Say "no" to add root but do it later seems to be a really important point in the original instructions by TheHurf which BluechipJ referred to, though that was in AiO V2.7. Really curious about the reason. @@
jessicaat said:
Say "no" to add root but do it later seems to be a really important point in the original instructions by TheHurf which BluechipJ referred to, though that was in AiO V2.7. Really curious about the reason. @@
Click to expand...
Click to collapse
The reason for saying no to add root at the time it is said is because (1) the tablet's HC Android 3.2.1 is (must be) already rooted and (2) the rooted and signed ICS Android 4.0.3 update file custom_update_signed.zip has not been created yet.
I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.
Sent from my DROID RAZR using Tapatalk 2
bart77 said:
I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.
Click to expand...
Click to collapse
My updating Condi's AiO tool's adb files to version 1.0.29 was done for the sake of caution because of reports that previous versions of adb have not played nice with the Android 4.0.3r1a update. Updating adb may or may not have been necessary, but hey, updating it didn't hurt! Also, I have used Condi's AiO tool severals times to root three different tablets; two tablets three times and one (the one I just rooted) two times. I run Win7x64 and via Windows Explorer have always double-clicked S.onyTablet.S.bat to start it and have never had it close down unexpectedly. Perhaps the problem is unique to your (and maybe others) computer.
bart77 said:
I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Or right click run as admin should do it
Thanks for this thread. I'm new to rooting, but I've been following this forum for a while. I picked up a second Sony tab from the Woot sale to replace my 16g and one for my wife.
The steps were a little different for me. The AiO tool (v 4.0 w/ updated adb files) stopped on me as well and in different places. It made it through, just answering "yes" for all options during the custom ROM and flash process.
Here's a few things I noticed that may help others undergoing this process.
I had to manually update the Sony USB driver (see bluechipj's video). After that it worked fine.
Mine was right out of the box. I had not installed hardly any apps on it as I still had my unrooted ICS 16g Sony Tablet that I was using while researching how to root.
I flashed 0035 >>0042 right out of the box then ran the AiO tool. After I finished the 4.0.3.r1a flash, I had myself a freshly rooted ICS tablet. I then went to go to the Play store (I had not updated it from the "Market" version that came with it from the factory. It kept telling me that I needed to associate a Google account to it (already associated) and prompted me to retry. App cache/data both cleared with no change. I did a factory reset and it worked fine after that. No sweat since I had not installed any apps or tied any accounts to it yet.
If you just got this tablet, I would say to try and update to the play store ahead of time. It might save you from having to do a factory reset later on.
Another oddity that I noticed was that AiO (adb) no longer recognized the tablet when I went to disable the OTA notifications. I had to again manually update the tablet USB driver (3rd option: composite) and after that it worked just fine. Not sure if that's because of the flash or factory reset or both. If the AiO tool stops recognizing your tab after the flash, check your driver.
For what it's worth, I'm running Win7 64.
Hope that saves someone a headache.
Thanks again for the run-through and links.
Here's a question for you folks. Can I just take the custom ROM that I created on my tablet and use it to flash my wife's tablet after I flash hers to 0042 and root it or should I go through the whole process again?
Thanks!
Cagedodger said:
Here's a question for you folks. Can I just take the custom ROM that I created on my tablet and use it to flash my wife's tablet after I flash hers to 0042 and root it or should I go through the whole process again?
Click to expand...
Click to collapse
I do not believe it is possible; however, I've never attempted it, I've always done the complete process on each tablet I've rooted, so I could be wrong. Condi would be the best person to answer your question, but he appears to be MIA right now, probably because of the recent birth of his daughter.
If each tablet uses the same nbx number, then yes, you can share.
Sent from my DROID RAZR using Tapatalk 2
bart77 said:
If each tablet uses the same nbx number, then yes, you can share.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
But will still have to use AIO process as I believe it tricks the tablet into disabling the signature check or tricking it somehow. If you were to just use the rooted ICS update it would fail due to an error about 'the whole signature did not match'. Otherwise we could decrypt the update add root and part sign etc and the flash that file over a unrootable tab.
Stifilz
Cat McGowan said:
…
Booted into recovery mode.
From recovery screen, selected Reset to factory settings.
From next screen, selected Yes -- delete all user data.
Allowed reset to complete.
…
Click to expand...
Click to collapse
Noob question: why do you have to reset to factory settings? What does it do?
Thx
olivierkes said:
Noob question: why do you have to reset to factory settings? What does it do?
Thx
Click to expand...
Click to collapse
But a good question, eh?
You do not have to reset to factory settings, but doing it clears out residual data and settings from previous installs, thereby creating a clean (but rooted) install.
Keep in mind that in my original post, I am not telling you what to do; instead, I am telling you what I did.
It's too late now but are you saying that I could of used the latest update to root my tablet running ics?
Vinny1967 said:
It's too late now but are you saying that I could of used the latest update to root my tablet running ics?
Click to expand...
Click to collapse
If your tablet's previous ICS (or HC) was already rooted, then yes, you could have rooted the ICS 4.0.3r1a update. Otherwise, no.
Hi all,
I am using AiO 5.2 and I have the following configuration:
SGPT111CH/S
Android version 4.0.3 (release1a)
Kernel 2.6.39.4 [email protected] #1
Build number TISU0R0150110
Recovery .30<3e>
When trying to root using AiO I get both permissions check and the VpnFaker injection successful but the script fails 3 times at the terminal phase.
I've tried wiping, factory reset but nothing works.
I also have a problem with the update decryption. When I launch it I get a build error and a Status 7 and it doesn't go any further. If at the recovery menu I try to launch the install.zip file it fails too.
At this point I am completely lost, I must say that I'm also a little confused. Is my hardware/software combination a problem ? Is the script not working for this device ? I'm more than willing to try any manipulations you want
Cheers,
Serge
bhillou said:
Hi all,
I am using AiO 5.2 and I have the following configuration:
SGPT111CH/S
Android version 4.0.3 (release1a)
Kernel 2.6.39.4 [email protected] #1
Build number TISU0R0150110
Recovery .30<3e>
When trying to root using AiO I get both permissions check and the VpnFaker injection successful but the script fails 3 times at the terminal phase.
I've tried wiping, factory reset but nothing works.
I also have a problem with the update decryption. When I launch it I get a build error and a Status 7 and it doesn't go any further. If at the recovery menu I try to launch the install.zip file it fails too.
At this point I am completely lost, I must say that I'm also a little confused. Is my hardware/software combination a problem ? Is the script not working for this device ? I'm more than willing to try any manipulations you want
Cheers,
Serge
Click to expand...
Click to collapse
1) root - you have to keep on trying...
2) update decryption - you have to be rooted already! - back to 1) !
condi said:
1) root - you have to keep on trying...
2) update decryption - you have to be rooted already! - back to 1) !
Click to expand...
Click to collapse
Hi condi,
Thanks for your reply. Despite many attemps I didn't manage to use version 5.2 to root the tablet, but then I tried this method :
http://forum.xda-developers.com/showthread.php?t=1886460
And use the script there and despite a few errors this worked. I then used your script to "root" again since I noticed that the script I used didn't seem to install busybox and I was concerned it wouldn't be compatible with the environment you setup.
For the update decryption, I had previously rooted the tablet with the manual root procedure and despite that it didn't work. I'll try again now that I have root on the tablet after a full wipe.
Best regards,
Serge Huber
bhillou said:
Hi condi,
Thanks for your reply. Despite many attemps I didn't manage to use version 5.2 to root the tablet, but then I tried this method :
http://forum.xda-developers.com/showthread.php?t=1886460
And use the script there and despite a few errors this worked. I then used your script to "root" again since I noticed that the script I used didn't seem to install busybox and I was concerned it wouldn't be compatible with the environment you setup.
For the update decryption, I had previously rooted the tablet with the manual root procedure and despite that it didn't work. I'll try again now that I have root on the tablet after a full wipe.
Best regards,
Serge Huber
Click to expand...
Click to collapse
Ok after looking at the script I noticed you were waiting for the recovery device. That's when I noticed that my recovery driver was not properly installed. Installing it solve the problem and I got shell access to the recovery !
Maybe this was also causing the issue with the rooting ? Is that possible ?
Best regards,
Serge Huber
Ok I managed to create a custom update but when I try to flash it with AiO everything seems to work fine until the reboot where it just gets stuck on the Sony logo. If I stop the tablet by pressing over 10 seconds on the power button and start it again I get back into my normal system. I also tried your custom prerooted ROM but the same thing happened. Any clues as to what is wrong ?
Cheers and again thanks for all the help,
Serge