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
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 ?
Hello everyone, it's my first post.
I have a strong desire to install Paranoid Android on my phone, one of the first things I did to accomplish this was root my phone.
Note, I don't remember how I rooted my phone, just that I did and executed a root checker to confirm that it was successful.
After rooting I began watching a video tutorial but found myself stuck at the boot screen, unable to proceed.
Here is the above mentioned video: http://www.youtube.com/watch?feature=player_embedded&v=a3pof_WSEEI
Still clueless, I reached out to Reddit for a better guide. It seemed that the video I was watching had assumed I had done certain steps which I had not, so I tried to learn what preliminary steps were necessary.
I was then referred to the following link: forum.xda-developers.com/showthread.php?t=1843585
I began to review all the content and started completing the steps one by one, but I got stuck.
When it came time to bring up my identifier token and submit it I was told that I failed somehow.
It was at this point when I noticed that my boot screen says; *** TAMPERED ***, *** LOCKED ***.
Interestingly enough, the boot screen in the above mentioned video tutorial does not say the same messages as mine, so I thought "herein lies the problem".
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
I tried running the program, as instructed, but failed.
Now I feel stuck, I didn't feel compelled to post here before, but now I do. I really just want to get what I want done ASAP.
I would greatly appreciate any and all help you can offer.
First of all, do a search for the "How to do everything to your HTC One X" thread in this forum. I think its best if you study this guide and go step by step to first unlock your phone, root it and then install whatever ROM you want. This is the best guide that I've ever seen on exactly how to accomplish this and its very very newbie friendly..
SirVivi said:
Hello everyone, it's my first post.
I have a strong desire to install Paranoid Android on my phone, one of the first things I did to accomplish this was root my phone.
Note, I don't remember how I rooted my phone, just that I did and executed a root checker to confirm that it was successful.
After rooting I began watching a video tutorial but found myself stuck at the boot screen, unable to proceed.
Here is the above mentioned video: http://www.youtube.com/watch?feature...&v=a3pof_WSEEI
Still clueless, I reached out to Reddit for a better guide. It seemed that the video I was watching had assumed I had done certain steps which I had not, so I tried to learn what preliminary steps were necessary.
I was then referred to the following link: http://forum.xda-developers.com/show....php?t=1843585
I began to review all the content and started completing the steps one by one, but I got stuck.
When it came time to bring up my identifier token and submit it I was told that I failed somehow.
It was at this point when I noticed that my boot screen says; *** TAMPERED ***, *** LOCKED ***.
Interestingly enough, the boot screen in the above mentioned video tutorial does not say the same messages as mine, so I thought "herein lies the problem".
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/H...OneXUnroot.zip
I tried running the program, as instructed, but failed.
Now I feel stuck, I didn't feel compelled to post here before, but now I do. I really just want to get what I want done ASAP.
I would greatly appreciate any and all help you can offer.
Click to expand...
Click to collapse
First, Root! http://forum.xda-developers.com/showthread.php?t=1709296
Second, Unlock Bootloader! http://forum.xda-developers.com/showthread.php?t=1672284
Third, Custom Recovery! TWRP Only, Install Goo Manager from market and install from there is easiest.
Make a nandroid of your current ROM (stock I assume) them you can flash PA.
Hope this helps.
You've made some big mistakes. I see from your other posts your device is the HTC codename EVITA (Snapdragon S4 version of the phone):
SirVivi said:
I was then referred to the following link: http://forum.xda-developers.com/show....php?t=1843585
Click to expand...
Click to collapse
Your link is busted, but I fixed it, to see where it points: http://forum.xda-developers.com/showthread.php?t=1843585
That's the wrong forum. Its from the international (Tegra3) version of the One X, codename ENDEAVORU. Completely different hardware. Flashing things, or following guides meant for the Tegra3 version will fail, and may brick your device.
You need to stick to the subforum for our (Snapdragon S4) version: http://forum.xda-developers.com/forumdisplay.php?f=1538
In particular, our Development subforum: http://forum.xda-developers.com/forumdisplay.php?f=1541
And to see all the resources in an organized list, check out my index thread (sticky at the top of Development): http://forum.xda-developers.com/showthread.php?t=1671237
SirVivi said:
I found some instructions, which I cannot find anymore, and downloaded an application to unroot my HTC one X.
Here is the above mentioned file I downloaded: http://downloadandroidrom.com/file/H...OneXUnroot.zip
I tried running the program, as instructed, but failed.
Click to expand...
Click to collapse
Link is busted, so I can't see what it actually points to. But I'd strongly caution against flashing/running things downloaded from random websites, unless you have good knowledge of what you are looking at, and have some reason to believe its a reputable source. Do yourself a favor and stick to this forum (many of those random websites just steal content from XDA, anyway). Even if the content is legit, other websites are not well organized (EVITA versus ENDEAVORU), and contain a lot of content meant for the international One X, which will damage your phone. Everything in our XDA device subforum (as I've linked above) is meant for our version, and known to be safe.
You're pretty lucky you haven't bricked your device at this point, as you've already applied several things not meant for our phone. My advice would be to follow the recommendations in the post above mine. Root, SuperCID, and unlock the bootloader, using the links he supplied (also found in my index thread I've linked above).
bimmernut318 said:
First, Root! http://forum.xda-developers.com/showthread.php?t=1709296
Click to expand...
Click to collapse
I started the process, it instructed me to "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
However, it does not explain how to do so.
SirVivi said:
I started the process, it instructed me to "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
However, it does not explain how to do so.
Click to expand...
Click to collapse
Do some reading here: http://forum.xda-developers.com/showthread.php?t=1754018
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Also, what carrier version is your phone (AT&T, Telstra, etc)?
And what firmware version (Settings>About>Software information>Software number)?
First, I repaired the links.
Next, my phone is AT&T and my software number is: 1.85.502.3 710RD
Finally, I just discovered that the adb tool is located under C:\Android\android-sdk\platform-tools
I'm currently reading the "Gunnyman's quick and dirty adb/fastboot primer" link you posted.
Note, I had to google to find out where the adb tool was located, the guide did not explicitly say where it would be.
Now that I know the the directory where the adb tool was stored, I think I can proceed with the following instructions: http://forum.xda-developers.com/showthread.php?t=1709296
PS: I need to go to work now, but I will be back at around 8:30 PM CST
SirVivi said:
Next, my phone is AT&T and my software number is: 1.85.502.3 710RD
Click to expand...
Click to collapse
Then you should be good to go with the links that bimmernaut318 gave above. Just wanted to make sure we were sending you in the right direction.
Good luck. Feel free to pop back on here if you have specific questions. It probably seems a pain to have to read and research all this stuff. But its all good stuff to know, and you will be better in the end for learning it.
---------- Post added at 11:19 AM ---------- Previous post was at 11:15 AM ----------
SirVivi said:
I figured that the reason why my identifier token was rejected is because I rooted my phone, so I proceeded to unroot my phone.
Click to expand...
Click to collapse
Just to clarify, root does not affect unlocking the bootloader. In fact, as you may have already determined, its required (to get SuperCID) in order to unlock the BL.
Unlocking the bootloader failed because the AT&T Carrier ID (CID) is blocked on HTCDev.com thanks to AT&T. Achieving SuperCID is the workaround.
Well, when I execute: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I get the following message:
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
EDIT:
Actually. I think it was successfull... I restored my phone and tried again, got this.
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\Android\android-sdk\platform-tools>adb shell rm /data/data/com.redbend.vdmc/l
ib/libvd*
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb shell ln -s /data/local.prop /data/dat
a/com.redbend.vdmc/lib/libvdmscomo.so
C:\Android\android-sdk\platform-tools>adb shell ls -l /data/local.prop
-rw-rw-rw- root radio 159216 2012-10-20 13:37 local.prop
C:\Android\android-sdk\platform-tools>adb shell "echo 'ro.kernel.qemu=1' > /data
/local.prop"
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Android\android-sdk\platform-tools>adb push su /system/xbin/su
2303 KB/s (91980 bytes in 0.039s)
C:\Android\android-sdk\platform-tools>adb shell chown 0.0 /system/xbin/su
C:\Android\android-sdk\platform-tools>adb shell chmod 06755 /system/xbin/su
C:\Android\android-sdk\platform-tools>adb shell rm /data/local.prop
C:\Android\android-sdk\platform-tools>adb reboot
C:\Android\android-sdk\platform-tools>
Strange... I'm running the Spoof-CID.bat and I'm stuck at 'waiting for device'
Similar to this user:
http://i.imgur.com/fmTUP.png
Ok, I think I got past that little hickup. However, now I've been presented with a new problem. Not quite sure how to handle...
Make sure your device has usb debugging mode enabled, and is
Press any key to continue . . .
Restarting ADB
Pulling files
Checking files
Checking if patch can be applied
Everything looks good, rebooting to bootloader.
Once you are in bootloader mode, press any key to dump the ci
Press any key to continue . . .
...
FAILED (status read failed (Too many links))
finished. total time: 0.314s
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.002s
Your CID should read; 11111111
If it doesn't, something when wrong!
Goto HTCDev.com to finish the unlock process with the code ab
After you get your unlock file, drop it into the same folder
Press any key and then follow the instructions on the phone.
Press any key to continue . . .
UPATE: after fiddleing I got the unlock code, however i mistakenly hit a key closing the program... so now I have to start over, lol.
i feel close !
EDIT: Ugh, I don't know what's wrong now. I put the unlock code in the folder as instructed but it's stuck at waiting on device...
EDIT2: OHHH I had to press the power button down whilst hovering over fast boot, THEN I get asked to unlock the bootloader!
Ok guys, I installed goo manager and I think my phone is good to go at this point.
Well.. I think I ****ed my phone.
I tried to pick up where I left off in the video tutorial above.. but when it came time to restart the phone and get to 4:00 in the video I didn't see the screen mentioned.. so now my phone can get to the boot menu but won't system restore.
EDIT: I don't know if anybody's willing to do this... but maybe I could work though this issue with someone's aid over skype?
Since I can still access the boot screen I'm just going to go out and assume that It's still possible to restore my phone, which is still rooted and has the boot loader still unlocked. By the way, I did create a backup at one point using the Android SDK tool I believe. I'm not sure if that helps me.
help.
all the links you posted in your OP are for the endeavoru. you have an evita. don't go back to looking at endeavoru information when you are sooooo close.
just to see where you are at. does bootloader say TAMPERED and UNLOCKED? did goomanager install twrp 2.3.1.0?
DvineLord said:
all the links you posted in your OP are for the endeavoru. you have an evita. don't go back to looking at endeavoru information when you are sooooo close.
just to see where you are at. does bootloader say TAMPERED and UNLOCKED? did goomanager install twrp 2.3.1.0?
Click to expand...
Click to collapse
I'm sorry, DivineLord, like the noob lord that I am I didn't know any better.
My bootloader says TAMPERED and UNLOCKED, I'm not sure if goomanager installed anything other than what it automatically installs upon startup.
EDIT: Would this help me? http://d-h.st/8pr and if so, how would I even use it?
All it takes is five mins of searching on google to realize we have an evita
omario8484 said:
All it takes is five mins of searching on google to realize we have an evita
Click to expand...
Click to collapse
I don't know why so called "how to install" videos don't preface their tutorials by saying precisely what their tutorial requires. :/
downloaded newest twrp http://www.teamw.in/project/twrp2/99
reboot into bootloader
fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img
* after that you will be good to flash roms. remember never factory reset from the bootloader or inside the rom. always factory reset from inside recovery.
Convert your ZenPad 3s 10 from CN to WW firmware
This guide will show you how to flash the WW firmware to your ZenPad Z500M that came preloaded with the CN (China) ROM. Up until recently, this was problematic because the CN firmware, as well as the 13.x series in general, is locked down. It does not provide flashing access via the common methods like unlocking+fastboot, recovery or SP Flash Tool. But thanks to a MediaTek temporary root tool invented by some evil genius, it's now possible to upgrade your CN ZenPad to the latest WW ROM. It's well known that this variant comes with Google apps and is fully unlockable and rootable.
DISCLAIMER
Any procedures described in this thread are done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from software bugs.
REQUIREMENTS
An ASUS ZenPad Z500M (P027) tablet with 13.x firmware
Either:
A PC with ADB installed to interact with your device, or
A terminal emulator app
Familiarity with ADB (if using PC) and basic Linux shell commands
Familiarity with the Thanks button under XDA posts
INSTRUCTIONS
Read and understand this whole procedure before you start. This is about as dangerous as installing a full OTA update, and you would have to try hard to mess it up in a way that your device cannot be recovered. But keep in mind that it is a possibility. Make sure your battery has decent charge or plug it into the charger.
Go to Amazing Temp Root for MediaTek ARMv8 and read the directions on how to open a root shell in ADB or a terminal emulator app, and make sure you understand them. Download the latest release of mtk-su. Support the developer.
Download and unzip the recovery image to your tablet. Link below.
Open a root shell and flash the image to your recovery partition with:
Code:
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
You may need to specify the full path of the img file.
Download the latest 14.x WW firmware from ASUS' support site. Link below.
Put the official zip package in the root of your internal storage. Rename the file by changing the letters "WW" to "CN". That is, rename UL-P027-WW-14.0210.1806.33-user.zip to UL-P027-CN-14.0210.1806.33-user.zip. This has to be done in the same boot session as the recovery flashing step.
At this point, the OS updater should detect the file, prepare the upgrade and ask you to reboot. Confirm that you want to reboot to install. Make sure that you have succeeded step 4.
Your tablet will reboot and automatically install the WW 14.x package. You may need/want to do a factory reset after this.
Alternative method to zip file autodetection: reboot to recovery and do an adb sideload install.
NOTES
Do not try to install any 13.x firmware package using this method. That's because if something goes wrong and your device fails to boot, you would not be able to get root access to repair it. It may be next to impossible to recover it. The 13.x releases are locked down, unlike the 14.x (Android 7) ones.
If for any reason you reboot your tablet after doing the dd flashing step but before successfully installing the 14.x ROM, your original recovery will get restored. You will have to flash it again before trying the upgrade.
Do not try to downgrade from a 14.x FW to 13.x via TWRP. It is a fact that this will make your tablet unbootable because the 13.x packages do not provide all the necessary images.
DOWNLOAD
WW-13.x Recovery Image
ASUS Z500M firmware downloads
CREDITS
Thanks to @lemon0o for successfully testing this method. :good:
Read-only file system error - way out?
Hi diplomatic,
Thanks a lot for sharing this beautiful method. I had two of these tablets with CN firmware and had pretty much given up on them until now.
Edit 2: I successfully used the adb sideload method to update to WW firmware. The autodetect did not work for me.
Original post:
I have had success with steps 1-4 (UID 0, selinux: permissive),
but when I am trying to paste the downloaded firmware file in root folder ( / ) I get the error Read-only file system. I pasted the renamed firmware file in /sdcard/ but the autodetection doesn't work.
I tried remounting root '/' with
Code:
mount -o rw,remount /
I was then able to paste the renamed firmware file (WW to CN) to (root) / . The autodetection still doesn't work.
Is there a guide you can point me to for adb sideload install? I have exposure to linux but haven't explored android innards much. I will keep looking.
Thanks again, really hoping I am able to make this work!
@bkmiictian, I'm glad you figured it out. (And finally have someone respond after like 8 months. ) But FWIW, the upgrade package should go into your internal shared storage to be detected. It's just following the standard installation procedure for Asus. Nothing to do with the root dir of the file system.
diplomatic said:
@bkmiictian, I'm glad you figured it out. (And finally have someone respond after like 8 months. ) But FWIW, the upgrade package should go into your internal shared storage to be detected. It's just following the standard installation procedure for Asus. Nothing to do with the root dir of the file system.
Click to expand...
Click to collapse
I had similar issues, was not clear what to do, how to make it recognized.
Here I found great detailed explanation on the asus website (can't put full link as I'm newbie support/FAQ/1011948/ )
Apart from that, great guide !! Thanks a lot!!
Spent hours before that finding a way to either root it or install Google Apps. Tried all rooting apps I could find ...
thanks for the details procedure
Please all noted the file should place under "internal shared storage" not root as seen in adb.
Details steps as provide by Asus in its FAQ:
FAQ/1011948
Hi, Thanks so much for the tutorial.
I'm also having issues with the Z500M with CN firmware.
I followed the steps until getting the selinux: permissive message on ADB.
But I'm lost on what to do with the Recovery.img & the WW 14.x firmware
I copied the files into the root directory, but I don't understand what to do next.
Edit:
Found the procedure to manually install the firmware update from Asus.
Disconnected the USB cable & it told me there was a new update.
After updating, it restarted and showed an android with the message "installing system update" but then it just gave an Error.
Then it restarted saying System update failed. Unknow error. System was restored to previous configuration.
I guess I'm doing something wrong...
I think my issue may be Step 4.
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
You may need to specify the full path of the img file.
Click to expand...
Click to collapse
That command does not seem to work.
ADB says "No such a file or directory"
If I try with this command I get an error too.
dd if=/root/recovery.img of=/dev/block/platform/mtk-msdc.0/11>
dd: /root/recovery.img: Permission denied
danielfd said:
I think my issue may be Step 4.
That command does not seem to work.
ADB says "No such a file or directory"
If I try with this command I get an error too.
dd if=/root/recovery.img of=/dev/block/platform/mtk-msdc.0/11>
dd: /root/recovery.img: Permission denied
Click to expand...
Click to collapse
Yes, this is the main point of this procedure. Where did you extract recovery.img? If it's, say, in your internal storage, you may need to specify
dd if=/storage/emulated/0/recovery.img of=/dev/block.....
Only reboot to install the FW if you have succeeded with this step.
diplomatic said:
Yes, this is the main point of this procedure. Where did you extract recovery.img? If it's, say, in your internal storage, you may need to specify
dd if=/storage/emulated/0/recovery.img of=/dev/block.....
Only reboot to install the FW if you have succeeded with this step.
Click to expand...
Click to collapse
Thanks Diplomatic
The new code seems to work for me.
dd if=/storage/emulated/0/recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
Click to expand...
Click to collapse
I still get an Error when I try to update to the WW firmware.
Will try the whole process from the beginning.
EDIT:
It worked!
Thanks a lot Diplomatic!
I made a factory reset to the tablet & followed again the steps & the update was successful.
So if I had 14x on Android 7, can I just move to the twrp recovery part of the forum, why not just manually update to 14x from 13x if 14x can be unlocked? Am I missing something?
So i had my pad working but i wanted to put KatKiss on it. Seen some cool features like the multi window...
So i used to do a lot of ROMs on phones a long time ago, when i had extra time. Recenntly i have been playing with Android TV boxes.
So i found my old TF101 tablet. It was working. Looked like i did customize it at some point with a ROM....
Anyways, i felt like smart earlier today and wanted to play around and update the ROM on this pad bc i wanted to start to use it more.... Long story short.
So I got TWRP installed but i just noticed it is only version 2.5.0.0 not 2.8.1 - Maybe this is the main issue with what was going on???
Because, I made a recovery/backup and then I was following the steps on the ROM thread for installing this ROM on my TF101
[ROM][MM 6.0.1] [ KatKiss - KatshMallow #034 ] [MultiWindow]
Then I got to this step:
The first time you install: Format /data (full wipe doesn't format)
After i did this all my zips were gone (setting up the install) and everything even the backup i created, gone... I must of did the wrong kind of wipe like an idiot,,,
So, I then used adb and tried to sideload it.
In TWRP i went to ADB Sideload option. enabled it and it would upload it:
Code:
C:\Users\Danny\Documents\ASUS-TF101-ROMS-Development\platform-tools>adb start-server
C:\Users\Danny\Documents\ASUS-TF101-ROMS-Development\platform-tools>adb devices
List of devices attached
42890844040e117 recovery
C:\Users\Danny\Documents\ASUS-TF101-ROMS-Development\platform-tools>adb sideload C:\Users\Danny\Documents\ASUS-TF101-ROMS-Development\KatKiss-6.0_034.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
sending: 'C:\Users\Danny\Documents\ASUS-TF101-ROMS-Development\KatKiss-6.0_034.zip' 100%
But after it uploads and i try and install it
It uploads that ROM .zip file from my laptop terminal as shown above. However the sideload.zip fails in TWRP:
It shows this:
Code:
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking MD5
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/data/media/sideload.zip'
So that was not working....
Then i did a adb push of the file to /sdcard/ but every time i try and install the KatKiss-6.0_034.zip file via TWRP 2.5 it fails with this error in TWRP:
Code:
Updating partition details...
Installing '/sdcard/KatKiss-6.0_034.zip'...
Checking MD5
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
Updating partition details...
So i was able to push and install CyanogenMod (cm-10-20130929-NIGHTLY-tf101.zip) without any issues. So i am confused here....
I am wondering what the issue was with KatKiss ROM i was trying to install?
Should i update TWRP and then try again??
What would be the best way for me to get this working with other ROMS like KatKiss??
I did not do anything special at all when i flashed CyanogenMod - cm-10-20130929-NIGHTLY-tf101 successfully.
I pushed it and installed it like i was with KatKiss Rom....
Also, anyone have any other suggested ROMS for TF101 tablet?? A newer one? I know its an old tablet...
Thanks in advance!!!
Note - DiPP02 is my original name on here but i could not figure out the email i used so i am using google ATM
Okay so i just realized that it was modded before with CM bc this ROM looked like what was on there..
So i would like to try the KatKiss Rom... Ill try updating TWRP and trying again.
Any advice would be great!
I tried to download TWRP 2.8 from this thread but i get a 404 not found error
forum.xda-developers.com/t/recovery-tf101-tf101g-sl101-twrp-2-8-1-1-unofficial-2014-11-06.2434422/
Where can i download this version for TF101?
hmmm i tried to update TWRP now the pad just sits at Eee Pad Asus splash screen and does not boot into CM and when i try and go into recovery it does not go into it.....
Now i am lost on what to do here...
Okay i was able to cold boot into the OS...
Now i am having the ASOP ending on me so i cannot type hahhaha
How can i update my recovery? Please any help would be very much appreciated!
ANy help?
I cannot get into Recovery...
I get the following when i run the EasyRecovery.bat file from oneclickrecovery for tf101:
Code:
List of devices attached
042890844040e117 device
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
/dev/block/mmcblk0p3: cannot open for write: Permission denied
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1319 KB/s (4835404 bytes in 3.579s)
Running wolf's exploit...
failed on '/data/local/tmp' - Permission denied
Going...
link failed File exists
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Flashing new recovery...
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Done!
Continue to reboot your tab, do the button combination to test recovery.
I have tried EasyFlasher and uploaded the Asus .zip to the asusupdate directory.
I have tried it alll...
Even trying to edit it using SDB and ADX
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot
I get the permission denied and i even tried su in terminal on the pad....
I tried to flash to th Asus stock using EasyFlasher but still nothing is working...
When the pad reboots its stuck at the Eee pad splash screen and if i try and enter recovery it just sits there.... Booting recovery kernel image
The only way i can get into the pad is cold booting....
I have access to ADX.
Can someone please help me fix this?
It seems the permission deinied is not allowing the recovery to flash using the oneclick script. It worked the first time i used it...
Please any help or advice i have spent 9 hours on this today.... i am going crazy at this point.