I rooted my UK tablet using the AiO tool, with the US version of ICS.
Now we have this update I'm unsure how to proceed. I'd like to update using the UK version.
So can someone point me in the right direction, I don't want to lose root.
blackadder666 said:
I rooted my UK tablet using the AiO tool, with the US version of ICS.
Now we have this update I'm unsure how to proceed. I'd like to update using the UK version.
So can someone point me in the right direction, I don't want to lose root.
Click to expand...
Click to collapse
Ok so you are currently US ICS???
Use region changer in AIO to change back to UK.
Then use AIO to preroot this:
UK
4.0.3 R1A WIFI ONLY
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
OR This
4.0.3 R1A WIFI + 3G
http://info.update.sony.net/ST003/nbx03_004/contents/0012/signed-nbx03_004-ota-120803061.zip
And install following instructions from AIO thread. If you do it right you will have new UK 4.0.3 R1A with root access.
Chur
Stifilz
stifilz said:
Ok so you are currently US ICS???
Use region changer in AIO to change back to UK.
Then use AIO to preroot this:
UK
And install following instructions from AIO thread. If you do it right you will have new UK 4.0.3 R1A with root access.
Chur
Stifilz
Click to expand...
Click to collapse
Right, having a problem with this. Changed the region to UK, seemed to work fine, tablet rebooted
Put the zip file (wifi only version) onto the SD card and ran the AiO tool. It went through some processes, it did say that the region needed to be changed. The tablet then shut down (didn't reboot) and the AiO tool closed. And that was that.
So what am I missing out here. Any help much appreciated
blackadder666 said:
Right, having a problem with this. Changed the region to UK, seemed to work fine, tablet rebooted
Put the zip file (wifi only version) onto the SD card and ran the AiO tool. It went through some processes, it did say that the region needed to be changed. The tablet then shut down (didn't reboot) and the AiO tool closed. And that was that.
So what am I missing out here. Any help much appreciated
Click to expand...
Click to collapse
Oh yeh v4.1 bit buggy like that. Try using v4.0 or even v3.4. You will need to turn updates off. It tells you when you open AIO so open v4.1 to read how to disable updates.
Good luck
Stifilz
Me again
Tried v3.4 and 4.0. First figured out how to stop it wanting to update.
V3.4 didn't seem to work, but v4.0 did at first. Went into menu 3 and chose option 1. This went through some processes and then to reboot into recovery mode. So far okay. Then installation failed (as it says on the AiO tool) but then the tool stops with 3 dots at the bottom. It offers no further instructions. The tablet asks whether to cancel and reboot or install from SD card.
So stuck again.
I tried watching the videos but for some reason I don't get any sound
Any other assistance would be appreciated and thanks so far.
An update if anyone can still help
When the tool creates the hack recovery file it seems to report some errors, something about not being able to verify googlegroups.com certificate but carries on. It then says it's pushing this file to the SD card and ask for the tablet to be rebooted into recovery mode. At this point the tools stops and goes no further.
I reboot into recovery it tries to install something but fails, so I go for the install from SD card but no hack recovery file there only an install.zip file. Reading the main discussion I see now that you install from this file. But it fails and I can go no further.
The main problem at this point is the AiO tool stop and hangs.
Currently trying v4, any ideas
Try using a newer adb version. It has helped others. Click faq link in signature adb 1.0.29.zip is attached there.
Stifilz
Sent from my GT-S5830 using xda app-developers app
blackadder666 said:
An update if anyone can still help
When the tool creates the hack recovery file it seems to report some errors, something about not being able to verify googlegroups.com certificate but carries on. It then says it's pushing this file to the SD card and ask for the tablet to be rebooted into recovery mode. At this point the tools stops and goes no further.
I reboot into recovery it tries to install something but fails, so I go for the install from SD card but no hack recovery file there only an install.zip file. Reading the main discussion I see now that you install from this file. But it fails and I can go no further.
The main problem at this point is the AiO tool stop and hangs.
Currently trying v4, any ideas
Click to expand...
Click to collapse
In decrypting the update file:
1-When asked to run _hack_recovery, run "install.zip". I guess there has been name confusions in all those updates.
2-"install.zip" will fail and then AiO will give you new directions. Now choose the firmware (signed-nbx03_001-ota-120803002.zip) or anything you have. You should copy it to SD card before the whole process.
Follow the instructions.
Another confusion in finally flashing the decrypted and signed update file:
When in recovery mode and AiO stops again,
1-run install.zip [it wouldn't fail], after this, AiO will simply tell you everything is done, delete or rename install.zip, and will exit. BUT NO ICS YET, and you're still in the recovery mode, on your own without further directions from AiO.
2-run _hack_recovery.zip [this one failed!!]
3-run the new install.zip [it was the old custom_updated_signed.zip]
Hope this helps.
jessicaat said:
In decrypting the update file:
1-When asked to run _hack_recovery, run "install.zip". I guess there has been name confusions in all those updates.
2-"install.zip" will fail and then AiO will give you new directions. Now choose the firmware (signed-nbx03_001-ota-120803002.zip) or anything you have. You should copy it to SD card before the whole process.
Follow the instructions.
Another confusion in finally flashing the decrypted and signed update file:
When in recovery mode and AiO stops again,
1-run install.zip [it wouldn't fail], after this, AiO will simply tell you everything is done, delete or rename install.zip, and will exit. BUT NO ICS YET, and you're still in the recovery mode, on your own without further directions from AiO.
2-run _hack_recovery.zip [this one failed!!]
3-run the new install.zip [it was the old custom_updated_signed.zip]
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to reply.
First I installed some new ADB files into the AiO tool 'files' folder and tried again
When the AiO tool asks to reboot into recovery mode I do that but the tool stops. I then ran the install.zip file and this fails (tablet stays in recovery) and the AiO tool does nothing further, just stops at the point telling me to reboot into recovery.
On your step 2 at the top, I run install.zip but get no new instructions from AiO
blackadder666 said:
Thanks for taking the time to reply.
First I installed some new ADB files into the AiO tool 'files' folder and tried again
When the AiO tool asks to reboot into recovery mode I do that but the tool stops. I then ran the install.zip file and this fails (tablet stays in recovery) and the AiO tool does nothing further, just stops at the point telling me to reboot into recovery.
On your step 2 at the top, I run install.zip but get no new instructions from AiO
Click to expand...
Click to collapse
hmmm... I vaguely remember in my case AiO said something like: now run the update, it is surely 100% safe, AiO won't allow anything to flash on your device, blah blah, and this was shown on the command window (not 100% sure here though). I used AiO v4.0, btw. Did you check other threads? I saw successful cases with different steps from what I went through. Good luck, anyway!
Related
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
Always be careful when updating a rooted device with any OTA updates. You are probably not likely to be able to update to 4.0.3R1A unless one of the developers on this forum mods the update package.
Spunky168
"Condi for president in 2012!!"
olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
This is the exact same position I'm in at the moment. I'm going to try using updated ADB drivers
blackadder666 said:
This is the exact same position I'm in at the moment. I'm going to try using updated ADB drivers
Click to expand...
Click to collapse
Adb 1.0.29.zip extracted from Android SDK attached here to post #1
http://forum.xda-developers.com/showthread.php?t=1828107
Stifilz
olegtord said:
Hi guys!
I've tried to upgrade my tablet from 4.0.3 to 4.0.3R1A as I did from 3.2.1 to 4.0.3, but I stuck on the first step menu 3-1. When I tried to start _hack_recovery.zip in recovery mode nothing happen in console of S.onyTablet.S tool and because of that I can't move forward
View attachment 1254796
Click to expand...
Click to collapse
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.
jessicaat said:
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.
Click to expand...
Click to collapse
Thanks for clearing that up jessiccat, remember i am doing this from memory as i cant root lol
Stifilz
Sent from my GT-S5830 using xda app-developers app
jessicaat said:
At this point, reboot tablet s into recovery mode, choose 2) update, and choose "INSTALL.ZIP". Note the file name is not "_hack_recovery.zip", which is the most confusing part.
After running "install.zip" AiO will talk again.
@stifilz, my problem with the adb files was far before reaching this point. Now I'm wondering that was only me having the problem. Maybe I shouldn't update my installed SDK tools. A simple way to test is to run "5-reboot device" in AiO to check if the adb drivers/files work correctly.
Click to expand...
Click to collapse
Strange that AiO can reboot my device and it does when i choose menu 3-1 but then it stopped. It looks like AiO is waiting for some response from device after launching install.zip (I've noticed that install.zip is launched automatically after reboot (AiO v4.1)).
When I updated device from 3.2.1 to 4.0.3 after choosing _hack_recovery.zip (aka install.zip) on AiO console (in Windows) was some movement and then you should choose signed-nbx03_042...zip.
I've replaced files from Adb 1.0.29.zip but have the same unlucky result
olegtord said:
Strange that AiO can reboot my device and it does when i choose menu 3-1 but then it stopped. It looks like AiO is waiting for some response from device after launching install.zip (I've noticed that install.zip is launched automatically after reboot (AiO v4.1)).
When I updated device from 3.2.1 to 4.0.3 after choosing _hack_recovery.zip (aka install.zip) on AiO console (in Windows) was some movement and then you should choose signed-nbx03_042...zip.
I've replaced files from Adb 1.0.29.zip but have the same unlucky result
Click to expand...
Click to collapse
I have the same problem. I updated my device also from 3.2.1 (german device) to 4.0.3 (us device). Then changed the region back to german with contis tool. Maybe it is a device problem?
my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1
k.bergmann2 said:
my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1
Click to expand...
Click to collapse
AiO 4.1 a little bit buggy, replace file in file folder by View attachment _submenu_custom_rom.7z it should help.
Concerning the second question: I upgraded without region changing and used 4.0.3 for my region.
k.bergmann2 said:
my problem is that after i choose 3-1 the tab goes off (as it is supposed to do) but also does aio. is that normal? shall i just flash install.zip in the recovery and then what? aio can't take over because it is closed...
and: i changed my region to the us. shall i download the 4.0.3R1A for germany or for the us? shall i use these links? http://forum.xda-developers.com/showpost.php?p=26882207&postcount=1
Click to expand...
Click to collapse
Is adb recoginizing tablet in recovery??
Check out FAQ thread in my signature link.
I have added some house keeping adb stuff.
Good luck
Stifilz
I'm still unable to install the latest update, having tried various things
I attach my build.prop file (hopefully attached correctly), not sure if it gives any clues as it means nothing to me
Thanks
blackadder666 said:
I'm still unable to install the latest update, having tried various things
I attach my build.prop file (hopefully attached correctly), not sure if it gives any clues as it means nothing to me
Thanks
Click to expand...
Click to collapse
Would be able to get more info from vendor.prop under vendor folder. You can save prop files as txt and upload that way. Prob easier.
Chur
Stifilz
stifilz said:
Would be able to get more info from vendor.prop under vendor folder. You can save prop files as txt and upload that way. Prob easier.
Chur
Stifilz
Click to expand...
Click to collapse
Thanks for taking the time to help
Vendor.prop file contains:
ro.sony.update.service_id=nbx03_003
ro.sony.sku.base=nbx03_003
ro.sony.build.id=TISU0017700
ro.sony.build.incremental=111104048
blackadder666 said:
Thanks for taking the time to help
Vendor.prop file contains:
ro.sony.update.service_id=nbx03_003
ro.sony.sku.base=nbx03_003
ro.sony.build.id=TISU0017700
ro.sony.build.incremental=111104048
Click to expand...
Click to collapse
This is link for r1a for UK
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
Are you planning on rooting?
I guess from your incremental you have root?
Chur
Stifilz
stifilz said:
This is link for r1a for UK
http://info.update.sony.net/ST003/nbx03_003/contents/0013/signed-nbx03_003-ota-120803004.zip
Are you planning on rooting?
I guess from your incremental you have root?
Chur
Stifilz
Click to expand...
Click to collapse
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything.
Must be doing something wrong but no idea what
blackadder666 said:
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything.
Must be doing something wrong but no idea what
Click to expand...
Click to collapse
Hmmm not too sure. All I can sugest is cat mcgowans tuit. You can find it post 2 of my faq link in signature. Follow to the letter and hopefully it will work, but thats all ive got
Good luck
Stifilz
blackadder666 said:
Already rooted with ICS, I just can't update to the new update r1a. AiO tool (v4) stops after telling me to reboot into recovery, updated ADB drivers, looked through this forum, in recovery I opt for install.zip then try the signed-nbx.zip, but still AiO tools stops. So posted my build.prop (and vendor.prop) to see if they showed up anything. Must be doing something wrong but no idea what
Click to expand...
Click to collapse
Condi's AiO v4.0 tool stalls at two points in the rooting process where it asks you to NOW ENTER RECOVERY MODE (at least it did for me). At both points, you just need to first update the system from the SD card using the install.zip file, then update the system from the SD card using the signed-nbx03.zip file during the first NOW ENTER RECOVERY MODE point, or the custom_update_signed.zip file during the second NOW ENTER RECOVERY MODE point. After starting the signed-nbx03.zip or custom_update_signed.zip update, WAIT! It may appear that the AiO tool has failed because it's not giving you any feedback, but it really has not failed. It takes several minutes (approximately 5) for the update to complete. Once the update has completed, AiO will spring back to life with additional prompts. I described my experience with what you are attempting HERE. The point you would be interested in reading is about half way through the post. Good luck.
olegtord said:
AiO 4.1 a little bit buggy, replace file in file folder by View attachment 1276079 it should help.
Concerning the second question: I upgraded without region changing and used 4.0.3 for my region.
Click to expand...
Click to collapse
that helped me. but now, when i am obliged to install the install.zip in the recovery, the tab tells me that the update was prohibitted as a result of checking version or base sku.
any clues?
Cat McGowan said:
Condi's AiO v4.0 tool stalls at two points in the rooting process where it asks you to NOW ENTER RECOVERY MODE (at least it did for me). At both points, you just need to first update the system from the SD card using the install.zip file, then update the system from the SD card using the signed-nbx03.zip file during the first NOW ENTER RECOVERY MODE point, or the custom_update_signed.zip file during the second NOW ENTER RECOVERY MODE point. After starting the signed-nbx03.zip or custom_update_signed.zip update, WAIT! It may appear that the AiO tool has failed because it's not giving you any feedback, but it really has not failed. It takes several minutes (approximately 5) for the update to complete. Once the update has completed, AiO will spring back to life with additional prompts. I described my experience with what you are attempting HERE. The point you would be interested in reading is about half way through the post. Good luck.
Click to expand...
Click to collapse
Finally got round to trying the above, still doesn't work. One thing however, when in recovery mode the tablet no longer comes up as an android device, it now shows as an unknown device. So looks like to loses the ADB driver. When I reboot the tablet normally it appears as an ADB device
Could that be the problem?
Thanks
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.
I've fastbooted so i'm completely on stock. No safestrap, or custom ROM.
The official JB OTA didn't work either, but that was before I fastbooted and I haven't been able to see if the OTA works instead of the manual install but we'll have to wait and see.
I place the JB file on my ext. sd card.
I go into recovery and hit install from sd card and choose the JB.
It starts to update, but it gives me this error shortly after.
"Verifying update package
Failed to verify whole-file signature
Signature verification failed
Installation Aborted"
I've redownloaded the JB files twice and so I don't think its the files are corrupt. I don't know where else to go from here. I always do it with above 60% battery so that isn't a issue either.
Any help? Can't seem to find anyone who can fix this for me.
Hi poncedeleon,
This method worked for me...(i'm assuming you arent a noob with this)
Head over to :
Razr ROMs Thread
Download the version you need. I used one of the RETAIL en.EU brandings but this might not be relevant to you.
1. Extract the .zip to a folder
2. Put the Razr into Fastboot and connect USB
3. Run prj-mfastboot.exe from the extracted folder - this is a really quick step
4. Run FlashME.bat - took about 5 mins and should boot into stock rom
You will need to re-root if you want.
Hope this helps
Informal Disclaimer - please dont blame me if it goes wrong or doesnt work. it worked when i did it.
arkoze said:
Hi poncedeleon,
This method worked for me...(i'm assuming you arent a noob with this)
Download the version you need. I used one of the RETAIL en.EU brandings but this might not be relevant to you.
1. Extract the .zip to a folder
2. Put the Razr into Fastboot and connect USB
3. Run prj-mfastboot.exe from the extracted folder - this is a really quick step
4. Run FlashME.bat - took about 5 mins and should boot into stock rom
You will need to re-root if you want.
Hope this helps
Informal Disclaimer - please dont blame me if it goes wrong or doesnt work. it worked when i did it.
Click to expand...
Click to collapse
Hey, thanks for your help but it ended up working anyways. I guess the download i had was corrupt and that was causing it. I downloaded the JB from another website and it worked flawlessly.
Again, thanks for trying to help
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
AronR said:
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I did this a week ago, and what a carry on I had, I thought i bust my tablet
I downgraded to .370 version using official firmware with flashtool, then I rooted using DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit (this is the easy part)
Then I used .109 version firmware (stripped ftf and flashable zip) - this is where it went wrong as I got into a boot loop
http://forum.xda-developers.com/showthread.php?t=2671276
I used both DE versions (German) for the flash/install - still works on UK tablet
I think there is a specific order to install busybox before or after dual recovery - this might be where it went wrong for me.
I also used an older version of dual recovery, (TabZ-lockeddualrecovery2.7.94-BETA.installer) and have yet to flash to the latest version
Sorry this is a bit muddled.
I just got my tab a couple days ago I guess I screwed up upgrading from 370 to 109. Following along closely to this thread
Sent from my SGP311 using Tapatalk
This is a guide that I wrote to enable root on Android version 4.3, build number 10.4.1.B.0.109 for SGP311. Follow at your own risk. I will not be responsible for damage to your Xperia Tablet Z! I am going by memory and XDA posts I have re-read.
Please read this first then follow the steps!!
1. Firstly you need to ensure you have the drivers installed for your tablet, so you could install Sony PC Companion http://www.sonymobile.com/gb/tools/pc-companion/
2. On your tablet make sure that Developer options is enabled (if not, press About tablet in the tablet settings menu several times), USB debugging is ticked and Verify apps over USB. Also turn on Unknown sources in Security settings
3. Assuming that the tablet is running version 10.4.1.B.0.109 you need to downgrade to version.370
4. Download and install Flashtool by @Androxyde http://www.flashtool.net/download.php - install this to your C: drive
5. Download the official .370 (I used SGP311_10.1.C.0.370 DE_Unbranded.ftf) firmware from here http://forum.xda-developers.com/showthread.php?t=2402863 thanks to @DevMark. This file should be placed inside the firmwares folder of Flashtool and thanks to @ donedos for his initial suggestion
6. Download the rooting kit from http://forum.xda-developers.com/showthread.php?t=2333566. Thanks to @DooMLoRD
7. It is suggested that a backup is carried out on the tablet as this flash/root will wipe the data from it – I never did this, as I was quite happy to install apps/.apk again, and I had a lot of crap on my tablet anyway
8. Open up Flashtool, power off the tablet, and plug the usb cable into the tablet.
9. With the tablet still turned off press the volume down button, and plug the usb cable into your PC, this should get your tablet into flash mode
10. There is a lightning bolt symbol on top left corner of Flashtool, click this, and two options should pop up. I think you click the top one; if so, you will be prompted to locate the .ftf file, select the .370 file. If this file is not visible, you probably need to select the second option that popped up!
11. The tablet should be flashing now, and takes a few minutes or so. Instructions will appear in Flashtool to unplug and power on your device.
12. It will take a while for your tablet to turn back on; when it does you might need to carry out the actions again in 2. above. Just make sure you are running firmware .370 now instead of .109
13. Now connect you tablet again to USB, device drivers might install again. Open up/extract DooMLoRD_Easy-Rooting-Toolkit_v17 and click the runme_win.bat file and follow the instructions – your tablet should now be rooted. Check for the Super SU app in your app list, or if it’s not there install from Play Store.
14. Download the file Xperia Tablet Z (SGP311) 10.4.1.B.0.109 VMo De from here http://forum.xda-developers.com/showthread.php?t=2671276, thanks goes to @bernddi . Extract the file so there are two files (SGP311_10.4.1.B.0.109_VMo De_stripped.ftf and SGP311_10.4.1.B.0.109_VMo De.zip)
15. Download and use this file http://www.winmd5.com/ to verify the md5 checksum matches the .109 files you downloaded.
16. If everything is okay, place the large zip file onto the root of your external memory card, and the .ftf file into the firmwares folder of Flashtool (later on don’t mix this file up with the .370 file)
17. Download the correct version of XZDualRecovery file for your tablet, – thanks to @[NUT]. I first tried the most recent version, but had problems with flash and root, so then I tried the older version TabZ-lockeddualrecovery2.7.86-BETA.installer. Files are linked from here http://forum.xda-developers.com/showthread.php?t=2261606.
18. Download and Install BusyBox from the Playstore, and run the app, then install again to your Tablet (using default options I believe) – this install failed first time for me, if same happends with you try again until it works
19. Connect your .370 rooted tablet to your PC, and run the DualRecovery file by clicking on install.bat – this will install the recovery to your tablet
20. Your tablet should power back on, or you’ll need to turn it on yourself. Make sure stuff works fine, you might need to carry out No. 2 again, I’m not sure
21. You should also have a file called NDR Utils on your tablet, if not install from the PlayStore, and run this. The option to boot into Philz Touch Recovery should be visible, select this option and reboot. You can reboot by pressing power up, while the tablet is turning on, but I have problems getting this to work. NDR makes it much easier
This is where it might get risky. It appears that the older version of DualRecovery does not have the option to verify the md5 checksum, but if the file winmd5free said the numbers match you should be okay
22. In recovery you need to select Install Zip, then select install zip from storage/sdcard1, then go to the zip file, and press it. The flashing of version .109 should begin – it takes a while
23. After the flash you must power off the device, DO NOT reboot
I believe this is where I got into a boot loop, and I am not certain how I got out of it. This link might help http://forum.xda-developers.com/showthread.php?t=2703882. Thanks to @Cat McGowan. When I finally got out of the boot loop, I started all over again from step No.8!
24. Open up Flashtool again, and flash the stripped ftf file like you did in No. 9 and No. 10
25. Follow the instructions to disconnect and power on your tablet, you should now have version .109 and still be rooted after the initial setting up of the tablet.
Please let this work!
If there is anyone reading this that spots an error or omission please post it
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
cirovi said:
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
Some root apps and recovery need it.
Sent from my SGP311 using Tapatalk
cirovi said:
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
actually it is already integrated in recovery package (/xbin/busybox), so there is no need to install it manually.
Well my tab went tits up a little while back, and I followed my guide and it worked
worked perfect for me... thank you very much
Help Needed
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
CentinelX said:
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Ok I managed to get out and install 370 again. But where did I go wrong?
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!