Hey all,
I posted this in wolf's thread as well as the thread here but not have not fixed yet so I thought I would post this problem in it's own thread.
I successfully downgraded my prime using the tool (batch file) to .15 with a US blob for my (what was) US .21 prime. I rooted with the tool and then voodoo OTA and protected root.
The prime sees the OTA to .21 and downloads it. Asks me to install it. When I say OK it boots into the android guy with the spinning wire mesh. The progress bar makes it up to around %25 and the android guy falls on his back and theres a triangle with a "!" in his open stomach. It sits there for 1 maybe 2 minutes and reboots back into .15 saying there was an error and I've been reverted back to .15.
In searching, I found a thread that detailed some steps that might prevent an update from installing. It started out by looking at the log located in /cache/ to find out what the problem is and fix it. However, my /cache/ folder is empty with no sub-folders.
I've been told it may be my build.prop. I don't think I have added or changed anything in it without changing it right back to the way it was. I change the model and manufacturer once to see if I could get a game from google play but changed them back to exactly what they were (including case).
Would anyone care to link me to a trustworthy .15 build.prop (trustworthy so I dont brick my device putting someone's practical joke in as build.prop). If thats the problem that might fix it.
I have a TB backup so if a complete wipe and factory reset is in order I'm up for that but not even sure how to go about that with the TFP. But I hope theres an easier way if anyone knows one. Would love to get back on the update path and also use the GPS dongle that came in yesterday.
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
buxtahuda said:
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
Click to expand...
Click to collapse
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Shinare said:
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Lol, yes, in the reply menu. Good stuff, glad it's worked out! I may edit this last post with a public link to the unmodified build.prop in my DB account, we'll see
*EDIT:
Just for other's reference if they face similar issues. Also never hurts to have yet another unmodified build.prop somewhere on the web lol
buxtahuda said:
Shinare said:
buxtahuda said:
Kind of forgot about you I know, I'm terrible lol
Install root explorer and again try to look at your /cache/recovery directory. Pretty sure you must have root access to see it, and root explorer will attempt to get just that when you start it the first time.
Let me know if this gets it so you can look at the recovery logs, if not then I hope more people have a look at your thread.
Click to expand...
Click to collapse
There are logs in there! Can u take a look and let me know?
Thank You!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Ok, yeah, build.prop is definitely your problem.
Code:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
I have a backup of my build.prop from .21, I'll get it to you and we'll see if that won't do the trick. If not, we'll have to take to the forums and hope some others will have a good build.prop or actual explanation for the issue.
http://db.tt/0tDq7Sih
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
Click to expand...
Click to collapse
no FOTA
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
Have you tried locating your DMClient in your apps and clearing its data/cache? Try that and see if maybe blob'ing between regions didn't just discombobulate it. The build.prop wouldn't help you there I don't think. I hate to say it, but try a factory reset?
hi
Have you tried locating your DMClient in your apps and clearing its data/cache?
Click to expand...
Click to collapse
yes. no efect
but try a factory reset?
Click to expand...
Click to collapse
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
MrCat226 said:
yes. no efect
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
Click to expand...
Click to collapse
Hmm. I haven't had a chance to collect all the different dlpkgfile files yet, I'm setting off on that adventure soon so hopefully I may run into your issue while I install all the different blobs.
I really don't know at this point. Have you also tried this route?
hi
now traing)
but 1 thing
Once downloaded, extract the zip. Inside, there's another file file.
Rename this one into EP201_SDUPDATE.zip and put it in the root of a microSD card.
Put the microSD card into the tf201.
Click to expand...
Click to collapse
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
MrCat226 said:
now traing)
but 1 thing
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
Click to expand...
Click to collapse
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
buxtahuda said:
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Click to expand...
Click to collapse
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
MrCat226 said:
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
Click to expand...
Click to collapse
Yes, when your Prime detects an update it downloads dlpkgfile to your /cache/ directory, and upon reboot updates the Prime. So putting a .21 WW dlpkgfile in your cache directory should update you to .21 WW.
The last one I linked to involving the UPDATE.zip has you manually update your Prime from recovery, as a last resort kind of thing and should work.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
i tried this. it dont see the update
after this trick in the cache folder i found 2 new files "last_log" "last_install"
No OTA after motherboard replacement
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
There is another post having a very similar complaint in:
http://forum.xda-developers.com/showpost.php?p=25890334&postcount=258
I have an extremely similar issue, that is:
Bought a TF201 on March 2012, updated OTA (several times) up to ICS .21
Sent to the local (Israel) lab complaining for WIFI and GPS issues.
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
I cannot say I feel any improvement with the WIFI or the GPS.
(BTW, the GPS dongle arrived a day after and that one makes miracles!
But only on .21! Furthermore, it is rather big [has the length of the TF201] so I guess I will not carry it with me daily)
Tried the wolf downgrade (US .15) - works fine.
Wiped as suggested on his page.
No OTA!
(rooted or unrooted)
Tried WW .15 and US .14 as well.
No OTA.
Waited over 24h (as suggested in some webpages).
Found the ratchet solution for S/N fixing - still no OTA (neither on WW nor US .15) - all wiped as well (long vol-down press while turning on + 2 x vol-up presses while wipe is flashing).
I've been through 3 factory resets in a row (As suggested in some sites) - both on .15 as well as .21
I'm just about to contact the seller and ask for a replacement (but I really don't feel like it).
I hope a solution is found in the next couple of days as I'm afraid I will have to deal with the seller by Sunday otherwise.
hi
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
Click to expand...
Click to collapse
Exactly the same problem!
BUT i put back the S/N(ratchet) witch no efect(
That sucks. Can't believe they're so sloppy they can't even make an annotation in the paperwork what firmware you were already on and give it back how they received it.
I'll keep looking around, but it's likely going to take someone more ingenious than I to come up with a solution since you're getting the SN Unknown issue. Does ASUS not even have properly working NVflash?
Related
As I sit here at work my mind start to think. There is a host file on the Nook Color that is used just as the host file on a Windows machine is used. The Nook Color can auto update itself with out knowledge of the user. Why not monitor the ip address the Nook Color downloads the Side Loader update zip file from and block that address in the host file? That is better then renaming the OTACert file and if the site isn't found by the device the device will not try and update its self.
I thought of it now one of you go figure it out....here is what you have to do;
1. Make sure your on 1.0.0 firmware on the B&N Nook
2. Run Monitoring program on your router to see incoming data and what IP's are being utilized.
3. Run WIFI on Nook
4. Look for new data (side loader being downloaded from B&N)
5. Block that IP address in the hosts file
6. Reboot nook and see if it still tries to update its self.
Post back results.
2nd Idea:
I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access rights through adb or root explorer.
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
mtl171 said:
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
Click to expand...
Click to collapse
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
xboxexpert said:
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
Click to expand...
Click to collapse
Aparently you can not chmod anything in /media folder
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
wvcachi said:
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
Click to expand...
Click to collapse
That works good but what if i wanted to stay on 1.0.1 with out updating...
How come some people get the auto update and some don't? I've been on 1.0 since before Christmas and haven't been forced into an update. I've even been sitting in B&N for hours at a time.
xboxexpert said:
That works good but what if i wanted to stay on 1.0.1 with out updating...
Click to expand...
Click to collapse
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
wvcachi said:
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
Click to expand...
Click to collapse
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
xboxexpert said:
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
Click to expand...
Click to collapse
It looks like that was based on one post that the poster later attributed to something else (read thread http://forum.xda-developers.com/showthread.php?p=10390633#post10390633).
So I see no reason not to disable otacerts on any firmware right now.
Hello everybody
I need a little help to a friend of mine who mistakenly deleted systemui.apk from the system using root permissions on his Transformer Prime
Now the system doesn't boot up, it gets stuck when reaches the ASUS mark.
So if anyone can show me a way to get back to the stock firmware, that'd be much appreciated. The device is rooted.
I've Searched the forums for a solution but found nothing that directly gives me a solution
Thank you.
if you plug it into the cpu does it come up?
I have a similar problem that I just posted. I renamed my /system/bin folder by accident and I'm stuck on Eee Pad screen too. Been looking and trying data wipe, n reset, nothing so far. Need to know if there is a way to access the file system b/c all I have to do is change the name of a damn folder. Sounds like you just need to copy n paste the missing file too.
This will require setting up your computer - drivers & ADB environment - and pushing some commands to your tablet that way ... I would think. Since we have no unlocked bootloader you can't boot into recovery.
Yeah, you're going to have to adb push the systemui.apk to /system/app
But that's only is you can even get adb to recognize your device while it's in the bootloop.... When I pushed my de-odexed framework folder and rebooted, I got stuck in endless bootloop, and the device wouldn't get to the point where adb would be able to see my device, therefore I couldn't push anything.
Also tired to put the ASUS recovery blob .13 .zip file on my micro sd card (since I couldn't access my main /sdcard on the Prime... that still didn't work... Long story short, Amazon is replacing my Prime, b/c it just stopped working ... now I just have to wait 4-6 weeks until they get new ones in stock (hopefully they get them sooner than that).
So Can any one of you guys get me these two filse from his Transformer prime
systemui.apk
systemui.opex
At least it is worth the try.
Replacing the Tablet is not an option because the guy shipped his tablet to another country it would be very painful to try to send it back to amazon.
Hi everyone, I accidentally my systemui.apk. Is this safe?
Loljk, you should be able to get it working i hope.
Sent from my tablet thing with XDA Premium.
jdeoxys said:
Hi everyone, I accidentally my systemui.apk. Is this safe?
Loljk, you should be able to get it working i hope.
Sent from my tablet thing with XDA Premium.
Click to expand...
Click to collapse
I am sorry i don't quite get what you mean ?
DELETED SymstemUI for ASUS Memopad 8
Hi,
I DELETED SymstemUI for ASUS Memopad 8 but I was able to save a backup in the external MicroSD card of my tab. Is there anyway that I can push this back to the system?
I'm still a noob and I am hoping that there's anyone who can help me.
I have not seen it posted here but wolf849 has put together a guide to downgrade so you can downgrade, root then upgrade to .21 all without the need for root access or unlocking.
I linked below
http://forum.xda-developers.com/showthread.php?t=1622628
Thanks! I stupidly updated to .21 right away when I first got my prime and regretted it ever since. Finally I can get some use out of this!
Man this is GREAT news.
Even a noob like me has down graded from .21 down to .15
Used Vipor Mod to reroot - Thank you Vipor Boy
Intalled OTA Rootkeeper and backed up my root
reinstalled the .21 updated
restored root!!!!
Thank You Wolf
Can a TF201 owner confirm?
Thanks.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed !!!!!
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed, I just finished.
Wooooooooot!!!! This is awesome.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed also.
Useless post was useless. figured it out. plz delete this post.
It worked! Downgraded to .15 from .21 and have now managed to install SuperUser and SU binary. Waiting for OTA Rootkeeper to install before upgrading to .21 again.
Finally I can fix some of the bugs that I've had to put up with due to Asus' incompetence, such as the bad I/O performance and shocking web browser performance.
Awesome, I've been looking for a solution for a good while. I'm glad this is confirmed. Hopefully someone will update the reference guide to link it to wolf's guide!
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
put the blob in the root directory of your internal sd.
I extrated the blob from the US version .15.
don't us .21 that is what you have installed now and that one can not be rooted
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Mekrel said:
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Click to expand...
Click to collapse
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Replying to see where this goes, not going to be a beta tester for it though.
kageebe said:
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Click to expand...
Click to collapse
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Mekrel said:
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
Click to expand...
Click to collapse
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
robertg9 said:
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Click to expand...
Click to collapse
ADB is a tool that comes with the Android SDK, so you need to install the SDK onto your laptop and install the SDK Tools and Platform Tools. Then edit your path variable so that your command line know's where to find the adb executable. You might also have to install Java development kit, I'm not sure if the Android SDK manager moans if you don't have it installed.
There's easier ways of using ADB, by just downloading the .dll and .exe and referencing them via command line but I always recommend having a full SDK tool install and learning about ADB as it's a god send.
kageebe said:
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
Click to expand...
Click to collapse
Like I said, go to "About Tablet" in your tablet settings and there's something called a "Build Number". Mine says IML74K.WW_epad-9.4.2.21-20120323 - the initials stipulate which region firmware you have, in my case "WW" aka World Wide.
If anyone can locate a US blob please let me know, I've been searching on the forums for a .15 US blob to no avail and no luck at all.
Hi, I am newly registered user here who bought a 32GB Tablet S on the Woot deal the other day, long story short there is a question about the configuration of the Woot deal tablets over in the developer section, but since I am a new user with less than 10 messages posted, I can't answer there, so I am answering here in hopes someone will point them to this message, and it may be helpful for others:
About Tablet reads:
Android Version 3.2
Kernel version 2.6.36.3 [email protected]#1
Build number 1.10.001100001
On a side point I would like to ask if these are rootable from 3.2? and should I upgrade to 4.03, I have read some on lack of root access on these devices?
thanks
p.s. I am fairly new to Android, have a version 2.2 phone, but have been running Linux as my primary OS for over a decade
Isaac-1 said:
Hi, I am newly registered user here who bought a 32GB Tablet S on the Woot deal the other day, long story short there is a question about the configuration of the Woot deal tablets over in the developer section, but since I am a new user with less than 10 messages posted, I can't answer there, so I am answering here in hopes someone will point them to this message, and it may be helpful for others:
About Tablet reads:
Android Version 3.2
Kernel version 2.6.36.3 [email protected]#1
Build number 1.10.001100001
On a side point I would like to ask if these are rootable from 3.2? and should I upgrade to 4.03, I have read some on lack of root access on these devices?
thanks
p.s. I am fairly new to Android, have a version 2.2 phone, but have been running Linux as my primary OS for over a decade
Click to expand...
Click to collapse
Hey. Thanks I thknk that was me. I don't have min.e yet but I think from reading alone that you can pull a zip from an early ics build and root it using condi's aio method. Don't quote me... I also think that you cannot root it out of the box.. but ics should hav e a new kernel.
As a linux dude maybe you can help out with the dev on these things.... it seems to be needed.
I would wait for someone in the know about this process to answer.
Thanks...I really hbope I can root it. Custom roms would be nice but a root is almost a requirement for me.
Thanks agaain for the reply
Sent from my SPH-D700 using xda app-developers app
Isaac-1 said:
Hi, I am newly registered user here who bought a 32GB Tablet S on the Woot deal the other day, long story short there is a question about the configuration of the Woot deal tablets over in the developer section, but since I am a new user with less than 10 messages posted, I can't answer there, so I am answering here in hopes someone will point them to this message, and it may be helpful for others:
About Tablet reads:
Android Version 3.2
Kernel version 2.6.36.3 [email protected]#1
Build number 1.10.001100001
On a side point I would like to ask if these are rootable from 3.2? and should I upgrade to 4.03, I have read some on lack of root access on these devices?
thanks
p.s. I am fairly new to Android, have a version 2.2 phone, but have been running Linux as my primary OS for over a decade
Click to expand...
Click to collapse
The kernel being build 10 will probably cause a failure trying to root the 3.2 directly to 4.0.3. First, run Condi's All-in-One tool (use AiO v4.0, I believe v4.1 has a bug that Condi needs to fix) to pre-root and install a version of 3.2.1r2 with a kernel build that is less than 10 like THIS ONE or THIS ONE. Then run Condi's All-in-One tool again to pre-root and install version 4.0.3r1a. Remember to take your time and read slowly, carefully, and completely before using the AiO tool. Good luck. BTW, I also bought the same Woot deal (my second Sony Tablet S). It is scheduled to arrive Monday and I will be doing the same pre-root and install.
Thanks, by chance do you know if there is a step by step howto on the condi All-in-One tool that is not full of insider only alphabet soup acronyms, I think I get the concepts, but I also know messing up can create a fairly expensive paperwieght. I have googled a few sets of instructions, but they seem to all inlcude steps like before running AIO make sure your ABC or XYZ is up to date, this may be fine for people that have done this a dozen times, but for those of us going down this road for the first time we have no idea of what an ABC or XYZ is, or even what it stands for, much less how to find out if they are up to date. It also seems most of these instructions take steps for granted, saying things like "copy file onto an SD" with no further explanation, such as must it be an SD card or will SDHC work, is file name or directory structure important, etc. I am not so much looking for handholding here as just some confirmation that my assumptions may be right, even such things as if these tools should be downloaded onto a computer running windows or onto the Tablet itself. With the woot sale I suspect that there will be many more people here soon with these sorts of questions, and many will be completely clueless, at least I do have 25+ years of running Unix like operating systems, and have been using Linux as my primary OS since the 2.0 kernel days, and to tell the truth am rather lost in all these messages full of acronyms and short hand descriptions.
Ike
Isaac-1 said:
Thanks, by chance do you know if there is a step by step howto on the condi All-in-One tool that is not full of insider only alphabet soup acronyms, I think I get the concepts, but I also know messing up can create a fairly expensive paperwieght. I have googled a few sets of instructions, but they seem to all inlcude steps like before running AIO make sure your ABC or XYZ is up to date, this may be fine for people that have done this a dozen times, but for those of us going down this road for the first time we have no idea of what an ABC or XYZ is, or even what it stands for, much less how to find out if they are up to date. It also seems most of these instructions take steps for granted, saying things like "copy file onto an SD" with no further explanation, such as must it be an SD card or will SDHC work, is file name or directory structure important, etc. I am not so much looking for handholding here as just some confirmation that my assumptions may be right, even such things as if these tools should be downloaded onto a computer running windows or onto the Tablet itself. With the woot sale I suspect that there will be many more people here soon with these sorts of questions, and many will be completely clueless, at least I do have 25+ years of running Unix like operating systems, and have been using Linux as my primary OS since the 2.0 kernel days, and to tell the truth am rather lost in all these messages full of acronyms and short hand descriptions. Ike
Click to expand...
Click to collapse
In the thread that covers Condi's All-in-One tool, what you see is what you get. But to get a good gest of how to root the Sony Tablet S, I recommend you watch BluechipJ's VIDEO and read TheHurf's POST, which is the post BluechipJ was following in his video. I also recommend you watch the video and read the post several times before you actually attempt performing the root. Please note that the video and post are based on using All-in-One v2.7. Regarding "SD", a standard SD or SDHC card can be used, but it must be formatted FAT32. I used a SanDisk 32 GB SDHC card. Again, good luck.
Thanks, I found the videos last night, but not the message threads they were refering too. Together I am sure they will be most helpful
So I read the posts referenced earlier on, and I watched the video, but both start from a rootable ROM already on the tablet. Since the Woot ones come with 3.2 with the un-rootable kernel 10, I'm not sure how to do the intermediate step of getting the rootable 3.2.1 version on there?
The tablet is offering me an OTA update, but it says it's for 4.0.3 - it doesn't seem to give an option to go to an earlier version first. Does this mean that we're boned on these ones, or is there another way to get a rootable version on first?
It looks like the ALLinONE tool can't do anything for us unless we either root the tablet or make it rootable - am I missing something or looking at something the wrong way?
dmahon said:
So I read the posts referenced earlier on, and I watched the video, but both start from a rootable ROM already on the tablet. Since the Woot ones come with 3.2 with the un-rootable kernel 10, I'm not sure how to do the intermediate step of getting the rootable 3.2.1 version on there? The tablet is offering me an OTA update, but it says it's for 4.0.3 - it doesn't seem to give an option to go to an earlier version first. Does this mean that we're boned on these ones, or is there another way to get a rootable version on first? It looks like the ALLinONE tool can't do anything for us unless we either root the tablet or make it rootable - am I missing something or looking at something the wrong way?
Click to expand...
Click to collapse
If you want to have root access on your tablet, DO NOT ALLOW THE TABLET TO PERFORM AN OTA UPDATE.
First, download the 3.2.1r2 and 4.0.3r1a files from the previously given links and store them on your computer. Next, download and install on your computer Condi's All-in-One tool. The most popular versions seem to be 2.7, 3.4, and 4.0. The previously mentioned video and post are based on version 2.7.
Now manually update the 3.2 to 3.2.1r2; don't not attempt to root it yet. Just copy the 3.2.1r2 file to a SD card (formatted FAT32) and install the card in your tablet. Power off (not sleep mode) your tablet. Power on your tablet into recovery mode by continuously holding down the VOL+ button and momentarily pressing the POWER button. Release the VOL+ button after you see the recovery mode logo. From the recovery mode's menu, select 2 Update system from SD card. (VOL+ and VOL- buttons are used to navigate the menu, POWER button is used to select the highlighted selection.) From the next menu, choose and select the 3.2.1r2 file. Allow the manual update to complete.
After your tablet has been updated to 3.2.1r2, leave the copied 3.2.1r2 file on the SD card and use Condi's All-in-One tool to root and reinstall 3.2.1r2 by following the directions given in the previously mentioned video and post.
Finally, after 3.2.1r2 is rooted and installed, delete the 3.2.1r2 file from the SD card and copy the 4.0.3r1a file to the SD Card. Again use Condi's All-in-One tool to root and install 4.0.3r1a by again following the directions given in the previously mentioned video and post.
To summarize: first update 3.2 to 3.2.1r2, then root and reinstall 3.2.1r2, then lastly root and install 4.0.3r1a. Good luck.
Thanks! It was late last night, and I must have been in the wrong headspace to be trying this, because I woke up in the middle of the night and thought "Oh, I bet I have to put it in recovery and flash that file..."
After that, everything went pretty smoothly along, just as everyone said. A couple places where the process varied from what the ALLinONE tool seemed to expect (the _hack_recovery.zip file doesn't get pushed, or rather gets pushed as "install.zip," which I guess is supposed to make it auto-flash when you enter recovery, but on mine it didn't, so I copied _hack_recovery.zip over manually and ran it with the same results). Otherwise very smooth. Everything looks great.
Thanks!
Cat: your link above with the 3 files (THIS,THIS and version 4.0.3r1a) to donwload, seems to have an issue, specifically the link to version 4.0.3r1a goes to a file with the exact same name as one of the "THIS" files, maybe a different copy of the same file as the link is different. Before making a major mistake I wanted to confirm that "this" is correct.
Ike
p.s. one more detail, should the zip files be copied to the SD card still zipped, or should they be unzipped to the SD?
Isaac-1 said:
Cat: your link above with the 3 files (THIS,THIS and version 4.0.3r1a) to donwload, seems to have an issue, specifically the link to version 4.0.3r1a goes to a file with the exact same name as one of the "THIS" files, maybe a different copy of the same file as the link is different. Before making a major mistake I wanted to confirm that "this" is correct.
Ike
p.s. one more detail, should the zip files be copied to the SD card still zipped, or should they be unzipped to the SD?
Click to expand...
Click to collapse
I checked all the links. They are correct.
The first THIS ONE and the second THIS ONE are links to the same file stored at two different locations; that is why I wrote "or". Both files are signed-nbx03_001-ota-0042.001.zip, which is a rootable version of 3.2.1r2. The first was uploaded to 4shared by Condi, the second was uploaded to 4shared by me. I provided both links just in case one of us decides to delete our upload. After all, the files are eating up our allotted 4shared storage space, eh?
The link for the 4.0.3r1a file signed-nbx03_001-ota-120803002.zip links directly to Sony's servers.
The zip files are to be used as is. Do not unzip them. They are encrypted and signed files. If you attempt to unzip them using programs like 7zip or WinRAR, you will receive error messages saying the files are corrupted even though they are not corrupted.
Isaac-1 said:
Cat: your link above with the 3 files (THIS,THIS and version 4.0.3r1a) to donwload, seems to have an issue, specifically the link to version 4.0.3r1a goes to a file with the exact same name as one of the "THIS" files, maybe a different copy of the same file as the link is different. Before making a major mistake I wanted to confirm that "this" is correct.
Ike
p.s. one more detail, should the zip files be copied to the SD card still zipped, or should they be unzipped to the SD?
Click to expand...
Click to collapse
Brand new FAQ here will answer your question. You will prob need to flash 0035 then 0042 as you are 11000. Please refer to FAQ. It works.
Stifilz
stifilz said:
Brand new FAQ here will answer your question. You will prob need to flash 0035 then 0042 as you are 11000. Please refer to FAQ. It works.
Stifilz
Click to expand...
Click to collapse
Thank you for posting a much need FAQ.
A couple of hours ago, FedEx delivered my (second) Sony Tablet S from Woot. It is a model SGPT112US/S. About tablet says Android version 3.2, Kernel version 2.6.36.3 [email protected] #1, Build number 1.10.001100001.
Above, you state 11000 (I assume you mean Build number 1.10.001100001) must be updated to 0035 (version 3.2 file signed-nbx03_001-ota-0035.001.zip) before updating to 0042 (version 3.2.1r2 file signed-nbx03_001-ota-0042.001.zip). I am curious, please explain why 11000 cannot be directly updated to 0042? Why the need for the intermediate 0035 update?
Like i said in an ealier post, I planned on updating 3.2 to 3.2.1r2, then rooting and reinstalling 3.2.1r2, then rooting and installing 4.0.3r1a. Is my plan with error? Am I wrongly advising others to do the same?
Cat McGowan said:
Thank you for posting a much need FAQ.
A couple of hours ago, FedEx delivered my (second) Sony Tablet S from Woot. It is a model SGPT112US/S. About tablet says Android version 3.2, Kernel version 2.6.36.3 [email protected] #1, Build number 1.10.001100001.
Above, you state 11000 (I assume you mean Build number 1.10.001100001) must be updated to 0035 (version 3.2 file signed-nbx03_001-ota-0035.001.zip) before updating to 0042 (version 3.2.1r2 file signed-nbx03_001-ota-0042.001.zip). I am curious, please explain why 11000 cannot be directly updated to 0042? Why the need for the intermediate 0035 update?
Like i said in an ealier post, I planned on updating 3.2 to 3.2.1r2, then rooting and reinstalling 3.2.1r2, then rooting and installing 4.0.3r1a. Is my plan with error? Am I wrongly advising others to do the same?
Click to expand...
Click to collapse
Not too sure with US but have had a user woth Mexico and had to install 0035 3.2.1 before 0042 3.2.1r2 as installation would abort. If it works without 0035 than thats awesome but atleast the way I described It will 100% work :fingers-crossed:
I assume it must be done this way because 0035 is 3.2.1 and 0042 is 3.2.1R2???
Check thread below posts 60 thorugh to 69.
http://forum.xda-developers.com/showthread.php?t=1687429&page=7
Thanks
Stifilz
stifilz said:
Not too sure with US but have had a user woth Mexico and had to install 0035 3.2.1 before 0042 3.2.1r2 as installation would abort. If it works without 0035 than thats awesome but atleast the way I described It will 100% work :fingers-crossed:
I assume it must be done this way because 0035 is 3.2.1 and 0042 is 3.2.1R2???
Check thread below posts 60 thorugh to 69.
http://forum.xda-developers.com/showthread.php?t=1687429&page=7
Thanks
Stifilz
Click to expand...
Click to collapse
No, thank you! I will change my plan to first updating with 3.2.1 file signed-nbx03_001-ota-0035.001.zip.
Cat McGowan said:
No, thank you! I will change my plan to first updating with 3.2.1 file signed-nbx03_001-ota-0035.001.zip.
Click to expand...
Click to collapse
OK........ WTF?? I was meaning if you wanted proof for the reason I suggest this method (0035 > 0042) then look at that thread. I was not implying you were a noob and needed to follow a step-by-step.
Stifilz
stifilz said:
OK........ WTF?? I was meaning if you wanted proof for the reason I suggest this method (0035 > 0042) then look at that thread. I was not implying you were a noob and needed to follow a step-by-step.
Stifilz
Click to expand...
Click to collapse
You seem to have misunderstood my reply to you. You said "Thank you" to me and I replied "No, thank you!" to you meaning that no, you should not be thanking me; instead, I should be thanking you. I hope I have cleared up the confusion.
Cat McGowan said:
You seem to have misunderstood my reply to you. You said "Thank you" to me and I replied "No, thank you!" to you meaning that no, you should not be thanking me; instead, I should be thanking you. I hope I have cleared up the confusion.
Click to expand...
Click to collapse
LOL, I get it now. Haha gotta love forum confusion . Anyway you may have been right aswell, over on FAQ thread, a US user managed to get by without flashing the 0035 inbetween....... Yet the Mexican region's update needed the 0035 inbetween. But I guess there is only 1 way to find out......
Stifilz
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Faznx92 said:
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Click to expand...
Click to collapse
If you put the 13.3.2.2 .bin file in the /storage partition of the kindle you can then swipe down to settings -> device -> software updates and it will be there. Then click update. If you switch on the internet and it will automatically do things for you, and rebooting and all that. I think that should answer your question.
ferrouskid said:
If you put the 13.3.2.2 .bin file in the /storage partition of the kindle you can then swipe down to settings -> device -> software updates and it will be there. Then click update. If you switch on the internet and it will automatically do things for you, and rebooting and all that. I think that should answer your question.
Click to expand...
Click to collapse
I know about manual updating and over the air updating (which I'll never use). I'm looking for a sure answer, is each update bin the full system update or is it upgraded in update steps (ex. On 13.3.1.0 --> 13.3.2.0 --> to upgrade to 13.3.3.0)? I think the bin file holds the full updated system but I'm not quite sure.
Faznx92 said:
I know about manual updating and over the air updating (which I'll never use). I'm looking for a sure answer, is each update bin the full system update or is it upgraded in update steps (ex. On 13.3.1.0 --> 13.3.2.0 --> to upgrade to 13.3.3.0)? I think the bin file holds the full updated system but I'm not quite sure.
Click to expand...
Click to collapse
I have opened one up before with 7zip archive manager, seemed to have absolutely everything, including all the preloaded apps (Silk, Camera & etc.). Based on that I made a little hunch, that the build.prop is the key to the update.I got it modified and put together back into a .bin, the kindle DID recognise it as an update but it failed to validate. Now I think that is because I didn't get it signed, and after some reasearch I found the Dalvik VM signature and and try to sign the "update" with that. If that fails, then I would like to use binwalk -a linux tool that allows people to analyse .bin files. With that I want to get the file signature from the new update- sign the 13.3.1 with that sginature and "update". I will attempt live booting ubuntu or something- and then use binwalk, but I'll try and see how it goes. Im telling you about this because I think that if I were to make a new thread Amazon would patch that sort of stuff.
I hope this might work- cuz if it does no waiting for ninety days, right?
If it works.
Which it might.
Faznx92 said:
I'm on 13.3.1.0. But if I want to update to 13.3.2.2, do I need to update in order up to 13.3.2.2 or just update with the 13.3.2.2 bin?
I not a 100% sure but I want a correct answer.
Click to expand...
Click to collapse
Just update to 13.3.2.2. The only differences between 13.3.2.1 and 13.3.2.2 are mainly with WhisperLink and WhisperPlay to support the release of Amazon's fireTV:
http://forum.xda-developers.com/showpost.php?p=51487613&postcount=12
FYI.