[Q] Problem after update w/ v2.4 flasher install - Sony Tablet S

Hi-
I have a US SGPT112US/S that was rooted and had SU installed. Win 7 with ADB working fine.
It was upgrading fine using flasher -2.4.7- it downloaded the first 3 files and installed and inflated them fine. Tool then asked about 1A and my internet was down for that bit, so it never installed final piece and then rebooted.
tried to reinstall, syas no su binaries. Probably made it worse by wiping data after that. :cyclops:
So, stuck at sony logo. Can boot into recovery mode. No adb anymore.
Any help greatly appreciated. read something about hack tool from the AIO.

devSlashDude said:
Hi-
I have a US SGPT112US/S that was rooted and had SU installed. Win 7 with ADB working fine.
It was upgrading fine using flasher -2.4.7- it downloaded the first 3 files and installed and inflated them fine. Tool then asked about 1A and my internet was down for that bit, so it never installed final piece and then rebooted.
tried to reinstall, syas no su binaries. Probably made it worse by wiping data after that. :cyclops:
So, stuck at sony logo. Can boot into recovery mode. No adb anymore.
Any help greatly appreciated. read something about hack tool from the AIO.
Click to expand...
Click to collapse
Boot into revoery. Hold Vol+ and press power, hold vol+ until boot recovery.
Click first link in my signature.
Search for US ICS or US ICS Release 1a and install these.
Should work as incremental should be lowered (if you are lucky)
If it works NEVER EVER reset to default if you are stuck at BOOT, you need USB debugging (off by default) to fix TAB.
If the above doesn't work then chances are it is foofed and you will need to send to Sony and hope they fix it under warranty.
I recently had to do this (it cam back with R5a so NOT ROOTABLE )
Stifilz

*Fixed *
Thanks stifilz !
I used your recovery image to get me to 1a and restore root. I read how you did about the same thing to yours. You are right- I was lucky !
I still need to run the flasher tool again to get up to rooted 5a. I don't really know why I need to do this- I read something about needing a hidden.img in order to migrate to jelly bean.
So, what I learned: make sure when you use flasher that you have good internet. It downloads quite a bit.
Big thanks to all the hard-working devs and moderators. Condi- what can we say- thanks for giving us new tablets !

follow-up
I went ahead and ran the flasher 2.4 again- but first I checked the firmware folder to see what was there- the 1a image showed zero K size, so I deleted it. Flasher tool re-downloaded 1a - was small- 17 K or so.
Re-ran the tool and it worked flawlessly. 5a with root. I have guest button now. Firmware tiny bit laggier than 1a previous.
The only other thing I wanted to note is that I was upgrading from a older firmware version- pretty sure it was 3.2.1 or whatever woot shipped these with. The reason I mention is that I read someone else making a big upgrade had similar trouble.
Thanks for all the help stifilz.

Related

Sony Tablet S Rooted/Updated from Stock Android 3.2 to 4.0.3r1a - My Adventure

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.

Can the LG Viper 4G LTE (LS84) be rooted?

