Database Info

[RECOVERY] Permanently replacing your recovery with ClockworkMod Recovery Image

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

[Q] No OTA for me and some noob questions

Hello,
I need some help to get the new ICS update. I have a TF101 (no G), serial B80, with firmware HTK75.WW_epad-8.6.6.23.
Previously I was on 8.6.6.19 and used razorclaw to root it. Then I have done the wipe data, and installed 8.6.6.23.
When I boot with Power and Vol- then Vol+ to enter RCK mode I get the green android guy with exclamation mark.
When I boot with Power and Vol-, then Vol+ I get 2 options: Wipe data and android cold boot.
I used some apps to test if the device is root and they say no.
Sorry for my english, but it's not my main language.
Any idea to fix this?

The 8.6.6.23 is firmware for the 3G model. You will not see OTA since ICS is not released for G model yet.
You can try to manually install 8.5.6.21. You could also try rooting and installing cwm recovery and flash the ICS ROM

Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model

mantorrix said:
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
Click to expand...
Click to collapse
Easiest way is to root, install CWM recovery and flash an ICS ROM. Either the stock rooted ROM or one of the many custom ROMs

I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!

Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]

DreadKing said:
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
Click to expand...
Click to collapse
What you did was put your tablet into APX mode. That's only good if you're doing NVFLash not ADB.
To use ADB just have yourtablet on like normal with USB debugging turn on

Hi,
thanks for your fast reply, you are right. i got my adb device id when beeing in the os, so this works. but, trying to use nvflash/Brk's Asus TF RootKit over apx, i got the initial connection, but when i want to flash it looses the connection or dies or something... no idea what
you got any hints how i can come back to a clean version, which is upgradable?
thx & best regards,
dk
this is the program output btw:
Creating backup of current boot and recovery img
this should take some time... please wait
Loading Bootloader to pad... please wait!
Starting...
Error! Could not load bootloader.
Click to expand...
Click to collapse

alexlarson011 said:
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Click to expand...
Click to collapse
Thanks! This worked for me. Thank you sir! Everything worked fine and I'm now on ICS!

followed exactly alexlarson011's instruction and voila - it works! thanks a lot!
best regards
-dk

Semi-Bricked my TF101

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

Installing CWR - Not working

Hi All,
I've looked all around for the answer to this and am thoroughly lost. I have the Verizon Galaxy S3 with VRALHE. I rooted it, then used EZ-Unlock 1.2 to unlock the phone, then installed Rom manager and flashed CWR. It says it installed 6.0.1.2 but when I try and go into recovery it only goes into Android Recovery. If I flash CWR and right away click the boot into CWR button it seems to go but after that it will only go into Android Recover both via Rom manager and holding Volume Up, Power and Home. Anyone know whats going on?
Thanks for your help!

If it does go into cwm the first time then after that stock there are two files you need to erase that basically reinstall the stock recovery on reboot. I can't recall them, but you could probably search here and find them. Or the easier way is busy flash a custom ROM n that first boot into cwm. By the way ez recovery is better for installing our recoveries, give it a shot.... It may sick without the extra stuff I just told you.
Sent from my SCH-I535 using xda app-developers app

Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.

Boss428man said:
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Click to expand...
Click to collapse
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.

I like to help, but Google stuff. This is what you would have found as the second result
/system/recovery-from-boot.p*
/system/etc/install-recovery.sh
Sent from my SCH-I535 using xda app-developers app

So to confirm to everyone, Deleting the 2 files above does work! So delete the files then re-flash CWR and restart that's it!
I wanted to thank everyone for the help!

Same problem but a little different
shimp208 said:
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
Click to expand...
Click to collapse
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.

Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
What rooting guide did you follow? Did you flash Clockworkmod Recovery yet? If you can provide me with this information I can try help you further. If you haven't flashed Clockworkmod Recovery yet then you will be presented with the normal stock Android recovery system that you described.

Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
Ummm... You do not necessarily go into recovery to root it. Have you installed and used Odin through your PC? You say you are trying to root your phone, so before you get ahead of yourself trying to flash recoveries I recommend reading up a little bit, it is very important you follow directions specifically or you will brick your device....
http://forum.xda-developers.com/showthread.php?t=2046439
There is even a video watch it while you root your phone, and pause along with it.
If you have already done some of this, and done any of it wrong there are steps to recover through Odin.

[Q] Inspire 4G Need help flashing rom with S-ON

Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag

You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.

bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag

Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again

RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.

http://forum.xda-developers.com/showthread.php?p=31211732

ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.

turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.

ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?