Related
Axioo PICOPAD QGN
Android OS, v2.2 Frozen Yogurt
Qualcomm MSM7227 (App: ARM11 600MHz)
This wont work on PICOPAD 9
This is a very unpopular device from Indonesia. Although it is very easy to Root using "Superoneclick". As more people got hold of this free set(via Singapore old Starhub Internet plans), more people are also starting to ask about the steps on rooting this device. I thought I should start a guide here where I've followed from different places, piece them together here.
Feel free to comment and share if there are other ways to root, flash and install custom roms or android version. More importantly over clocked kernels. (remember seeing a link at kwbr's thread)
There are similar sets "CSL Spice Mi700 DroidPad", "Viewpad 7", etc
Alternatively you could research more by heading on to Viewpad 7's thread as I found out that device is very much similar and more developers are active there. I've also tried flashing kwbr's rom and it works for me.
Well if you are going to follow this thread to root, then read on...
WARNING! You warranty is now VOID & I will not be responsible if you brick your device.
Click to expand...
Click to collapse
Sections:
1. Rooting your device (wiki)
2. Installing Clockwork recovery (wiki)
3. Setting up ADB (optional)
4. Setting up partition on SDcard to free up device main space (WIP)
1. ROOT & Busybox (comes in a package)
Use these steps to root with "SuperOneClick". (Thanks to SuperOneClick)
Download and install "SuperOneClick"
Alternatively, download older version (some say works better) 1.6.5 1.7.0
Make sure you have .NET Framework v2.0 for Windows XP(win update)
On picopad, Unmount your SD card. From settings -> sd card -> unmount
Enable USB debugging, Setting -> Applications -> Development -> tick USB Debugging
Connect picopad to Pc via usb, ignore pctools if popup.
Goto Windows Explorer, Picopad will appear as "CD-ROM", explore CD-ROM and run SETUP.exe, ignore pctools
Open "SuperOneClick"
Change the option from "psneute" to "rageagainstthecage"
Click Root.
Rooted , Superuser & Busybox installed
Mount back your SDcard if u wish and reboot your device at least twice.
Congrats! Your device is rooted!
If you are satisfy with only root and superuser access, then you can stop here.
If you would like to install(flash) Clockworkmod recovery so you can backup your device(nandroid) and flash rom/kernel/stuff easier, proceed to step 2. (Highly Recommended)
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
2. ClockworkMod Recovery 5.0.2.6
2a. Preparing to installing CWR
Download CWR 5.0.2.6 and Flash_Image
Unzip, then copy "flash_image" and "cwm5026.img" to the root of your sdcard. (if you don't know how.. take your SDcard out and use a card reader)
Power on the device and install a terminal app so you could type commands in, try Android Terminal or Terminal Emulator
Once installed, open the app and start typing:
Gain superuser access type
su (once in superuser, you will see "#")
Click to expand...
Click to collapse
copy flash_image to system/bin
cp /sdcard/flash_image /system/bin
Click to expand...
Click to collapse
Install the flash_image
chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
Backup your original Recovery
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
Click to expand...
Click to collapse
And if you ever want to restore back for warranty issues
flash_image recovery /sdcard/orirecovery.img
Click to expand...
Click to collapse
2b installing ClockworkMod Recovery 5.0.2.6
The previous ver 2XXX is pretty outdated, thanks to mb-14 for sharing 5026.
Now you are ready to flash ClockworkMod Recovery
Assuming the file name that you download from CWR is "cwm5026.img" Type
flash_image recovery /sdcard/cwm5026.img
Click to expand...
Click to collapse
Done!
Now to run Clockwork Recovery:
First, turn off your device.
Now, hold down both volume button and press the power button at the same time, when you see recover on the corner of the screen, you can let go as you will boot up in Clockworkmod Recovery.
How to use 5.0.2.6 CWR?
Use the device vol+ and [/b]vol- to move up and down or the soft keys menu for "down", home for "up"
Select options by pressing the power button or , use the soft keys search for "enter"
back is for "back".
When you load into CWR, you could do many stuff, some simple info on the main options,
Wiping data is resetting your device to factory default, but CWR remains as long as you do not flash a stock recovery or a rom with a different recovery inside.
You could do stuff like formatting and partitioning SDcard to prepare for Apps to be install in SDcard to save space in device. Other than that, you could do a Backup for your entire device which is also known as nandroid backup, but it doesn't backup the bootloader and radio, so take note if you are going to flash custom radio or bootloader.
If you have a backup, you could restore back to that backup, this is good if you accidentally flash something bad or dislike a rom
Fixing permission is good if you always have FC.
You can mount SDcard to your pc from here and manage files with from your PC.
You could use ADB to push / pull files in and out of your device from PC.
you could install other roms, kernel and files using the "install zip" option.
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
3. Installing ADB on your windows
Download and install Latest JAVA SE Development kit "JDK" and Android SDK.
Follow the steps here on installing ADB, Android Debug Bridge.
3a. SET PATH for ADB: Check if you had set the path to sdk platform tools folder, this is to run adb command from any path. Steps for Windows XP:
Right-click ‘My Computer’ and click ‘Properties’.
In the ‘System Properties’ window, click the ‘Environment Variables’ button on the ‘Advanced’ tab.
Find ‘Path’ in the ‘System variables’ section and double-click it to edit it.
Make sure NOT to delete the existing entry in ‘Variable value’.
Just add the following string to the end of it, including the semi-colons:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools;C:\Program Files\Android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
Start ADB shell to command picopad from your pc:
Make sure Picopad is connected to pc via USB and sdcard is mounted.
From PC, Goto command prompt (Start -> Run type "CMD")
Type "ADB devices" from command prompt ( to see if path is set and picopad is connected, you should see 1 device attached, not more, not less)
C:\Documents and Settings\tish>adb devices
List of devices attached
FM88888888888 device
Click to expand...
Click to collapse
Troubleshooting:
If you can't get the adb command to work, probably you didn't set the path correctly, refer back to SET PATH or go to your adb actual folder to type the command which should be here C:\android-sdk-windows\platform-tools\
3b. Using ADB
At recovery or booted up device, on Pc Type:
adb shell (you will see "$")
Click to expand...
Click to collapse
now access superuser type
su (allow superuser access from Picopad and you will see "#")
Click to expand...
Click to collapse
Here you can copy files using (push/pull), I recommend you google for ADB commands to have a better understanding.
4. More sections to come eg: The space problem on the device, so alternative is partitioning sdcard to install apps as to free up space in device........
You could buy me a beer if you really appreciate my work here.
Updates from Fri the 21th April 2012
Reorganizing error section
Adding missed out steps here and there
Placing direct link for faster downloads
Added 2 older ver. SuperOneclick which works better
Removed CWR 2.5.1.2 details since it's outdated.
Added some details on 5.0.2.6 CWR
Updates from Fri the 13th Jan 2012
Added CWM 5.0.2.6 and soft keys steps.
Added possibility to explore Viewpad 7's dev forum.
Included some wiki info on root and CWR(Clockworkmod Recover)
Added troubleshoot for Set path to android sdk adb folder.
Included ADB set and using step
I first rooted my Picopad using guides from hucqim80, however they are not meant for Picopad and I've gather the info and posted them here.
Original recovery image provided by jax79sg here
This is to recover original recovery and replace clockworkmod recover.
This step is done because you need to send your set for warranty repair probably.
Remember to do a factory reset first before replace with original recover.
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
I will upload mine somewhere after i try your steps above.
sure, thanks
axioo picopad.
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
did u go to cd-rom folder and execute setup.exe before u click superoneclick?
No , I did not run the setup.exe from the cdrom drive cos when i plugin the device it automatically ask me to do the PC syncing. Actually i tried that before but that din work either.
I ran both PC running win7 and winXP, both also stuck at Running psneuter ...
Hi,
I ran into this error which puzzles me greatly.
# flash_image recovery /sdcard/cwrecovery.img
flash_image recovery /sdcard/cwrecovery.img
flash_image: permission denied
Do you know how to resolve this?
Thanks in advance.
Warmest Regards
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
same with me....anybody can give another tips ?
try to turn on picopad usb first. then try to ru he setup in picopad identified as " cd-rom" try again
Sent via Picopad
is there any custom ROM compatible for this device ?
help
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
can this Stock ROM modified for support with App2sd by Trkton ?
Vuska said:
can this Stock ROM modified for support with App2sd by Trkton ?
Click to expand...
Click to collapse
It supports without any modification in the first place.
Roms, probably the MI700's custom rom will work, get to hucqim80's signature, the link is there.
nhasir said:
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
Click to expand...
Click to collapse
probably ur file is not in that directory for this error message to appear.
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
Okay, i know your problem... just change the option in superoneclick from psneuter to rageagainstthecage... and then root it...
when the superoneclick start to not responding, just re root it using the same method....
then to enable your superuser, install z4root to your device
I managed to root the picopad and flashed as stated.
When i boot up pressing both power and vol button, i was brought into this FTM mode. And from there i can't do anything...... the screen looks as follows.
Hmm....the cwrecovery didn't get flashed?
SWVer=3.240
MODEL: FM6-0001
HWVer:106
Power on with pressing VOLUME_DOWN keys to leave Auto FTM.
[Resolved]
Try holding both up and down volume buttons instead of just one of them
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
jax79sg said:
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
Click to expand...
Click to collapse
Im still using my picopad.
Thanks!
Sent from my Nexus S using XDA App
can anyone help me with original backup for the splash and welcome screen axioo pico pad?
my pico pad splash and welcome screen change to viewsonic because i install viewpad 7 ROM in to my pico pad.....
somebody....help me please !!!
thankyou
[MOD][One Click Root]ClockworkMod version 3.1.0.1[RFS & EXT4]
One Click Root does NOT work on Gingerbread!Read on for why.
Standard disclaimer: I think you guys know the deal by now. I am not responsible for anything you do, don't do, don't read, or brick.
If you are already rooted and have ClockworkMod installed and you just need to upgrade CWM please visit DRockstar's thread: [RECOVERY][GPL] ClockworkMod 3.1.0.1 PURPLE UPGRADE RFS/EXT4/USB CUSTOM FOR EPIC4G
This is an updated and refreshed One Click Root based off Dameon87's 3.0.0.6 version here (originally based off work from noobnl and firon). It has been updated and fixed by myself (Rodderik) and DRockstar.
Huge credit goes to DRockstar. Without his persistence and hard work we would not have a new working recovery image. He spent many hours fixing and testing the image after bugging koush to compile a ROM Manager compatible, dual file system recovery. Credit also goes to the noobnl and firon for the original one click root scripts, koush for giving us a new better recovery, Dameon87 for his one click changes and EXT4 conversion script, tanimn and all the other developers that worked hard to contribute to the new recovery.
UPDATED 6/24/2011
updated to Clockwork Mod 3.1.0.1_purple by DRockstar
updated busybox to latest (1.18.4)
updated recovery.fstab
tweaked script to hopefully improve success rate
fixed redirector (again)
plus some other misc fixes
Includes:
Dual file system support (RFS & EXT4)
New ClockworkMod (v3.0.2.5)
koush's latest hacked adbd
Superuser.apk (v2.3.6.1)
busybox (v1.18.0.git)
su (v2.3.1-ef)
Switched to bmlwrite for flashing
Added scripts for mounting UMS (by DRockstar)
FIXED REDIRECTOR!!!
Rom Manager Compatible
Works properly on Mac OSX
Tested with EC05 (Froyo), EB13 (Froyo), and DI18 (Eclair)
Works on: Windows, Linux, and Mac OSX
For future reference the rageagainstthecage root exploit has been patched in Gingerbread. Refer to DRockstar's post on Gingerbreak for rooting Gingerbread (this also works on the Epic running Froyo)
Instructions:
Windows
1. Extract zip to a folder
2. Ensure phone is in usb debugging mode and connected to your computer
3. Run the run.bat
4. Follow on screen instructions
Linux
1. Extract zip to a folder
2. Ensure phone is in usb debugging mode and connected to your computer
3. Open a terminal and navigate to the unzipped folder
4. Type: chmod 777 run.sh
5. Type: ./run.sh
6. Follow on screen instructions
Mac OSX
1. Extract zip to a folder
2. Ensure phone is in usb debugging mode and connected to your computer
3. Open a terminal and navigate to the unzipped folder
4. Type: chmod 777 run.sh
5. Type: ./run.sh
6. Follow on screen instructions
qbking77 has done a nice video tutorial on using Windows to root and install ClockworkMod using this method. You can see his video here: http://www.youtube.com/watch?v=ymN1H2e9YMk
Thanks qbking77!
dansan382 also made a video that you can find here.
Notes:
1. Button mappings are slightly different from older versions of CWM. Volume buttons = Up and Down, Power or Camera = Enter, Capacitive Back = Back. Capacitive Home also works as enter but not correctly from the main menu so if you hit it and the screen disappears hit Capacitive Home again or Capacitive Back to bring it back.
NOTE: As of 3.1.0.1 the buttons have been sorted out.
2. KNOWN ISSUE: When invoked, reboot recovery requires a re-plug of the usb cable for adb to work again. Simply unplug the usb cable and plug it back in.
3. If the script does not reboot your phone at the end please run the script again. If it still doesn't work reboot the phone and run the script again.
4. USB Mass Storage can be mounted from inside of recovery. 'adb shell' into the phone and type 'mountums' MAKE SURE YOU SAFELY REMOVE/EJECT BEFORE RUNNING 'umountums' to safely unmount sdcard.
NOTE: As of 3.1.0.1 mounting from the menu works again!
5. There is a Go Back menu option but it must be enabled. See the post here.
6. VIRUS ALERT!!! rageagainstthecage may be detected by your antivirus program but it is NOT harmful to your computer. See this post for an explanation.
7. A few users report issues with 3.1.0.1 not booting. If that happens then use 3.0.2.5.
Download: http://devphone.org/files/epic4g/oneclickroot/OneClickRootCWM3.1.0.1-EC05.zip
md5: 57d787dba5a478eb088f148e0dff2ef0
Previous version(s): http://devphone.org/files/epic4g/oneclickroot/OneClickRootCWM3.0.2.5-EC05.zip
EXT4/RFS Conversion:
For converting RFS to EXT4 or EXT4 to RFS please see this post by chris41g: Rfs2Ext4 and Ext42Rfs CWM 3.0.25 flashable zips. These will work fine with ClockworkMod 3.1.0.1
k0nane said:
FYI, the EXT4 conversion script is not necessary if you are flashing a ROM that properly formats to EXT4, unless you plan to keep data (which isn't recommended coming from stock anyway, use MyBackup Root if you must). Currently, only SRF, Bonsai, and the journal-off version of midNIGHT (I have not checked 5.3) do this. Other ROMs only use delete_recursive() in their updater-script - so flashing them will work, but you'll get RFS!
Click to expand...
Click to collapse
If you are flashing a new rom please make sure you check or ask if you need to take additional steps to convert your filesystem.
Here is sample output from a run in Linux. Windows and Mac OSX should be similar. You may or may not get "sudo: adb: command not found" but it is ok so long as the script runs correctly. Getting the error is dependent on how your environment is set up. If you get any other errors you will need to run the script again.
[email protected]:~/Desktop/OneClickRootCWM3.0.2.5-EC05$ ./run.sh
One Click Root & CWM 3.0.2.5 for the Epic 4G
Updated and tweaked by Rodderik and DRockstar 5/10/2011
Original one click by joeykrim and one click installer by noobnl and firon
busybox by skeeterslint
Huge credits go out to:
koush - dual fs recovery binary
DRockstar - recovery kernel build
Press any key to continue...Starting adb server
sudo: adb: command not found
sudo: adb: command not found
Copy and run the exploit (may take up to two minutes)
98 KB/s (5392 bytes in 0.053s)
0 KB/s (43 bytes in 0.044s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2662, 2662}
[*] Searching for adb ...
[+] Found adb as PID 2974
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
96 KB/s (4793 bytes in 0.048s)
Copying files onto phone...
499 KB/s (26264 bytes in 0.051s)
2097 KB/s (196521 bytes in 0.091s)
2048 KB/s (927544 bytes in 0.442s)
6 KB/s (327 bytes in 0.052s)
Setting permissions...
Installing busybox...
Installing clockworkmod redirector
108 KB/s (6535 bytes in 0.059s)
push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery.fstab
push: recoveryfiles/sdparted -> /system/bin/recoveryfiles/sdparted
push: recoveryfiles/mountums -> /system/bin/recoveryfiles/mountums
push: recoveryfiles/umountums -> /system/bin/recoveryfiles/umountums
push: recoveryfiles/fix_permissions -> /system/bin/recoveryfiles/fix_permissions
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
push: recoveryfiles/tune2fs -> /system/bin/recoveryfiles/tune2fs
push: recoveryfiles/recovery_wrapper -> /system/bin/recoveryfiles/recovery_wrapper
push: recoveryfiles/nandroid-md5.sh -> /system/bin/recoveryfiles/nandroid-md5.sh
push: recoveryfiles/killrecovery.sh -> /system/bin/recoveryfiles/killrecovery.sh
push: recoveryfiles/e2fsck -> /system/bin/recoveryfiles/e2fsck
push: recoveryfiles/parted -> /system/bin/recoveryfiles/parted
push: recoveryfiles/adbd -> /system/bin/recoveryfiles/adbd
push: recoveryfiles/postrecoveryboot.sh -> /system/bin/recoveryfiles/postrecoveryboot.sh
14 files pushed. 0 files skipped.
1538 KB/s (2018303 bytes in 1.280s)
push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery.fstab
1 file pushed. 0 files skipped.
8 KB/s (515 bytes in 0.060s)
push: recoveryres/images/progress_bar_empty_right_round.png -> /system/bin/recoveryres/images/progress_bar_empty_right_round.png
push: recoveryres/images/icon_clockwork.png -> /system/bin/recoveryres/images/icon_clockwork.png
push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_error.png
push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/indeterminate2.png
push: recoveryres/images/progress_empty.png -> /system/bin/recoveryres/images/progress_empty.png
push: recoveryres/images/progress_fill.png -> /system/bin/recoveryres/images/progress_fill.png
push: recoveryres/images/progress_bar_fill.png -> /system/bin/recoveryres/images/progress_bar_fill.png
push: recoveryres/images/icon_firmware_install.png -> /system/bin/recoveryres/images/icon_firmware_install.png
push: recoveryres/images/progress_bar_empty_left_round.png -> /system/bin/recoveryres/images/progress_bar_empty_left_round.png
push: recoveryres/images/icon_firmware_error.png -> /system/bin/recoveryres/images/icon_firmware_error.png
push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/icon_installing.png
push: recoveryres/images/progress_bar_left_round.png -> /system/bin/recoveryres/images/progress_bar_left_round.png
push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/indeterminate3.png
push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres/images/progress_bar_right_round.png
push: recoveryres/images/progress_bar_empty.png -> /system/bin/recoveryres/images/progress_bar_empty.png
push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/indeterminate6.png
push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/indeterminate4.png
push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/indeterminate5.png
push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/indeterminate1.png
push: recoveryres/keys -> /system/bin/recoveryres/keys
20 files pushed. 0 files skipped.
78 KB/s (81069 bytes in 1.010s)
Installing clockworkmod recovery...
794 KB/s (66884 bytes in 0.082s)
3213 KB/s (5478824 bytes in 1.664s)
Cleaning up files...
sudo: adb: command not found
All done!
If your phone did not reboot or root does not
work correctly. Please rerun the script.
Press any key to exit the script.
[email protected]:~/Desktop/OneClickRootCWM3.0.2.5-EC05$
Click to expand...
Click to collapse
Thats pretty baller!!! Thanks hotrod!!
Hehe, it's about time, this needs sticky at top of the dev board!
Great work, Rodderik spent some time learning root and the cwm redirector, to make this happen.... I think we both have tweaked it out, so that anyone on any computer can use it, now
I've been waiting for a single solution for a long time now, so I'm very glad to see it happen.
DRockstar said:
Hehe, it's about time, this needs sticky at top of the dev board!
Great work, Rodderik spent some time learning root and the cwm redirector, to make this happen.... I think we both have tweaked it out, so that anyone on any computer can use it, now
I've been waiting for a single solution for a long time now, so I'm very glad to see it happen.
Click to expand...
Click to collapse
Yeah buddy! I couldn't have done it without your work and help. Thanks a bunch and I can't wait for the AIO.
Rodderik & drockstar, you both rock and thank you.
If 3.0.2.8 that comes in bonsai doesn't workout for me, its nice to have another option......thanks again
Nice work........
Rodderik said:
EXT4 Conversion (and RFS soon):
If you want to convert to EXT4 you can use this script from Dameon87. There are two ways you can use it. Please read the all the steps below before attempting conversion. Failure to read all the steps ahead of time and putting all the files needed on your sdcard can result in an unbootable device.
Click to expand...
Click to collapse
So I have a suggestion that 'may' help w/ this..
my wife's Transform has a version of CWM that has an integrated terminal option in the main menu. you open terminal and type "RFS" or "EXT4" into the window w/ the keyboard and it will auto convert to either file system..
I'm not sure how they do this, but I'm wondering if during the install of CWM, maybe you can push the required files to the SD card and make menu options that will perform the operations using the files that were pushed to the SD card during install ??
I don't know a whole lot about this stuff, but It was something that popped into my (sometimes filled w/ cob webs) head. LOL..
Excellent work BTW
FYI, the EXT4 conversion script is not necessary if you are flashing a ROM that properly formats to EXT4, unless you plan to keep data (which isn't recommended coming from stock anyway, use MyBackup Root if you must). Currently, only SRF, Bonsai, and the journal-off version of midNIGHT (I have not checked 5.3) do this. Other ROMs only use delete_recursive() in their updater-script - so flashing them will work, but you'll get RFS!
EDIT: And, lots of credit to tanimn for tireless hard work on this project.
Wow. You guys never seem to amaze me. Thank you all. Thanks for your input ko about the roms doing this. That will help save people a step. You guys rock man.
Btw... this should be a sticky
Sent From My Evo Killer!
k0nane said:
FYI, the EXT4 conversion script is not necessary if you are flashing a ROM that properly formats to EXT4, unless you plan to keep data (which isn't recommended coming from stock anyway, use MyBackup Root if you must). Currently, only SRF, Bonsai, and the journal-off version of midNIGHT (I have not checked 5.3) do this. Other ROMs only use delete_recursive() in their updater-script - so flashing them will work, but you'll get RFS!
EDIT: And, lots of credit to tanimn for tireless hard work on this project.
Click to expand...
Click to collapse
Quoted your post in the OP and added tanimn to credits. Thanks K0nane for pointing this out.
@Rodderick, or DRockstar, quick question please.
I installed per your instructions. Then once I rebooted, I installed RomManager. But I reboot into recovery from within RomManager, it takes you to cwm-3.0.0.6. Isn't it supposed to take you to cwm-3.0.2.5? Also, is the cwm3.0.2.5 in DRockstar's thread the updated version of cwm3.0.2.5? If not, can we get a flashable .zip of the updated cwm3.0.2.5 please?
sniperkill said:
I installed per your instructions. Then once I rebooted, I installed RomManager. But I reboot into recovery from within RomManager, it takes you to cwm-3.0.0.6. Isn't it supposed to take you to cwm-3.0.2.5? Also, is the cwm3.0.2.5 in DRockstar's thread the updated version of cwm3.0.2.5? If not, can we get a flashable .zip of the updated cwm3.0.2.5 please?
Click to expand...
Click to collapse
if you install rom manager and click flash clockworkmod recovery and select epic4g it says that the epic doesn't have an officially supported cwm yet but allows you to manually say yes and this should allow rom manager to work...this is all we can do until koush gets back in town to make the change to rom manager for us but he did compile this cwm recovery binary for us so it is official. it just required some tweaking by DRockstar and tanimn and a few of the other devs to get it all working correctly.
Rodderik said:
if you install rom manager and click flash clockworkmod recovery and select epic4g it says that the epic doesn't have an officially supported cwm yet but allows you to manually say yes and this should allow rom manager to work...this is all we can do until koush gets back in town to make the change to rom manager for us but he did compile this cwm recovery binary for us so it is official. it just required some tweaking by DRockstar and tanimn and a few of the other devs to get it all working correctly.
Click to expand...
Click to collapse
Thanks for the quick reply. But yes, I did do all that with RomManager, but it still takes me to cwm-3.0.0.6. But, if I shut it down, then 3 fingure boot, that takes me to cwm-3.0.2.5... Also, I greatly appreciate all the hard work you guy's do, so dont take me wrong, i'm deffinatly not complaining.. I love all the work you guys do!!!
sniperkill said:
Thanks for the quick reply. But yes, I did do all that with RomManager, but it still takes me to cwm-3.0.0.6. But, if I shut it down, then 3 fingure boot, that takes me to cwm-3.0.2.5...
Click to expand...
Click to collapse
what kernel are you using? if the kernel hasn't been updated and you flashed after the one click process then rom manager will boot whatever recovery comes with your kernel. 3.0.2.5 should still be one bml8 for 3 finger boots unless the rom reflashes that as well. run the one click again now after you are all setup and rom manager should boot into 3.0.2.5
Rodderik said:
what kernel are you using? if the kernel hasn't been updated and you flashed after the one click process then rom manager will boot whatever recovery comes with your kernel. 3.0.2.5 should still be one bml8 for 3 finger boots unless the rom reflashes that as well. run the one click again now after you are all setup and rom manager should boot into 3.0.2.5
Click to expand...
Click to collapse
Nice catch, I didnt even think about that. And yes, I did flash midnight-5.3.. So, imma have to figure another route.
On another note, does this OneClickRoot cwm-3.0.2.5 work with the official EC05?
Also, if you run the OneClickRoot cwm3.0.2.5 more than once, does it just overwrite the previously written files from running it the first time?
sniperkill said:
Nice catch, I didnt even think about that. And yes, I did flash midnight-5.3.. So, imma have to figure another route.
On another note, does this OneClickRoot cwm-3.0.2.5 work with the official EC05?
Also, if you run the OneClickRoot cwm3.0.2.5 more than once, does it just overwrite the previously written files from running it the first time?
Click to expand...
Click to collapse
i think i just got a bad flash testing this for you...i loaded eb13 and will ota to EC05 but it was tested to work.
Rodderik said:
i think i just got a bad flash testing this for you...i loaded eb13 and will ota to EC05 but it was tested to work.
Click to expand...
Click to collapse
Im sorry man, you dont gotta do that for me, as I'm sure I'll figure it all out. I'm pretty good at most of this kinda stuff. Fix your phone and keep up the great work buddy!!
sniperkill said:
Im sorry man, you dont gotta do that for me, as I'm sure I'll figure it all out. I'm pretty good at most of this kinda stuff. Fix your phone and keep up the great work buddy!!
Click to expand...
Click to collapse
it's all good...i did the OTA to EC05 again and verified the one click root does work. being as how the OTA is odexed I know my kernel refuses to boot it as ext4 (its the only scenario it wont boot) i'm going to restore my nandroid and rerun the one click but we might have to wait until kernels are updated
i'll let you know shortly
ok so i figured out we should just wait until you favorite kernels update to the new CWM as to keep the issues to a minimum. you can try to run the one click again but it all depends on how your favorite kernel handles recovery. the safest bet will be to wait until they have a chance to update them.
The information provided in this thread is no longer up to date, although useful troubleshooting information can be found for those having issues. For those who would prefer to have the most up-to-date versions of CM9, CM10 or ParanoidAndroid supported by an awesome developer, go here
WARNING: IF YOU UPDATE YOUR TABLETS TO THE LATEST v03 UPDATES OF THE OFFICIAL ROM, YOU WILL LOSE THE ABILITY TO ROOT IT USING THE SUPERBOOT METHOD AND IT WILL BECOME A HUGE PAIN TO RE-INSTALL CWM/CUSTOM ROMS. INSTRUCTIONS FOR THIS SITUATION ARE PRESENTED BELOW, BUT PLEASE KEEP THIS IN MIND AND TRY TO READ THE THREAD CAREFULLY BEFORE MAKING SUCH CHANGES.
For those who need it, you can find a nandroid backup of Vodafone Romania's stock ROM for the v71a, here
Hello friends. With great thanks to utkanos, Koush and mobilx we now have a public alpha CWM and root available on both the ZTE V11A and the V71A, also known as the SFR StarTab 7/10, Vodafone SmartTab 7/10, as well as Sprint's (ZTE) V55 with credits due to utkanos for porting CWM, mobilx for being arguably the most motivated searcher of the holy root grail, and PaulOBrien from modaco and his superboot solution. We also thank alterbridge86 and eldarerathis for their advice and support. Additionally, credits go to joe.stone for custom kernel with loop device support, OC, touched voltages and a few other goodies.
Also, for interested developers, I have made the source code of the kernel available in a more easily accessible fashion. The source code (3 parts, contains the source for both models) is available here:
Part 1, Part 2, Part 3.
INSTALLING CWM:
A new optimized version of CWM for 7"and 10" tabs has been put together by joe.stone. I will also keep utkanos' links available below for those who prefer his versions or wish to thank him for his early efforts in making our tablets awesome
joe.stone said:
For those who have troubles with cwm recovery (freeze while backup ) i have created a new version. Flashable from fastboot.
10" CWM Recovery
7" CWM Recovery
Credit goes to joe.stone.
Click to expand...
Click to collapse
joe.stone said:
If you updated your tablet ROM via OTA or updater exe and can no longer install CWM, follow the following instructions:.
In firmware v03b fastboot flash is disabled and from a running system flash_image will fail too.
Download the twrp recovery http://goo.im/devs/joestone/twrp/v71_recovery.img
download the twrp recovery zip flashable version too
http://goo.im/devs/joestone/twrp/V71A_TWRP.zip
download kernel #60
http://www.4shared.com/zip/tzrUo5_N/v7_kernel_60.html?
copy the two zip files to the sdcard
If you want flash kernel#60 then do the following:
adb reboot bootloader
the tablet will reboot and you will get only a blank screen . Be sure that the drivers are installed from windows update for the fastboot interface.
check it with : fastboot devices. If you get waiting for device the drivers are not installed.
fastboot boot v71_recovery.img
The twrp recovery comes up. Now you can install twrp by selecting install menu. Browse to the v71twrp.zip on the sd and install it. Now you have permanent twrp recovery.
now go back to install menu browse to the v7_kernel_60.zip and install it.
reboot and enjoy.
These are kernel #60 links for the other models :
Sprint Optik (V55)
http://www.4shared.com/zip/RTZrSXyV/v55_kernel_60.html?
SmartTab10 (V11A)
http://www.4shared.com/zip/PrW1TWHF/v10_kernel_60.html?
OR
You can flash cwm using adb , you need root rights .The best is when adbd is running in root mode (for eaxample kernel#60).
Download this :flash_image binary
then turn on usb debugging.
to flash cwm you need the following commands:
adb push CWMrecovery.img /data/local/tmp
(where cwmrecovery.img is the name of the cwm image file name.)
adb push flash_image /data/local/tmp
adb shell chmod 755 /data/local/tmp/flash_image
adb shell (you need # not $ for flashing , so if you got $ type su to get #)
cd /data/local/tmp
./flash_image /dev/block/mmcblk0p18 CWMrecovery.img
Dont forget to remove the install-recovery.sh file from /system/etc othervise it will install stock recovery at system start if it has not the stock recovery.
To revert the bootloader you need to flash NON-HLOS.bin"to "/dev/block/mmcblk0p1" and "emmc_appsboot.mbn" to "/dev/block/mmcblk0p7" from a previous version .
Click to expand...
Click to collapse
Utkanos' v11a version is here.
Utkanos' v71a version is here.
Credit goes to utkanos, mobilx and koush. I have also attached these files at the end of the post.
Also attached, is the original 7-inch stock recovery file, for users who may wish to return to stock and have not performed backup.
--> Plug your tablet into usb, launch a command line, and use "adb reboot bootloader"
--> Download the CWM Recovery image from the link that fits your device.
--> Place it into the adb/fastboot folder (I am assuming you have downloaded fastboot already from the link above, during the root procedure).
--> In the command line, navigate to that folder (use "cd <path>").
--> input the command "fastboot flash recovery <filename>".
--> Reboot into recovery mode (should be Power + Volume down).
--> You should now be in CWM Recovery, and can now attempt to perform a nandroid backup.
Also, in order to prevent a possible hang, you should:
--> Reboot the tablet into the Android OS;
--> Mount it through USB;
--> Go into the clockworkmod folder;
--> Create an empty file with no extension called ".hidenandroidprogress"
After a period of testing this will be submitted to the Koush's Rom Manager. Source code is also available herehere, linked from utkanos' post.
What works:
Nandroid backup/restore on internal sdcard
Battery stats wipe
Dalvik wipe
Cache wipe
etc.
What does not work so far:
USB mass storage
credits:
utkanos
Koush
Click to expand...
Click to collapse
Modified Kernel Available, all credits to joe.stone, give him thanks here:
joe.stone said:
Here it is.
There is a new kernel version available. The new version is #60 and flashable from cwm recovery .
Changelog :
-Revert GPU overclock
-Revert change of system audio files (because of bootloops on some devices after installation #55)
-Increased system volume on kernel level
-Changed VMALLOC_RESERVE=0x19000000 to VMALLOC_RESERVE=0x10000000
-Added Apple Magicmouse HID support
-Added Microsoft HID support
-Changed cpu minimum freq 345MHz to 432 MHz to avoid the black screen effect (the screen does not wake up , you have to reset )
V55_kernel_60.zip Hope will work fine on v55.
V7_kernel_60.zip
V10_kernel_60.zip
Click to expand...
Click to collapse
Also, Benny3 has put together a CWM-flashable ROM package for the V55 tablet, including Joe's kernel #60 and a number of useful goodies. You can thank him and download the package from here.
Both device (v71, v11) were migrated into one kernel tree , so they both use the same source. (In case of v71 it is much newer source)
The whole kernel source was updated from the v55 sources .
Now they are in cwm recovery flashable format , because this package updates the kernel modules too in /system/lib/modules and enables to use the agps and NTP server setting was corrected . It points to europe.pool.ntp.org instead of the test one . Now my tab finds position within seconds . With the new kernel for me it seems the touchscreen is much better , but as before I am waiting for the feedbacks. Other fixes include: Touchscreen sensitivity, USB Charging etc.
Installation :
download the zip file
copy it to your tab's internal storage
start the tab in clockworkmod recovery
select install zip from sdcard
select the file for your model
install
reboot
and stock kernel for 10" :
stock kernel[/QUOTE]
Finally, if you want to obtain a dump of boot.img, please consider the following advice, also by mobilx, here:
mobilx said:
It is a mmcblk device not mtdblock
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
Click to expand...
Click to collapse
ROOTING:
mobilx said:
It is recommended that you skip these steps and proceed to flashing clockwork mod for your respective device from the start using fastboot, and from inside CWM install joe's kernel (or custom rom), which you can find below. Joe's kernels and rom already come with significant updates to stock Vodafone systems, and are pre-rooted.
We will use superboot to root. What does superboot do? It puts the SU binary and makes a 'insecure' kernel to be loaded temporarily on to the device through ADB remount. So it's only purpose is to make ROOT. After execution, you will still be on the stock kernel, only with root privileges.
This method is for the advanced users only who want to have root before we have a fully functional CWM running. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What will you need?
--> Download Fastboot+Superboot.img from here.
--> Install ADB through the SDK, download from here, although the ADB included with the ZTE drivers should also work.
--> Install the ZTE drivers, you can find them here, although they should already be included on your device when first mounting it.
--> don't forget to enable USB debugging in the tablet's application settings.
--> Put the fastboot.exe and the superboot.img files in the working directory you will be running adb from (Default should be at "C:\Program Files\ZTE Handset USB Driver".
--> Open a Command Line (Start Menu > Run > CMD) and navigate to the working directory. (Use "cd C:\Program Files\ZTE Handset USB Driver" or alter the path accordingly).
--> Write the following commands withing the command line:
--> adb reboot bootloader
--> fastboot boot superboot.img
--> The device should now boot with the Superuser.apk installed and SU in the /system/xbin/su, as well as allowing you adb root commands. Now run the following:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
--> You can now exit the ADB shell and reboot the tablet.
--> Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution
Click to expand...
Click to collapse
Reserved for future posts
I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.
assdksl said:
I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
Click to expand...
Click to collapse
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.
Click to expand...
Click to collapse
Haven't looked for it, but so far accessories for this line of devices seem to be lacking. With the popularization by Vodafone and the launch of the new Sprint V55 and similar tablets, these accessories should become more popular.
I haven't had any problems with the time on my device, sounds really weird.
assdksl said:
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Click to expand...
Click to collapse
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.
Thank you both for quick answering my questions.
mobilx said:
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.
Click to expand...
Click to collapse
Yes, indeed, but when I untick sync with Network-provided time, clock is ticking faster then it should.
It seems that clock chip on my device is not calibrated well or there is some other bug, it seems that it is HW issues... this is little more explained here:
http://blogs.keynote.com/mobility/2...wrist-watch-android-doesnt-keep-the-time.html
It seems that I was unfortunate and get device with bad clock, also without root I'm unable to use ClockSync app that will solve my problem.
But what is bugging me, is the fact that I also have SGS I9000, and it is synchronizing with Vip network just fine.
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
Click to expand...
Click to collapse
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.
assdksl said:
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
Click to expand...
Click to collapse
Yes it happend to me once. First I unticked the network-provided time sync and after restart I ticked it again. The clock is fine since than.
assdksl said:
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.
Click to expand...
Click to collapse
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
These are some of the useful bits of advice I received that could probably be put to good use when I have some free time. If you feel that anything is helpful, feel free to try it out.
sangemaru said:
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
Click to expand...
Click to collapse
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Click to expand...
Click to collapse
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
assdksl said:
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
That's fine. We have a dev utkanos who agreed to build the CWM for our device. He is very experienced in this stuff. The only way to build a proper CWM is to get a boot.img dumped or extracted from a leaked ROM.
So what we need to do:
Get root via some exploit (there is none for 3.2 HC yet) , dump boot.img and build CWM, flash CWM with fastboot, or
Find leaked ROM , extract boot.img, build CWM, flash CWM with the fastboot, root device with Update.zip
Yes the fastoboot is working and the bootloader is unlocked.
I have tried these exploits so far:
GingerBreak
psneuter
zergRush
Also I have tried:
Acer iconia 100 method ADB
Acer iconia 500 method
All ideas are welcome.
Ladies and gentleman the ROOT is here Device is successfully rooted with the superboot method.
Thanks to my friend sangemaru who made this possible.
Expect CWM soon. utkanos is working on it.
Need some testing, before this goes to public
That's great news mobilx! Looking forward to a root and ICS sometime in the future
Congrat`s guys,nice work and many thanks from all users.
This is a beginning of a beautiful friendship with SmartTab
We expect nice custom roms and maybe in a short time and ICS rom for this excellent tablet.
If I or we (other members) can help with something,please,let us know,i dont know programming but i can use Paint (just kidding)
Jeeej!!! I'm looking forward to it!
Ok lets roll
While we are waiting for CWM to be build we can root ZTE V11A/V71A aka Vodafone SmartTab 10/7 with the superboot.
What the superboot does? It puts SU binary and makes a 'insecure' kernel to be loaded temporally on to device( ADB remount). So it's only purpose is to make ROOT. After reboot you are on your old kernel but with the root.
This method is for the advanced users only who want to have root before we build a CWM. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What we need?
ADB installed through SDK
Zte drivers installed --> debugging ticked in options
fastboot + superboot.img --> Put files in the adb working dir
>adb reboot bootloader
>fastboot boot superboot.img
Device should boot with Superuser.apk installed and SU in the /system/xbin/su.
>adb remount
>adb shell
#ln -s /system/xbin/su /system/bin/su
Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
#exit
$exit
>adb reboot
Device will reboot with the stock kernel but rooted.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution
Thx mobilx! Hvala
All it's OK
It's working also on v71a.......LOL
10x man
urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
I can also confirm this working on 7 inch
urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
jakaka said:
I can also confirm this working on 7 inch
Click to expand...
Click to collapse
That is great guys. sangemaru will be very happy because he owns A71A
So you can confirm that it boots and the touchscreen is working? That means the kernel is the same for those two variants.
V17A
YES, all work perfectly...........setcpu, blackmarkt,root uninstaller, lucky patcher, etc
The only differences between v11a and v71a is the size of the display
we are wating for CWM..........10x again
v71a
Hi,
I am new to this forum that is the reason for asking this question in this section but I have a experience in scripting, rooting, modding and (un-) bricking different hardware.
Ok, I am a new owner of a Acer A511 (it's like A510 but with 3G) and tried to root it like this description in this Thread.
If I start the script runit-win.bat I am getting the following output.
Code:
Full root for A100, A500 and A510 ICS. Simple method.
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tmp/su
push: tools/runit.sh -> /data/local/tmp/runit.sh
push: tools/mount.sh -> /data/local/tmp/mount.sh
push: tools/mempodroid -> /data/local/tmp/mempodroid
push: tools/getroot.sh -> /data/local/tmp/getroot.sh
push: tools/delroot.sh -> /data/local/tmp/delroot.sh
push: tools/busybox.sh -> /data/local/tmp/busybox.sh
push: tools/busybox -> /data/local/tmp/busybox
8 files pushed. 0 files skipped.
1044 KB/s (840355 bytes in 0.786s)
1174 KB/s (37273 bytes in 0.031s)
-
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root! :(
-
Error!
-
Press any key.
Ok, I took a look to the scripts and I think the command "/data/local/tmp/mempodroid 0xd9f0 0xaf47 sh /data/local/tmp/getroot.sh" doesn't work. I opened a shell "(Windows Shell) adb shell" and executed the command "/data/local/tmp/mempodroid 0xd9f0 0xaf47 sh" and also the command "/data/local/tmp/mempodroid 0xaf47 sh" for getting a single root shell but it doesn't work. If I try to do a reboot via shell I am getting the message "reboot: Operation not permitted".
Also I have deactivated the pre installed Anti Virus (Mc Affee) on tablet. I have no idea anymore but it seems to me that the exploit mempodroid doesnt't work for me or my FW version.
<edit on>
With my HTC Desire HD I had to unlock the bootloader and to install the Clockwork Mod. I understand the description by ZeroNull for rooting the Acer A5xx that this isn't a prerequisite. Is this correct?
<edit off>
Informations
HW: Acer A511
Acer APN-Version: 1.203-1(t)
Flex-Version: Acer_AV041_A511_1.028.00_EMEA_DE
Do you have some ideas more or can you move this problem to the correct thread so I am nearer to solve the problem!?
Best regards
Hi.
To prevent a crossposting can a moderator/admin move this posting to http://forum.xda-developers.com/forumdisplay.php?f=1211 please?
I am not be able to delete my own posting so Idon't want to post it a second time.
I haven't saw this section and I think is the better to place the question there.
Best regards and thank you in advance.
@Mod, please move to http://forum.xda-developers.com/forumdisplay.php?f=1648
Btw, I've also confirmed it does not work. Also tried finding other offsets (with n95-offsets) and tested with those as well, but still no root.
I'm afraid the exploit has been fixed in the A511, and we'll have to wait till someone builds a fixed kernel...
Your ROM seems newer than the only one I found (Acer_AV041_A511_1.011.00_WW_GEN1). You may want to try and downgrade (although my ROM is even much older than that). I don't want to upgrade yet before I can find a way to make a full backup (cwm recovery doesn't work either).
nikagl said:
Btw, I've also confirmed it does not work. Also tried finding other offsets (with n95-offsets) and tested with those as well, but still no root.
I'm afraid the exploit has been fixed in the A511, and we'll have to wait till someone builds a fixed kernel...
Your ROM seems newer than the only one I found (Acer_AV041_A511_1.011.00_WW_GEN1). You may want to try and downgrade (although my ROM is even much older than that). I don't want to upgrade yet before I can find a way to make a full backup (cwm recovery doesn't work either).
Click to expand...
Click to collapse
Thanks, that somebody recognize the posting.
I will take a look for a downgrade it. If it possible to downgrade it without root access and cwm.
Best regards
Well... for A511 I found a way! First cwm recovery and then root update zip. See the following thread:
http://forum.xda-developers.com/showthread.php?t=1729432
WARNING. THIS is ONLY for tablets running ICS. If you are running Jelly Bean, You May Brick your device!!
Again, this is for ICS ONLY!
Running this root on a Jelly Bean OS can cause your tablet to stop functioning as it is designed for ICS only. If you have a Jelly Bean Operating system, then please use Vorbeth's or Moscow Desire's Easy Root Package located in the Development Forum. If you do not know which OS you currently have, then you should ask questions before rooting.
Method 1. Universal for A700 and A701 Tablet
1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
3. Download arhive. Unpack it to any place.
4. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
runit.bat
Your firmware is now rooted.
5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
------------------------------------------------------------------------------------------------------
Method 2. With the patched kernel from the A700 tablet
For ICS A700 firmware only!
1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
3. Download this arhive. Unpack it to any place.
4. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-ICS-patchedBoot.bat
Your boot.img is now patched and firmware is now rooted.
5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
6. Now you will have to install the following programs:
BusyBox
Titanium Backup
7. Run BusyBox and go through the install steps. During this SU should ask permission to give BB root access, if it does, it worked!
------------------------------------------------------------------------------------------------------
Method 3. From CWM recovery for A700 and A701 Tablet - Not available due to problems in the work of CWM recovery!
1. At the tablet must be installed CWM recovery.
2. Download arhive ICS_Rooting_recovery.zip. Put it on SD-card. Insert the SD-card in the tablet.
3. Run CWM recovery on the tablet and flash ICS_Rooting_recovery.zip.
Your firmware is now rooted.
4. Now you will have to install the following programs:
SuperUser
Titanium Backup
At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
------------------------------------------------------------------------------------------------------
Method 1, in contrast to method 2, does not affect the core of the system. This makes it possible to receive future firmware update. But only if you do not forget to make backups before making changes to the system and restore it before upgrading.
PS: I tried to make a method 1 as safe as possible. But I have not had a chance to test it completely. So if it does not work, be sure to let me know in this thread and I modified it.
great work ! Thank you for this :good:
BTW the the script is called "flashpboot.bat" and not "flash-ICS-patchedBoot.bat" in the archive.
Really great thanks for it.
Just a question, can it be unrooted/undone by flashing 028-stock rom?
Gesendet von meinem A700 mit Tapatalk 2
KruSan said:
Really great thanks for it.
Just a question, can it be unrooted/undone by flashing 028-stock rom?
Gesendet von meinem A700 mit Tapatalk 2
Click to expand...
Click to collapse
yes
the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo
moom999 said:
the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo
Click to expand...
Click to collapse
same problem here
moom999 said:
the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo
Click to expand...
Click to collapse
Rename Acer_AV043_A700_1.028.00_EMEA_FR to update.zip and put it in an external sd card.
There's a startup mode that installs it automatically, you have to press the left volume+power buttons at startup if I remember well.
alx5962 said:
Rename Acer_AV043_A700_1.028.00_EMEA_FR to update.zip and put it in an external sd card.
There's a startup mode that installs it automatically, you have to press the left volume+power buttons at startup if I remember well.
Click to expand...
Click to collapse
you missunderstand, they mean, when you have 1.028 you cant flash the patched bootloader because they stuck onn boot screen
No problem to flash again Acer_AV043_A700_1.028.00_EMEA_FR or Acer_AV043_A700_1.025.00_EMEA_CUS1
The problem the patch doesn’t work with any of this two rom
moom999 said:
No problem to flash again Acer_AV043_A700_1.028.00_EMEA_FR or Acer_AV043_A700_1.025.00_EMEA_CUS1
The problem the patch doesn’t work with any of this two rom
Click to expand...
Click to collapse
The size of the patched bootloader seems wrong, I guess that's why it's faulty.
OK, so how do we fix this ??
Edit, reflashed with update.zip, so all OK, phew !
Cannot reproduce with Acer_AV043_A700_1.028.00_EMEA_FR !
Just stays at Acer logo with unlocked bootloader and forces me to re-install as update.zip which leaves me without root.
Which Firmware is working ?
Has anybody allready tested with which firmware this method is working and with which not ??
Be careful, same issue on NORMAL french firmware, not the crappy totally unknown one everybody seems to like, so i guess that's it : this patch STUCK YOUR TABLET ON ANY KNOWN FIRMWARE THIS FAR
Okay, so i just tried to push insert the superuser.apk into the Acer_AV043_A700_1.028.00_EMEA_FR file and flashing this, but as i was expecting, it didn't work out... it didn't even install.
edit: i can confirm, that it does neither work with the Acer_AV043_A700_1.028.00_EMEA_FR, nor the Acer_AV043_A700_1.025.00_EMEA_CUS1 !
so, i guess we have to wait for ZeroNull to come up with another way to get this to work.
Flashboot.bat not responding
I unlock my bootloader with Blackthund3r's A510 Bootloader Unlocker v1.0.0 and go the "unlocked" status. Rebooted the tablet, went into the patched-boot folder and ran as administrator "flashboot.bat". The screen displayed a bunch of what looks like gibberish and when I pressed the Enter key, the screen went to :
"Flashing patched boot.img
<waiting for device>
Then the process just sits there and doesn't go any further. Am I missing something in what I am doing?
---------- Post added at 02:27 PM ---------- Previous post was at 02:18 PM ----------
I used Root Checker Pro to verify root and here is what the app displayed:
"Root Access is not properly configured or was not granted.
Superuser Application Status:
Superuser application - version 3.0.7 installed!
(I had downloaded and installed this from the Market after the first attempt failed)
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1"
Anybody got any ideas on what to do next?
Thanks!
You have to reboot into bootloader for the script to work.
But if you had read the comments above, you might have seen, that the described method does not yet work and several people state, that after flashing the Boot.img the device is stuck in boot.
Gesendet von meinem A700 mit Tapatalk 2
Just to be clear : This method specific to A700 does not work at all yet BUT this WORKS PERFECTLY with the A701 patched rom ZeroNull released at the same time
check this post for the a701 patched rom, you don't need to put it on sdcard it includes BAT files to flash it all from bootlader
http://forum.xda-developers.com/showpost.php?p=27742776&postcount=39
Hello jpearn or doanb555,
With which release of the "update.zip" you can restore your Iconia Tab A700 ?
thx
spoque said:
Hello jpearn or doanb555,
With which release of the "update.zip" you can restore your Iconia Tab A700 ?
thx
Click to expand...
Click to collapse
i'm not jpearn or doanb555 but what kind of question is that ? you got only two roms, both are working. what's your point ?