Hi guys my girlfriend bought a LG Viper 4G LTE and she told me to root it to remove the sprint crap, so I was wondering if anyone has already done this and if yes, can they tell me how to s-off + root + custom recovery + and probably custom ROM.
If anyone can help, please I'll appreciate it. Since I searched here for that phone and is not even listed.
The phone is running android 4.0.4, is this ICS or Jelly bean?
I do not know how to get into fast boot boot loader cause I don't think it is POWER + VOL DOWN.
Thanks in advanced
Have a nice day
:what::what::what::what::what::what:
Sent from my Nexus 10 using Tapatalk HD
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Confirmed above!
jared_schaefer said:
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Click to expand...
Click to collapse
I can confirm that the above will work. I have a refurbished Viper from Sprint that I got because my 3G radio quit sending. It would receive great, but couldn't send any MMS or upload anything while on 3G. 4G was great, just no joy on 3G. Strangest thing. Anyway, got the phone replaced, and on the replacement was of course the dreaded unrooted ZVK. Gotta have my root back...
So I decided to try all this stuff out, and It worked.
To add a little further info, if you've got a relatively bare install of Windows, especially XP, you might need BOTH the VisualC++ Runtime Redistributables from 2010 (mentioned in the above thread) AND the one from 2008! If you don't have both, the LG FlashTool will not run. You can find them on Microsoft's site.
Once the flash tool has successfully downgraded your Viper, make sure you perform a factory reset, as indicated in the instructions for the FlashTool. Then use the "Activate" app to get your 3G/4G on. After that, set up your Google account under "Accounts and Sync" in "Settings".
I did the whole operation completely on a linux system, using a virtual machine running Windows XP for the FlashTool, then the bash script from here: http://forum.xda-developers.com/showpost.php?p=43530152&postcount=3253 with the v.31 rooting tool from the original post in that thread.
I had to edit the script in a very minor way, as was pointed out by its author, so it could find my adb command. I just placed the path to that command in the line that said:
Code:
for test_adb in "adb" "stuff/adb"
in the place of the first "adb", so I got:
Code:
for test_adb in "/home/user/android-sdk-linux/platform-tools/adb" "stuff/adb"
Make sure to replace "user" with your username, without the quotes.
Then I stuck the script in the same folder as the runme.bat file. After the script and root tool had done their work, my phone had rebooted a total of three times, and I had a perfectly functional Superuser app!
Huge thanks to LoveMyAndroid2010 in the post linked above. Great script - some love for linux!
Now to get RootKeeper and upgrade back to ZVK...
The aforementioned root method worked for me. Since I've rooted, I've compiled my findings into another thread. I haven't been able to unlock the bootloader yet, unfortunately.
how to upgrade LG Viper to Jelly bean or higher
After I root as per instructions, how can I upgrade the OS?
Please help. I'm a newbie and would appreciate any help you may offer. Haven't rooted any phone before.

[Q] LG Optimus Exceed (aka LG Lucid) VS840PP won't take a root

