Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:
God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!
Great news! Who might have thought that a working exploit is already out there?
This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.
FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!
Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.
22 hours and 5 badly needed factory resets were worth it ^^
Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!
after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks
Amazing how much of a difference having root on this tablet makes.:good:
Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?
Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?
First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.
i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...
Somebody buy that man a beer.!!!!!!
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?
Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these
Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
TF101, SL101 and TF101G on ICS firmwares anything else is untested.
Also should work on TF201 and TF300T on ICS ONLY!
For Windows, tested on windows 7 x64 bit, xp 32 bit and windows 7 32 bit.
Your data will be retained, unless you wipe in TWRP or something
UPDATE:
Added V0.41 which includes TWRP
Also V0.42 which is even newer TWRP!
apk not working sofar :[
If you have a TF201, or TF300T, this will work still, but you need to replace the included file 'recoveryblob' with a recoveryblob from a recovery from your device (download the .zip file for the recovery you want, and extract the 'blob' or 'recoveryblob' file from it and place in PERI folder, naming it recoveryblob and overwriting the otherone!)
Initiate project-PERI:
Since there's no one-clicks that I've stumbled across, and many people are asking if this-that etc.. works with .24, I've made an easy one-click (ish) that guides you through it and runs the necessary commands.
Thanks to:
Team Rouge (I used their touch recovery version)
Wolf (For his method to flash recovery!)
Roach (Bootloop fix)
Members here for testing help :] (I'm bad about typos...)
Download here (feel free to mirror):
V0.1- Platypus - 13.42MB
Version 0.1
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
V0.2- Elephant - 13.39MB
Version 0.2
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.3- Raptor - 13.39MB
Version 0.3
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.4- Indri - 13.39MB
Version 0.4
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.41- TwrpyIndri - 14.29MB
Version 0.41 (TWRP 2.3.2.3)
V0.42- TwrpyIndri Cutting Edge - 14.15MB
Version 0.42 -- Recommended (TWRP 2.5.0.0)
Just unzip it to a folder anywhere and run the .bat file!
Works with or without MicroSD, just let the device totally reboot (E.G. don't let any commands run at the splash screen or in recovery.)
Fixed reboot confusion in V0.2 -Didn't fix in v0.2, Did fix in v0.3 though
If I did anything wrong, or offended any devs, killed someone's cat, or something else, Please let me know!
Post here with any questions or problems, I tested this and everything worked fine, but still consider it as final? release candidate 4.
Did it work?
This should do everything needed, and all is included in zip!
If you want to skip any steps that you've already done if you mess up, just unplug the USB and pretend that it isn't throwing 'device not found' errors, then get back to where you were.
If superuser isn't installing but you have recovery, try 'fix permissions' in recovery. -- Fixed (hopefully) in V0.2
Read the readme and run as administrator! Video-tut is here!
**Also attached to thread.**
PERI - Changelog --
Code:
[*][B]V0.42[/B]
-- Added [I]cutting edge[/I] TWRP 2.5.0.0
-- Thanks jazzruby
[B]V0.41[/B]
-- Added TWRP 2.3.2.3 recovery, finally c:
-- Fixed a couple typos.
-- Fed a llama candy.
[B]V0.4[/B]
-- Added option for ROOT users to just flash recovery.
-- Added unbrick/bootloop fix option for those that can access adb (hopefully works)
-- Bug fix, minor layout change.
-- Second-Last windows release! :D 'Last is auto APX unbrick..' Then the app.
-- Indri
[B]V0.3[/B]
-- Fixed reboot typo that causes failed reboot
-- Other layout issues and typos
-- [I]Added a Readme, read it[/I]
-- Got angry at video recorder for not working.
-- Raptor
[B]V0.2[/B]
-- Fixed a few layout issues and typos.
-- Added driver autoinstaller for Windows 7. (XP Can still use manual)
-- Updated the SU zip I was using, hopefully fixes fake error messages.
-- Fixed reboot confusion (Reordered command layout)
-- Elephant
[B]V0.1[/B]
[I]-- Initial Release[/I]
-- Helps you root and install recovery.
-- Simple mostly automated batch script.
-- Driver install guide too!
-- Reboot bug included!
-- Platypus
[/CENTER]
Tl;DR: This installs recovery and walks you through rooting your device from total stock. It includes everything you need, download is above.
It also functions as a unbrick for soft-bricks where you can access ADB or if your recovery is bootlooping and won't flash anything.
If you already have root: This tool will work on an already rooted tf to install Rouge's latest Touch Recovery (Reads from internal and external)
--if you're in a bootloop and can boot into android via-cold-boot, this will fix it! --
So if anyone who's already rooted doesn't mind doing further testing on it that would be great, the more reports the better!
If the superuser.zip isn't giving you root (For whatever reason ) try flashing the attached SuperSU I packed.
Video:
How to use PERI to root your Transformer!
**coming soon**
Unbricking/fix recovery bootloop:
I added an unbricking help/feature in V0.4 that'll help with bootloops or softbricks. PERI will help you through it.
**If you want to use the 'I'm already rooted just flash recovery' feature, you need to have given adb su access already!!!**
I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know.
It might have bugs though and not work, in which case 'Don't taze me bro!'
I pretty much copy-pasted roach's bootloop fix.
--
If I helped, click thanks!
Thing O Doom isn't responsible for bricks, dead cats, or thermonuclear war. (Although I will help you with the first two. Seek a bomb shelter if you experience the third problem.)
The .bat is open-source, download the .zip and take a look at the .bat with notepad++, if you like.
If you're having driver issues, give USBdeview a looksee.
What does it do, exactly ? You are downgrading and then rooting with it ?
No, it doesn't need to downgrade, it just runs wolf's exploit and directly flashes recovery on your tf. All user data is safe.
If it was a downgrade, the filesize would be alot bigger as I'd have to include a stock ROM.
tried it on my transformer with the latest .24 update but it could not flash the recovery at first time, got error ..... lemme check again
Edit: got error --- "cannot stat 'recoveryblob': No such file or directory" ---
I am sure that I am using the same transformer as yours as mine was imported from USA.
About Guide
Hi all,
I think ıt should be a more detailed guide.
"Just unzip it to a folder anywhere and run the .bat file!" it seems very easy.
I do not want to offend the developers and Thing O Doom
tigerfire25;
you can try that move the blob file internal memory of asus and try again. I an now at work so I can not try the method. I am just suggesting you, do not hope too much
I tried to make with simplicity in mind, so that really is all you need to do:
1. Make folder and extract contents of .zip into it.
2. Run the .bat file, which then holds your hand through the whole process.
3. ???
4. Profit.
EDIT5: Tigerfire, please try with a MicroSD inserted. This may fix it, thanks for reporting back.
Done
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Yeah, the reboot to recovery scripts don't work, it's actually just a simple 'adb reboot' command. I couldn't get 'adb reboot recovery' to work, sorry about that, that's why I detailed the manual instructions in there.
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
worked for me o/
I now have revolution HD Rom on my .24 TF101
thanks for your help ^^
Hi Thing O Doom,
Nice work and thanks
Thing O Doom said:
I tried to make with simplicity in mind
Click to expand...
Click to collapse
You might be able to automate the process a little better by running the PnP Utility ('PnPutil.exe').
e.g.
Code:
pnputil -i -a %~dp0\adb-drivers\android_winusb.inf
-a - add package
-i - install package
You can skip the install command (-i) if you like (drivers will now be in the 'driver store' (-a) and installed when device is connected).
PnPUtil - TechNet
Thing O Doom said:
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
Click to expand...
Click to collapse
You might want to try/use the su pkg from HERE
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
It uses a newer 'update-binary' and cleaner/updated 'updater-script' & pkg.
-JR-
Thanks for the pointers, I'll be uploading V0.2 a bit later to fix some of those bugs and automate the process a bit better.
Added V0.2 and Changelog in OP.
Thanks jazzruby for pointers!
@ Thing of Doom
Quarkko,
1. You use the same recoveryblob (Tf101 and Tf101G are very similar, so 3rd method works on both.)
2. You don't need to do anything, as you won't get OTA updates anymore if you install CWM. You can manually flash rooted updates in CWM later if you want to update.
3. Following to the letter, almost 0. You'd have to unplug your tf DURING the flashing of the recoveryblob. (The dd if command)
4. You still can't use NvFlash, since you have a Tf101G, sorry it hasn't been cracked yet.
Clear guide- Use my PERI: one click root and recovery installer (in my sig), it walks you through it and runs the commands for you. Works on the tf101G
Click to expand...
Click to collapse
Thanks for the reply.
I tried your PERI method! But unfortunately I use XP for these jobs. Should I wait for the xp drivers. Thanks anyway.
You can still use PERI with xp, just not the Autoinstall of drivers portion of it. Hit no when it asks to install drivers, then when it gets to the section that asks if a device shows up, hit no and then it will redirect you to a manual install of the ADB drivers.
All it needs are ADB drivers, which are easy enough to install.
TF101/G ONLY! anything else is untested.
does it mean onnly the g version or only the tf101?
kind regards
gandalf
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Worked for me.
Asus Transformer TF101 | ICS 4.0.3 | Compilation IML74K.WW_epad-9.2.1.24-20120503
Thank You!
xxanthor said:
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Click to expand...
Click to collapse
I have a TF101 serial number starting with 0 and US version. I also have to face with reboot problem twice.
Command Screen say that;
Reboot: Operation not permitted. (both Revovery and Flashing screens)
I used a laptop with operating windows 7 32 bit. After reboot problem, this time I try to exectue the batch file as an administrator but, the laptop can not see the device.
Finally, I reboot my device twice manually. Then, I waited for the final reboot. The final reboot completed. There is no Superuser apk. I get into the recovery menu and I installed by manually.
Thing O Doom said:
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Click to expand...
Click to collapse
-thanks.. it did it,but no root.-and the recovery- if i trie to go to recovery after pressing vol up i only see the android layinf with a red triangel and exclamation mark.
May i try once more?
Kind regards and sorry for my englisch
By the way :funny comments
Try V0.2, it fixes reboot problems mostly. If it can't see it, then drivers need to be re/installed. Is USB debugging enabled?
So did you manage to get Rouge recovery on there and root?
Is there a possibility for getting root and CWM recovery on this device? i have achieved to get into E3 Recovery, Bootloader mode, and some other test screen.. i posted pics and a description on how to do it. i would really like to get root on this device, i can can help anyone in all ways possible.. p.m. me.
Link to video is in a text file..
I wait for S2109 root too...
I want buy this devise, but without root its difficult use it...
I wait for S2109 root too...
you can find on support.lenovo.com Open Source Code:
fih_uboot_0618.tar.gz 10.7MB
kernel_s2109.tar 445MB
how to obtain these files
Hey how do I find the files u are talking about? Like a link?
nevermind got em
Maybe someone can start developing on the uboot.bin and the system image to obtain some root access
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
WOO!!!
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
Awesome! thank you so much! the CWM root worked perfectly. However, the driver from the SDK folder wasn't recognized so I just used the Lenovo ADB driver that came shipped with the device and that worked just fine. Took me about 20 minutes to complete - that includes resolving the driver issue.
Niiice
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
2) In step 3 of el_fuego's instructions, he says "add following to both the [Google.NTx86] and [Google.NTamd64] sections:", add this instead:
Code:
;Lenovo S2109
%SingleBootLoaderInterface% = USB_Install, USB\VID_17EF&PID_748B&REV_0100
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_02
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_74CC&REV_0216
How easy is this root? I'm not really familiar with the process and don't want to brick the device, which I'm concerned about as I don't quite understand the directions.
Lenovo s2109 rooted
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
@all: As I imply above the rooting process was free of problems and I have successfully installed CWM. However, after rooting I've run into some other problems:
First:
I rooted before performing a Software update (i.e. I still have the original version 4.0.3). I was planning to make a backup of the system after CWM installation and then update to 4.0.4.
When I try to backup the system using CWM everything works fine until the step "Backing up data..." I get the following messages:
- No /sdcard/.android_secure found. Skipping backup of applications on external storage.
- Backing up cache...
- No sd-ext found. Skipping backup of sd-ext.
- Generating md5 sum...
- Backup complete!
After backing up, I find in the internal sd card 4 files (in total 500K) and a directory called "blobs" with several subdirectories. In total about 2000 files. Is that the backup?
Furthermore, when I try to update to 4.0.4 using CWM, I get the following:
- Finding update package...
- Opening update package...
- Installing update...
- Mount partition
- Verifying current system...
- assert failed: apply_patch_check("/system/app/Launcher2.apk", .....
- E:Error in /sdcard/update.zip
- (Status 7)
- Installation aborted.
If I try to update from the normal system (i.e. outside CWM), CWM stops the update upon reboot.
Any ideas of how to update to 4.0.4 after CWM has been installed?
Second:
I have installed Super Manager from the market. When I try to enable ROOT, I get a message telling that ROOT functions are nor supported in my device. As it could be expected, Superuser does not inform that there is an app trying to get root priviliges, and Super Manager does not appear listed in the superuser's app list.
Third:
It appears that in newer Android builds, it is not possible for third party apps (apps that were not preloaded on the device, but you manually installed or downloaded from Android Market / Google Play) to gain write access to the external SD card. This was not an issue on Android 2.x but it became a problem on Android 3.x.
The implications of this (at least in my cse) is that I can not create folders, copy files or move apps to the external sd card. That even happens with the preinstalled ES Explorer. The solution to this problem is easy if root access is available. One just needs to add the line <group gid="media_rw" /> within the WRITE_EXTERNAL_STORAGE section of the file /system/etc/permissions/platform.xml.
I have pulled the file platform.xml with adb and updated it accordingly. However, I can not push it back because the directory /system/etc/permissions is read only. Any ideas of how to circumvent this problem?
Cheers,
Pisuke
pisuke2012 said:
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
Click to expand...
Click to collapse
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Jittery Jim said:
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Click to expand...
Click to collapse
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Jittery Jim said:
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Click to expand...
Click to collapse
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
pisuke2012 said:
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
Click to expand...
Click to collapse
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Bricked my s2109
Jittery Jim said:
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Click to expand...
Click to collapse
Well, me like the previous people and Jittery Jim above, being too ambitius after rooting s2109 tried JB customs rom's. I did try to flash JB because I have installe CWM V.6.0.1.0 and did make a back up. I used that back-up to restore my ideatab s2109 and it worked fine!
Now after trying to flash JB, which failed :crying:, I can not make a succesfull nandroid back up using CWM . I tried advanced restore and I can restore succesfully : boot , system, cashe, sd-ext, but I can not restore data.
Now my S2109 just boot loop :crying:
Also, I did try the factory reset and it is not working. The same result as boot loop...
Any help available?:angel:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
luckyjay said:
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
Click to expand...
Click to collapse
All I can find is the adb interface driver for the thinkpad tablet, is that the same as the ideapad?
Also, I downloaded the SDK tools but there wasn't an option for Android 4.04 , just 4.0 (API 14) and 4.03 (API 15). Will it go ahead and install the revision for 4.04? (I assume that I'm supposed to install the SDK tools on my Windows 7 Pro 64bit device, though the instructions just say to download them.)
Thanks.
---------- Post added at 02:55 AM ---------- Previous post was at 02:05 AM ----------
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
I downloaded the Android-SDK that was on their site and installed it, but I'll be darned if I can find the files that your instructions say to modify. There's no such directory anywhere on my system. I finally used the exe to install SDK tools thinking that would place the files in the appropriate place but there aren't any. Perhaps the instructions are for downloading the German version? Could you provide a link to the appropriate download site?
Update: I have now downloaded and installed the ADT package and have run the SDK installation standalone (not sure why I need to do both of these steps, but what the heck). I found the correct inf file and did the modifications. However, I did get an error when installing the adb driver so assume I have to install a different fdriver. I have a win7Pro x64 box and am trying to root an S2109 with Android 4.04 installed. I've set the developer tools to enable debugging mode when connected to usb. But is there another adb driver I should download? Is there a driver located on the device itself that might be more appropriate? Again, couldn't find a lenovo s2109 tabet driver, just the thinkpad tablet driver, and it's files don't look right.
Update2: Took a few educated guesses and it worked! I installed the thinkpad tablet adb files after modifying them, by just overwriting the files that were already there. Worked perfectly when it came time to define the drivers and after that it even identified the right device name (rather than Blaze). The rest of it went pretty smoothly. Thanks for updating the instructions on the German site, that was helpful.
Anyone Making progress with CM on S2109?
Or happen to know where there is an active forum discussing the S2109. I also have an HP touchpad running CM9 and it performs much better than my 2109. I'd really love to get CM working on the 2109.
Did this get uploaded?
Otamay said:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Click to expand...
Click to collapse
I'm needing a clean copy of this. I bought a display unit that was monkeyed with and the rom is corrupt on it.
If you would be willing to share it with me please contact me at [email protected].
Thanks.
Has there been any work on getting a Jelly Bean Rom for this tablet? Would be nice if we could get CM10.2.
I am having the "Encryption Unsuccessful" message and cannot break through to a solution. I saw the post above where the user seems to have gotten past the error by formatting the data partition via ADB. Can someone tell me how that was done exactly? I am getting a device not found error when I try to use ADB (from the screen entitled (Encryption Unsuccessful) and I cannot for the of me (or google) figure out how to issue the mke2fs and tune2fs commands!
Thanks to anyone who can help!!!
<<<Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Hi all,
After countless checks on forums and other threads on XDA, I've decided to post this thread as I couldn't find a similar case anywhere.
Situation is I have a TPT from China. Long story short, it was from my company, and when I moved back to Europe I got to keep it.
Anyway, the problem is that it comes with a blocked Lenovo Store, meaning I can't access any of European/US/international apps. Going to Google Play store online doesn't work ("you haven't used any device with this account") - tried from tablet or from computer.
So I thought I would root and install a custom ROM that could enable me to get to the store and personalization/optimization of the device.
I managed to root my TPT thru this thread: http://forum.xda-developers.com/showthread.php?t=1925025
Everything went OK but then I am stuck at the next stage.
If I understand well from this thread http://forum.xda-developers.com/showthread.php?t=1846044, I need to install CWM and then install the custom ROM.
The thread about installing CWM, http://forum.xda-developers.com/showthread.php?t=1831161, just doesn't work, maybe I'm doing something wrong.
If anyone can help it would be very helpful, right now my TPT is just useless...
Thanks all, any help will be very much appreciated.
M0t3l
Here are the specs:
Thinkpad Tablet 32GB
Android version 4.0.3
Kernel: 2.6.39.4-g9b8008b-dirty
Build number: A400_03_0070_0132_SC
Machine Type/model: 183825C
I am on Windows 7 and Mac OSX
Needing a few more details than "just doesn't work"... Are you getting an error message?
Thinkpad Tablet from China
da_reeseboy said:
Needing a few more details than "just doesn't work"... Are you getting an error message?
Click to expand...
Click to collapse
Hi Da Reeseboy, thanks for answering first.
ADB drivers have already been installed on my windows machine in order to root the TPT.
Then at step 3 of the tutorial ("backup your old recovery"), I tried to input the commands into the TPT but nothing happens.
I have installed an application from the chinese lenovo store called SuShell in order to do that (I do speak some chinese). SuShell just tells me "command executed", that's it.
Actually I am not clear if I have an "old recovery" or if it's only for people already with CWM.
So I went on to step 4.
I did copy the file "recovery.img" to an SD card, stick it into the TPT and tried to proceed on the TPT via SuShell again, but when I type in the commands, SuShell tells me "command executed", but nothing happens again.
So I am a little confused if I am doing something the wrong way or typing the commands not thru the right channel or something else.
That's where any help will be very useful.
Thanks again!
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
TPT from China
da_reeseboy said:
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
Click to expand...
Click to collapse
Thanks da_reeseboy, that made it!
I had a few gliches on the way but nothing major that I couldn't overcome.
I did follow the steps on the tutorials and now CM seems to be working fine on the tablet. It seems that a couple of functions on the TPT are either crashing or not working correctly, will try to look into it, but mainly I am now able to access the Play Store and said goodbye to the Chinese Lenovo Store.
Cheers again!
M0t3l
So for Stock A500 users stuck at the Acer Logo, or maybe some other strange issue with the tablet not booting, you may want to try this method first before rolling up your sleeves and moving on to getting your UID, which involves the use of Linux for the most part.
Download these full ICS Update files for the A500 (501 owners can try this also, but you'll have a 500, but that might can be changed later)
These files are already "decrypted" and are named differently as to keep them separate. Download them all to a folder.
Now, select one of them, rename it to "update" (end result is a file called update.zip) copy it to SD card, boot tab and see if it installs. If it hangs on the install, delete it from SD card, and do the same with the next. Hopefully one of them might take. You may have to try all 4 of them before one works. It's hit and miss.
http://d-h.st/Zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/KXl
Mega Links:
https://mega.co.nz/#!lM5iQYLZ!TKx3ZIsN1-L4-Lk2LveHhEjb-PejZ1ZNZPwdsBsuNZM
https://mega.co.nz/#!8R5X3T6C!D-j_EcGhkWyhG8nyprhimcic_uf2chA-rXlnqaLIe7k
https://mega.co.nz/#!sBwwVDQB!cDmVCNH63i-eAMnvtrro7rMGjXDMJPqJbgbXjzX6jDQ
https://mega.co.nz/#!MQhB1L5R!Dj06bqJVgXZ1JAnLGvX1CuUqNs3lXtg8NkxkfbU4osY
Hope this gets you going.
MD
Bricked Iconia A500 working again
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
studioph said:
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
Click to expand...
Click to collapse
How long does it take to load, how long should I wait to try the next one?
gonka95 said:
How long does it take to load, how long should I wait to try the next one?
Click to expand...
Click to collapse
Because it is some weeks ago I can't remember how long it took to load but it was not extreme. I think all was done in 1 or 2 hours. But during the process you get already some info that the tablet is working "normally"
Good luck with trying, my tablet is still working fine
PH
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
megoza said:
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
Click to expand...
Click to collapse
First of course, is that the file must be renamed to just "update.zip" and if you are doing this from a Windows machine, you may not see the ".zip" part. Do not be worried about that and just rename to "update". I copied each file, in turn, to the MicroSD card BEFORE renaming the file. That way, you retain the original and don't end up with "update", "update(1)", update(2), etc.
Have your Iconia A500 fully charged and powered off. Disconnect the power cable. Install the MicroSD, loaded with the "update.zip" file (the gold contacts side of the card face the screen side on the A500) into the card slot in the top of the Iconia A500. Holding the left side of the Volume Switch down, press and hold the Power Button down. When the tablet powers up, release just the Power Button. When you see the writing appear in the top left corner of the screen showing that it is loading the update file, release the Volume Switch. You should shortly see an Android figure with a spinning ball of triangles (not sure of the correct geometric term) in its belly. If the Android changes to laying down, with a red triangular exclamation, that version did not work. You should see a light blue thin progress bar if it is loading.
---------- Post added at 03:14 PM ---------- Previous post was at 03:01 PM ----------
I tried the different files. The "41-124-01-update.zip" loaded, but the progress bar only got about 20% - 25% along the way before not progressing any further. I left it overnight, and in the morning, it was still the same. The ball of triangles is still spinning in the Android's belly, but no progress is happening. The first time this happened, after an hour, I manually powered down the tablet, and then powered it back up. I got the buzz and the ACER logo (constant brightness), but it went no further. It just hangs there. And yes, I tried the external Factory Data Reset, and no, it did not work either!
Any ideas on what might be stopping the progress bar, or how to get the update to completely load?
Has anyone had any luck installing an alternative bootloader and then installing a different image?
Is this a software or hardware issue?
NOTE: My A500 Iconia experienced the exact same issue regarding failure to boot that has been described by hundreds on various forums. I was hoping that I'd finally discovered a fix.
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Aelliseu said:
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Click to expand...
Click to collapse
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
lahor said:
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
Click to expand...
Click to collapse
Well, they will run on a 501, but you won't get 3g or GPS.
www.acer.ru has the 501 ICS update files. You will need to match the update to your current Operating System Build. The reason, is that they run "patch" updates. So if you've been running a custom ROM, you will need to roll back to a factory 3.x.x and use the matching update file.
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Thank you so much!!!! You save my tablet!!!!:good: :good:
Aelliseu said:
Thank you so much!!!! You save my tablet!!!!:good: :good:
Click to expand...
Click to collapse
I did?
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
lahor said:
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
Click to expand...
Click to collapse
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Moscow Desire said:
So for Stock A500 users
MD
Click to expand...
Click to collapse
I used these update.zip's to upgrade my 4.0.2 to 4.0.3. Great, but I can't get adb to recognize the A500. Is there a trick to this?
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
rasmith3530 said:
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
Click to expand...
Click to collapse
Get your CPUID here, using Ubuntu.
http://forum.xda-developers.com/showthread.php?t=1751978
Download the following Timmy Deans 3.2.1 rollback tool and extract to your PC;
https://mega.co.nz/#!FFoxzRLY!fSmY49VDxCdr-hwv6Tw7GPLIzUQNOzSgDzmzAspwmNc
Run the PBxxx.exe and use administrators rights, Wait till it gives the pop up to put your tab in apx mode and do it and connect. Enter uid number.
Hope it works. Remember that acer no longer has ota servers, for a year now, so you will have to do a manual update.
Thanks for the information MD. I will try this and report back here my results.
Moscow Desire said:
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Click to expand...
Click to collapse
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
lahor said:
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
root[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
Click to expand...
Click to collapse
Moscow Desire Thanks!
I have know Jellytime 4.3 on my tablet.Need a 10 days to make this. In the beginnig everything was difficult but now it seems so simple and easy.
My description for more clarity:
1. UBUNTU last version
2. In this version you have a GCC but not libusb-1.0-dev. The best option is synaptic package manager. Install this from UBUNTU software center.
Open the synaptic and search the all files with libusb -you will get the list with the required files . Just install the all!
3.Make or download apx.c. If you have 32 bit you can use code from this site (something about printif changing). Make the folder APX on Dekstop and put file apx.c there .
4. Open the terminal ( if you can not find the terminal(no experience with UBUNTU , just in search type terminal).
5. In the terminal type dir or ls,. You can see the all folders and then type
cd Desktop/APX. If you get something strange or you get no result try to type sudo su for "refresh"
6. type gcc apx.c -o apx -lusb-1.0
7. If you get message with errors this mean that your libusb 1.0 dev is not installed. If you see a new file apx near your old file apx.c then is OK
8.type ./apx .....(if you get the message acces denied or cannot open device just type sudo su for refresh)and your CPUID is there.
9. then you need SBK
10. Download V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip and unzip this
11.Make APX mode on your tablet ( push reset button(with needle) then power(with finger ) ) everything is black(that's good) and you are ready.
12. open the V8-UNL-ICS-HC-bootloader-MULTI-cwm with V8.bat file, and follow instructions. Use your SBK, choose option 2 and go next(two times). When you get PASS on your tablet your tablet is ready.
13. Download the jellytime 4.3 with GAPPS to your microsd. from
http://forum.xda-developers.com/showthread.php?t=2376662 or HC 3.2 for ( in my case) A501 from this forum
no need to change name to update.zip .
14. The next step: Volume down +power (you are going to the recovery mode) and folow the instructions
Boot in recovery mode to flash theJellytime or HC3.2.
First, don't forget to execute a 'Wipe Data/Factory reset'
Flash the Jellytime
Flash the Gapps
Do a 'wipe cache partition'
Reboot
15. That's it!
16. Enjoy!