I don't know what to do now - Eee Pad Transformer General

hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,

I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.

Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app

If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method

sfetaz said:
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Click to expand...
Click to collapse
I hope there is program like that
Backwardsblade said:
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think so.
I try but don't find the device
frederuco said:
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
Click to expand...
Click to collapse
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21

1090t said:
I hope there is program like that
I don't think so.
I try but don't find the device
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
Click to expand...
Click to collapse
unzip first. inside another zip file.

goodintentions said:
unzip first. inside another zip file.
Click to expand...
Click to collapse
Yah, i do that

.........................

why is the only rom i can install and work is the: Android Revolution HD ?!

1090t said:
why is the only rom i can install and work is the: Android Revolution HD ?!
Click to expand...
Click to collapse
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.

1090t said:
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
Click to expand...
Click to collapse
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.

goodintentions said:
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
Click to expand...
Click to collapse
it doesn't work i just wait there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is that right why to boot in to rom (from cold-boot) ?
horndroid said:
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
Click to expand...
Click to collapse
I try many time with these the Recovery still same
even with the old version ..nothing

1090t said:
it doesn't work i just wait there
is that right why to boot in to rom (from cold-boot) ?
I try many time with these the Recovery still same
even with the old version ..nothing
Click to expand...
Click to collapse
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.

feisty_noodle said:
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
Click to expand...
Click to collapse
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.

The op's problem is very similar to this one http://forum.xda-developers.com/showthread.php?t=1549062 which has been resolved.

goodintentions said:
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
Click to expand...
Click to collapse
You are right, I may have misinterpreted the OP.
Still, I think the solution is the same.
When the device boots into recovery and can be cold-booted into ROM, the most likely culprit is the 'boot-recovery' flag which is set in the /misc partition. When the system sees that upon boot, it goes straight into recovery.
It should be the recovery's job to blank out that flag at some point, but CWM 5.5.0.4 (and, perhaps this recovery the OP is using) does not do this.
So, the solution is to reset it with the 'echo ...' command (or blanking out the first few bytes of /dev/block/mmcblk0p3) in shell.
My suggestion is very conservative.

I'll gave try and let u know

when i connect to the computer nothing shows up
even the Asus sync don't found it
I'll gave try on Linux

any help

Related

[TOOL][Updated 5.9.12]viperMOD PrimeTime v4.6 | Auto Root/Unroot/Busybox/CMW Flash!