After scrounging, searching, hunting, and generally scrubbing every tree/rock/bush for answers, I have decided that it is time to post. As I am new to these forums, I sincerely appreciate any assistance in this matter. I have tried the only two methods that I can find to root my phone. the one by Bin4ry which is found at http://forum.xda-developers.com/showthread.php?t=1886460. and another one from a different site that was for JB. I have made sure that both debugging is on as well as allowing installations of non-market applications. I have tried every single usb mode, that just on the off chance, mine was that one phone that wanted to seperate itself from society. Since my phone is running ICS 4.0.4 I should be using Bin4ry's version, but I get stopped by this
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.06.2013) v31 =
======================================================================
Device type:
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
Doing a Backup first, please confirm this on your device!
Now unlock your device and confirm the backup operation.
Done!
Press any key to continue . . .
Please select the RESTORE MY DATA option now on your device!
Now unlock your device and confirm the restore operation.
Please press any Key when restore is done.
Press any key to continue . . .
Going to reboot now ...
mount: Operation not permitted
3679 KB/s (380532 bytes in 0.101s)
2668 KB/s (1500495 bytes in 0.549s)
3647 KB/s (1165484 bytes in 0.312s)
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
mount: permission denied (are you root?)
Rebooting again, please wait!
Could Not Find C:\Users\USERNAME\Desktop\newroot\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
Now unlock your device and confirm the restore operation.
Please press any Key when restore is done.
Press any key to continue . . .
Going to reboot last time now ...
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
It says that It's done and that all is done, but I think that because the mounting permission was denied that it wasn't able to root the device. If I could get some assistance on this from someone with more experience, I'd appreciate it. Does anyone know how to fix/root this device? I don't know if this will make a difference or not but it says the software is VS840PP2
Bump, anyone know anything?
I wish someone would
cecpuman said:
Bump, anyone know anything?
Click to expand...
Click to collapse
I wish someone would resolve this I see people all over the place bragging they have rooted their exceeds "showing proof" and no-one seems to give a crap that some people can't afford the most easily rooted phones and are forced to get the most workable less expensive phones. I have student loans and would have to pay a $400.00 deposit to be able to pay 150 dollars for a semi decent phone and my carrier won't allow me to use the phone I've had for a couple years that I rooted myself. I just want a viable answer to how do you root the exceed I know what I'm doing but I work for a living (making very little at that) and have a child to support so I can't devote a week to figuring it out and am frustrated that nobody seems to give a crap about anything but the new razr or the iphone (trendys).
Rooted mine
D3d10ck said:
I wish someone would resolve this I see people all over the place bragging they have rooted their exceeds "showing proof" and no-one seems to give a crap that some people can't afford the most easily rooted phones and are forced to get the most workable less expensive phones. I have student loans and would have to pay a $400.00 deposit to be able to pay 150 dollars for a semi decent phone and my carrier won't allow me to use the phone I've had for a couple years that I rooted myself. I just want a viable answer to how do you root the exceed I know what I'm doing but I work for a living (making very little at that) and have a child to support so I can't devote a week to figuring it out and am frustrated that nobody seems to give a crap about anything but the new razr or the iphone (trendys).
Click to expand...
Click to collapse
Yep, I just rooted my VS840PP, seems you need to use the Lg Spectrum root, but since I'm new I can't post links, but you will need the driver file "LG VZW_United_WHQL_v2.11.0.exe" and "LG_Spectrum_ICS.zip" (put these into a search engine)
Install Instructions
Download and unzip
Connect your phone to your PC
Make sure to have the LG USB drivers installed
Make sure to have debugging enabled
Make sure to have USB connectivity set to internet connection
Run the script for your OS (.bat for Windows, .sh for Linux)
Enjoy
I really did think it would make my phone not boot, but surprisingly it worked! EDIT 8-16-13 treat this phone like any other LG Lucid, which means you can go to CM 10 4.1 Jellybean on this phone.
scififan68 said:
Yep, I just rooted my VS840PP, seems you need to use the Lg Spectrum root, but since I'm new I can't post links, but you will need the driver file "LG VZW_United_WHQL_v2.11.0.exe" and "LG_Spectrum_ICS.zip" (put these into a search engine)
Install Instructions
Download and unzip
Connect your phone to your PC
Make sure to have the LG USB drivers installed
Make sure to have debugging enabled
Make sure to have USB connectivity set to internet connection
Run the script for your OS (.bat for Windows, .sh for Linux)
Enjoy
I really did think it would make my phone not boot, but surprisingly it worked! EDIT 8-16-13 treat this phone like any other LG Lucid, which means you can go to CM 10 4.1 Jellybean on this phone.
Click to expand...
Click to collapse
Big thanks.Any roms that work on our phone?
---------- Post added at 02:16 AM ---------- Previous post was at 02:01 AM ----------
Can you post instructions on how to flash CM10?
Do i do standard Lucid downgrade to GB procedure?
Thanks in advance.
lviv73 said:
Big thanks.Any roms that work on our phone?
Click to expand...
Click to collapse
Yeah one which is Android 4.1.2, the file is called "cm-10-20130424-UNOFFICIAL-vs840.zip", but you have to rollback to GB 2.3.6(due to locked ics bootloader), install root, CWM and finally install the CM 10 based LG Lucid beta rom. I see you edited your post and yes it is the standard LG Lucid Gingerbread downgrade method. The forum thread title is "[ROM][BETA] CyanogenMod 10 for the LG Lucid" and its on "androidforums.com" all info you need should be in that forum thread. I can tell you that Jellybean works very well on this phone, and I never want to go back to 4.0.4. :good: But of course there are some bugs, as it seems signal strength is lower, but I may have the wrong baseband for this phone.
how to flash clockworkmod
scififan68 said:
Yeah one which is Android 4.1.2, the file is called "cm-10-20130424-UNOFFICIAL-vs840.zip", but you have to rollback to GB 2.3.6(due to locked ics bootloader), install root, CWM and finally install the CM 10 based LG Lucid beta rom. I see you edited your post and yes it is the standard LG Lucid Gingerbread downgrade method. The forum thread title is "[ROM][BETA] CyanogenMod 10 for the LG Lucid" and its on "androidforums.com" all info you need should be in that forum thread. I can tell you that Jellybean works very well on this phone, and I never want to go back to 4.0.4. :good: But of course there are some bugs, as it seems signal strength is lower, but I may have the wrong baseband for this phone.
Click to expand...
Click to collapse
Ok i got it rolled back to gb, but it says i need a sim card and no wireless or 3g, i cant download the cwm unless i restore to ics. Im ecstatic that i got this far I rooted it rolled it forward
Installed rom manager and downloaded the restore but i cant run it without some sort of data connection. Thank you all for getting me this far but what do I do?
D3d10ck said:
Ok i got it rolled back to gb, but it says i need a sim card and no wireless or 3g, i cant download the cwm unless i restore to ics. Im ecstatic that i got this far I rooted it rolled it forward
Installed rom manager and downloaded the restore but i cant run it without some sort of data connection. Thank you all for getting me this far but what do I do?
Click to expand...
Click to collapse
You may have to install the baseband for the Exceed. I think in the CyanogenMod beta thread on AndroidForums there is a link but I'm not sure. Use ROM Manager to install CWM Recovery and then Flash CM10.
Vs840pp 4.1.2
D3d10ck said:
Ok i got it rolled back to gb, but it says i need a sim card and no wireless or 3g, i cant download the cwm unless i restore to ics. Im ecstatic that i got this far I rooted it rolled it forward
Installed rom manager and downloaded the restore but i cant run it without some sort of data connection. Thank you all for getting me this far but what do I do?
Click to expand...
Click to collapse
As long as you're rooted, search on the internet for "cwm installer for lucid" and follow the install instructions on gingerbread, then you want to flash the CWM touch recovery by searching for LGVS840_CWMT.zip and clicking on "CWM Touch Flashable Recovery for LG Lucid 4G - LG Cell Phones ..." Make sure you have the CWMT zip and LG Lucid CM 10.1 zip on your micro sd card. You then use rom manager to boot into recovery and flash the CWMT zip, then do a factory reset and clear caches and finally flash the LG Lucid CM 10.1 available on androidforums.
scififan68 said:
As long as you're rooted, search on the internet for "cwm installer for lucid" and follow the install instructions on gingerbread, then you want to flash the CWM touch recovery by searching for LGVS840_CWMT.zip and clicking on "CWM Touch Flashable Recovery for LG Lucid 4G - LG Cell Phones ..." Make sure you have the CWMT zip and LG Lucid CM 10.1 zip on your micro sd card. You then use rom manager to boot into recovery and flash the CWMT zip, then do a factory reset and clear caches and finally flash the LG Lucid CM 10.1 available on androidforums.
Click to expand...
Click to collapse
May I ask which firmware are you suppose to use to do a roll back? Can you just use the Lucid's firmware or does it have to be the Exceed firmware to work for the roll back?
ls5280 said:
May I ask which firmware are you suppose to use to do a roll back? Can you just use the Lucid's firmware or does it have to be the Exceed firmware to work for the roll back?
Click to expand...
Click to collapse
It's the stock gingerbread for the LG Lucid and you look for the method to install with LG's tool and you will need the file "VS840ZV6_06.S6_06.P58014.R5.cab" and look for how to roll back to gingerbread on the lg lucid to find out how to roll it back.
scififan68 said:
It's the stock gingerbread for the LG Lucid and you look for the method to install with LG's tool and you will need the file "VS840ZV6_06.S6_06.P58014.R5.cab" and look for how to roll back to gingerbread on the lg lucid to find out how to roll it back.
Click to expand...
Click to collapse
Thanks a bunch, I thought it would be okay to do that but just wanted to make sure before doing it.
Hmm, after restoring successfully, for some reason I cant get the Wi-Fi to work. I tried both versions the V5 and V6 in the dropbox posted on android forum. Can root and everything but unable to access any internet without wifi. Kinda stuck without CWM. Any clues?
Edited: Whoops, Haha, a Factory Reset fixed it.
Edited: Blah after being able to install Rom Manager and installing CWM "Successful" I still get into CWM recovery.
Edited: CWM solved but now I get the "Cant Mount Sd" in CWM. Trided both "fat and "extFAT" and no go. Any Help?
Edited: Finally! Bad SD card! CM 10 up and running! Woot!
ls5280 said:
Hmm, after restoring successfully, for some reason I cant get the Wi-Fi to work. I tried both versions the V5 and V6 in the dropbox posted on android forum. Can root and everything but unable to access any internet without wifi. Kinda stuck without CWM. Any clues?
Edited: Whoops, Haha, a Factory Reset fixed it.
Edited: Blah after being able to install Rom Manager and installing CWM "Successful" I still get into CWM recovery.
Edited: CWM solved but now I get the "Cant Mount Sd" in CWM. Trided both "fat and "extFAT" and no go. Any Help?
Edited: Finally! Bad SD card! CM 10 up and running! Woot!
Click to expand...
Click to collapse
Glad to see you got CM 10 on this phone, since it runs pretty good, the only issue I had is the way it handles low signal areas, which is why I upgraded to the LG Spectrum plus I wanted Verizon 4G LTE.
scififan68 said:
Yep, I just rooted my VS840PP, seems you need to use the Lg Spectrum root, but since I'm new I can't post links, but you will need the driver file "LG VZW_United_WHQL_v2.11.0.exe" and "LG_Spectrum_ICS.zip" (put these into a search engine)
Install Instructions
Download and unzip
Connect your phone to your PC
Make sure to have the LG USB drivers installed
Make sure to have debugging enabled
Make sure to have USB connectivity set to internet connection
Run the script for your OS (.bat for Windows, .sh for Linux)
Enjoy
I really did think it would make my phone not boot, but surprisingly it worked! EDIT 8-16-13 treat this phone like any other LG Lucid, which means you can go to CM 10 4.1 Jellybean on this phone.
Click to expand...
Click to collapse
I have tried this root and all I get is nothing, I am attaching what the root program says if anyone can help
kibbles-n-bits said:
I have tried this root and all I get is nothing, I am attaching what the root program says if anyone can help
Click to expand...
Click to collapse
I think I may have had the same issue and it turned out the root files didn't extract correctly the first time, so I deleted the root files and extracted them again and it worked. Of course I can't exactly remember it now, but its worth a try. EDIT: Wait no, it looks like root installed fine, are you on stock ICS or Gingerbread? As Gingerbread has special root tools that are different from ics, also make sure you have superSU installed and try the root checker from the playstore.
Will I be stuck in activation mode?
scififan68 said:
I think I may have had the same issue and it turned out the root files didn't extract correctly the first time, so I deleted the root files and extracted them again and it worked. Of course I can't exactly remember it now, but its worth a try. EDIT: Wait no, it looks like root installed fine, are you on stock ICS or Gingerbread? As Gingerbread has special root tools that are different from ics, also make sure you have superSU installed and try the root checker from the playstore.
Click to expand...
Click to collapse
New to the community and was hoping this was a good place for a related question. I have an exceed and I rooted without problem yesterday. I believe my SD Maid app deleted some important files or something because I stopped receiving incoming calls and texts. Anyway, I soft bricked my phone a few times and got the "Long time no see" message. I thought I unrooted my phone so I tried doing a hard reset thinking I would possibly fix the problem. That made matters worse. My soft brick became the only thing I could see no matter how many times I pulled the battery out and rebooted I was stuck at that screen. After hours of trying to get my pc to recognize my phone/get my phone in download mode, I finally fixed it and rooted again. Problem is that when I went through the unbrick process and flashed the kdz file to my phone, it was then stuck in activate mode. It wasnt a big deal because I just played dumb with verizon and they fixed it in their system being that when trying to activate it didnt give me the option to activate on my same plan/number. A bit annoying but better than nothing. My question is when I roll back to gingerbread or flash CM10 will I be stuck in activation mode again? Sorry for the long post, just figured I would give the what and why before my question!
derekpoole890 said:
New to the community and was hoping this was a good place for a related question. I have an exceed and I rooted without problem yesterday. I believe my SD Maid app deleted some important files or something because I stopped receiving incoming calls and texts. Anyway, I soft bricked my phone a few times and got the "Long time no see" message. I thought I unrooted my phone so I tried doing a hard reset thinking I would possibly fix the problem. That made matters worse. My soft brick became the only thing I could see no matter how many times I pulled the battery out and rebooted I was stuck at that screen. After hours of trying to get my pc to recognize my phone/get my phone in download mode, I finally fixed it and rooted again. Problem is that when I went through the unbrick process and flashed the kdz file to my phone, it was then stuck in activate mode. It wasnt a big deal because I just played dumb with verizon and they fixed it in their system being that when trying to activate it didnt give me the option to activate on my same plan/number. A bit annoying but better than nothing. My question is when I roll back to gingerbread or flash CM10 will I be stuck in activation mode again? Sorry for the long post, just figured I would give the what and why before my question!
Click to expand...
Click to collapse
You mean the activation screen, that you can quite easily bypass, also once it is is active it doesn't need to be activated again. Here is how to bypass activation https://www.youtube.com/watch?v=8WGKCdlnt1s
wow how did i miss that one!
scififan68 said:
You mean the activation screen, that you can quite easily bypass, also once it is is active it doesn't need to be activated again. Here is how to bypass activation
Thanks for the link. I apologize for not researching that better. CM 10 here i come!
Click to expand...
Click to collapse
I know this is an old post but I just snuck and rooted the girlfriends LG Lucid VS840ZV9 / 4.0.4 / software update version 6.3.0_B7
tonight using spectrum_root_windows
http://www.mediafire.com/download/on6cnik4h0fo697/spectrum_root_windows.zip

