Ok hi guys while trying to get AOKP to work i was messing around with the blob tools and i flashed an update .zip with this blob and it just boots straight in to recovery tried the recovery fix no luck im on B80 so unless nvflash for sbkv2 comes out tomorow im guessing im screwed well heres the blob youtube video coming. Heres My recovery log
the first time i rebooted i held down the left rocker and it didn't even ask me if i wanted to wipe data or coldboot it just said wiping data booting to recovery
"wiping user data and indicators before cold booting Linux
Please wait a few minutes
Booting recovery kernel image"
Did you flash a custom recovery agent like CWM?
If not, you could try downloading the latest official ASUS firmware for your device. Unzip the file one time (it will still be a zip file) and put it on the top level of a microSD card and boot.
If you did flash a custom recovery, you will need to know how to get into the custom recovery agent. CWM hold VOL DOWN and POWER for 10-12 seconds and then press VOL UP within 5 seconds to enter recovery.
frederuco said:
Did you flash a custom recovery agent like CWM?
If not, you could try downloading the latest official ASUS firmware for your device. Unzip the file one time (it will still be a zip file) and put it on the top level of a microSD card and boot.
If you did flash a custom recovery, you will need to know how to get into the custom recovery agent. CWM hold VOL DOWN and POWER for 10-12 seconds and then press VOL UP within 5 seconds to enter recovery.
Click to expand...
Click to collapse
Thanks for the reply but i have cwm installed and when holding down it just straight boot to cwm with going to the coldboot menu watch the video you'll see
I downloaded the firmware file and it didnt even read it just booted straight to recovery
If you still have cwm recovery, try flashing a stock ROM. That should get you unroot and stock recovery.
You can then root and install cwm again.
baseballfanz said:
If you still have cwm recovery, try flashing a stock ROM. That should get you unroot and stock recovery.
You can then root and install cwm again.
Click to expand...
Click to collapse
I've tried flashing custom Rom after custom Rom it doesn't go throught the blob flash animation I don't want to try flashing a stock Rom and losing cwm then ill be completely screwed I think the staging partition might be borked but cwm formats it fine in the morning ill try the super wip script and see if that fixes it I really hope it isn't bricked
Sent from my HTC Amaze 4G using xda premium
tried the super wipe script with no luck no matter what the thing won't go in to the blob flashing part of the boot when a new blob would be found i don't know why
Mine does the exact same thing. Did you get it fixed?
sixcoronas said:
Mine does the exact same thing. Did you get it fixed?
Click to expand...
Click to collapse
Nope not yet I think it might be a problem with the mount points but I'm not sure I'm waiting for say roach or someone who knows about the internal workings of the device because I never really messed with it like I do my o ther devices
Sent from my HTC Amaze 4G using xda premium
sportsstar89 said:
Nope not yet I think it might be a problem with the mount points but I'm not sure I'm waiting for say roach or someone who knows about the internal workings of the device because I never really messed with it like I do my o ther devices
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I got mine going with nvflash from here:http://www.tabletroms.com/forums/transformer-general-development/976-nvflash-unbricking-forever-root.html
Ohh yeah, the 5.5.0.4 mount points are different- you might have to mount them through adb or flash a rom that is packaged to use the partition names, not mount points.
I think your TF is fine- it's probably just missing a rom so it keeps booting into recovery. Try flashing this- it's just a kernel, but the updater script doesn't rely on the mount points. If it flashes, then your tf is fine other than the lack of firmware.
http://www.mediafire.com/download.php?53oyqaib2jxra3r
gee one said:
Ohh yeah, the 5.5.0.4 mount points are different- you might have to mount them through adb or flash a rom that is packaged to use the partition names, not mount points.
I think your TF is fine- it's probably just missing a rom so it keeps booting into recovery. Try flashing this- it's just a kernel, but the updater script doesn't rely on the mount points. If it flashes, then your tf is fine other than the lack of firmware.
http://www.mediafire.com/download.php?53oyqaib2jxra3r
Click to expand...
Click to collapse
Trying now I really hope this works I don't want a broken 500 buck toy
Sent from my HTC_Amaze_4G using xda premium
gee one said:
Ohh yeah, the 5.5.0.4 mount points are different- you might have to mount them through adb or flash a rom that is packaged to use the partition names, not mount points.
I think your TF is fine- it's probably just missing a rom so it keeps booting into recovery. Try flashing this- it's just a kernel, but the updater script doesn't rely on the mount points. If it flashes, then your tf is fine other than the lack of firmware.
http://www.mediafire.com/download.php?53oyqaib2jxra3r
Click to expand...
Click to collapse
Ok i flashed it from cwm but nothing happened on reboot just right back in to recovery
sportsstar89 said:
Ok i flashed it from cwm but nothing happened on reboot just right back in to recovery
Click to expand...
Click to collapse
No blue progress bar at the eee pad logo?
gee one said:
No blue progress bar at the eee pad logo?
Click to expand...
Click to collapse
Nope it just won't go in to that blob flashing action but is there any word on nvflash for sbkv2 because I can get in to apx it has to be something software though so there has to be a way to fix it
Sent from my HTC_Amaze_4G using xda premium
Odd indeed- I wonder if it has to do with how you wiped the /misc partition. I'm not sure if there is other info in there, but if there was, it's gone now.
Problem is, somehow the 'boot into recovery' command got stuck - it won't even get to flash the blob.
You can do the following (fixed my tab when I had the same problem):
1. In recovery, connect to PC
2. ADB Shell into the tab
3. Clean the MISC partition (or whichever holds the boot commands) using dd:
dd if=/dev/block/zero of=(the partition, /dev/block/mmcblk0p[n] where N is the partition number of MISC) bs=1024
4. Flash any blob
5. Reboot for blob to get flashed.
gee one said:
Odd indeed- I wonder if it has to do with how you wiped the /misc partition. I'm not sure if there is other info in there, but if there was, it's gone now.
Click to expand...
Click to collapse
Yea no matter what its either not finding the blob or the part of the functionality the sees the blob has been currupted or deleted or something messed up with the mount points. Is the folks at android root.mobi still working on nvflash for sbkv2 or did they stop
Sent from my HTC_Amaze_4G using xda premium
sixcoronas said:
I got mine going with nvflash from here:http://www.tabletroms.com/forums/transformer-general-development/976-nvflash-unbricking-forever-root.html
Click to expand...
Click to collapse
What model number do you have
fonix232 said:
Problem is, somehow the 'boot into recovery' command got stuck - it won't even get to flash the blob.
You can do the following (fixed my tab when I had the same problem):
1. In recovery, connect to PC
2. ADB Shell into the tab
3. Clean the MISC partition (or whichever holds the boot commands) using dd:
dd if=/dev/block/zero of=(the partition, /dev/block/mmcblk0p[n] where N is the partition number of MISC) bs=1024
4. Flash any blob
5. Reboot for blob to get flashed.
Click to expand...
Click to collapse
Heres the command i ran
Code:
adb shell dd if=/dev/block/zero of=/dev/block/mmcblk0p3 bs=1024
it says no no such file or directory
sportsstar89 said:
Heres the command i ran
Code:
adb shell dd if=/dev/block/zero of=/dev/block/mmcblk0p3 bs=1024
it says no no such file or directory
Click to expand...
Click to collapse
I tried mounting staging in recovery and it just says error mounting staging
Edit: After formatting it it let me mount it
Related
Since the Evo just got NAND protection removed, I figured I'd share the persistent version of ClockworkMod recovery
Currently ROM Manager is using a recovery hot replace to give you a custom recovery. But I'll eventually be packaging this into ROM Manager's flashing process like the other phones it supports. I'll wait a week or so to switch, while everyone switches over to the new root.
For those that want to make ClockworkMod their default recovery on recovery boot, use this image:
These step assume you have already unlocked your NAND using the "Part 2" thread in the forums.
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-supersonic.img
http://www.droidaftermarket.com/koush//recoveries/flash_image
Place these files on the root of your SD card.
Then run this from a root Android shell.
cd /data/local
cat /sdcard/flash_image > flash_image
chmod 755 flash_image
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Done!
For insurance stuff, will we need to flash stock recovery img to get rid of everything?
<3
Will we be able to update this with ROM Manager?
Re: Permanently replacing your recovery with ClockworkMod Recovery Image
You are a God!
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
<3
Will we be able to update this with ROM Manager?
Click to expand...
Click to collapse
Yes, in a week, when everyone has done their NAND unlock, ROM Manager will start flashing and replacing your recovery for you, so you don't need to do this manually. I do not want to switch right now, because that will leave people who haven't unlocked out in the cold.
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
no, it means when you choose reboot to recovery in any application, ROM manager, quickboot or thru adb it will reboot to the phone's recovery partition but instead of loading the stock recovery, it will load this custom recovery!
this is basically a permanent or "sticky" recovery where as before we had to load the custom recovery every time as a temporary or "non-sticky" recovery. the days of temporary or non sticky recoveries are OVER ... at least until the next update from HTC/Sprint!
Koush, I m still a completely rookie on root part, EVO4G is my first androind phone, and 0 experience on root. Besides, i haven't done anything about rooting evo4g yet (still kinda struggle here, worrying to brick such a$$kicking phone, anyway). So please forgive if my question sounds ridiculous and stupid.
lets say if i decide do root like next months, so i should follow the 1st part root my phone by "PC36IMG.zip", then what's next step? should I use adb shell complete flash recovery, and 2nd part to remove NAND protection, at last run ROM Manager flash recovery permanently? or I can just directly use ROM Manager after root'd phone, like the instruction "[TUTORIAL] IDIOT-PROOF Root Guide! No ADB, no fuss!" by theBiles, to flash recovery permanently?
Koush said:
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
Click to expand...
Click to collapse
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
Hrm, let me double check on mine
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
I get the android with the white triangle as well when using reboot into recovery from rom manager. However the normal recovery is now clockwork great job and thx K!
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
jeremydk said:
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
Click to expand...
Click to collapse
Found the problem Fix is being uploaded!
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Koush said:
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Click to expand...
Click to collapse
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
So what exactly does this do or look like? I'm a bit confused on that one.
phinnaeus said:
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
Click to expand...
Click to collapse
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Koush said:
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Click to expand...
Click to collapse
Oh gotcha. So thats what that progress bar is before it loads up? And this won't happen with the updated ROM Manager coming in a week. I guess thats not really a question, but if I'm wrong feel free to correct me
Koush said:
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Click to expand...
Click to collapse
Worked great but it might help to change that to
./flash_image recovery /sdcard/recovery-clockwork-1.8.2.2-supersonic.img
Took me a second to figure out why it said directory or file doesn't exist
Thank You for all your work
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Red Fox said:
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Click to expand...
Click to collapse
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
simms22 said:
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
Click to expand...
Click to collapse
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Red Fox said:
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Click to expand...
Click to collapse
ahhh, i misunderstood you first. try flashing the recovery again.
simms22 said:
ahhh, i misunderstood you first. try flashing the recovery again.
Click to expand...
Click to collapse
I just tried the recovery OS ROM, no progress, still freezing the same. Could you please explain this recovery, that you suggest?
If the system doesn't make it to the next stage/screen, w/the android. I feel like something is missing to pass go, and collect $100 big one's, LOL!
Sent from my Nexus S
Note: I also attempting this through, ROM Manager. As Bootloader triggers same results. ROM's are all DL'ed from http://mirror.teamdouche.net/?device=crespo (Blank Stare)
Sent from my Nexus S
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Red Fox said:
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Click to expand...
Click to collapse
I do have exactly the same problem.
Which recovery.img did you flash?
stiefa00 said:
I do have exactly the same problem.
Which recovery.img did you flash?
Click to expand...
Click to collapse
Here is the recovery.img that I flashed:
http://www.megaupload.com/?d=C933QJOO
Same recovery.img used when rooting, here is the source:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
Sent from my Nexus S
Another alternative, Terminal Emulator:
- install recovery to sd-card(no folders)
- Terminal:
su
flash_image recovery /sdcard/name-of-recovery.img
-=Edit=-
Phone should pause for a second and then show you a new blank line. Turn it off and back on. Holding down VolumeUp and Power to ensure it flashed correctly. Done.
Sent from my Nexus S
thx, got it!
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
ykphuah said:
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
Click to expand...
Click to collapse
Dude, this is discussed in multiple threads already.
The OTA 2.3.1 and 2.3.2 updates place a new script in the /etc folder that checks the crc on your recovery image at every bootup. If it fails, a backup copy of stock replaces it.
If you want to stay on Clockwork, you need to rename the file /etc/install-recovery.sh to something like /etc/install-recovery.sh.bak
Ah ok thanks! I din know where or what term to search for this.
I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?
Have you tried reformat your sd card?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.
Hey jump hour PM me.
Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?
Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk
Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.
Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.
Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?
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+
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