Database Users

[RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH

CLICK PIC FOR TEAM HOMEPAGE​
ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH (Update 03/05/12)
This version of ClockworkMod Recovery is based on version 5.5.0.4 and has the following "perks:"
Touchscreen
Capacitive buttons can select, move up/down, and go back
Download:
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR_Touch_5504_B15_normalfont_DRH.img (NVFLASH)
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR5504_recovery_B15.zip (Flashable Zip)
How to Install:
There are 2 ways to install. Either run the update through the "CWMR5504_recovery_B15.zip" file or use the "CWMR_Touch_5504_B15_normalfont_DRH.img" image if you will be flashing it with NVFLASH.
NVFLASH Command
To flash use the following commands:
Code:
nvflash --bl bootloader.bin --download 9 CWMR_Touch_5504_B15_normalfont_DRH.img
Changelog:
Added DRH logo
Roboto Font
Changed Mount UDB Storage to the /EMMC
Added the option to format the internal sdcard /emmc
Fixed the magic number mismatch issue
Ability to select update from External SDCard or Internal SDCard
Made internal/external partitions clear
Fixed reboot recovery loop
Allowed the /misc partition to be formatted incase you get stuck in a reboot recovery loop
Swap size bug fixed
Kanged commits to fix the UI overlapping the buttons
Removed /misc (fixes hanging at birds)
Switched from stock Viewsonic kernel to Pershoot's
To Do:
Proper reboot into CWM Recovery
More will be added to the list as more bugs are encountered (if any)
How to Perform a Backup
For those wanting to do backup. Here is the step by step on how to get it to work until a proper fix is done (thanks raj...didnt' understand what you were were saying at first):
REMOVE external sd
Boot to CWMR
Go to "mounts and storage" & select "mount /sdcard" (this is what I didn't understand..how internal could be seen as /emmc & /sdcard)
go back to main menu & select "backup and restore"
select "backup to internal sd"
watch backup complete (including .android_secure on the internal sd)
Thanks to AlAbbo for the instructions!
For the people who wonder what this does:
http://www.youtube.com/watch?v=bGKahQaJadQ
Ported to the G-Tablet by Plastikman
-based on CWM from Koush
-Other credits: gweedo767, cennis91, utkanos
-Original Google+ project page here

Reserved for future use.

I think this was a great idea...nice job...
i have clock work 5.0.2.7...something like that...and wen i install ur zip it works....pull battery...gor right cack into recovery...and its not urs anymore...where can i get clockworkmod 5.5.0.4...so then it willl stay on...i guess i need an update of clock work mod recovery...can you help me out...thanks in advance... ;-)

Guys
I am stuck in a recovery boot loop
How do you fix this?

chief1978 said:
Guys
I am stuck in a recovery boot loop
How do you fix this?
Click to expand...
Click to collapse
Fixed with nvflash

guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?

dony71 said:
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
Click to expand...
Click to collapse
ROM backups need to be backed up and restored with the same version of CWM.
Sent from my ICS powered g-Tablet using XDA Premium.

rmarinella said:
ROM backups need to be backed up and restored with the same version of CWM.
Click to expand...
Click to collapse
Not necessarily.

rajeevvp said:
Not necessarily.
Click to expand...
Click to collapse
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.

rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
Click to expand...
Click to collapse
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.

rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Click to expand...
Click to collapse
fosser2 said:
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
Click to expand...
Click to collapse
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities with CWM-5.x which only come up when you create a backup in CWM-5.x and then try to restore in one of the older CWM versions. (Going the other way is no problem--ie. CWM-5.x will happily read and restore the backup files created by all the older versions of CWM.):
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.

rajeevvp said:
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities when it comes to CWM 5.x.
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
Click to expand...
Click to collapse
What you've stated should be the case. However, I have had issues with compatibility between versions. Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Sent from my HTC Thunderbolt using xda premium.

Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Click to expand...
Click to collapse
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
rmarinella said:
However, I have had issues with compatibility between versions.
Click to expand...
Click to collapse
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.

rajeevvp said:
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
Click to expand...
Click to collapse
How confrontational! Sorry, I don't keep logs.
Sent from my HTC Thunderbolt using xda premium.

rmarinella said:
How confrontational! Sorry, I don't keep logs.
Click to expand...
Click to collapse
Nope. Helpful, actually. Meant specifically to help answer questions like this one.

Originally Posted by chief1978 View Post
Guys
I am stuck in a recovery boot loop
How do you fix this?
Fixed with nvflash
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.

hungsohlo said:
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
Click to expand...
Click to collapse
What kind of boot loop?
For an ordinary kind of boot loop, simply boot into CWM and do a "wipe data/factory reset".
For a recovery boot loop see this thread.

I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.

same as the above poster
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1

genei.09 said:
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
Click to expand...
Click to collapse
hungsohlo said:
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
Click to expand...
Click to collapse
Both of you have the same problem. You have a 1.1 bootloader, but, this version of CWM has a kernel built to run on a 1.2 bootloader (this is indicated in the thread title, actually).
Use one of the versions of CWM with a 1.1 kernel in it. See this thread.

Boot Loop

I unlocked and rooted my tablet awhile ago when i first got it.
Now i had the bright idea to flash cwm on it and I can't fix it.
I can get twrp to start i cleared the cache dalvik and other format
it several times and still no results any suggestions?
On twrp it says no OS installed. Did it delete it when i formatted it?
It also says its an insecure image rom i think
I'm thinking i need to flash a stock rom but i'm not sure how since it's not really letting me

May I knw whch tab u r usng and did u tried to flash a custom rom
your's
ajeteja.
---------- Post added at 03:58 PM ---------- Previous post was at 03:58 PM ----------
Flash a custom rom
your's
ajeteja.

cwm fail
i just tried to flash cwm i'm not sure what you mean by tab. twrp v 2.5.0.0? and i downloaded the cwm from the app in the play store

If your twrp is working then flash a custom rom fir nexus
your's
ajeteja.

kamedende said:
I unlocked and rooted my tablet awhile ago when i first got it.
Now i had the bright idea to flash cwm on it and I can't fix it.
I can get twrp to start i cleared the cache dalvik and other format
it several times and still no results any suggestions?
On twrp it says no OS installed. Did it delete it when i formatted it?
It also says its an insecure image rom i think
I'm thinking i need to flash a stock rom but i'm not sure how since it's not really letting me
Click to expand...
Click to collapse
Wugfresh toolkit.

Looking to full wipe (and format system)

Looking to full wipe (and format system), with my s3 I just left the ROM and gapps on the microsd so they survived.. Any guides around that can tell me how to get those files back on from within recovery so I can flash them? Thx..
Sent from my SCH-I535 using Tapatalk

Recovery should be able to flash from the sd card. My Galaxy Tab & s4 work that way.

wtherrell said:
Recovery should be able to flash from the sd card. My Galaxy Tab & s4 work that way.
Click to expand...
Click to collapse
nexus 7 has no microsd card slot

Boot into recovery. Factory reset. Install ROM and gapps. Done.
Sent from my Nexus 5

rhcreed said:
nexus 7 has no microsd card slot
Click to expand...
Click to collapse
Sorry, I misunderstood your post. Thought you were talking about the S3.
---------- Post added at 09:40 AM ---------- Previous post was at 09:37 AM ----------
rhcreed said:
Looking to full wipe (and format system), with my s3 I just left the ROM and gapps on the microsd so they survived.. Any guides around that can tell me how to get those files back on from within recovery so I can flash them? Thx..
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ADB or WUG's Nexus ToolKit.

ugh...
did the full wipe, used toolkit to push files (rom and gapps), flashed rom and gapps, boots up great!
Sign in, all good!
use TB to restore my apps and setting, BOOTLOOP!!
How can I diagnose and repair this bootloop? Nothing on screen to see of report!
thx!

rhcreed said:
did the full wipe, used toolkit to push files (rom and gapps), flashed rom and gapps, boots up great!
Sign in, all good!
use TB to restore my apps and setting, BOOTLOOP!!
How can I diagnose and repair this bootloop? Nothing on screen to see of report!
thx!
Click to expand...
Click to collapse
Did you restore system data in TB? If so, try just restoring missing apps + data instead.

CM12 Theme engine - HowTo Recover from Boot Loop with some themes

Hi.
If you are a Theme enthusiast while testing new themes sometimes end up with a bootloop which happened to me many times
only way out is data wipe which is a worst nightmare for the flasher(without having backup)
here is a solution where data wipe is not involved
Requirements
Recovery filemanager like AROMAFileManager/TWRP Recovery (which has inbuilt FileManager)
incase if you are using AromaFM you shold know how to use it in recoverry
Patience
Steps
Boot into recovery
Open Recovery File manager
goto Data/system/
Delete theme folder
Done
Reboot
No Boot loops. Change the theme once you boot
Hope this saves many hours for users like me who struggle to recover the data.

Wrongly posted in development forums
Reported to moderators to move the thread to general section

I have a tiny question. If I'm using TWRP, can I flash a ROM from an external device? (Attaching a pendrive inside TWRP)

xavier666 said:
I have a tiny question. If I'm using TWRP, can I flash a ROM from an external device? (Attaching a pendrive inside TWRP)
Click to expand...
Click to collapse
Yes, you can.
Sent from my XT1032 using XDA Free mobile app

Umer520 said:
Yes, you can.
Awesome! Thanks - saved me a LOT of trouble... Dunno why I didn't think of it before...
Click to expand...
Click to collapse

reversegear said:
Hi.
If you are a Theme enthusiast while testing new themes sometimes end up with a bootloop which happened to me many times
only way out is data wipe which is a worst nightmare for the flasher(without having backup)
here is a solution where data wipe is not involved
Requirements
Recovery filemanager like AROMAFileManager/TWRP Recovery (which has inbuilt FileManager)
incase if you are using AromaFM you shold know how to use it in recoverry
Patience
Steps
Boot into recovery
Open Recovery File manager
goto Data/system/
Delete theme folder
Done
Reboot
No Boot loops. Change the theme once you boot
Hope this saves many hours for users like me who struggle to recover the data.
Click to expand...
Click to collapse
Didn't work mate, theme is still applied causing bootloop...

HeD_pE said:
Didn't work mate, theme is still applied causing bootloop...
Click to expand...
Click to collapse
Delete installed theme also /system/app folder.100% works

Life saver! I almost re installed my rom !

Thanks! Works perfectly!

Testing... I hope it'll work ^^
---------- Post added at 11:32 PM ---------- Previous post was at 11:01 PM ----------
Ok it worked! Thx for the solution. It seems bootloop appears only because the boot animation.

ASHURiCAN said:
Testing... I hope it'll work ^^
---------- Post added at 11:32 PM ---------- Previous post was at 11:01 PM ----------
Ok it worked! Thx for the solution. It seems bootloop appears only because the boot animation.
Click to expand...
Click to collapse
yes good one

Thank you so much!!!! Glad i didnt have to rofermat my phone thank yooooouuuuuuuuuuuuu

OldYellowBricks said:
Thank you so much!!!! Glad i didnt have to rofermat my phone thank yooooouuuuuuuuuuuuu
Click to expand...
Click to collapse
Ya I know the pain
Sent from my Moto G using Tapatalk

It didn't work for me D:

I don't see file manager in the recover to get to delete the folder. Any clue, please?\
Update: Now got it, just installed TWRP Recovery from Odin.

Thanks! Better to go into data/system/theme and delete bootanimation.zip instead though.

Can't be made a flashable script that does this without a recovery based file manager?
I'm stuck at Cyanogen Recovery of Pac-rom and can't flash non signed zips like Aroma file manager.
EDIT: I have flashed TWRP through Odin, so I can continue with the tuto, thanks

can I install twrp recovery without root?

billysusanto777 said:
can I install twrp recovery without root?
Click to expand...
Click to collapse
Yes.

Thanks, work like a charm
One question : So , That Particular theme is not compatible with mine rom - right

Roms wont flash?

I dont usually make threads just for questions and just ask them in the question thread but i think this one deserves a thread as i can't find anybody else who has asked this same question.
Basically, i go into recovery and i wipe everything, i then flash the rom, it will go through the process and will say it is successful, however the rom doesnt boot and when i check the system folder through recovery file manager, it is empty. Which means the rom didnt install. How do i fix this?

Okay if nobody wants to help, can someone link me to a guide which will help me to restore back to stock kitkat. D802.

Can't help you with the flashing process and what's going wrong with the d802 here is guide for going back to stock
http://forum.xda-developers.com/showthread.php?t=2432476

use otg cable and install another rom from usb

Envy-X said:
Okay if nobody wants to help, can someone link me to a guide which will help me to restore back to stock kitkat. D802.
Click to expand...
Click to collapse
no one can help you because you didn't write the following:
1. your device model/variant
2. which rom you're trying to flash and/or which rom you're trying to get back to
3. which twrp version you have
4. everything else you find important and informative for someone to help you
cheers

60nine said:
no one can help you because you didn't write the following:
1. your device model/variant
2. which rom you're trying to flash and/or which rom you're trying to get back to
3. which twrp version you have
4. everything else you find important and informative for someone to help you
cheers
Click to expand...
Click to collapse
The only info i have is d802, cloudy 3.3 to cloudy 2.2, and twrp is 2.8.6.1

Envy-X said:
The only info i have is d802, cloudy 3.3 to cloudy 2.2, and twrp is 2.8.6.1
Click to expand...
Click to collapse
that already makes a difference...
i think i've already seen several posts that describe the same procedure that you want...
here is one of that posts
http://forum.xda-developers.com/showpost.php?p=62372703&postcount=11181
just do a full backup in twrp before you do anything...

60nine said:
that already makes a difference...
i think i've already seen several posts that describe the same procedure that you want...
here is one of that posts
http://forum.xda-developers.com/showpost.php?p=62372703&postcount=11181
just do a full backup in twrp before you do anything...
Click to expand...
Click to collapse
I dont think you understand my problem. No matter which rom i flash, nothing happens. I will go through the process of flashing, twrp will say it has installed successfully, but when i check the system folder, nothing is there. Meaning no rom has been installed.

Envy-X said:
I dont think you understand my problem. No matter which rom i flash, nothing happens. I will go through the process of flashing, twrp will say it has installed successfully, but when i check the system folder, nothing is there. Meaning no rom has been installed.
Click to expand...
Click to collapse
logic tells me you messed up the partitions trying to flash kk over lollipop...
so please try what i posted above...
returning to kk requires flashing that patch which sets up kk partitions again...

60nine said:
logic tells me you messed up the partitions trying to flash kk over lollipop...
so please try what i posted above...
returning to kk requires flashing that patch which sets up kk partitions again...
Click to expand...
Click to collapse
I followed what he did, flashed the return to kitkat patch, then wipe everything except internal, then flash rom but the same thing happens.
To people who may be reading this and not understanding the problem, ill try and explain a little more. When i enter recovery, i can see i have 1.5gb of internal memory left. I wipe everything except internal storage, now i have about 4.5gb left, because system and data has been wiped. Now i flash new rom from storage, it says rom installed successfully, however recovery still shows i have 4.5gb internal storage. Nothing has installed. Understand?

@bender_007 any idea on this?
---------- Post added at 04:13 AM ---------- Previous post was at 04:09 AM ----------
oh, one more question
when you checked system partition (which you say is empty) - did you mount it first? (in recovery)
system shows empty by default in twrp if you don't mount it first...
did you try to reeboot to rom after this last flash? (1st boot might take 10-15 minutes with half of it showing blinking led and lg logo)
btw internal storage is a different partition from system...
rom installs in "system" partition...
internal storage is used for all your data, pictures, music, etc... (like an internal sd card that's built in, not removable)
---------- Post added at 04:29 AM ---------- Previous post was at 04:13 AM ----------
addendum
i've just entered twrp, and mine shows "internal storage (6300mb)" (or around 6400mb)
so it's a max size i think, not available size...
sorry for the confusion (i may have even wrote the wrong thing about partitions), i'm tired, it's very late here...

60nine said:
bender_007 any idea on this?
---------- Post added at 04:13 AM ---------- Previous post was at 04:09 AM ----------
oh, one more question
when you checked system partition (which you say is empty) - did you mount it first? (in recovery)
system shows empty by default in twrp if you don't mount it first...
did you try to reeboot to rom after this last flash? (1st boot might take 10-15 minutes with half of it showing blinking led and lg logo)
btw internal storage is a different partition from system...
rom installs in "system" partition...
internal storage is used for all your data, pictures, music, etc... (like an internal sd card that's built in, not removable)
---------- Post added at 04:29 AM ---------- Previous post was at 04:13 AM ----------
addendum
i've just entered twrp, and mine shows "internal storage (6300mb)" (or around 6400mb)
so it's a max size i think, not available size...
sorry for the confusion (i may have even wrote the wrong thing about partitions), i'm tired, it's very late here...
Click to expand...
Click to collapse
When i said internal storage, i just meant memory all together of the phone.
I mounted system many times before flashing, still nothing and i also rebooted after flash and nothing, stuck ok boot anomation. No rom to start apparently.

Maybe twrp itself isn't working, should I try flashing the latest version from here? http://blastagator.ddns.net/twrp/2-8-7-1.php Will it work? Currently on LP.

You can safely flash it (it surely wont harm your system)
Maybe it's the older twrp that makes a problem (doesn't do any problems to me)

about twrp...
i'm using the version prior to latest and don't have problems (d802, cloudy3.3)
you say you're stuck on boot animation - did you let the phone boot for about 10 minutes? (i've said that the 1st boot takes some 10-15 minutes - half of that time the phone is in LG logo/flashing led state that looks like nothing is happening)

60nine said:
about twrp...
i'm using the version prior to latest and don't have problems (d802, cloudy3.3)
you say you're stuck on boot animation - did you let the phone boot for about 10 minutes? (i've said that the 1st boot takes some 10-15 minutes - half of that time the phone is in LG logo/flashing led state that looks like nothing is happening)
Click to expand...
Click to collapse
I left it over night. Ive updated to the latest twrp and nothing, same problem. TWRP says rom has installed even though nothing has.

Then I would flash a kdz, do a Factory deset. Then root, install twrp and then proceed to ROM flashing.
Poslano sa mog LG-D855 koristeći Tapatalk

bender_007 said:
Then I would flash a kdz, do a Factory deset. Then root, install twrp and then proceed to ROM flashing.
Poslano sa mog LG-D855 koriste?i Tapatalk
Click to expand...
Click to collapse
Does flashing kdz delete internal storage? and what is the difference between d80220d and d80210b?

10 is jellybean, 20 is KitKat. Cse flashing does wipe also the interval. Normal flashing doesn't.
Poslano sa mog LG-D855 koristeći Tapatalk

Thanks both of you for trying to help me.