Develop Bugs

[Recovery][JB/KK]ClockWorkMod Recovery[6.0.4.7]

{
"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"
}
CWM for TF300T
Latest compiled: 6.0.4.7
Download: Downloads tab on the top of the page (This is a devDB project so if you're viewing on mobile: open in web browser)
Both a recovery.img and a flashable zip for your current recovery will be available.
Source:
Device tree: https://github.com/CyanogenMod/android_device_asus_tf300t
Recovery: https://github.com/CyanogenMod/android_bootable_recovery
Make sure you reboot into android after flashing before going back to recovery!
Flashing via fastboot tutorial courtesy of Xplodwild, slightly edited:
XpLoDWilD said:
Step-by-step guide
Download the CWM .img file
Unlock your bootloader with Asus Unlock app
Connect your tablet to your computer
Shutdown your tablet
Hold Power + Vol Down until you see the 3 icons on your screen
At this point, your computer should recognize Fastboot device (Windows will notify you here, OSX/Linux stays calm)
Flash recovery image with fastboot: fastboot -i 0x0B05 flash recovery recovery_6047.img (if we suppose recovery_6047.img is in your current directory)
Once the operation is done, type fastboot -i 0x0B05 reboot to reboot your tablet
Click to expand...
Click to collapse
Flashing via terminal courtesy of twrp website (edited):
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to recovery.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4 (replace recovery.img with whatever it is called.)
Then reboot to complete installation.
Click to expand...
Click to collapse
XDA:DevDB Information
Clockworkmod Recovery for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
ebildude123
Version Information
Status: Stable
Current Stable Version: 6.0.4.7
Stable Release Date: 2014-02-01
Created 2014-02-01
Last Updated 2014-02-01

Posted 6.0.4.7

Can I use this recovery both JB and KK? I dont want brick my tablet!

@up
Make Nandroid & NVflash, and try by yourself
Second!

which works with the bootloader?
My tablet works but I was wrong recovery and I have serious problems to use it, although with TWRP manager can do the wipe and perform the flash
thanks and regards
sorry for my english

which bootloader version is this recovery for?

solitarywarrior1 said:
which bootloader version is this recovery for?
Click to expand...
Click to collapse
10.6.1.15.3, 10.6.1.27.1, 10.6.1.27.5

Hello,
Where is the download link of ClockWorkMod Recovery 6.0.4.7
Thank

hzaire said:
Hello,
Where is the download link of ClockWorkMod Recovery 6.0.4.7
Thank
Click to expand...
Click to collapse
Go back to the first post in web view. There is a downloads tab at the top of the page. Click that and it shows the file you have requested.
Sent from my TF300T using Tapatalk

great,
thank a lot

@ebildud123
Thanks for your activities.
I downlaoded your file and I renamed it (as sel explanatory)
Asus_TF300T_Recovery_CWM_6.0.4.7.img (recovery native image)
Asus_TF300T_Recovery_CWM_6.0.4.7_update.zip (recovery updatere via recovery)
I have some proposals
delete previous version (6.0.4.6)
rename the current 6.0.4.7 zip file as "Asus_Tf300T_Rrecovery_CWM_6.0.4.7_update.zip"
comrpess the img file in a zip and name it as "Asus_TF300T_Recovery_CWM_6.0.4.7.zip"
To distribute the img file compress can avoid crash/brick if the img file downloaded is not correct (corrupted download).
Do you know if can i use this TWRP recovery on Asus Memopad HD 7 (ME173X) device?

6.0.5.0
I am using your 6.0.4.7 and it is running well. I have CM11 nightly. In the changelog they are up to 6.0.5.0 but my recovery never gets updated with the nightly. Is this normal?
How do I get the 6.0.5.0 recovery that CM are using? Or maybe it doesn't matter.
No other bugs and recovery is backing up just great.

ebildude123 said:
10.6.1.15.3, 10.6.1.27.1, 10.6.1.27.5
Click to expand...
Click to collapse
Works with 10.6.2.11? (TF300TG)

BRANDT SMART TV ROOT

Hi guys i wanna get root for my smart tv brandt 32 ( andriod 6 ) the original manufacter of this device is konka (chinese brand ) i have access to the stock clock recovery i triyed the standard root apps like kingroot and kingoroot but the root fails i was able to extract the boot.img and recovery.img files from system using adb shell commands but i dont know how to continue so anyone have experience with that help me plz
more details on the picture below
thank u for ur time
{
"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"
}

rafaboubou said:
Hi guys i wanna get root for my smart tv brandt 32 ( andriod 6 ) the original manufacter of this device is konka (chinese brand ) i have access to the stock clock recovery i triyed the standard root apps like kingroot and kingoroot but the root fails i was able to extract the boot.img and recovery.img files from system using adb shell commands but i dont know how to continue so anyone have experience with that help me plz
more details on the picture below
thank u for ur time
View attachment 5171625View attachment 5171627View attachment 5171631View attachment 5171635
Click to expand...
Click to collapse
Hey...that would be hard
first you need a modified recovery like twrp. but you i think you would not find twrp for that device. so there is just one option...you must learn how to port twrp for that device to build a costum one.
then you need a root solution like supersu or magisk. but the same thing here. you need to port a existing supersu or magisk to your device.
because the devices firmware is just for read but not for write access in system partion
I forgot...if you can extract the boot partion (boot.img) from device or external downloadet firmware. Then you can try to put it on a smartphone that is rootet with magisk. then you can try to modify the boot.img (on internal storage of phone) with magisk. After that you can try to push it back to the Tv and get root permission that way.
good luck
solong
speedson

speedson said:
Hey...that would be hard
first you need a modified recovery like twrp. but you i think you would not find twrp for that device. so there is just one option...you must learn how to port twrp for that device to build a costum one.
then you need a root solution like supersu or magisk. but the same thing here. you need to port a existing supersu or magisk to your device.
because the devices firmware is just for read but not for write access in system partion
I forgot...if you can extract the boot partion (boot.img) from device or external downloadet firmware. Then you can try to put it on a smartphone that is rootet with magisk. then you can try to modify the boot.img (on internal storage of phone) with magisk. After that you can try to push it back to the Tv and get root permission that way.
good luck
solong
speedson
Click to expand...
Click to collapse
10x man for replying i tried to patch the boot.img with magisk in my phone but my phone not rooted and always get the error message in the patch process (while magisk try to unpack the boot I get an error message "unsupported " ) is that because of root access in my phone?

rafaboubou said:
10x man for replying i tried to patch the boot.img with magisk in my phone but my phone not rooted and always get the error message in the patch process (while magisk try to unpack the boot I get an error message "unsupported " ) is that because of root access in my phone?
Click to expand...
Click to collapse
then try it with a rooted phone/device....alternativ you can use the AIK Android Image Kitchen from dev osmosis (sorry i forget to tell you )
[TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
Android Image Kitchen -- Unpack/Repack Kernel+Recovery Images, and Edit the ramdisk. Windows ports of the necessary Linux utils for Android image (kernel/recovery) mod work: mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg...
forum.xda-developers.com
good luck
solong
speedson

speedson said:
then try it with a rooted phone/device....alternativ you can use the AIK Android Image Kitchen from dev osmosis (sorry i forget to tell you )
[TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
Android Image Kitchen -- Unpack/Repack Kernel+Recovery Images, and Edit the ramdisk. Windows ports of the necessary Linux utils for Android image (kernel/recovery) mod work: mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg...
forum.xda-developers.com
good luck
solong
speedson
Click to expand...
Click to collapse
10x man now i get unpacked image for both boot and recovery how should i patch the boot or recovery to get root access plz

rafaboubou said:
i was able to extract the boot.img and recovery.img files from system using adb shell commands
Click to expand...
Click to collapse
did you find a solution? and what commands did you use to extract boot.img ?

nassim20 said:
did you find a solution? and what commands did you use to extract boot.img ?
Click to expand...
Click to collapse
NOT YET

rafaboubou said:
NOT YET
Click to expand...
Click to collapse
And my second question?

Magisk v22

So I have installed new magisk app and I cannot install magisk via recovery. I read magisk installation guide as far as I understand I should patch my recovery image. The problem is my custom rom doesn't have recovery image in it can I use my stock rom's image?
Edit:
Finally solved. Just renamed magisk.apk to zip and flashed it with good old recovery method.

Did you read the guide properly?
Patch the boot image file using the app and then flash the magisk patched boot image using fastboot.
Good luck

VD171 said:
Did you read the guide properly?
Patch the boot image file using the app and then flash the magisk patched boot image using fastboot.
Good luck
Click to expand...
Click to collapse
Yes I read it properly I don't have ramdisk so I should flash recovery correct me if I am mistaken

KenanT. said:
Yes I read it properly I don't have ramdisk so I should flash recovery correct me if I am mistaken
Click to expand...
Click to collapse
Why do you not have ramdisk?

VD171 said:
Why do you not have ramdisk?
Click to expand...
Click to collapse
Ummm, I don't know is there a way to activate it or install?

What is your device?

VD171 said:
What is your device?
Click to expand...
Click to collapse
İt is redmi note 8

Redmi note 8 has ramdisk.

VD171 said:
Redmi note 8 has ramdisk.
Click to expand...
Click to collapse
{
"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"
}

Magisk app says I don't have Ramdisk.
Installing Magisk 22 from recovery (OrangeFox 11.0.1) via the rename/flash method results in a bootloop to recovery.
Even when I uninstall Magisk (by renaming the zip to uninstall.zip) I can't boot anymore and I have to reflash rom.
I'm on Redmi Note 8T (willow) with official MIUI global 12.0.2.

MichaelMay said:
Magisk app recognises that you don't need a ramdisk patch and doesn't employ it.
What ROM and what build are you using? Also, what build of the recovery.
Click to expand...
Click to collapse
Both are latest stable versions for my device (Redmi 8T/Willow):
ROM: miui_WILLOWEEAGlobal_V12.0.2.0.QCXEUXM
OrangeFox: 11.0_1

mrror said:
Magisk app says I don't have Ramdisk.
Installing Magisk 22 from recovery (OrangeFox 11.0.1) via the rename/flash method results in a bootloop to recovery.
Even when I uninstall Magisk (by renaming the zip to uninstall.zip) I can't boot anymore and I have to reflash rom.
I'm on Redmi Note 8T (willow) with official MIUI global 12.0.2.
Click to expand...
Click to collapse
Try flashing older Magisk v21.4 first via recovery, that worked for me. Then update it to latest version via the Manager app. For some reason, Magisk v22 is failing on a lot of devices running MIUI 12.
Also, with the manual method, you should patch boot.img not recovery.img. Xiaomi is an exception to NO ramdisk installation method.

I had to tinker a bit more (first time it would still boot to recovery, I had to reflash rom) but I ended up having Magisk 22 installed. Thanks for pointing me to the right direction!

KenanT. said:
So I have installed new magisk app and I cannot install magisk via recovery. I read magisk installation guide as far as I understand I should patch my recovery image. The problem is my custom rom doesn't have recovery image in it can I use my stock rom's image?
Edit:
Finally solved. Just renamed magisk.apk to zip and flashed it with good old recovery method.
Click to expand...
Click to collapse
try format data when you get bootloop

General 📌 [Shared] TWRP by skkk

NUWA
{
"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"
}
REC VERSION
Install with TWRP or fastboot***
flash recovery_ab twrp.img(cmd)
or
./flash recovery_ab twrp.img(Power Shell)
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/nuwa/
Spoiler: Change the language.

Can this recovery be used to flash magisk?

Jaberbenet said:
Can this recovery be used to flash magisk?
Click to expand...
Click to collapse
Yep.

NOSS8 said:
NUWA
REC VERSION
Install with TWRP or fastboot*** flash recovery_ab twrp.img
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/nuwa/
Spoiler: Change the language.
Click to expand...
Click to collapse
can't we flash the official miui recovery zip files with it?

cherri said:
can't we flash the official miui recovery zip files with it?
Click to expand...
Click to collapse
Yep...

NOSS8 said:
Yep...
Click to expand...
Click to collapse
before flashing do we need to change any slots like it should be in A or B

cherri said:
before flashing do we need to change any slots like it should be in A or B
Click to expand...
Click to collapse
What do you want to do, update or change version?

NOSS8 said:
What do you want to do, update or change verneed to china beta recovery rom
Click to expand...
Click to collapse

NOSS8 said:
What do you want to do, update or change version?
Click to expand...
Click to collapse
need to flash china beta recovery rom

cherri said:
need to flash china beta recovery rom
Click to expand...
Click to collapse
So, an update?
If after selecting the zip, if it offered you choose, both.

NOSS8 said:
So, an update?
If after selecting the zip, if it offered you choose, both.
Click to expand...
Click to collapse
not an update right now my boot loader is unlocked and no os in it wiped everything but flashing china beta from showing a different error which I didn't seen it before let me flash it again and share you the screenshot

cherri said:
not an update right now my boot loader is unlocked and no os in it wiped everything but flashing china beta from showing a different error which I didn't seen it before let me flash it again and share you the screenshot
Click to expand...
Click to collapse
Twrp/wipe format data type yes/reboot TWRP.
This will create a new partition if needed.
If errors, reds lines restart the operation by restarting on the Twrp, at each try.

NOSS8 said:
So, an update?
If after selecting the zip, if it offered you choose, both.
Click to expand...
Click to collapse
ok i got it bro when i flashed it first time is showed me to reboot recovery again to flash more zip files since the recovery rom file size is huge we need to flash the same zip file 2nd time after rebooting the recovery once again . now it booted successfully

cherri said:
ok i got it bro when i flashed it first time is showed me to reboot recovery again to flash more zip files since the recovery rom file size is huge we need to flash the same zip file 2nd time after rebooting the recovery once again . now it booted successfully
Click to expand...
Click to collapse
What rom did you flash (full name)?

NOSS8 said:
What rom did you flash (full name)?
Click to expand...
Click to collapse
miui 14 china beta rom

cherri said:
miui 14 china beta rom
Click to expand...
Click to collapse
See here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com

Update
Recovery for Xiaomi devices - Browse /nuwa at SourceForge.net
List of relevant recovery in one place
sourceforge.net

Update 7.7
2.71 GB folder on MEGA
32 files and 13 subfolders
mega.nz

So i need to unlock bootloader first to install this twrp?

energykriger said:
So i need to unlock bootloader first to install this twrp?
Click to expand...
Click to collapse
Exactly:
Unlock bootloader
Xiaomi Community
new.c.mi.com
Apply for unlocking Mi devices
en.miui.com

Question Any Idea About How Successfully Root Redmi Note 12 4g ?? (tapas) (23021raaeg)

I've Tried Regular Way For Rooting Redmi Note12 But The Tutorial Was For 5g Version .. Anyway It Was All Safe And Success Even When Patched Boot File + Flashed it Into Bootloader (Fastboot)
But Sadly It Didn't Show Anything In Magisk app After Booting With Patched Boot.img file
.. Still Magisk Root Statue : N/A
So does Anyone Knows What's the Solution For That
ext.info/ I knew that it has dual Boot Type A/B So It Has Dynamic Partition , So Does That Helps With Getting the Solution tho ?
MIUI Version:
global_images_V14.0.7.0.TMTMIXM
And Great Thanks For Ur Reply For Getting More Support For This Model ❤

XBoda said:
I've Tried Regular Way For Rooting Redmi Note12 But The Tutorial Was For 5g Version .. Anyway It Was All Safe And Success Even When Patched Boot File + Flashed it Into Bootloader (Fastboot)
But Sadly It Didn't Show Anything In Magisk app After Booting With Patched Boot.img file
.. Still Magisk Root Statue : N/A
So does Anyone Knows What's the Solution For That
ext.info/ I knew that it has dual Boot Type A/B So It Has Dynamic Partition , So Does That Helps With Getting the Solution tho ?
MIUI Version:
global_images_V14.0.7.0.TMTMIXM
And Great Thanks For Ur Reply For Getting More Support For This Model ❤
Click to expand...
Click to collapse
Hey! I can help you as I had exactly the same issue.
On the Redmi Note 12 you must patch init_boot.img instead of boot.img and then flash the patched init_boot.img using the "fastboot flash init_boot *patched image*" command.
Hope this helped

Max70290 said:
Hey! I can help you as I had exactly the same issue.
On the Redmi Note 12 you must patch init_boot.img instead of boot.img and then flash the patched init_boot.img using the "fastboot flash init_boot *patched image*" command.
Hope this helped
Click to expand...
Click to collapse
Woah it Worked!!!
Man. You are a life Saver ❤❤❤

Max70290 said:
Hey! I can help you as I had exactly the same issue.
On the Redmi Note 12 you must patch init_boot.img instead of boot.img and then flash the patched init_boot.img using the "fastboot flash init_boot *patched image*" command.
Hope this helped
Click to expand...
Click to collapse
Hey! I using "fastboot flash init_boot *patched image*" command but not work.
{
"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"
}

scuslon said:
Hey! I using "fastboot flash init_boot *patched image*" command but not work.View attachment 5925939
Click to expand...
Click to collapse
The partition is full
means u didn't flash files with a right way
Follow this video
Specially for you for how to flash Root file with a successful way

i flash file twrp working rom xiaomi.eu 14.0.7.0
https://sourceforge.net/projects/recovery-topaz/files/TWRP/twrp-3.7.0-RN124G_V2.img.7z/download
Flash instructions:
• USE LATEST PLATFORM TOOLS
(https://dl.google.com/android/repository/platform-tools-latest-windows.zip)• Download and extract recovery.img to platform tools (adb tool) folder
• Open CMD and open platform tools folder
• Reboot phone on fastboot mode, take USB connection on PC and write this two command on cmd:
- fastboot flash recovery_a recovery_filename.img
- fastboot flash recovery_b recovery_filename.img
• Reboot to recovery
TWRP 3.7.0 - Unofficial | Android 13
Build Date: 16/05/'23
By @rama982

scuslon said:
i flash file twrp working rom xiaomi.eu 14.0.7.0
https://sourceforge.net/projects/recovery-topaz/files/TWRP/twrp-3.7.0-RN124G_V2.img.7z/download
Flash instructions:
• USE LATEST PLATFORM TOOLS
(https://dl.google.com/android/repository/platform-tools-latest-windows.zip)• Download and extract recovery.img to platform tools (adb tool) folder
• Open CMD and open platform tools folder
• Reboot phone on fastboot mode, take USB connection on PC and write this two command on cmd:
- fastboot flash recovery_a recovery_filename.img
- fastboot flash recovery_b recovery_filename.img
• Reboot to recovery
TWRP 3.7.0 - Unofficial | Android 13
Build Date: 16/05/'23
By @rama982
Click to expand...
Click to collapse
did it work tho ?