HP 7 Plus and Cydia Impactor Root now tablet resets upon reboot

Ok first and fore most thanks for all the roots and guides, I have used over the years.
So I purchased a HP 7 Plus (NOT SLATE 7 PLUS) and rooted it via the Cydia Impactor method, it worked like a charm. I set everything up, im having a blast it worked. I reboot my phone and boom im back to initial setup.
WTF.....
So over the course of several days I have scoured the interwebs for a fix, I have seen similar problems with a app called busybox which I DO NOT have. So its not that.
I have done a factory hard reset, still does it, I tried to flash the stock rom but the stock HP rom image will not boot from a SD only from the internal (yeah stupid huh? dumb hp design) so basically if I try to put it on the internal memory it just gets wiped away when it restarts and resets. I tried sideloading through adb, nada. It works like a charm when its on and still maintains root even after all the above.
But its extremely annoying that on the instance an app, someone, or I reboot my tablet I have to go through the bs of setting it all back up again.
Any help would be grateful. I have literally nerded out for days trying to fix this myself but its beyond my skill set. I need a master mind to figure this out.
Right now its sitting freshly restored still with root.
You guys rock....
Brett
anyone?
Anyone have any suggestions, im no expert but I believe its something in the bootloader that is causing it to reset upon reboot.
Just flash HP official update. Zip via apply from adb/fastboot
sent from HP 7 PLUS 1301
it's not working
rakshakb said:
Just flash HP official update. Zip via apply from adb/fastboot
sent from HP 7 PLUS 1301
Click to expand...
Click to collapse
tried it but not working !!!
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
same problem as you. tired of trying everything to reset it back.anyone please make CWM/TWRP to flash hp 7 plus .....need it badly !!!!:crying::crying::crying::crying::crying::crying:
Its,
Working just you need correct one zip from HP site. Reboot tablet recovery (volume- & power button) select apply update from adb sidelode.
please send me the correct update.zip file .....
rakshakb said:
Its,
Working just you need correct one zip from HP site. Reboot tablet recovery (volume- & power button) select apply update from adb sidelode.
Click to expand...
Click to collapse
thanks for reply,
please attach the correct update.zip file !!!!
need it very badly my tablet is not working ....:crying::crying::crying:
hp 7 plus 1301
http://ftp.hp.com/pub/softlib/software12/COL53679/ob-134254-1/update.zip
click thanks if i help you
ibanezcollector said:
Ok first and fore most thanks for all the roots and guides, I have used over the years.
So I purchased a HP 7 Plus (NOT SLATE 7 PLUS) and rooted it via the Cydia Impactor method, it worked like a charm. I set everything up, im having a blast it worked. I reboot my phone and boom im back to initial setup.
WTF.....
So over the course of several days I have scoured the interwebs for a fix, I have seen similar problems with a app called busybox which I DO NOT have. So its not that.
I have done a factory hard reset, still does it, I tried to flash the stock rom but the stock HP rom image will not boot from a SD only from the internal (yeah stupid huh? dumb hp design) so basically if I try to put it on the internal memory it just gets wiped away when it restarts and resets. I tried sideloading through adb, nada. It works like a charm when its on and still maintains root even after all the above.
But its extremely annoying that on the instance an app, someone, or I reboot my tablet I have to go through the bs of setting it all back up again.
Any help would be grateful. I have literally nerded out for days trying to fix this myself but its beyond my skill set. I need a master mind to figure this out.
Right now its sitting freshly restored still with root.
You guys rock....
Brett
Click to expand...
Click to collapse
have you solved this?
this helped me with mine: http: //supportdot h p dot c o m /us-en/document/c04074925
except install from SD won't display the update.zip file so I had to sideload.
adb devices won't list the device so I had to do this:
http: // h30434 dot www3 dot hp dot c o m /t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
to figure out where to place the edited .ini and .inf files, do the echo command and put all three files there (the .ini, .inf, and .zip).
My device is now running official 4.4.2, sadly, with no root. And not a lot of material to work with, either.
(Sorry, it won't let me post links)

Asus MeMO Pad 8 (ME181C): Recovery Guide

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?!

Categories

Resources