Original Thread: ASUS TF201 Prime
This has been confirmed working! Using Option 1. on the asus TF101
-viperboy- said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PrimeTime Reviews
​
I do not have a TF101 anymore, but it has been reported that you can root the latest ICS update via option 1. Do so at your own risk! And PLEASE don't flash recovery if you're not on a Prime. That option is ONLY for TF201's!!
THIS WILL NOT ROOT .21 AT THIS TIME!!​
Introducing viperMOD PrimeTime! An automated rooting program for your Asus Transformer Prime TF201 (ICS or HC supported) and the Asus Transformer TF101. It is very simple and easy to use with extra features that other root methods don't have. Works on Prime's that lost root with the ICS OTA! Now, here is how it works...
Download the .zip
Plug in your Transformer and make sure to install the drivers located in the included .zip (unless you can already adb into your device, then no need for drivers)
Kill Asus Sync and Splashtop! - very important!!
Make sure you have NO OTHER ANDROID DEVICES connected via USB!
If on Linux, you may need to do "chmod a+x /path/to/primetime/primetime.sh" (no quotes)
Run the viperMOD PrimeTime.exe and choose an option.
After rooting, download OTA Root Keeper from the Market!
???
Profit?
It's as simple as that! I have tested this about 30 times (both rooting and unrooting) and it works just fine! I would HIGHLY recommend downloading Voodoo Root Keeper!! Any issues or questions, please feel free to post here! Enjoy your rooted Prime
Things you should NOT do!
Try to root with the Transformer in the dock
Use a USB extension cable
Not download OTA Root Keeper
Not follow directions
Updated 5.9.12 - v4.6
Replaced OLD CWM recovery with latest TWRP 2.1
Fixed sparkym3's donate link
HC root based on NachoRoot by jcase and TeamAndIRC.
ICS root based on TPSparkyRoot by sparkym3.
Latest ICS root based on https://github.com/saurik/mempodroid by Saurik.
Download
Windows (v4.6): Main Link, Mirror 1, Mirror 2
Linux/Unix (v4.1 - update coming soon!): http://bit.ly/PrimeTime_v4_1_Linux​
Click to expand...
Click to collapse
Trully i managed easily to root my TF101 S/N B80 with ANDROID ICS but when i enter the recovery mode (by pressing power and down and the the up volume) i take a black screen and a dead droid with a warning sign and after a long waiting time it boots to the operating system
What has gone wrong with flashing it?
Same problem with this guy ( http://forum.xda-developers.com/showpost.php?p=22999664&postcount=1042 )
Any suggestions?
ASUS EEE TRANSFORMER TF101 B80
Bratsaki said:
Trully i managed easily to root my TF101 S/N B80 with ANDROID ICS but when i enter the recovery mode (by pressing power and down and the the up volume) i take a black screen and a dead droid with a warning sign and after a long waiting time it boots to the operating system
What has gone wrong with flashing it?
Same problem with this guy ( http://forum.xda-developers.com/showpost.php?p=22999664&postcount=1042 )
Any suggestions?
ASUS EEE TRANSFORMER TF101 B80
Click to expand...
Click to collapse
Did u install cwm manually because i did so and cwm works
Sent from my Optimus 2X using xda premium
I added manualy with the RecoveryInstaller.apk adn i use ClockworkMod Recovery v3.2.0.1 roach2010-tf101-r1.
But i cannot apply update from sdcard or even mount sdcard.
I have the error E:Can't mount /sdcard/update.zip
Even if i try to mount my USB device i have the error:
E:Unable to open ums lunfile (no such file or directory)
As a result i cannot install any custom rom or another CWM. If there was a diferent CWM installable from .apk file if would be great
Bratsaki said:
I added manualy with the RecoveryInstaller.apk adn i use ClockworkMod Recovery v3.2.0.1 roach2010-tf101-r1.
But i cannot apply update from sdcard or even mount sdcard.
I have the error E:Can't mount /sdcard/update.zip
Even if i try to mount my USB device i have the error:
E:Unable to open ums lunfile (no such file or directory)
As a result i cannot install any custom rom or another CWM. If there was a diferent CWM installable from .apk file if would be great
Click to expand...
Click to collapse
Wierd i used roach one and worked fine, try re-install
My new TF101 has a serial number starting with BB0, and was upgraded to stock ICS downloaded from the Asus website (US build version US_epad-9.xx....). Is this the appropriate tool for rooting my TF101? Do I need to install CWM first before rooting? Thanks!
mj56gt said:
My new TF101 has a serial number starting with BB0, and was upgraded to stock ICS downloaded from the Asus website (US build version US_epad-9.xx....). Is this the appropriate tool for rooting my TF101? Do I need to install CWM first before rooting? Thanks!
Click to expand...
Click to collapse
yes, it works fine! Just run it and choose the first option (tested with TF101 B80, WW_epad 9.2.1.11). Have fun!
Bratsaki said:
I added manualy with the RecoveryInstaller.apk adn i use ClockworkMod Recovery v3.2.0.1 roach2010-tf101-r1.
But i cannot apply update from sdcard or even mount sdcard.
I have the error E:Can't mount /sdcard/update.zip
Even if i try to mount my USB device i have the error:
E:Unable to open ums lunfile (no such file or directory)
As a result i cannot install any custom rom or another CWM. If there was a diferent CWM installable from .apk file if would be great
Click to expand...
Click to collapse
You do have a removable micro sd card inserted into the TF correct?
Confirmed root here :
brand new TF101
HTK75.ww_epad-8.x.x.x
S/N : BCOKAxxxxxx
Unboxxed, plugged in , option #2 done !
Impressive tool, keep up the good work !
With viperMOD PrimeTime v4.5, I successfylly Rooted my TF101 with ICS 4.03 and firmware update WW 9.2.1.17. The root tool is amazingly simple and good. However, I have the following concern about unroot:
After rooting, I manually installed ROM manager, flashed clockworkMod recovery (current recovery clockworkMod 5.5.04) and nothing else. ASUS is goning to put a new OTA and I would like to get ready for it. I would greatly appreciate it if anyone can help me with the following questions:
1. Does OTA rootkeeper work for a rooted device with cwm recovery and stock ROM?
2. Does viperMOD unroot tool take care of restoring stock recovery automatically during unroot process?
3. If stock recovery has to be done manually, how to do it and where to get the ASUS WW recovery image?
Many thanks in advance.
e
as
to go back to the stock recovery for the OTA and then switch back to clockworkMod recovery. Would
you please tell me:
1. How to restore the stock recovery?
Does option #1 work on TF101 B80 HC 3.2.1, WW_8.6.5.21?
Or should I use #3? Thanks...
I don't want to update to ICS!
I had a B60 on .21 and option #3 worked for me. I tried #1 and it looked like it worked but no root, then I tried #3 and got root.
I used the method on my TF101 ICS and it worked great. Used option 1 and I was rooted within five minutes. The person that created this was a GENIOUS!
Sent from my Triumph using Tapatalk
Damn. Hate to be that guy but..
I have done this before on roomates computer easily. Well I just did not know to do option 1. I installed the drivers and everything. It keeps saying "error more than one device and emulator"
It says my build is 9.2.1.17
Does that not support root anymore?
Damn really?!
So I read it might be something about ADB being active.
I did factory reset on my tablet and had no apps running. They started to install but I stopped them. Somehow, superuser was installed though. I deleted it last time.
Still that same error message. What multiple emulator is running? Do I need to not back up anything. Don't know how to wipe the dalvik and everything on non root and non cwm
Worked great for my Transformer on 9.2.1.17 (ICS 4.0.3). The first option that is.
Thank you.
So, that error about more then one emulator running has been dealt with.
I used roomates computer and it worked flawlessly. I think it's because I have bluestacks running. Technically, that is an android emulator. I did notice that ADB was running and it was also why it worked on my roomates PC. But anyways I'M ROOTED NOW YAY. So easy if your computer is not screwed up.
Unlocking Issue
I have no luck to unlock my rooted TF101. I tried option 5 and unlock program gets installed on my Epad but when I run it, I get "This device is not supported" error. Any help how to unlock TF101 with ota ICS will be greatly appreciated.
Getting a 404 File not found on the download link.
Krojack said:
Getting a 404 File not found on the download link.
Click to expand...
Click to collapse
same here. sadness.

[Q] flashing cwm recovery

I have flashed skrilax v8 unlocked BL with v8pubA50 recovery
I flashed it using blackthund3r ATX flashtool
My question is
1. Why I can't enter boot recovery, it's just show green robot with exclamation at its body
2. How I can flash cwm recovery since it's extension is .Img
(fyi). I use UNroot A501 with stock HC 3.2.1
Thanks
Sent from my A501 using xda app-developers app
Help help :'(
gigacats said:
Help help :'(
Click to expand...
Click to collapse
IF you are sure you have the v8 bootloader installed, you should be able to install a recovery.
You must have an ICS rom installed, or on the Ext SD card, have an ICS rom ready to flash.
If you currently have a stock ICS rom installed, then you need to be rooted, and delete the "boot recovery" file (or similar name). Or else when you boot your tab, the custom recovery gets overwritten.
You can look at Civato's Bootloader and Recovery guide for the exact name of the file.
Note that v8 bootloader and ICS recoveries, DO NOT work well with HC based roms. You must have an ICS Rom.
MD
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
gigacats said:
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
View attachment 1218774
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
1) the robot is the 'stock recovery.img'
2) you must be rooted before you can flash 'anything'
3) The only way to do this (on HC) is by installing a custom pre-rooted rom
4) If you want ICS your tab should update itself, you will need acer enhancement app from the market. then Settings>About Tablet>System Update
5) you can install a stock or custom ICS rom BUT you must have root to update to the patched bootloader which some of the custom roms require.
6) you cannot "open" recovery.img.
Ok, so please stop posting the same issue in other threads, or you will never get your problem solved.
Now. You say you have Skirlax_cz's V8 bootloader installed. Correct? If so, you should be able to boot into the menu system of it (vol+ and PWR). If you get the bootloader menu, good.
Now, you will need the Android SDK (google it and download and install it). After installation, go to c:\windows\program files (x86)\android\android-sdk\platform-tools. Open a command window here. (it may be installed in program files)
Boot your tablet like I described above, and at the bootloader menu, select "fastboot". The tablet should say fastboot mode.
Now, copy your recovery.img (or whatever you named it) into the platform tools folder on your PC. It has to be in the same folder as fastboot.exe
Now, make sure you have the rom you want to install on your EXT SD Card.
Next, plug in your tab to the USB (I always make sure in device manager that the tab is recognized as a fastboot device)
In the command window you opened earlier, type in the following;
fastboot flash recovery recovery.img
Remember, if your recovery image is named "public-recovery.img" for example, that is what you should type in the command above.
Once the recovery is successfully flashed, then turn tab off.
Unplug from USB
Hold PWR and Vol- untill you see the message "booting recovery kernel", then release both. You should boot into the custom recovery now. Then you can do your wipes and stuff as per the rom install instructions.
Of course, this is ONLY if you have the V8 bootloader running.
Also, I posted a better rom. Evil Alex Unleashed, so you should install this. It has problems fixed.
MD
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
gigacats said:
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
Click to expand...
Click to collapse
Wow! It worked!!!!!!!!!!!!
Damn, better than I thought.
Gotta love Skirlax_CZ and putting flashboot in the bootloader v8. Throw a thanks at him when you get the chance please. And if you used EZTerry's public recovery, please throw a thanks at him also. And anybody else who helps you. That's how it works here.
I hope you installed Evil Alex. She's much better than Alex V. Alex V is a good girl, but she need the wakelock app from the market. Evil Alex hopefully does not. After all, these are Acer leaks. AKA "beta". So we really don't know what to expect. And things "will" change in the next month, and new builds "will" be released.
Am glad you got it running.
And Dibbs, throw a thanks to him also His instructions were after all, correct (he didn't know your V8 was working).
Any issues, please put them in my rom thread.
MD

[Q] Problem with my A500

Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Vipe.teo said:
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Click to expand...
Click to collapse
You need to unlock your bootloader and flash a recovery
blackthund3r said:
You need to unlock your bootloader and flash a recovery
Click to expand...
Click to collapse
Thanks for your reply, can you recommend threads to teach me how to go about doing it?
I believe Mlopik page did mention if I follow correctly, I would have already unlocked my bootloader, am I right?
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Moscow Desire said:
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Click to expand...
Click to collapse
Hi, thanks for coming to my aid, sorry for PM-ing U asking for help.... but I'm a super noob for this....:silly:
1) I have a boot screen by Skrilax_cz, but how do I fastboot a CWM recovery via a command prompt window?
2) A few min ago, I tried to use AfterOTA it got stuck at [3/4 flashing recovery] for a long time..... (Force restart)
3) I saw a solution <Click Here> then after downloading the recovery.img and running the code... It say done but after i restart nothing happen.
4) I continue using AfterOTA, again it got stuck at [3/4 flashing recovery] for a long time.....(Force restart)
I out of option....
erm... Help ???
Use fastboot to do a complete wipe.
Run ICSROOT. Zip to get rid of the boot.p file.
Reflash the v8 and cwm using apxflash tool
Boot straight to cwm and flash yr rom.
Do not use any type of rom manager apps to flash roms
Sent from my GT-I9300 using Tapatalk 2
FIXED !!!
Yeah !!! Got It to work !!!
Big THANKS to all who have help and spend time answering my noob questions...
THANK !!!!

