Database Users

Clockwork mod recovery update

Clockwork mod recovery has been updated via rom manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus S using Tapatalk 2

Delete..........

Might want to add that the touch-version (6.0.0.6) still suffers from broken usb-mount. It's fixed in current non-touch (6.0.0.7).

having trouble flashing the crespo4g recovery.img with fastboot...anyone else?? I ran
Code:
$ fastboot devices
my phone's there & connected. when I run
Code:
$ fastboot flash recovery recovery.img
I get error: cannot load 'recovery.img'
any help?

hp420 said:
having trouble flashing the crespo4g recovery.img with fastboot...anyone else?? I ran
Code:
$ fastboot devices
my phone's there & connected. when I run
Code:
$ fastboot flash recovery recovery.img
I get error: cannot load 'recovery.img'
any help?
Click to expand...
Click to collapse
Check if the .img you have downloaded is named recovery.img :]

madd0g said:
Check if the .img you have downloaded is named recovery.img :]
Click to expand...
Click to collapse
+1, also, remove the $ the command i've always used is fastboot flash recovery recovery.img if recovery isn't saved as recovery.img either replace that w/ actual file name or rename img file... or you could cheat & update through rom manager app
Sent from my Nexus S 4G using xda premium

i tried updating mine through rom manager. after that, it shows successfully flashed recovery and its v6007. i reboot into recovery and its still v5020...*sadface*

[tools][Offical] Unlocker By Clirim Furriku [v2.0.0]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unlocker V2.0.0
Features
ADB comands
Reboot
Reboot Recovery
Hot Reboot
Reset Password
Manual ADB comand
ADB universal drive autoinstaller
Install/Uninstall Mobile Drivers
Samsung Drives
LG Drives
Motorols Drives
Sony Drives
MTK Drives
ADB Drives
Rom Downloader
Samsung stock Rom Finder
LG Stock Rom Finder
HTC Stock Rom Finder
Extract Repack
System.img extract
System.img repack
Boot.img Extract
Boot.img repack (beta)
Recovery.img extract(beta)
Recovery.img repack (beta)
[*]Mobile Flash tool (included)
Odin (for Samsung)
SP Flash Tool (Fot MTK)
LG Flash Tool
Sony Flash Tool
XiaoMi Flash Tool
RSDLite Flash Tool (Motorola)
[*]ZIP signer
Supported testkey and personal keys
[/LIST]
[*]Check for update function
Note:Beta features may not working fine
Click to expand...
Click to collapse
Donate Me
Click to expand...
Click to collapse
Screenshots
Screenshots
Compability
Windows 7,8,8.1,10
Download links
V2.0.2
Google Drive
V2.0.0
Google Drive
V1.0
(not available for XDA)
Version Information
Status: Stable
Current Version: 2.0.2
Release Date: 2016-09-06
Created 2015-10-16
Last Updated 2016-09-06

Moved to http://forum.xda-developers.com/android/software/tools-unlocker-clirim-furriku-t3456372

Xiaomi mi A1 cannot boot images, recovery etc from fastboot.

Hello!
I have been trying to boot from boot.img/recovery.img with "fastboot boot" command but it doesn't work, so I can't root my phone with magisk.
I have to use "fastboot flash" to root it, and that way I lose the option to do OTA updates.
The issue:
1. I connect the phone to the computer in fastboot mode.
2. I use "fastboot boot patched_boot.img or twrp.img"
3. Phone goes into charging mode.
Things I've tried:
- Different cables
- Different computers
- Latest platform-tools
- Flashed stock ROM from fastboot
I am currently on Android Pie but I have this issue since around June 2018.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions?

1. Connect turned on phone to PC
2. adb reboot bootloader
3. Wait for fastboot logo
4. fastboot boot boot.img
5. Should boot after about 30 seconds

[SOLVED] Thank you BlackChimaera
BlackChimaera said:
1. Connect turned on phone to PC
2. adb reboot bootloader
3. Wait for fastboot logo
4. fastboot boot boot.img
5. Should boot after about 30 seconds
Click to expand...
Click to collapse
It worked! Thank you BlackChimaera for your advice.

Glad to hear it ) Been in this situation myself. Not sure what the cause of it.

Reboot to EDL mode from FASTBOOT!

Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_to_EDL from : https://www.mediafire.com/file/yr7csyo64e97vbu/Fastboot_to_EDL.zip/file
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3.
Proof:

saved my ass
thanks a lot ahmed.....
i bricked my phone.. went to flash twrp without unlocking bootloader and it bricked..
this tool saved the phone else mom was gonna whoop my ass..
peace:good:

Totally bricked Huawei PRA-LX1

I'm struggling with this phone for couple of months, trying to fix it from time to time. Now I feel like there's no hope for it anymore. Tried flashing a lot of custom recoveries for this phone with no success - after turning on the phone and after the Huawei logo I just see fastboot-similar screen with a title 'Error Mode' and with errors: Func NO: 11 (recovery image) and Error NO: 2 (load failed).
I tried TWRP, Elite TWRP and nothing, always stuck at Error mode. I believe this phone is bootaloader and FRP unlocked (you can see in fastboot). I tried extracting recovery, system images from firmware but recovery_ramdisk spits out 'FAILED (remote: partition length get error)' and also I'm not really sure which image should I extract from the update.app.
I'm attaching 3 images - error mode, fastboot mode, images list from the extractor. If anyone has some ideas, I'm happy to hear them.
Error mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot mode:
Extractor:

szerbi said:
remote: partition length get error
Click to expand...
Click to collapse
Are you sure your phone is running EMUI 8?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.