Database Info

[Q] Clockworkmod Recovery refuses to install on Xoom 3.2.1

So, basically, the details on the Xoom:
Android Version: 3.2.1
Build: HTK75D
Kernel: 2.6.36.3-g111d827 [email protected] #1
Bootloader is unlocked
I am trying to install Tiamat's Clockworkmod image via the ADB method. I do exactly these steps:
adb reboot bootloader
fastboot flash recovery Tiamat-*********-cwm.img
According to the adb console, it says it flashed correctly, and the fastboot also gives the same confirmation.
fastboot reboot
I boot up normally, and run:
adb reboot recovery
It then gives me the dreaded ! mark.
I've spent more than 5 hours trying to get the recovery working, and have tried re downloading the img, changing cables , and the only method that gave me a small glimpse of hope is flashing another img file (cwm 3.0.2.8 flashed) which worked once and then reverted to the ! mark.
Help? If any other info is needed, I will gladly provide.

try this:
1) Flash the recovery via bootloader and the fastboot command
2) After the flash, issue fastboot reboot to reboot the xoom
3) At the M logo during bootup, start hitting the volume down until you see Recovery on the top left corner then hit volume up to select it
That should get you into clockwork mod recovery, after you flash the root package you'll be good to go

Scsa20,
Has this been verified?
Should the offending files, (/system/recovery-from-boot.p OR
/system/etc/install-recovery.sh) be removed per Joe Ferreira's post?
I will try this fix after it has been verified (I've given you a thanks already )

Moto G CWM Recovery Not Working

Hello everyone!!
After doing a lot of extensive research I finally decided to flash Cyanogenmod 11 on my device (btw it's Moto G XT1033). I followed all the instructions of an xda member. Unfortunately my phone fails after flashing the recovery image. It shows on the cmd prompt that the flashing was successful but everytime I go to recovery mode I am no longer able to access the recovery.img
All I get is a blank screen with occasional blanks, freezes and various types of patterns on the screen. I followed each and every instruction to the letter still I do not know why this is happening. cannot even access the default bootloader now!
Here are the steps I used:
1. Unlock the bootloader
2. Installed adb and fastboot and copied the img file to the adb directory
3. Restarted my phone to the boot menu
4. used the command "fastboot flash recovery recovery.img"
5. got a message that the operation was successful.
However after these steps, I am unable to access the cwm bootmenu. Even the default one is no longer accessible.
Please help!!!:crying::crying:

After flashing recovery, do not reboot the phone. Use the phone's volume buttons to enter fastboot from the phone's fastboot menu.

I would install trwp instead.

I agree on Kannz2's suggestion for TWRP.
AFAIK, the recovery you're trying to flash is closed sourced and is no longer being updated.
Here's a link to TWRP:
http://techerrata.com/browse/twrp2/xt1032
Link to ADB and Fastboot that I use:
http://forum.xda-developers.com/showthread.php?t=2588979

flash G6-U10

hey
i was working on boot.img for add TWRP 2.7 Recovery
after i flashed boot.img from here
How to Install TWRP 2.7 Recovery:
TWRP 2.7 works only with the Android 4.4.2 KitKat powered Huawei Ascend P6.
You must have installed Android ADB & Fastboot drivers on your PC. Get the Fastboot folder using the guide.
Once done with the ADB and Fastboot installation, download TWRP 2.7 Recovery.img file.
Rename the downloaded file to boot.img.
Enable USB debugging mode on your Huawei Ascend P6 and connect it to your PC.
Now open the Fastboot folder that you created using our ADB & Fastboot guide.
Press and hold the shift key and then right click on an empty area inside the Fastboot folder, now click on “Open Command Window Here”.
Now in command prompt type “adb reboot bootloader”.
It should reboot your phone into the bootloader mode, now push this command in command window
“fastboot flash boot boot.img”
This will quickly flash the TWRP 2.7 recovery in your device.
Once done, reboot your device.
Boot into recovery by pressing Volume Up or Down Key as soon as you see the Red LED while booting up your phone.
You should see the TWRP recovery interface now.
That’s all with the recovery installation on the Huawei Ascend P6. In case you got any queries or your facing any problems regarding this post, feel free to stop by the comment box below and reach us. Thanks all.
Click to expand...
Click to collapse
phone wont start only fastboot mode
please help me guys to reinstall system again

You nee to Flash stock boot.img or all rom...

TWRP 3.1.0-0 for V3961 (Cloudfone Excite Prime 2, Wiko U Pulse, Qmobile CS1 Plus)

(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Due to how this device works, we can only flash a stock recovery or else it won't boot with custom recovery at all
Click to expand...
Click to collapse
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)

Help me Please
Pls help. My Cloudfone Excite Prime 2 got bootlopp in orange state after trying to fastboot unlock oem and flashed twrp. is there any fix please. I cant turn off my phone its always restarting on orange state on repeat.

Bootloop (
My wiko u pluse got bootloop too :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

Fixed - Forgot to read note LOL
I fastboot flash it lol :v

Hello,
Does it work on U-pulse lite ?
Thanks
Laurent

link for download twrp not working
pls provide link for download twrp u pulse v3961, that one not working anymore

twrp?
pls provide twrp for u pulse v3961, thanks

Update the twrp link please, i need it for my wiko u pulse

3DMapPlayer said:
(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)
Click to expand...
Click to collapse

I have old phone here which is Cloudfone next lite. I want to root this phone, but I need twrp first but I don't see twrp for my phone. Is there somebody can help me 🥹

The Ultimate guide to flash and root Xperia L (aka, taoshan)

This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.​
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!

Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"​
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!​
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.​
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.

Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.