[SOLVED][HELP] Wrong rooting went down to boot fail (Pics and Video)

First of all I want to tell everybody I work as a WebDeveloper and designer. Last year I had rooted and changed my rom on HTC HD2 (to know i am not a newbie to this area) not a big deal. Me and my brother decided we can root our ACER ICONIA A500 because we.. just wanted it, but I guess we mess it up hard. Here is what we have done:
1.Find a SD card - Format it to FAT32 - Upload the GingerBreak.apk - USB Debugging (ON) - Original thread - http://forum.xda-developers.com/showthread.php?t=1055354 - DIDNT WORKED
2.Format the SD card for second time on FAT32 and run the files on PC from this thread http://forum.xda-developers.com/showthread.php?t=1546593 (ofcourse following all steps one-by-one) - and guess what -> IT DIDND WORKED
So we tought rooting for this device wont work, we have to try something else and I uploaded "update.zip" (this ZIP was from http://forum.xda-developers.com/showthread.php?t=1633907 ) into my formatted SD card and run the tablet with Power btn and Vol- it started to load it everythig seemed OK till it restarted by itself and showed me this VIDEO
So where I am now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
on the second pic it says "boot verified failed..."
The version before I bricked it was with Android 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer _AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.031.00_WW_GEN1
P/N: FM.S14A0.00U
What can I do now?
EDIT: I've got it running back by putting stock "Acer_AV041_A500_1.031.00_WW_GEN1" into SD card naming it update.zip and booting by Pwr btn and vol-
But Now... How to root it?
If u never root or unlock bootloader so maybe your a500 still on hc bootloader n u just doing upgrade it into ics rom woth hc bootloader with unsigned version update. Zip,maybe u can find how to push the honeycomb rom update. Zip into root of sdcard using adb and doing flash again pwr+vol -
Sent from my HTC Desire VC
oregorn said:
But Now... How to root it?
Click to expand...
Click to collapse
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM
Moscow Desire said:
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM
Click to expand...
Click to collapse
This is like step 1 then step 2 or just three different methods I can get my tablet rooted?
Could you please help me with some links? Thank you
oregorn said:
Thats the options like step 1 step 2 or just methods i can get root?
Could you please help me with some links? Thank you
Click to expand...
Click to collapse
The ONLY way to get root with full system RW, is to go to this thread;
http://forum.xda-developers.com/showthread.php?t=1622425
There are several ways to do this (unlocked bootloader and CWM) You HAVE to do the bootloader, and you HAVE to install a CWM. And you HAVE to install a pre-rooted rom. The thread offers different methods to do this via an application run from PC.
Root, is just allowing access to view the hidden system files. Most root apps, demand to do writes to the /system. Example, is SU. It does remounts so it can install SU binaries. Just having the Superuser app doesn't mean anything without /system RW. And the only way you get that, is by running an insecure kernel. And the only way you get an insecure kernel on ICS/JB, is via CWM. And of course the only way all this works, is via unlocked bootloader.
That's why we have the package in that link.
You "might" get by with doing the bootloader and CWM. Afterwards, Flash one of the kernels in the dev section (just look), then install SU and Busy Box from the market. This might probably keep your current rom intact. Or, just install a custom rom.
Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.
oregorn said:
Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.
Click to expand...
Click to collapse
Can't see anything from yr links for some reason BUT to clarify.
No you are not right!
If you want root to install a recovery, it doesn't work like that with the acer, you must unlock the bootloader.
The unlocked bootloader AND custom recovery are 1 package - if the flash is successful you will already have cwm.
The link Moscow provided you with gives you everything you need.
Which ever method you choose (manual nvflash or auto tools) you must follow each step to the letter!!!
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
If you really only want r/w access use blackthund3r's ICSRoot tool...in the link Moscow posted.
Also if you are on stock rom be sure to read that post regsrding boot.p file.
All of this information is in that post, please take some time to read thru it so u know exactly what is involved. ...if u need further help there are guides in my sig as well.
dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
dibb_nz said:
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
Click to expand...
Click to collapse
This is the word i was missing all time.
What i have done?
Installed TWRP, Wiped off SYSTEM,Factory, Dalvik Cache, Cache and finally installed stock rom with full root.

[Solved] [Q] [4.4] [Nexus 7 2012 3G] Rooting problem: ineffective flashing of superSU

Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Solution
I was just using outdated tools : my version of CWM and SuperSU were both too old to work on 4.4.2
Always get the latest of those two on their respective websites.
OneXdude said:
Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Click to expand...
Click to collapse
Hi, OneXdude...
Due to security changes in KitKat, Chainfire had to re-work the way root worked, so it's probable your rather old SuperSU-v1.80 (which worked with Jellybean) is the cause of the problem...
Try the latest version, SuperSU-v1.93...
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Rgrds,
Ged.
Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"
OneXdude said:
Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"
Click to expand...
Click to collapse
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.
GedBlake said:
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.
Click to expand...
Click to collapse
I followed this exact procedure, but sadly the problem remains.
I still get the error message.
OneXdude said:
I followed this exact procedure, but sadly the problem remains.
I still get the error message.
Click to expand...
Click to collapse
This is very puzzling...
Rooting the Nexus 7 should be a piece of cake... it certainly was for me.
I have to go out for an hour or so... but when I get back, I'll test flash SuperSU-v1.93 on my own Nexus 7 using ClockWorkMod recovery.
Normally, I use TWRP for such things... but I'll see how it goes with CWM and see if I can grab some screenshots and any error messages that may result.
--------------------------
Incidentally, I notice the version of CWM you have installed, is an older version - v6.0.1.9... the latest is v6.0.4.3, and is available from here...
https://www.clockworkmod.com/rommanager
Possibly fastboot flashing a more up to date version of CWM on your Nexus 7 may resolve your problem.
Rgrds,
Ged.
Hi again, OneXdude...
Further to my previous post...
As I've said, I normally use TWRP recovery (TeamWin Recovery Project) for rooting and flashing stuff like Custom ROMs and flashing 'mods' like Xposed framework...but I have used CWM (ClockWorkMod) recovery in the past... so my recollection of how CWM works, as it currently stands, is now a little hazy.
Hunting around on my laptop, I find the earliest version of a copy of CWM I have for the Nexus 7, is v6.0.2.3 with a date/time stamp of 3rd of January 2013!!
Which means your currently installed version of CWM v6.0.1.9 significantly pre-dates that...
...and is very, very out of date!!. Possibly dating it back to 2012.
So, I would strongly recommend you update your version of CWM to the latest version... which is v6.0.4.3.
I suspect, because you're using such an old version of CWM to root, is the probable cause of why your attempts to root have so far failed.
---------------------
Anyway...
I've just test flashed SuperSU-v1.93 on my own Nexus 7 (2012-WiFi ony) model... via CWM v6.0.4.3.
And it largely succeeded... the SU binary was successfully 'pushed' to /system/xbin... the only thing missing was the SuperSU app itself.
I've had this rather peculiar problem before... but it's easily resolved by just installing it from Google PlayStore.
Here is my CWM v6.0.4.3 output listing, when flashing SuperSU-v1.93... and is the sort of thing you should expect to see...
(Apologies for the poor quality of this screen shot... both TWRP and CWM recoveries lack the ability to directly take screenshots, so I had to photograph the screen using my Samsung Galaxy).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------
So, in conclusion...
I would recommend you update your version of CWM to the latest version... and try flashing SuperSU v1.93 again.
Hope this helps... and good luck.
--------------------------------------------------
EDIT: Additional info...
Just spotted an incongruity/inconsistency in your first post... and which I have higlighted in red.
OneXdude said:
..
...I just updated my Nexus 7 2012 3G...
..
Click to expand...
Click to collapse
...and...
OneXdude said:
..
....by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
..
Click to expand...
Click to collapse
-----------------------------------
If your Nexus 7 is 3G capable (and has a SIM card it in it), then you MUST ENSURE you have the correct Custom Recovery installed for your specific Nexus 7 type.
So... not only are you running a very old version of CWM, you're also running an incorrect version of CWM.
-----------------------------------
A 'grouper' Custom Recovery is intended for WiFi only Nexus 7's... like mine, for example.
However, your Nexus 7 is a 3G Nexus 7... and so you need a 'Tilapia' Custom Recovery installed.
For the latest version of CWM for your 3G/GSM device, that would be... recovery-clockwork-touch-6.0.4.3-tilapia.img.
And which you can find here...
https://www.clockworkmod.com/rommanager
...under the title of Google Nexus 7(GSM).
Download to your PC... and fastboot flash it.
Regrds,
Ged.
You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.
OneXdude said:
You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.
Click to expand...
Click to collapse
No apologies required... What is obvious to some, may be obscure to others.
You got there in there end... and that's what matters.
But make sure you have the right version of CWM installed (see the edit to to my previous post)... it will matter if you need to perform NANDROID backups.
Rgrds,
Ged.

Categories

Resources