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?!
Related
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
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.
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
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?
I've been hacking on this on and off for days. Success. Basically the solution is a bait and switch.
I've tried so many things, this is recalled from memory and the following steps may be incomplete. I used the latest of ES File Explorer. SuperSU, etc.
Get angguesss' update.zip here: http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21 . Rename it to update zip and keep it safe.
Make sure you know how to root, get the proper Intel drivers, Phone Flash Tool Lite, etc.
OVERVIEW:
What is being done here is to prime the 7840 for an update by downloading the stagefright fix with a rooted device and swapping out that fix with angguesss' older update.zip. It's like starting over. Upon reboot the 7840 updates to angguesss' older update cleanly, paving the path for the stagefright fix to update successfully.
Special thanks to angguesss, Social Design and everyone who unknowingly provided little pieces of knowledge here and there.
CAUTION:
You might brick, wipe, lose root, lose customizations, void warranty, get frustrated, look at the device hatefully and all the standard caveats, no guarantees. Do at your own and the device's risk.
HERE IT IS:
This is the BAIT part:
1. Root the 7840
2. Download the stagefright patch (DO NOT REBOOT)
3. In an editor: Go To \data\data\com.dell.systemupdateota
4. Copy the patch somewhere safe (extsd, for example, just in case)
5. Review the properties of the update.zip in the com.dell.systemupdateota
6: Note permissions of RW- --- --- and the owner/group "u0_a29"
This is the SWITCH part:
7. Copy over to \data\data\com.dell.systemupdateota angguesss' update.zip here while renaming it update(1).zip
8. Change the permissions and owners of the update(1).zip to match the update.zip
9. Delete the downloaded update.zip (the stagefright download)
10. Rename update(1).zip to update.zip. angguesss' update will now be the update!
11. In \system\app delete the supersu folder (containing the supersu.apk)
12. in \data\data delete the eu.chainfire.supersu data folder
13. Press the on/off button, select reboot
14. Let the 7840 reboot
15. After a few seconds the 7840 will "figure out" there is an unused update and begin to shut down.
16. Wait out the shutdown (mine took about five minutes).
17. The tablet will begin to update in the usual fashion (Andy, the progressing blue line)
18. Let the update finish and allow to boot to completiton.
19. Go to settings->about tablet->update and download (yes, again) the stagefright fix.
20. Install, reboot (wait...) and upon reboot let the update proceed as normal. Should be no errors.
21. Hopefully, you now have a Stagefright updated 7840 5.1
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
UPDATES:
The Dell Stylus still appears to work.
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low level speaker "clicks" at boot time.
Update and clarifications to instructions steps 6, 12, 13
Hey, thanks for posting this. I am trying to accomplish the same thing you have done.
I followed your guide up through number 16, but the tablet never reboots and there is never any update screen.
If I boot up by pressing the power button I am still on 5.1 and the stagefright update still fails for me...
Is this a problem you encountered?
On step 16 I waited quite awhile and waited and waited. I was tempted to bail out but didn't. It might have been ten minutes.
TonyBigs said:
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low lever speaker "clicks" at boot time.
Click to expand...
Click to collapse
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
olvrick said:
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
Click to expand...
Click to collapse
Thank you for the response, I'm in the process of trying the process all over again. Maybe I missed something.
Successful again. Note changes to steps 6, 12, 13
Today when updating from 5.0.1 to 5.1 I'm not sure what happened but I ended up with the stragefright ota also installed. At least I think it is. System update is no longer finding any available updates. I did lose root. The strangest part was that I was having trouble updating to 5.1 until I booted into tethered TWRP (Have only used cwm on this device in the past when flashing first 5.1 update). First time trying to boot into TWRP I just got a black screen after leaving the bootloader and having the white text populate on screen. Second attempt though TWRP loaded up and immediately began running a script, or flashing the update I suppose. Tablet rebooted automatically and I haven't lost any data. Everything works fine so far. How can I determine if the latest stagefright has been installed?
TonyBigs said:
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
Click to expand...
Click to collapse
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
toxic_garden said:
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
Click to expand...
Click to collapse
I understand, so don't rerun the rooting process. It's the user's choice of what to do next after returning the 7840 back to a non-rooted state that will accept OTA fixes and updates.
TonyBigs said:
This is the BAIT part:[...]
This is the SWITCH part:
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
Click to expand...
Click to collapse
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
toxic_garden said:
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
Click to expand...
Click to collapse
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
jamebarron88 said:
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
Click to expand...
Click to collapse
They both work fine. I can't say how it was before, because I never used Sensing Assist in the past. But for now, it works.
toxic_garden said:
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Click to expand...
Click to collapse
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
wayne710 said:
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
Click to expand...
Click to collapse
Yes where can we find the source. And how do we get to stock recovery if already rooted and used cwm tethered recovery.
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
toxic_garden said:
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
Click to expand...
Click to collapse
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
wayne710 said:
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
Click to expand...
Click to collapse
you're right, i should correct that in my description. Glad it worked for you. Personally, i only used root for removing McAffee and installing AdBlock. Well, McAffee is just frozen for now and adblocking happens on the router, so no big loss for the moment. The only thing i might miss is Titanium Backup. Helium does a good job, but is in no way comparable to the mighty power of Titanium. ^^
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
Seriously? why not make a normal guide for those who havent done it before?
olvrick said:
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
Click to expand...
Click to collapse
seems like mega has some issues at the moment. Just drop me a PM if it's still broken in 1 hour or so, then i'll upload the zip somewhere else