Database Info

[REF] Axioo Picopad QGN (Root, Busybox, CWR, etc)

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

Pantech Sky Vega Racer IM-A770K room, recovery,update zip etc

friends here you can find Pantech Sky Vega Racer IM-A770K room, recovery, update zip etc.

Friends
I bought used SKY IM-A770K phone from our local market and used it, although it is with android 2.3.3 but it is really great phone. At first I use Samsung I900, HTC HD, Xperia Arc, I9000 etc. but it gives me more and more pleasure. It is a greeeeeeeeeeeeeeeeeeeeeeeeeet phone.
There is no third party custom rom or kernel found.
I request to XDA developers and other XDA community please works on that phone and create custom roms and kernels for it
I found Pantech SKY IM-A770K update zip, clockworkmod Rom, root, USB drivers and recovery from a china’s website bbs.xda.cn/forum-507-1.html here is a complete forum part on IM-A770K and A760s. You can translate this site using goole chrome.
I also up load these files on mediafire. These links are here. You can also download from mediafire.
SKY_UniUSBDriver_v3.6.6
mediafire.com/?grae6s0x9130y94
UniUSBDriver_v355
mediafire.com/?pgjltz97wkgoitj
a770k root zip
mediafire.com/?q8ipw1xd4aec3e3
VegaRacer-kdh4865-cwm-v101 recovery
mediafire.com/download.php?34rfp6stg34jmj5
770K update zip
A770Kupdate.part1
mediafire.com/?a9ybdy3hc7ye5aa
A770K Rom
A770K clockworkmod rom.part1
mediafire.com/?ogqugupqqensqja
A770K clockworkmod rom.part2
mediafire.com/?8mlsd74fju3h29u
And also download these files from these direct links but these sites are in Chinese.
For update Zip
bbs.xda.cn/thread-10905022-1-1.html
for complete Rom
115.com/file/bhtcie50%20#clockworkmod (1). rar

Need original GB firmware for Sky Vega Racer IM-A770K
Hi amunaf.
Thanks so much for posting those links for the Sky Vega Racer IM-A770K. I also have such a phone. I like it too very much too because of the fast CPU and its large screen.
Unfortunately I am now in a dilemma. When I got this fone, details of the "about phone" were as follows:
Android version - 2.3.3
Baseband version - S0833144.TP15.R1090
Kernel version - 2.6.35.7.perf [email protected] #2
Build number - GINDERBREAD
Board and Software version - MSM8260_SURF V1.44
I was so happy being able to root with the above specs using SuperOneClick v2.3.2
Right after rooting and rebooting the phone, I received a message reminder from SKY (seen at the taskbar) saying there was an OTA update available for download. I then proceeded with the OTA download and upgrade and noted the file for download was only 13MB. Thought the download was quite quick, the file being loaded to my phone unusually took to a long time (almost 30mins to load) and I wondered why since the downloaded file was only 13mb. I noted the following changes on the "about phone" after the upgrade or patch:
Android version - 2.3.3
Baseband version - S0833144.TP15.R1090
Kernel version - 2.6.35.7.perf [email protected] #1
Build number - GINDERBREAD
Board and Software version - MSM8260_SURF V1.47
After the OTA upgrade I then proceeded to again root the phone using the same SuperOneClick v2.3.2. Unfortunately, the rooting process always stalled on step 7 and again I tried several times but no luck. I already tried several rooting apps including the link you gave which uses fastboot but still no luck. There is now an update to SuperOneClick which is v2.3.3 but unfortunately still could not root.
I am recommending all those who are still on software version 1.44 to avoid that update in case they intend to root their Racer.
I'm now thinking if there is firmware out there at that Chinese site you had recommended if they have a version 1.44 for download. I am having a hard time translated that Chinese site, moreover that when I attempt to download any file. though I can't understand the Chinese commands, I'm sure the site was requiring me to enter a user name and password which is impossible for me to do and navigate the Chinese site.
Hoping you could help me on with my dilemma.
And that XDA developer gurus could make us a nice custom rom for the IM-A770K.

Rooting update 1.47
Hi
I was also upgrading my phone from 1.45 to 1.47. After upgrading I was also unable to root my phone then I use VR root to root my phone and successes with V1.47. you can download Vr root zip from here
mediafire.com/?a00ct1cofzbaag9
un zip it on your C: drive then using CMD load rooting.exe before it your phone is plug on to your computer and debugging mode must checked.
This method will install busy box, Superuser and su shell on your phone. You can uninstall the applications using unroot.exe

