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!
Related
Okay, so I am far from a newbie at this stuff, but I did try to unlock/root my new EVO 4G LTE today with disastrous results. As it stands right now, I've got the bootloader unlocked with TWRP installed, but no matter what ROM I install, after the HTC screen, it just sits at a black screen indefinitely. But here's where I really got screwed: I accidentally hit "Factory Reset" on the bootloader screen when I hit the volume down twice instead of once to get into recovery (and then hit power by force of habit). So now my internal SD card is completely empty and can't be recognized by my computer. I do have a MicroSD card, though, that I can access to get files onto it. So here's where I am. I can't boot into ANY ROM, so I can't just RUU it back to stock, my internal SD card is cleared, and I'm pretty much freaking out right now. This is my 8th Android device, all of which I rooted and installed custom ROMs on, and I've never bricked it so bad I couldn't fix it. Does anyone have any ideas to help me out? I royally effed up somewhere, and I can't figure out how to fix it!
SOLVED! Check out the DON'T PANIC thread to fix pretty much any of your problems, especially the one I outlined above.
Boot 1.15+ require you to fast boot the kernel, extract boot.image from zip and place in adb directory, then from terminal type fastboot flash boot boot.image. next jump into twrp and mount your external SD to your computer, copy the ROM zip to your phone. Now you can flash the ROM and reboot
om4 said:
Boot 1.15+ require you to fast boot the kernel, extract boot.image from zip and place in adb directory, then from terminal type fastboot flash boot boot.image. next jump into twrp and mount your external SD to your computer, copy the ROM zip to your phone. Now you can flash the ROM and reboot
Click to expand...
Click to collapse
So extract the the boot.img from the ROM zip and then ADB it to the phone through fastboot?
Yes, its pretty simple. Take a look at my guide I break down everything I can possibly think if and I update it like a mad man....maybe Bilbo is right about it being stickied...oh well
om4 said:
Yes, its pretty simple. Take a look at my guide I break down everything I can possibly think if and I update it like a mad man....maybe Bilbo is right about it being stickied...oh well
Click to expand...
Click to collapse
Oh my god. You are a God among men. It's finally booting! Thank you SO much. Watch for a donation. I can't thank you enough. I'm assuming that extra step is because of S-ON?
I just sent you a $20 donation for your help. You saved my ass tonight. The wife was ready to kill me. lol
Yes HTC has disabled access to boot. They decided to disable it with a few phones, someone must love us over there because this phone originally had an hboot that allowed recovery to write to boot. HTC promptly removed it in the very next update
I put that link up to humor the gf, never thought anyone would use it. She set up a PayPal when I lost my job and I wasn't about to argue since she is now the one who pays rent. Thank you for proving her right, I will never hear the end of it lol
om4 said:
Yes HTC has disabled access to boot. They decided to disable it with a few phones, someone must love us over there because this phone originally had an hboot that allowed recovery to write to boot. HTC promptly removed it in the very next update
I put that link up to humor the gf, never thought anyone would use it. She set up a PayPal when I lost my job and I wasn't about to argue since she is now the one who pays rent. Thank you for proving her right, I will never hear the end of it lol
Click to expand...
Click to collapse
so her argument is right and $20 goes to her for your work LOL!
om4 said:
Yes HTC has disabled access to boot. They decided to disable it with a few phones, someone must love us over there because this phone originally had an hboot that allowed recovery to write to boot. HTC promptly removed it in the very next update
I put that link up to humor the gf, never thought anyone would use it. She set up a PayPal when I lost my job and I wasn't about to argue since she is now the one who pays rent. Thank you for proving her right, I will never hear the end of it lol
Click to expand...
Click to collapse
$20 is a drop in the bucket of the hell I'd have had to pay with the wife if I couldn't get it fixed. That's money well-spent, in my eyes. You really did save me last night, and though you probably thought it was a stupid mistake I made, you earned it. Thanks so much again. And, um, sorry about proving her right. Hopefully you're proved right by others too.
this is my exact problem.can this be explained with noob bumpers please?
Did you fastboot your kernel?
You need the adb tools package to use fastboot. I would post a link but I'm not at my pc, do a search for evo4glteroot2.zip
---------- Post added at 08:15 PM ---------- Previous post was at 08:05 PM ----------
chrisliphart said:
$20 is a drop in the bucket of the hell I'd have had to pay with the wife if I couldn't get it fixed. That's money well-spent, in my eyes. You really did save me last night, and though you probably thought it was a stupid mistake I made, you earned it. Thanks so much again. And, um, sorry about proving her right. Hopefully you're proved right by others too.
Click to expand...
Click to collapse
What's so stupid about an honest mistake? A lack of knowledge does not equal stupidity
om4 said:
Did you fastboot your kernel?
You need the adb tools package to use fastboot. I would post a link but I'm not at my pc, do a search for evo4glteroot2.zip
---------- Post added at 08:15 PM ---------- Previous post was at 08:05 PM ----------
What's so stupid about an honest mistake? A lack of knowledge does not equal stupidity
Click to expand...
Click to collapse
ok i found the zip and downloaded it.I have my phone in recovery FASBOOT USB is in red, BOOTLOADER is in blue.I have the boot image of the rom i tried to flash on my cpu.I'm so lost if I fix this I think I'll retire.
Im assuming your in windows. Place the boot.img in the adb folder. Click windows start button and type cmd in run, this will open dos prompt terminal. In the terminal use the command CD (folder) to go to what ever directory adb tools is in if you need to look at your list of folders type dir. Once you are in your adb folder type fastboot flash boot boot.img
dirtred1031 said:
ok i found the zip and downloaded it.I have my phone in recovery FASBOOT USB is in red, BOOTLOADER is in blue.I have the boot image of the rom i tried to flash on my cpu.I'm so lost if I fix this I think I'll retire.
Click to expand...
Click to collapse
fastboot is not recognized as an external on internal command I get
Odd, are you sure you were able to navigate to the folder? You have to be in the folder
I'm a bit out of practice when it comes to windows, but I believe the structure would be c:\users\your user id\downloads\evo4glteroot2 or something similar depending on where you unzipped the folder
om4 said:
Odd, are you sure you were able to navigate to the folder? You have to be in the folder
I'm a bit out of practice when it comes to windows, but I believe the structure would be c:\users\your user id\downloads\evo4glteroot2 or something similar depending on where you unzipped the folder
Click to expand...
Click to collapse
said sending boot this time.Did I get it right thus far?
It should say OK and give a write time. Now you can try to reboot normally
om4 said:
It should say OK and give a write time. Now you can try to reboot normally
Click to expand...
Click to collapse
MAN!!!!!!!!!!!!!!!!!!!!!!!! you saved me! This has to be done with each rom? My phone screen blacks out with this CyanogenMod 10. Is there a more stable rom or can i go back to stock?
Can you explain black out? You only have to flash the kernel when switching base ROMs or when the kernel for your ROM has any significant changes. Its usually a good idea to flash the kernel anyway. I got a ton of info in my guide, the link is in my sig
Hello everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
cficklin31 said:
Hello everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
Click to expand...
Click to collapse
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
flumpster said:
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
Click to expand...
Click to collapse
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
cficklin31 said:
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
Click to expand...
Click to collapse
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
flumpster said:
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
Click to expand...
Click to collapse
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
cficklin31 said:
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
Click to expand...
Click to collapse
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
flumpster said:
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
Click to expand...
Click to collapse
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
cficklin31 said:
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
Click to expand...
Click to collapse
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
flumpster said:
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
Click to expand...
Click to collapse
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
cficklin31 said:
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
Click to expand...
Click to collapse
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
flumpster said:
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
Click to expand...
Click to collapse
Thanks,
Just to make sure I know what I'm doing. I have put the blob file in my ADB directory. Now are these the commands? :
adb shell
fastboot -i 0x0b05 flash recovery twrp.blob
Then if that doesn't work, I try:
adb shell
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
In that post you say to reboot normally, not to recovery. But since I have no rom installed, I need to go back to recovery and try to flash the Hairybean 2.11 rom again. Is that correct?
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
cficklin31 said:
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
Click to expand...
Click to collapse
Fastboot is not adb. You need the Fastboot.exe
---------- Post added at 08:11 PM ---------- Previous post was at 08:04 PM ----------
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
I am going to brick my tablet like yours to try and get out of it.
Try the Fastboot method for now from bootlader.
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
cficklin31 said:
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
Click to expand...
Click to collapse
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
flumpster said:
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
Click to expand...
Click to collapse
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
cficklin31 said:
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
Click to expand...
Click to collapse
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
flumpster said:
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
Click to expand...
Click to collapse
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
cficklin31 said:
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
Click to expand...
Click to collapse
You can only use nvflash if you created backups with it while on ICS.
You know when it says that sending recovery/writing recovery in fastboot, do you see a blue line filling?
No, there is no blue line. Nothing on the bootloader screen seems to change at all.
Sent from my SCH-I535 using xda app-developers app
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Sane116 said:
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Click to expand...
Click to collapse
what about installing the first RUU?
i think it can help you
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=s-on
This is actually exactly what I need, however I can't even complete the first step by putting the files on the internal storage, because it cannot be accessed via CWM as I don't currently have an OS.
koby058 said:
what about installing the first RUU?
i think it can help you
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=s-on
Click to expand...
Click to collapse
Sane116 said:
This is actually exactly what I need, however I can't even complete the first step by putting the files on the internal storage, because it cannot be accessed via CWM as I don't currently have an OS.
Click to expand...
Click to collapse
as for my understanding you don't need nothing to run the RUU
i think it is reinstalling all partitions from scratch
You can use adb push from both twrp and cwm... But yeah for the ruu you don't need to put anything on your phone.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 04:02 AM ---------- Previous post was at 03:57 AM ----------
Also if you are going to do the ruu, keep in mind that it flashes the radio as well. So if you are on a later radio you will need to flash that one
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
You can use adb push from both twrp and cwm... But yeah for the ruu you don't need to put anything on your phone.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 04:02 AM ---------- Previous post was at 03:57 AM ----------
Also if you are going to do the ruu, keep in mind that it flashes the radio as well. So if you are on a later radio you will need to flash that one
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Can't you plus a recovery img in fastboot using
fastboot flash recovery nameoffile.img
Sane116 said:
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Click to expand...
Click to collapse
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
sdamark said:
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
Click to expand...
Click to collapse
hello sounds like sound advice my relative did the same but i dont know how to get the phone to be recognized by my computer because when i put the commands to see the device it dosent work it say device error because it dosent see it. you have any pointers on how i cant help out in this mess. i tried to use commands in fast boot and in adb and i got nothing system wont mount cant flash ruu nothing. any information would be very appreciative. im at a lost this is a first for me so not sure where to go. searched for hours and cant find what i need.
demon28 said:
hello sounds like sound advice my relative did the same but i dont know how to get the phone to be recognized by my computer because when i put the commands to see the device it dosent work it say device error because it dosent see it. you have any pointers on how i cant help out in this mess. i tried to use commands in fast boot and in adb and i got nothing system wont mount cant flash ruu nothing. any information would be very appreciative. im at a lost this is a first for me so not sure where to go. searched for hours and cant find what i need.
Click to expand...
Click to collapse
Try installing PDAnet on your computer.
You don't really need the tether app part of the install, but it doesn't hurt.
The main thing you are after, is the drivers it will install.
Run the installer and follow the prompts on your monitor.
That should get the device recognized, assuming you have adb/fastboot set up properly.
Your going to laugh but install pdanet and it will reinstall adb. I don't like cwm I'd advise u gonwith twrp unless ur going to use cm 11
Sent from my HTC6435LVW using XDA Premium 4 mobile app
have you fix this problem help me same problem
I accedently format the internal my android device huawei g610 in my computer now it wont open. Plss help mee
Thank You Very Much
sdamark said:
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
Click to expand...
Click to collapse
Hello. A real big thank you for you. You gave me a big hope by the two words "Dont Panic". Your advice was a huge hint on how to get back my HTC One. I researched on ADB Sideload and within One Hour I got back my phone to normal. Thank You. You are God!
I downloaded a custom ROM and did the adb sideload. It worked. If computer doesnt recognise your device in recovery, try plugging it into other usb ports on your computer.
I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
vwnut13 said:
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
Click to expand...
Click to collapse
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
toxinburn said:
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
Click to expand...
Click to collapse
Is your device activated. Straight Talk said that reset via recovery (it's in the phones manual...) would work after activated, but that seems like BS.
full user guide from LG
Okay I got the full user guide that was NOT included this is the LG Full guide. Just Click it, had to put it on 4shared as it is too large to upload as .pdf on here.
Root worked for me after I followed this guide. http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/ Make sure you change the values in post #1, and remounting /system as explained in reply #1.
vwnut13 said:
I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
Click to expand...
Click to collapse
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
---------- Post added at 07:51 AM ---------- Previous post was at 07:46 AM ----------
yackaro said:
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
Click to expand...
Click to collapse
now that i think about it my device was bricked.... maybe this is a special recovery designed to act only when problems are detected in the boot sequence?
Well, looks like I'm in the same boat now, lol. Going against everything I've learned in the 5 years messing with Android, I had a non-thinking DOH! moment and changed the screen density. After reboot, I just have a bootlooping cheap paperweight for the time being. I can get into recovery, but there's no menu options. I am going to try to push the backed-up build.prop.
They really have this one locked down. I haven't found an OTA zip in my searches yackaro, but I'll keep an eye out for you.
root for lg fule kinda works
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
ColtonDRG said:
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
Click to expand...
Click to collapse
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
skyline247 said:
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
Click to expand...
Click to collapse
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
ColtonDRG said:
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
Click to expand...
Click to collapse
True. They probably are. I don't know why they would block at least hard factory reset, though. But then again, since we paid for our device (albeit only $30) seems like we could have more freedom with it. Oh well.
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
FlyingPoo said:
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
Click to expand...
Click to collapse
Sounds like we are a little closer, however you can push a .img thru adb already I know some people that did a mako build only problem is it bricked it.
thatguyrightthere said:
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
Click to expand...
Click to collapse
It's the new security features of kitkat. Only allows apps to access their own folders. Try SDFix (root app from play store ). I now can read, write, copy to/ from sd or system.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 09:16 PM ---------- Previous post was at 08:55 PM ----------
@FlyingPoo
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 10:00 PM ---------- Previous post was at 09:16 PM ----------
[/COLOR
@FlyingPoo
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Sent from my LGL34C using XDA Free mobile app
ibub said:
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Click to expand...
Click to collapse
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
ibub said:
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Click to expand...
Click to collapse
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
FlyingPoo said:
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
Click to expand...
Click to collapse
Yeah, we might only get one shot at success (before jtag ), so it's probably best to compile from our recovery and source. I used Apktool to decompile recovery (dd if =dev/ block/ mmcblk0p17 of =/cache/ testrecovery/recovery.img). Ramdisk has./ sbin/recovery. Copied that to /Sbin/ . Disappears after reboot. Haven't yet decompiled boot.img. Hoping to find "boot", and fastboot. More later.
Sent from my LGL34C using XDA Free mobile app
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
ibub said:
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all your work. Im also very interested in being able to boot into stock recovery. Mainly to be able to preform a factory reset. Do you know of an alternative method to do a factory reset at this time since booting into any recovery isnt possible ATM?
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.