For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Did you use ROM manager to flash CWM? It can cause bootloops.. Try roaches repacked touch thread, he's got a diff of the fix there.
Hmm. Tried flashing roaches touch but it wont stick. Also tried updating to the latest from rom manager but that wont stick either.
I use 4ext recovery on my desire z but the app isnt available from tablets (mine anyway).
I run linux and dont have adb setup. Is there any other way to flash recovery?
Sent from my Transformer TF101 using xda premium
No, what I mean is, use the fix in Roach's thread to fix recovery. Don't just ROM manager, it just doesn't work on the tf101 very well. Use Gnufabio's RecoveryInstaller app (in development) to flash CWM 3.2.0.1 then update to a later if you wish, manually without ROM manager.
^^
Reading your post, if you have no access to android on your tab (you have ubuntu only) then you need to set up adb to fix it. I assume you're running android though.
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
The bad thing is .. I can't even cold boot into android ..
As of my knowledge cold-booting is volume-down + power.
This only takes me to recovery again, no matter what I do..
So when you hit the button combo do you see the asus screen with some writing at the top left? Something along the lines of 'press up for recovery or wait 5 secs for other options'.
Sent from my HTC Vision using xda premium
If you can access adb shell from recovery, flash a new recovery using:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4
reboot
Place the recoveryblob extracted from the CWM flashable zip somewhere on your tf accessible from cwm.
MarkyG82 said:
For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Had to use it tonight big thanks..
I have the same problem, after flash a kernel [KERNEL][ICS] Harmony (OC/UV), boot loop on recovery (rogue XM 1.5.0), tried in adb to push a recovery blob, but don't work....
Line error is /sbin/sh: push: not found
The same with the other comand, like: device, /sbin/sh: device: not found
I have tried a flash, new rom, new kernel, new recovery, any trick but nothing!!!
in adb only reboot comand work
Help me please
try the /temp/ folder or somewhere like that, which doesn't need system write permissions, or mount the system as writable. The commands to use after getting the blob on are a few posts up.
I've try this, dd if=/sdcard/blobrecovery of=/dev/block/mmcblk0p4 end adb whrite new recoveryblob, but after reboot won't work, restart anytimes on recovery....
If nothing else works, try NvFlash (in my sig) just released for Sbkv2
I also facing same problem. When i switch on my pad every time going to recovery mod can't go to android. restart anytimes on recovery....
Try a reflash of recovery, if all else fails, Nvflash.
Ok so run into same problem. However I can't get ADB to recognize it, I also can't get it to cold boot. Then lastly I can't get the version on her to see the sd card so I can't even load files onto the tablet to even try running the one script that was on here. Any suggestions from here?
Ok so managed to get it back to cold boot after running a new rom into it. Dunno why that'd work but it did. Gonna keep this file in place permanently. Would still like to see other options if you were in my spot since everything seems to rely on everything I was missing.
Nvflash. Yet again, only true rescue in a really bad brick situation.
MarkyG82 said:
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Hi Marky,
Can you help me how you fix your problem because i also facing same problem.
Minnaing.
Can you cold-boot to android? Volume down + power and wait.
yes, I can go cool-boot to android.with Vol+
Related
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Did you wipe before restore?
davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!
DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....
Then NVFlash will fail still...
davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/
Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?
Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision
Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.
Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?
Hi everyone, I've got a BIG problem with my sbk2 TF101.
I don't know why but I cannot access the Recovery. I don't know if it is actually installed or not, but I cannot access it nor I can flash it with CWM Manager or Recovery Installer
-When I restart, it simply stucks at the EEE logo.
-I cannot boot in recovery with any of the apps made for this;
-Every time I want to start the tablet, I need to start it using cold-boot (first, vol- and power, and then vol+), because it seems to be always starting in recovery.
-Without recovery I cannot flash a new recovery or a new rom, and I'm stucked with an AOKP cooked in the firsts days of may (I don't remember the name)
-I've got random and frequent reboots, freezes, and can't do something for more than 5 min because the tablet freezes.
-Standard voltages.
-My tablet is not recognized when I plug it in Windows or Mac OSX, didn't try with Ubuntu.
Please help me!
Thank you very much in advance for your great help.
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Thing O Doom said:
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Click to expand...
Click to collapse
First of all, thanks a lot for trying helping me.
The problem is that I don't know how to use ADB or wich commands should I use or where I could find the boot.img. Using a virtual terminal means running a trminal on the tablet? Can I use the internal memory instead of an SD card? I can confirm I've still got root, by the way.
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
wanzer said:
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
Click to expand...
Click to collapse
Use PERI/my easyflasher tool to reflash recovery from nvflash.
Read more here:
http://forum.xda-developers.com/showthread.php?t=1688012
Hello guys, I have a problem with my tf101! is brick, and only goes with apx.provo easyflasher wheelie but returns error when it finishes loading bootloader towards the closed dell'applicazione!
sorry for the English, are Italian
I figured out that the OP had the ROM manager bootloop :/
Romyfra - is it a Tf101 Wifi-only or a Tf101G, if it's a Tf101 then you can use NvFlash to reflash it
I brick my wifi tf101 with serial bcoka ..., ICS v24ww 1.6e 4.0.3 I can not even come out with a wheelie! This is what I done, done correctly with the root easyflasher 0.4, after I stupidly installed netformer 1.6 (that idiot) and restart it disappeared with the cmw.ho riflashato easyflasher and end of proceedings, the tab will not light! is only apx, so no recovery! the problem is that when I start wheelie crash and does not pass to nvflash! is possible that the flash is corrupt?? as a last resort if you think I'll send you notice of changes in the RMA? ICS had no stock and cmw più.possono dump and see what happened or there is no trace?? thanks
Just picked up a TF101 and it had the Cryo (whatever it is called) OS with ClockworkMod Recovery v5.8.3.4. The OS didn't pick up wifi on the apps but it is on and logged into the router so I did a reset. Once I reset the TF101, i am stuck at CWM. It won't boot into any OS or anything else. I tried almost everything I found googling (this site and others) but nothing works. I did, however, got the TF drivers for my laptop so I can connect to it but I can't get the USB debug option on (of course).
So what are my options? how do I "unbrick" this thing? is this what some people call it soft-brick as it does boot but there just isn't any OS in there? I tried to put the OS zip file from Asus on a MicroSD but when I went to install zip from sdcard, it i can't get to the microSD to install it. it doesn't find it at all.
what can I do? what are the steps in unbricking this thing? I got this for my dad for father's day (chinese father's day which is TODAY...) and would like to get it to him.
Thanks in advance!
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
baseballfanz said:
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
Click to expand...
Click to collapse
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
chivas228 said:
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
Click to expand...
Click to collapse
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
baseballfanz said:
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
Click to expand...
Click to collapse
Sorry to sound ignorant but what's ad and what command (extra code after the .exe) do I add afterwards?
I'd try to flash a ROM via NVFLASH.
You may download it from here, but you must know if your TF101 is WW version, US version or any other. You must also know if your device is SBK1 or SBK2. That depends on the serial number. For example, mine starts by B50 and it's SBK1. If yours is SBK2 then you'll have to take a look at wheelie. If not, take a look here.
http://forum.xda-developers.com/showthread.php?t=1620758
However, I'm not responsible for any damage your device might suffer.
Take a look at that and tell me
here's the endall- easyflash version 0.8.3b whitekidneys just updated it and saved my brick. it'll save yours too. just install it on your computer, along with naked drivers 0.7, put the tf in apx, and flash. literally that easy.
Follow the link to easy flash / nvflash and follow the steps...
http://forum.xda-developers.com/showthread.php?p=26893961
Sent from my Transformer TF101 using xda app-developers app
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
thefunkygibbon said:
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
Click to expand...
Click to collapse
Try Install different recovery... download and flash the new recovery through CWM..
Sent from my Transformer TF101 using xda app-developers app
CWM-based recovery 6.0.1.9 for the Acer Iconia TAB A510
Another recovery build? Yes... But I can say this recovery is pretty safe. Having said that, however:
*** I am not responsible for anything that happens to your device ***
There is still a risk in bricking your tablet
I've been testing various different ways to get custom ROMs going on this tablet, for over 6 months now. Developing for this tablet seems kinda dangerous (compared to my private building on HTC devices), and I already had to send my device back to Acer because of a brick once. At this point, I guess this recovery seems pretty safe, and hence I'm willing to release it in public. This recovery is inspired by the CWM-based recovery 6.0.1.1 for the Icona TAB A700 by pawitp. So first of all, I want to say thanks for his work and the talks we had.
The recovery itself is built by me so all partitions on the A510 are propely initialized, sized, and mounted: Including access to both internal storage (the 'fake' sdcard) and external MicroSD cards, as well as the flexrom partition. As an additional (see below) precaution, i've supressed 'EMMC wipe' commands in the recovery.
The kernel for this recovery has been compiled by me, disabling all the MMC_CAP_ERASE functions to prevent the 'Samsung EMMC brick' from happening. This does not give you a 100% guarantee, but it comes pretty close.
As explained in this post, the new CWM recovery does not really format your /data partition. It simply removes all files with the 'rm' command, leaving your 'fake' sdcard intact. The recovery in this post does format your other partitions, but it should show this message: 'warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware'. Don't worry, that's a good thing!
Things to note:
I have mounted every partition with this recovery without problems
I have formatted/wiped every partition with this recovery without problems
I have backed up and restored (nandroid) every partition with this recovery without problems
I have installed custom .ZIP files with this recovery without problems
I still won't give you any warranties - This recovery can brick your tablet
How to install:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
Copy the file attached to this post (remove_recovery_from_rom.zip, (MD5: 73aea1147f571a83caeb8743cd5972b4)) to your tablets internal memory or SD Card. Download the CWM-Based Recovery by NoThrills for A510 tablets and save it somewhere on your computer.
Step 2:
If your device is already bootloader unlocked, skip step 3. Your boot screen (the one with the Acer logo when you turn the device on) should read Bootloader Version x.xx.xx-ICS (Unlock Mode). If your device is not yet unlocked, continue to the next step:
Step 3:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot oem unlock
Then, quickly press the Volume down (**) button on your tablet, followed by the Volume up (*) button to confirm the unlock. When done:
fastboot reboot
Step 4:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot flash recovery recovery_nothrills.img
This assumes you have put the nothrills_recovery.img in the same folder as the ADB utility.
Step 5:
Reboot your tablet with the following command, but you have to keep the Volume down (**) button pressed when the tablet boots:
fastboot reboot
Step 6:
Install the remove_recovery_from_rom.zip file from the Recovery, then reboot your device.
Your tablet now has this new recovery installed. You can enter the recovery by typing the command adb reboot recovery, or by booting your tablet with the Volume down (**) button pressed.
Downloads:
CWM-Based Recovery 6.0.1.9 (mirror) (mirror)
(MD5 for .img: 950b877a8d10d7de80ec7055b6367893)
CWM-Based Recovery 6.0.1.4 (mirror) (mirror)
(MD5 for .img: b0f9d33342943b44b998bd8f127800a8)
CWM-Based Recovery 6.0.1.3 (mirror) (mirror)
(MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Stock Acer 1.044.00 recovery (mirror) (mirror)(note: you only need this to return to a stock Acer recovery)
(MD5 for .img: 7b58b9b76c4e39cafa9d926b57fe08fd)
Anything else?
That's what this thread is for, so post away...
Reserved
Great news! I'll have a try after i get my tab back.
btw, is there any Custom Rom available for A510?
finally we have CWM! Can´t wait to get CM10 on my A510!
Seems to work quite well, so far no probs - thank you
Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.
Great, thanks !
Great piece of news!
jessejames44 said:
Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.
Click to expand...
Click to collapse
Make sure to have the required DLLs in the same directory you are executing adb from (or in a specified PATH).
Sent from my A510 using xda app-developers app
Well I flashed this and even though it says the recovery is successfully written, when I reboot into recovery all I get is the android with the red exclamation mark and it never boots into the recovery at all??? weird.
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
I have tried both of the files from the regular and the mirror sites and it says it completed ok, but I still do not have the custom recovery. I have done this many times on different devices and this is the first time it does not work, I am following the instructions by the letter too. LOL!!!
Anyone with A511 tested it ?
Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.
Jesse6749 said:
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.
Click to expand...
Click to collapse
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.
jokerzlh said:
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.
Click to expand...
Click to collapse
I did check the MD5 and it matches the MD5 on the OP and on your post as well, so the file is good. I have re downloaded the file 4 times already too.
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
This is what I'm thinking as well. I should probably edit the instructions on the first post, as I didn't think about the fact that people might not have the recovery_from_boot files removed.
Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today. I got it to boot into recovery once and then went back to the dead android, then I followed the updated instructions on the op and now it works every time and it boots into the CWM recovery every time.
Sent from my Transformer Prime TF201 xda premium
Jesse6749 said:
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today.
Sent from my Transformer Prime TF201 xda premium
Click to expand...
Click to collapse
I've updated the first post with a 'remove recovery' .ZIP file. Follow the new instructions and you should be set.
Super cool to see the development for the A510 finally with some results!!!! I love tyo get some custom stuff for our A510's...is there anything I can help you with? If there's something I could do to speed up the custom ROM process, just ask
So I am stuck.
Info:
Using CWM 6.0.1.3
Updated to 10.6.1.8 via Asus using recovery.
Now some reason its going to an infinite boot loop straight to the CWM recovery.
Holding Vol down while its rebooting wont go to fastboot, but after it goes to Recovery, I can adb it to go to fastboot with adb reboot-bootloader.
But once there it does not show lists of devices. So I will get a freeze up when flashing anything. It says successful in CMD, but once holding down the power button for it to restart, I see no changes. Tried changing Recovery's, blobs, and stuff. And the Sdcard wont mount. Only thing I can mount is System and Cache. If the Sd mounted, I would be able to do a easy recovery, but I cant do ANYTHINGGG.
Blahhhhhh
Also, when flashing stock asus blob again, I see the Green box in fastboot glowing a bit, like lagging, but no progress bar. Its been running for 40mins now. Dont think its working...lol
pyovue said:
So I am stuck.
Info:
Using CWM 6.0.1.3
Updated to 10.6.1.8 via Asus using recovery.
Now some reason its going to an infinite boot loop straight to the CWM recovery.
Holding Vol down while its rebooting wont go to fastboot, but after it goes to Recovery, I can adb it to go to fastboot with adb reboot-bootloader.
But once there it does not show lists of devices. So I will get a freeze up when flashing anything. It says successful in CMD, but once holding down the power button for it to restart, I see no changes. Tried changing Recovery's, blobs, and stuff. And the Sdcard wont mount. Only thing I can mount is System and Cache. If the Sd mounted, I would be able to do a easy recovery, but I cant do ANYTHINGGG.
Blahhhhhh
Click to expand...
Click to collapse
Well, you are not the first to run into this issue; lots of similar reports in these forums...
As far as I know, there is no way out yet, unless you count sending it to Asus service.
You might want to read up the threads on the 4.2 bootloader. Though reading them ahead of time would have been cheaper.
Sent from my TF300T using Tapatalk HD
As you can still access fast boot, this thread might help you:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD