I updated my vibrant to 2.2 used kies, and then I rooted it. I don't remember how exactly, it was a few months ago.
Now, I would like to remove the root. I've looked all over the internet.. and all I see is How To's for 2.1, I did find 1 thread however said use use like odin or something like that. I'm not super good at this whole rooting, recovery, adb.. IDK what most of those even mean. Please help!
Can someone please help me ASAP. This is really interfering with my work.
Go get super one click and unroot using that! Or odin back to stock and that will unroot u.
Sent from my SGH-T959 using XDA Premium App
movieaddict said:
Go get super one click and unroot using that! Or odin back to stock and that will unroot u.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Ok I just did it, and it said Error: Device does not have superruser, after ti went though like 30 steps for 2 minutes. I had superruser before
... how can I just that my decide is unrooted for sure? Because superruser is not there.
WAIT Just realized superruser is still there.. the unroot thing doesn't think i have superruser? SuperOneClick does not find superruser on my phone? I can see it in my apps?
Here is what is displayed.
SuperOneClick v1.9.1.0
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...
459 KB/s (585731 bytes in 1.245s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
375 KB/s (1062992 bytes in 2.765s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Remounting system with read-write access...
OK
Removing su...
OK
Removing Superuser.apk...
OK
Removing Superuser.apk...
Failure
OK
Remounting system with read-only access...
OK
Then a big error message comes up saying: Device Does not Have superuser. I may donate to someone if I can get my problem fixed!
if anyone knows what I can do to solve my problem.. please help... this is KILLING ME!
Go into download mode:
power off phone
pull out battery
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
Then odin back to stock and u should be unrooted and on 2.1
Also, to get the latest odin and files that are known to work, you should download the AIO Vibrant Toolbox, its a pretty handy tool, it have all the steps you need to follow to go back to stock.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
What is odin?
Im like.. BRAND new to this kind off.... what is odin?
LaxHoss said:
Im like.. BRAND new to this kind off.... what is odin?
Click to expand...
Click to collapse
s15274n guide to go back to stock jfd 2.1 (what your phone probable ame with)
odin's a program that wipes everything and puts it back to how it was when you got the phone
that guide should explain everything you need to know, check his other guides (in his signature) aswell if you still need more info
it helped me alot when i first started
Type odin tutorial in xda search
Sent from my SGH-T959 using XDA Premium App
After an unfortunately failed experiment at releasing the Droid root exploit after raising money to buy himself a Droid 4 and $300 to charity, the creator of the exploit, Dan Rosenberg has released his root which works on 2.3.6 entitled "Motofail"
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
You can download it from the link above and it should be able to root 6.12.173 on Droid RAZR directly without having to OTA rootkeeper 748 and upgrade.
Enjoy~~
And please consider donating to his fund which is still at the link. It all goes to the Red Cross now.
mattlgroff said:
After an unfortunately failed experiment at releasing the Droid root exploit after raising money to buy himself a Droid 4 and $300 to charity, the creator of the exploit, Dan Rosenberg has released his root which works on 2.3.6 entitled "Motofail"
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
You can download it from the link above and it should be able to root 6.12.173 on Droid RAZR directly without having to OTA rootkeeper 748 and upgrade.
Enjoy~~
And please consider donating to his fund which is still at the link. It all goes to the Red Cross now.
Click to expand...
Click to collapse
You beat me to it I was just about to post about this haha. I just downloaded and might try it out tomorrow.
Sent from my DROID RAZR
Is there a "unroot.bat" in the downloadable?
stupidchicken03 said:
Is there a "unroot.bat" in the downloadable?
Click to expand...
Click to collapse
No. There is not an unroot.bat
Posted links to this thread and the dev's site on my blog. Thanks for the heads up guys! Keep spreading the word!
Sent from my Droid Razr Maxx
mattlgroff said:
No. There is not an unroot.bat
Click to expand...
Click to collapse
Just tested and DoomLord's unroot works fine, once the phone is rooted. I then rerooted with no problem with this one.
I dont need it at this point but going to buy a new phone. If it works I will donate.
Anyone who lost root due to the ota update successfully root with this new method?
Sent from my DROID RAZR using Tapatalk
tgeigel said:
Anyone who lost root due to the ota update successfully root with this new method?
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Yes
Sent from my DROID RAZR using xda premium
Ronin3178 said:
Yes
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
Awesome thanks. I can now update and root. I'm a happy camper
Sent from my DROID RAZR using Tapatalk
Ronin3178 said:
Just tested and DoomLord's unroot works fine, once the phone is rooted. I then rerooted with no problem with this one.
Click to expand...
Click to collapse
Ah good to know
Does anyone know if it's possible to get this exploit updated to run with Mac/Linux? Some of us are very afraid of Windows computers.....
jgoose said:
Does anyone know if it's possible to get this exploit updated to run with Mac/Linux? Some of us are very afraid of Windows computers.....
Click to expand...
Click to collapse
http://www.mediafire.com/?3742xlbyff8ywa3
Thanks for the link to the Mac/Linux version.
I can't get my phone to root though. This is what I am getting:
[*] Motorola universal root script (OS X version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, and Droid RAZR
[*]
[*] Before continuing, ensure USB debugging is enabled, that your
[*] device is in 'Charge Only' mode, and your phone is connected via USB.
[*]
[*] Press enter to root your phone...-e
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2361 KB/s (359392 bytes in 0.148s)
[*] Owning phone...
[*] Waiting for phone to reboot.
[*] Root successful! Persisting...
remount succeeded
3075 KB/s (26264 bytes in 0.008s)
link failed File exists
3042 KB/s (1867568 bytes in 0.599s)
3708 KB/s (196521 bytes in 0.051s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
I think it might have something to do with me having the phone rooted already when the update hit and it screwed something up.
Right now I do have SuperUser in my App drawer and I cannot uninstall it. My razr only gives me the option to uninstall updates.
does anyone have any suggestions?
jgoose said:
Thanks for the link to the Mac/Linux version.
I can't get my phone to root though. This is what I am getting:
[*] Motorola universal root script (OS X version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, and Droid RAZR
[*]
[*] Before continuing, ensure USB debugging is enabled, that your
[*] device is in 'Charge Only' mode, and your phone is connected via USB.
[*]
[*] Press enter to root your phone...-e
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2361 KB/s (359392 bytes in 0.148s)
[*] Owning phone...
[*] Waiting for phone to reboot.
[*] Root successful! Persisting...
remount succeeded
3075 KB/s (26264 bytes in 0.008s)
link failed File exists
3042 KB/s (1867568 bytes in 0.599s)
3708 KB/s (196521 bytes in 0.051s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
I think it might have something to do with me having the phone rooted already when the update hit and it screwed something up.
Right now I do have SuperUser in my App drawer and I cannot uninstall it. My razr only gives me the option to uninstall updates.
does anyone have any suggestions?
Click to expand...
Click to collapse
Yea you are gonna have to uninstall SuperUser. If its not letting you then restore to 748 with My Utility (full version) and upgrade up.
I wanna root my Razr but have never done one is it pretty easy to do and is there a guide to step by step you on what to do?
it's worked `` 651.167.19 GSM`
mattlgroff said:
Yea you are gonna have to uninstall SuperUser. If its not letting you then restore to 748 with My Utility (full version) and upgrade up.
Click to expand...
Click to collapse
I'm not finding My Utility on my razr or in the market place. What and where do I need to search to find it?
Successfully update OTA and kept root!!!
---------- Post added at 02:05 PM ---------- Previous post was at 02:01 PM ----------
jgoose said:
I'm not finding My Utility on my razr or in the market place. What and where do I need to search to find it?
Click to expand...
Click to collapse
because its not in the market.
Thanks to mattlgroff here is his thread: http://forum.xda-developers.com/showthread.php?t=1491410
tgeigel said:
Successfully update OTA and kept root!!!
---------- Post added at 02:05 PM ---------- Previous post was at 02:01 PM ----------
because its not in the market.
Thanks to mattlgroff here is his thread: http://forum.xda-developers.com/showthread.php?t=1491410
Click to expand...
Click to collapse
lol I should have been more clear on that. Enjoy!
Details : I lost root.
What happened: Was running stock Rogers RAZR 2.35, rooted with Clockwork on boot.
I upgraded to 2.36 when the upgrade came, and since have lost root.
I tried using MOTOFAIL afterwards to restore, but despite trying, it failed.
Any assistance would be appreciated.
bbabiuk said:
Details : I lost root.
What happened: Was running stock Rogers RAZR 2.35, rooted with Clockwork on boot.
I upgraded to 2.36 when the upgrade came, and since have lost root.
I tried using MOTOFAIL afterwards to restore, but despite trying, it failed.
Any assistance would be appreciated.
Click to expand...
Click to collapse
Motofail is the root method to 2.3.6
Did you turned on debug usb? Post your error message from motofail.
Btw how did you updated ur system? Was rsd lite?
Cheers
Sent from my XT910 using Tapatalk 2
pedrotorresfilho said:
Motofail is the root method to 2.3.6
Did you turned on debug usb? Post your error message from motofail.
Btw how did you updated ur system? Was rsd lite?
Cheers
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
1. USB Debug was on.
2.
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
3922 KB/s (501292 bytes in 0.124s)
[*] Owning phone...
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Attemping persistence...
remount failed: Unknown error: 0
21 KB/s (22364 bytes in 1.000s)
ln: /system/xbin/su: No such file or directory
2922 KB/s (1867568 bytes in 0.624s)
2640 KB/s (843503 bytes in 0.312s)
[*] Cleaning up...
/sbin/sh: /data/local/motofail: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
3. Installed a Rogers nandoid to restore missing bloatware from when I rooted then used OTA.
Could the problem be when MOTFAIL reboots the phone and CWM fires up?
bbabiuk said:
Could the problem be when MOTFAIL reboots the phone and CWM fires up?
Click to expand...
Click to collapse
Exactly. This is a known issue. Flash cwm remove first and you'll be okay
Sent from my XT910 using Tapatalk 2
pedrotorresfilho said:
Exactly. This is a known issue. Flash cwm remove first and you'll be okay
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
forgive me if this sounds noobish but exactly how do I do that? I've bricked a phone or 2 in my life. I'm trying to be careful with this device.
pedrotorresfilho said:
Exactly. This is a known issue. Flash cwm remove first and you'll be okay
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
nvm... i remembered.... i am good. rebooting right now and it appears to have worked. tring to reroot in a sec
bbabiuk said:
nvm... i remembered.... i am good. rebooting right now and it appears to have worked. tring to reroot in a sec
Click to expand...
Click to collapse
yup! all better!
Curious. Is there a CWM that can be installed that doesn't pop up at reboot every time? That was annoying.
bbabiuk said:
yup! all better!
Curious. Is there a CWM that can be installed that doesn't pop up at reboot every time? That was annoying.
Click to expand...
Click to collapse
dont think there is really.. i mean as far as i can remember there is a setting in the script that can be changed from 1 to 0 and it wouldnt pop up but then kinda defeats the purpose of the recovery. unless you plan on changing it constantly whenever you need it lol
pedrotorresfilho said:
Exactly. This is a known issue. Flash cwm remove first and you'll be okay
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
Im having the exact same problem & am kind of new to this. how do i flash cwm remove first??
explosivo777 said:
Im having the exact same problem & am kind of new to this. how do i flash cwm remove first??
Click to expand...
Click to collapse
Here it's
http://forum.xda-developers.com/showthread.php?t=1385283
Cheers
Sent from my XT910 using Tapatalk 2
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
Looks like you are in store for a full system restore to the original stock image. You can try the recovery image from my signature to get rid of the TWRP recovery if you want. Just place the recovery file in the PDA box and start.
So, is that why I am getting that message when I am trying to root my phone again?
killdawabbit said:
So, is that why I am getting that message when I am trying to root my phone again?
Click to expand...
Click to collapse
It could be but not 100% sure. Each user is different. I would start there though and see if it works.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Cilraaz said:
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Click to expand...
Click to collapse
Yes
killdawabbit said:
Yes
Click to expand...
Click to collapse
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
killdawabbit said:
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
Click to expand...
Click to collapse
crikfromcincy said:
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
Click to expand...
Click to collapse
Sent
So I picked up this tablet at MicroCenter. Not bad for $40. Not a lot of features, but I knew that going in. Nice that it has 4.2.2 and the Play Store works like it should!
I wanted to start a general thread to keep up to date on any recoveries, fixes or ROM's people come across.
I used this method to root http://www.cydiaimpactor.com/ it worked the first try. I had to do it on an old XP machine because my Windows 8 would not load the right Android drivers. See posts below for another method.
Please post any additional information you may have on this tablet. Let's see if we can make the most out of our $40!
A special thanks to BLuFeNiX for jump starting this whole thread with his knowledge, CWM recovery and stock NANDs, and for taking time to gather all the info into a useful post.
Also thanks to extreme tester dsulliii for the willingness to sacrifice his tablet in the name of science and for all his insight and help.
Don't forget to hit the thanks button for them !!!!!
CWM Recovery, Return To Stock, and More!
My dropbox links keep getting suspended, so here is a media fire link for all my files: https://www.mediafire.com/folder/gm9wb67b05bs4/Azpen_A700
Also, check out the forums at SDX: http://forum.sdx-developers.com/viewforum.php?f=528
ClockworkMod Recovery
Changelog:
Code:
CWM build 5 (2013-12-02)
* corrected internal and external sdcard mount points (previously, the external sdcard was being mounted at /emmc, which is just wrong. The new mount points are /sdcard and /external_sd)
* added more partitions under "mounts and storage" (in case anyone wants to mount them or format them)
CWM build 4 (2013-11-29)
* first working build
Downloads:
CWM build 5 (2013-12-02) Image File | Flashable ZIP
CWM build 4 (2013-11-29) Image File | Flashable ZIP
Stock Recovery Image File | Flashable ZIP
MD5 Hashes:
Code:
73ab81b2e6b1404f1e4e1ed91f32ae7d ./CWM_recovery-Azpen_A700-build-4.img
db028be865f27797bf92cfbd04496101 ./CWM_recovery-Azpen_A700-build-4.zip
8c4ab86c29e83eb9f492623218828142 ./CWM_recovery-Azpen_A700-build-5.img
8e67fa7cb333e242a19306a2859b050c ./CWM_recovery-Azpen_A700-build-5.zip
ff080997ff01838e9d35807e08846724 ./stock_recovery-Azpen_A700.img
816b643ea090b2dd55226b380982c686 ./stock_recovery-Azpen_A700.zip
How to install a flashable ZIP:
Boot into recovery and select "install zip from sdcard." You must be using a custom recovery for this to work (otherwise authentication will fail).
How to install a recovery image:
Copy the image file to your SD card and run the following commands via ADB or a Terminal Emulator:
Code:
su
dd if=/sdcard/name_of_recovery.img of=/dev/block/nandg
sync
You can now reboot into CWM recovery.
Return To Stock ROM
NOTE: These images are not 100% stock because they are fully rooted. If you want true stock, just replace the /system/xbin/su binary with the original, which is preserved as /system/xbin/su.original
The easy way:
I have created an flashable zip to return to stock. You can download it here: Azpen A700 Stock ROM Flashable ZIP
Just copy it to your SD card, boot into CWM, and select "install zip from sdcard." Before rebooting, select "wipe data / factory reset."
The hard way:
Alternatively, stock images for the Azpen A700 can be downloaded here. To return to stock, download the important nand images (a, b, c, d, g) and, copy them to your SD card and then run the following commands via ADB (you must be booted into CWM if you wish to flash anything other than recovery/nandg):
Code:
su
dd if=/external_sd/nanda.img of=/dev/block/nanda
dd if=/external_sd/nandb.img of=/dev/block/nandb
dd if=/external_sd/nandc.img of=/dev/block/nandc
dd if=/external_sd/nandd.img of=/dev/block/nandd
dd if=/external_sd/nandg.img of=/dev/block/nandg
sync
Before rebooting, select "wipe data / factory reset."
Unbricking via Livesuit
First, your device needs to be in FEL mode. There are a few ways to accomplish this:
dsulliii said:
1) Make sure your A700 is turned off. (Do NOT have the micro-USB end plugged into your A700 at this time, that is for later.)
2) Start LiveSuit on your computer. (The COMPUTER end of your USB cable should be plugged into ONLY your computer at this stage.)
3) Select the ROM that you want to flash to your A700.
4) Hold down the Vol button on your device (I usually hold it down Vol-, not Vol+, but I believe that this device does not matter which.)
5) While holding down Vol, plug the micro-USB end of the cable into your A700. Keep holding down the Vol button.
6) While still holding down the Vol button, WITH the USB cable now connected between your computer and your A700, press and release the A700's Power button 10 times, and wait for a second to a few.
7) The LiveSuit program will detect your A700 going into download mode and begin prompting you for what to do.
8) Follow LiveSuit's recommendations, including formatting. It will take less than 5 minutes.
*** IF *** you don't get the LiveSuit prompting after step #6 as described in step #7, it means that you don't have the ADB-USB drivers for the A700 installed into your Windows. The easiest way to do that is to run each of the three other ".exe" driver install programs that are in your LiveSuit directory. ONE of those properly installs the needed driver to make LiveSuit detect your A700. *** EndIF ***
Click to expand...
Click to collapse
You can also get into FEL mode by using a specially formatted SD card. Read about it here: http://linux-sunxi.org/FEL
The file you want to write to the SD card is here: fel-sdboot.sunxi
NOTE 1: Be sure to backup the SD card first, since the data will be gone.
NOTE 2: There is no on-screen indication that your device is in FEL mode. You can tell by plugging the device into your PC and seeing if it is recognized.
Next, flash the livesuit image from here using the Livesuit software. This will install an older version of android on your A700 (a current version image is not yet available). After you unbrick, you can return to stock jellybean 4.2.2 using the instructions found above.
Partition Descriptions
nanda -- bootloader (loads android or recovery and contains boot animation, battery charging images, etc.)
nandb -- env (sets environment variables and helps bootloader)
nandc -- boot (android kernel and ramdisk, this loads on normal boot)
nandd -- system (everything in /system)
nande -- data (everything in /data)
nandf -- misc (used to store temporary data between boot stages and reboots)
nandg -- recovery (recovery kernel and ramdisk)
nandh -- cache (various temporary files)
nandi -- databk (a backup of some of the more important files in /data)
nandj -- sdcard (internal sd card)
Extended Power Menu mod [by ften]
Read the original post here: http://forum.xda-developers.com/showpost.php?p=48225023&postcount=134
Download the flashable zip here: Azpen A700 EPM installer
If you like my work, feel free to donate.
We'll see
After my 1st round of "what's it gonna take to root this". And I do a appreciate a fairly slim JB dist. But I think this lil guy could use a few tweaks here and there.
I'm leaning towards "Kingo Root" for simplicity's sake. Or, "Cydia Impactor" Honestly though, I'm prolly too busy to spend the interrupted time to do a root for a bit. So I'll just check in and see what's up. GMTA ComStart. Thanks!
ranchdude said:
After my 1st round of "what's it gonna take to root this". And I do a appreciate a fairly slim JB dist. But I think this lil guy could use a few tweaks here and there.
I'm leaning towards "Kingo Root" for simplicity's sake. Or, "Cydia Impactor" Honestly though, I'm prolly too busy to spend the interrupted time to do a root for a bit. So I'll just check in and see what's up. GMTA ComStart. Thanks!
Click to expand...
Click to collapse
Well, the device is already rooted over ADB. You just need to shell in and replace the su binary with one that doesn't restrict user apps from gaining root.
Getting back to stock
I'm a neophyte, so I bought this one knowing that if I broke it (which I most likely would -- and did), then I wouldn't be out a whole lot of money. My experiences in learning so far with these A13s is that they're practically un-brickable... once you ruin them, there always seems to be a way to get back on track. So after messing this one up, I was again surprised that all was not lost. I found an ICS ROM that did install using LiveSuit, and it's back up and running again. Only problem is... it was a very nice, slick little JellyBean 4.2 machine before I messed it up. I'd love to get it back to where it was before I messed it up (like I've been able to with other A13s), but ran into an unexpected impasse... CWM Recovery.
The way I got back to installed-version before was by installing a workable ROM then using CWM Recovery to copy ROM-dump files that I pulled prior to messing around back into it. Well, unbeknownst to me, THIS one doesn't have a CWM Recovery yet. And developing one is way beyond my abilities at this point... I am totally relying on you-all with way-more experience than me.
When I went to the Azpen support site, the only ROM they have is allegedly an A700/A701. THAT one doesn't flash using LiveSuit. It errors out at the beginning. So I'm guessing that Azpen support isn't up-to-date yet. I wrote to them, but haven't heard back. I really want to be able to reset it back to its original flashed ROM. Without CWM Recovery, my expected plan for restoration kind of croaked.
So here's my question.... do any of you know of an original ROM that I can get my mitts on that WILL indeed flash to this Azpen A700? I'd love to get its original JellyBean 4.2 working on it again. PLUS... the ICS ROM that DID work in it makes it a different signature... I want it to be an Azpen A700 again.
I know... asking lots and contributing nothing. I'd be thrilled to help anybody gain the same victory that I did with the Mach Speed Trio Stealth 7c A13b if they're having trouble -- in return. Just a hobby of mine, but I hope to someday be good like ya'll.
David
dsulliii said:
So here's my question.... do any of you know of an original ROM that I can get my mitts on that WILL indeed flash to this Azpen A700? I'd love to get its original JellyBean 4.2 working on it again. PLUS... the ICS ROM that DID work in it makes it a different signature... I want it to be an Azpen A700 again.
David
Click to expand...
Click to collapse
I can send you a CWM build that might work. I've been working on one. I make no promises though. My last 2 builds bricked and I had to return the tablet for a new one. I suppose you won't be in any worse of a place though, since you found a working livesuit image. Can you send me a link to the livesuit image? I haven't found a working one yet.
So, let me know if you want me to send my possibly-working CWM build.
BLuFeNiX said:
I can send you a CWM build that might work. I've been working on one. I make no promises though. My last 2 builds bricked and I had to return the tablet for a new one. I suppose you won't be in any worse of a place though, since you found a working livesuit image. Can you send me a link to the livesuit image? I haven't found a working one yet.
So, let me know if you want me to send my possibly-working CWM build.
Click to expand...
Click to collapse
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:25 PM ----------
PS -- as soon as I re-find that link, I'll post it for you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 08:17 PM ---------- Previous post was at 07:43 PM ----------
dsulliii said:
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:25 PM ----------
PS -- as soon as I re-find that link, I'll post it for you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
_______________________________________________________________________________
Okay, I found it at:
(Just discovered that I'm not experienced on the site enough to post links yet.)
It's on a dot-com site called moveontechnology, and it's by hugoenchina with a page id of 220. It's in Spanish.
Maybe you can use some of this info to locate it on Google Search since I can't post the link.
(I used Google Chrome so that I could translate the page from Spanish to English)
Then find the section just a little down the page:
************************************************** **
TABLETS FIRMWARES A13 CPU BOARD BEGINS WITH INET XXX, eg Inet 86vs
(A13) (86VS-M758C1) (CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480) (BLOGHUGOENCHINA) 20130725. Zip "inform me also works in denver electronics TAC-70051" and the Mitsui model MID7104SC
Although the ICS ROM above works, do NOT use it. It incorrectly partitions the device
(A13) (86V-M758B) (CPT-FTG700D3-50PIN-800X480) (TOUCH-NOPLANO) (BLOGHUGOENCHINA) 20130725. Zip
(A13) (86V-M729) (CPT-LT70009-40PIN-800X480) (BLOGHUGOENCHINA) 20130725.zip
(A13) (86V-M758A) (CPT-FTG700D3-50PIN-800X480) (TOUCH-UP) (BLOGHUGOENCHINA) 20130725.zip
************************************************** **
As you can see, I downloaded the first one. I don't know whether the other three work or not because this one works great, although it's ICS.
If you click on that first one, it will give you another link that I can't post on depositfiles.
The actual file is mus464gwg.
Then using Azpen's LiveSuit A701.exe, after extracting the "img" out of the "zip", this "img" works.
Although the ICS ROM below works, do NOT use it. It incorrectly partitions the device
(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.zip
(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img
BLuFeNiX said:
I have started investigating how to create a CWM recovery for this device. All the information I currently have is in my reddit thread (which I cannot link due to my low post count). The title is "Can anyone help me build a CWM recovery for the Azpen A700 tablet? (work I've already done and details inside)"
If anyone has any info that may help me in this endeavor, please message me here or on reddit.
EDIT: How can we get a sub-forum started for this device?
Click to expand...
Click to collapse
I just read through your reddit thread here http://www.reddit.com/r/androiddev/comments/1qt0tk/can_anyone_help_me_build_a_cwm_recovery_for_the/ - great job! Looks like you are making some progress. I also saw the cyanogen thread where the guy took his tablet apart to take some pictures. Can't miss the big Allwinner A13 chip.
Sent from my A700 using XDA Premium 4 mobile app
dsulliii said:
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Great, thanks for testing for me! Here are the links:
CWM build 1
CWM build 2
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
CWM build 1
BLuFeNiX said:
Great, thanks for testing for me! Here are the links:
<<snipped the links>>
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
Click to expand...
Click to collapse
__________________________________________________________________
Currently running the (A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img ROM on Azpen A700.
1) Currently running actively from the desktop and selecting SystemSettings-->Backup&Reset-->RecoveryMode-->Ok. (Wait for shutdown & restart)
2) Started into "Android system recovery <3e>". Where "Android system recovery utility (EVB: vol up/vol down, home, enter)" prompt has following options:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
3) Had copied cwm6028-a700-text.zip to internal SD card, and it does indeed list in "apply update from external storage". Seems that some folks should get some consistency between the meaning of "internal" and "external". But that's neither here nor there. So I am selecting your zip file after volume-downing to it and pressing the power button to select...
RESULTS:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
4) So now i will "reboot system now" and ensure that nothing detrimental occurred....
YEP -- No problem! Device still not bricked, so that's good for me.
The ball's still in your court on this one (that was still fun, nevertheless, thanks.)
-- David
---------- Post added at 09:00 AM ---------- Previous post was at 08:47 AM ----------
BLuFeNiX said:
Great, thanks for testing for me! Here are the links:
<<links snipped>>
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
Click to expand...
Click to collapse
_________________________
Title: CWM build 2
Everything same as before, but this time it is "cwm6028-a700-test2.zip" that I have selected to install.
Results:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
(Still exciting though... getting to watch the status bar increase to about 5% before failing.)
Looking forward to the next hurdle. COOL!
dsulliii said:
RESULTS:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
(Still exciting though... getting to watch the status bar increase to about 5% before failing.)
Looking forward to the next hurdle. COOL!
Click to expand...
Click to collapse
Ah, okay! I just have to re-sign the zip file. I'll send you some resigned builds shortly.
Happy Thanksgiving
BLuFeNiX said:
Ah, okay! I just have to re-sign the zip file. I'll send you some resigned builds shortly.
Click to expand...
Click to collapse
Excited to try it again. But the wife and I are about to take off across town to the oldest son's home for the Holiday feast. I may-or-may-not get to it before the day is out, but I'm going to be chomping at the bit to get home and give it another try. It's 11:30am here (Mountain time). Later, thanks, and Happy Thanksgiving!
dsulliii said:
Excited to try it again. But the wife and I are about to take off across town to the oldest son's home for the Holiday feast. I may-or-may-not get to it before the day is out, but I'm going to be chomping at the bit to get home and give it another try. It's 11:30am here (Mountain time). Later, thanks, and Happy Thanksgiving!
Click to expand...
Click to collapse
Hey, no problem. Have a happy Thanksgiving! Here are the new (hopefully correctly-signed) zips:
Signed zip test 1
Signed zip test 2
Looking forward to hearing the results!
Hey BLuFeNiX, I was fortunate to connect to xda on my son's wi-fi and download your new ones. They both failed signature verification again. He's interested as well, so we can probably keep plugging away at this through the day. -- David
Sent from my M758C1 using Tapatalk
dsulliii said:
Hey BLuFeNiX, I was fortunate to connect to xda on my son's wi-fi and download your new ones. They both failed signature verification again. He's interested as well, so we can probably keep plugging away at this through the day. -- David
Sent from my M758C1 using Tapatalk
Click to expand...
Click to collapse
Okay. Let's try this a different way. Is your tablet rooted? if so, please install Android Terminal Emulator from the Play Store.
Also, copy these img files to your internal sdcard:
Image test 1
Image test 2
Open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/recovery-TEST.img of=/dev/block/nandg
sync
reboot recovery
This will flash the recovery directly from Android instead of having to boot into recovery. If the first one doesn't work, you can try the second one. If we are successful, you should boot into CWM. If not, you'll probably need to flash using livesuit again.
If you are not rooted (you will get an error when you use the "su" command), let me know and I will tell you how to obtain root.
Good luck, and thanks again!
Yep, rooted, su worked okay in terminal, got the #.
Dowloaded okay, will try the dd flash. If it doesn't work and I have to reflash, won't be able to let you know until I get home tonight.
Sent from my M758C1 using Tapatalk
---------- Post added at 04:32 PM ---------- Previous post was at 03:39 PM ----------
Forgot my cell phone had Tap-a-talk on my cell phone. Interesting... reboot recovery from terminal rebooted system, but not recovery. So used settings app to reboot into recovery. When I did that, I got little colorful Andy who just stayed there and never went into recovery nor system. Forced a shutoff using the power button. Turned on... same freeze point. Forced power off again and tried to start recovery with volume and power. Same no-go. Only could try the first img since it's stuck. Will now have to wait till we get home then I"ll flash the ICS ROM and try your second img.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
ADDENDUM: The problem that I had with not rebooting recovery from a shell command has gone away. I suspect that it might have something to do with the ICS ROM that I was using partitioning the device wrong. Make sure you use BLuFeNiX's modified ROM for proper A700 partitioning, and NOT the one that I recommended earlier in the thread.
dsulliii said:
Yep, rooted, su worked okay in terminal, got the #.
Dowloaded okay, will try the dd flash. If ut doesn't work and I hace to reflash, won't be able to let you know until I get home tonight.
Sent from my M758C1 using Tapatalk
---------- Post added at 04:32 PM ---------- Previous post was at 03:39 PM ----------
Forgot my cell phone had Tap-a-talk on my cell phone. Interesting... reboot recovery from terminal rebooted system, but recovery. Do used settings app to reboot into recovery. When I did that, I got little colorful Andy who just stayed there and never went into recovery nor system. Forced a shutoff using the power button. Turned on... same freeze point. Forced power off again and tried to start recovery with volume and power. Same no-go. Only could try the first img since it's stuck. Will now have to wait till we get home then I"ll flash the ICS ROM and try your second img.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Interesting results. The second image loads the ramdisk from a different memory address, so hopefully the behavior you saw was what happens when an incorrect memory address is used. Maybe #2 is the correct one
Thanks again for doing all this testing.
Just looked over my posts from earlier. So VERY sorry about the spelling errors! I wasn't looking back to see the mis-predictions. I hate it when people do that. Anyway, on my way home now. Should be able to let you know about the second img in about an hour. (8:00pm mountain time).
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Image test 2
BLuFeNiX said:
Okay. Let's try this a different way. Is your tablet rooted? if so, please install Android Terminal Emulator from the Play Store.
Also, copy these img files to your internal sdcard:
<<links snipped>>
Open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/recovery-TEST.img of=/dev/block/nandg
sync
reboot recovery
This will flash the recovery directly from Android instead of having to boot into recovery. If the first one doesn't work, you can try the second one. If we are successful, you should boot into CWM. If not, you'll probably need to flash using livesuit again.
If you are not rooted (you will get an error when you use the "su" command), let me know and I will tell you how to obtain root.
Good luck, and thanks again!
Click to expand...
Click to collapse
_____________
Okay, I'm home now.
Before getting started, I restarted the A700 using the power button. It (again) did not progress beyond the teensy colorful Andy.
So I connected my USB cable to the computer and tried to ADB it.... ADB did not see it. I predicted it did not get any farther, but I just wanted to make sure and to let you know as well.
So I used LiveSuit A701.exe to flash the ICS "(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img" ROM again ... complete success as always.
After it powered up to the ICS desktop, I "ADB devices" which resulted positive. Followed by "ADB shell" whereupon I got the "#" indicating that this ROM comes rooted, it started in as superuser.
I copied your "recovery-TEST2.img" to the internal SDcard.
Went back into ADB Shell and at the # prompt typed:
su ' superfluous since already superuser
dd if=/sdcard/recovery-TEST2.img of=/dev/block/nandg
sync
reboot recovery
Again, the shell "reboot recovery" command did not reboot the recovery partition... it rebooted the system partition back into my ICS desktop.
So again I SystemSettings->Backup&Reset->RecoveryMode->Ok. And waited for it to power off and restart.
I got the small colorful Andy.... forever.... and again no sign of any additional advancing.
Still had the USB cable plugged in, so tried ADB devices again while it was sitting on Andy. No good, no ADB running.
Used the power button to force a power off.
After it powered off, waiting 30 seconds, I used the power button to turn it back on.
It displayed the colorful little Andy.... and didn't go anywhere still.
So I will re-flash the ICS ROM and wait for you to find some more magic.
Yeah, this is fun. THANKS BLuFeNiX. :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:15 PM ----------
More experimentation. I installed Uberizer's tollkit to have it perform the reboot into recovery. Identical to the shell's reboot recovery, it also reboots into the system. It appears that this ROM and the Azpen JellyBean 4.2 ROM must know something special about this tablet, eh?
Sent from my M758C1 using Tapatalk
ADDENDUM: The "reboot recovery" issue from a shell command has gone away. I believe that it was most likely caused by the ICS ROM that I was flashing -- having the device partitioned incorrectly.
dsulliii said:
_____________
Okay, I'm home now.
Before getting started, I restarted the A700 using the power button. It (again) did not progress beyond the teensy colorful Andy.
So I connected my USB cable to the computer and tried to ADB it.... ADB did not see it. I predicted it did not get any farther, but I just wanted to make sure and to let you know as well.
So I used LiveSuit A701.exe to flash the ICS "(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img" ROM again ... complete success as always.
After it powered up to the ICS desktop, I "ADB devices" which resulted positive. Followed by "ADB shell" whereupon I got the "#" indicating that this ROM comes rooted, it started in as superuser.
I copied your "recovery-TEST2.img" to the internal SDcard.
Went back into ADB Shell and at the # prompt typed:
su ' superfluous since already superuser
dd if=/sdcard/recovery-TEST2.img of=/dev/block/nandg
sync
reboot recovery
Again, the shell "reboot recovery" command did not reboot the recovery partition... it rebooted the system partition back into my ICS desktop.
So again I SystemSettings->Backup&Reset->RecoveryMode->Ok. And waited for it to power off and restart.
I got the small colorful Andy.... forever.... and again no sign of any additional advancing.
Still had the USB cable plugged in, so tried ADB devices again while it was sitting on Andy. No good, no ADB running.
Used the power button to force a power off.
After it powered off, waiting 30 seconds, I used the power button to turn it back on.
It displayed the colorful little Andy.... and didn't go anywhere still.
So I will re-flash the ICS ROM and wait for you to find some more magic.
Yeah, this is fun. THANKS BLuFeNiX. :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:15 PM ----------
More experimentation. I installed Uberizer's tollkit to have it perform the reboot into recovery. Identical to the shell's reboot recovery, it also reboots into the system. It appears that this ROM and the Azpen JellyBean 4.2 ROM must know something special about this tablet, eh?
Sent from my M758C1 using Tapatalk
Click to expand...
Click to collapse
Alright, I am starting to run out of ideas. Try this build (use the dd method again):
CWM recovery test 3
If this one doesn't work, I'll need to spend some more time doing research. Thanks and good luck!