Hi amunaf,
Thank you again for your assistance. Unfortunately VRRoot via its rooting/unrooting.exe still didn't work for my A770K. Please see the rooting messages below:
The A770K is still DISCONNECTED with these messages:
C:\>rooting
C:\>adb remount
C:\>adb push busybox /data/busybox
C:\>adb shell chmod 6755 /data/busybox
C:\>adb push su /system/bin/su
C:\>adb shell "chown 0:0 /system/bin/su"
C:\>adb shell chmod 6755 /system/bin/su
C:\>adb shell /data/busybox ln -s /system/bin/su /system/xbin/su
C:\>adb push Superuser.apk /system/Superuser.apk
C:\>adb shell chmod 644 /system/Superuser.apk
C:\>adb shell mv /system/Superuser.apk /system/app/Superuser.apk
C:\>adb shell rm /data/busybox
C:\>adb reboot
The A770K is already CONNECTED with these messages
C:\>rooting
C:\>adb remount
remount failed: Operation not permitted
C:\>adb push busybox /data/busybox
C:\>adb shell chmod 6755 /data/busybox
Unable to chmod /data/busybox: No such file or directory
C:\>adb push su /system/bin/su
C:\>adb shell "chown 0:0 /system/bin/su"
Unable to chmod /system/bin/su: No such file or directory
C:\>adb shell chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\>adb shell /data/busybox ln -s /system/bin/su /system/xbin/su
/data/busybox: not found
C:\>adb push Superuser.apk /system/Superuser.apk
C:\>adb shell chmod 644 /system/Superuser.apk
Unable to chmod /system/Superuser.apk: No such file or directory
C:\>adb shell mv /system/Superuser.apk /system/app/Superuser.apk
failed on '/system/Superuser.apk' - No such file or directory
C:\>adb shell rm /data/busybox
rm failed for /data/busybox, No such file or directory
C:\>adb reboot
I also tried fastbooting and the process just stops and stalls with no activity at all after sending the boot.img.sk.insecure file
C:\>sk
C:\>adb reboot bootloader
C:\>fastboot boot boot.img.sk.insecure
BTW I've already wiped cache partition, wipe data/factory reset and wipe internal sd partition. Unfortunately doing all that did not help. What do you think will happen if I initialize sd partition? I tried it before but it was cut short because my battery was went dead and that process I'm guess could take around 3-4 hours.
I'm still hoping there's still a way to root my phone.
Thanks a lot for the effort and help you've extended!

installing custom rom
You root it again with custom rom using this method below and after rooting use VR rooting. I hope it will work for you.
It also work even your phone brick or do nothing.
Steps:
1 Turn off the phone
2, while holding down the Volume Up (+) button, power button and search button three key until the boot. Screen will display "S / W Download" message.
into the sky's official website, (skyservice.co.kr/jsp/info/DownSW.jsp) find the USB driver just said that the download page, there is an option (vega racer im-770K (upgrade version 1.47)
to upgrade this system is self-vega, vega is popular to say the rom package itself. But can not download, install only online.
3. install USB drivers
The emergence of an icon and a S / W Upgrade after , plug in a USB port on the computer
4: Go to web address:
(dmfile.isky.co.kr/NewSelfUpgrade/index.html)
Note: for above web site use “internet explorer” browser other browser may be not work
Than will be prompted to install the plugin, click to install!
5: Wait for the icon from gray to pink
this process is relatively long, about 10 minutes or so. Until the progress bar has completed, the phone will automatically restart. This phone will return to factory state.You install the program will be cleared away flies, including the root before the operation. But the good news is that the content is still the phone book, photos, still. . .
At this step, your phone seems to back you just start state, then you have to do is to repeat the beginning of the operation of this tutorial. Re-root, again carefully delete unnecessary procedures, may once again face the risk of bricking again ... until the perfect resume ... so
After this you can root you phone via VR rooting

Success!
Hi amunaf,
I want to thank you with all my heart for being so helpful, patient and for the effort you did for the tutorial in solving my dilemma. My vega is finally again rooted! Though I encountered some problems such as a drained battery, slow inerconnect connection during download process (it took around one hour and fifteen mins. to download), etc. To make a long story short, in addition to the live firmware download from SKY, the SK.exe you pointed to download which vame with Vrroot also helped root the phone.
Thank you so so much more power to you!

Hi Guys,
I'm a newbie using a Vega Racer IM-A770K. Could you step by step guide me how to upgrade S/W, how to enter recovery mode.....
Thanks you so much !!!!

Hello, i have Sky Vega A770K with "too many pattern attempts" !
Please help!

Sky IM-A770K utilities
anthony411 said:
Hi Guys,
I'm a newbie using a Vega Racer IM-A770K. Could you step by step guide me how to upgrade S/W, how to enter recovery mode.....
Thanks you so much !!!!
Click to expand...
Click to collapse
Sky Vega Racer IM-A770K utilities
To go into RECOVERY MODE
1. Turn off phone
2. Simultaneously press:
VOLUME DOWN BUTTON
SEARCH BUTTON
Lastly POWER BUTTON
3. Release all three buttons when the SKY VEGA boot logo appears
4. When Android character w/ white triangle (with exclamation point inside) appears, press the MENU soft key (lower left side of the phone’s front face). The Android system recovery menu should appear
5. To choose a function, use the up/down volume buttons on the left side of the phone
6. To select and activate a function, press the SKY soft key
To go into Soft/Ware download mode
1. Turn of phone
2. Simultaneously press:
VOLUME UP button
MENU button
And lastly press the POWER button
3. S/W Upgrading will now flash on the screen
To upgrade firmware to version 1.47, you first need to download and install the USB drivers. You can get it directly from this site:
mediafire.com/?pgjltz97wkgoitj
Or from the Sky site:
http://www.isky.co.kr/sw/swdownloa...oftware/USB&filename=UniUSBDriver_v355[2].zip
When you reach the above page, there will be a java script with two identically sized boxes (Ignore the smaller box beneath the right box). Clicking the right side box will bring up the download box. Save file to computer.
4. After you have installed the drivers, test your phone’s connection to the computer to initially determine all the required drivers were installed properly. But before doing this, make sure that you have activated USB DEBUGGING on your phone.
>settings
>applications
>development
>usb debugging (must be checked)
5. Using Microsoft Internet Explorer v9, proceed to this page:
http://dmfileidc.isky.co.kr/NewSelfUpgrade/index.html
Notice when that page opens, it will prompt you to install ACTIVE X. Allow that installation to proceed.
6. After ACTIVE X has been installed, notice on the left side there is a phrase noting USB with some Korean characters. Underneath that phrase is a clickable rectangular PINK box. If that box is instead colored gray with a rotating circle, that might mean ACTIVE X did not load or install properly. Or you might be using a different browser or maybe something else. Notice the GRAY box is NOT clickable.
7. Clicking the PINK box will turn it into a progressing lavender bar. At this point, put phone into S/W download mode (volume up/ search /power buttons) and connect the A770k to the computer. Notice the characters on top of the progress bar may change and at this point there is communication between the phone and the Sky download site. It may take a few minutes for the phone to establish a download connection between Sky’s services. Once a connection is established, the characters above the progress bar will turn into a progressing percentage bar starting from 1% and ending into 100%.
There will be two phases of the progressing percentage bar. The first phase is downloading the software while the second is loading the v1.47 software into the phone. After the 2nd phase, the phone will automatically reboot. The first phase will depend who slow or fast your internet connection is. My download took around an hour.
As most tutorials here at XDA say, I take no responsibility if something goes bad after performing the above procedure. Do at your own risk. I’ve done this twice and so far so good.

A high performance-price ratio machine
Seems this is a machine that can draw xiaomi（a very hot machine in china mainland) from a so-called best performance-price ratio position. But as you know, software also play very important role in a phone system.

hi everyone ,
I have a Sky Im A 690s. I use the app " gingerbreak" to root and it worked, now my phone rooted. but I can find any recovery and dont know how to flash recovery. anyone know please help me

Hi Guys,
I got a problem when rooting by VRRoot same as Astro49. After upgrade new firmware via OTA (V1.47) then my IM-A770K cant be rooted by VRRoot. So can you guys help me the way to root my phone step by step.
Thanks you

anthony411 said:
Hi Guys,
I got a problem when rooting by VRRoot same as Astro49. After upgrade new firmware via OTA (V1.47) then my IM-A770K cant be rooted by VRRoot. So can you guys help me the way to root my phone step by step.
Thanks you
Click to expand...
Click to collapse
When you downloaded VRRoot, there were also 3 executable files that came with it. KT, LG and SK. With your phone connected to the computer and also necessary drivers installed, run SK but making sure USB debugging is also checked. Then after that process, run again rooting. Hope it'll work for you 'cause that worked for me when I also upgraded to 1.47 via OTA then could anymore root. Good Luck!

I've loaded CWM based recovery by @KD4865 v5.0.2.7 but my nandroid backups dont work. My phone always restores to its factory state. I've already made several backups but every time it goes back to phone's original settings as in I would have to setup from scratch and all my apps and personal data are gone. What could I be missing or doing wrong???

astro49 said:
When you downloaded VRRoot, there were also 3 executable files that came with it. KT, LG and SK. With your phone connected to the computer and also necessary drivers installed, run SK but making sure USB debugging is also checked. Then after that process, run again rooting. Hope it'll work for you 'cause that worked for me when I also upgraded to 1.47 via OTA then could anymore root. Good Luck!
Click to expand...
Click to collapse
Finally, My A770K has been rooted by VRRoot. Thanks you so much

how do root my device? a770s fw 1.47. I unknow about VRRoot. I used SK.exe => screen back to Fastboot Mode. Next stept?

Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
zongsheng said:
how do root my device? a770s fw 1.47. I unknow about VRRoot. I used SK.exe => screen back to Fastboot Mode. Next stept?
Click to expand...
Click to collapse
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted

anthony411 said:
Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted
Click to expand...
Click to collapse
How long is PC install new device complete? Can you help me through teamview?

anthony411 said:
Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted
Click to expand...
Click to collapse
don't install file rooting.exe after install file SK.exe????

[ROOT + CWM + OC KERNEL + Ubuntu] ZTE V11A / V71A / v55 HC3.2

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

[Q] Busybox Normal Install Failed - su not found, phone has been unrooted.

Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem

BLU Advance 5.0 HD

It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.

So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.

I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good

@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.

mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.

sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.

I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works

Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26