Database Develop

[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
​Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!

Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.

already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now

Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.

Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!

well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?

Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium

Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC

Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.

for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.

Just put your new recovery in the superguide and gave you credit. Keep up the good work!

There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew

drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100

Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew

drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100

Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk

I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.

hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.

Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse

ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks

[Recovery] CWM 5.0.2.0 - Flashable Zip

Attached is a flashable zip of CWM 5.0.2.0. I successfully installed the file from CWM, CWM Touch, and TWRP.
Good luck!
(All the usual warnings apply: flash at your own risk, etc., etc.)
____________________________________________________
Back Story:
Today I was flashing an alternate recovery when I got stuck at the boot logo. I (foolishly) had no other zip flashable recoveries on my phone. Since I had no PC access, I was SOL until I got home. I searched the forum and found no flashable standard CWM recovery. So, I decided to make one.
Do yourself a favor, save a copy on your sd card and hope you never need it!

I think all recoveries in THIS thread can be flashed via recovery. Just choose the zip format and colors of your choice. I've tried before flashing via TWRP. Anyway,thanks for sharing.

You are correct. And romracer's recovery is great, but I wanted CWM.
Sent from my MB860 using xda app-developers app

Question - why is it necessary to format /cache before flashing? I mean, the recovery log is in there (/cache/recovery/log).

I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?

yeahmann said:
I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?
Click to expand...
Click to collapse
Not exactly.. It's when we wanna change recovery to others. Like changing TWRP to any button recoveries. But,we still can access recovery. If we can't access recovery,the only way is by flashing image format via fastboot command.

Before I made this file I analyzed other zip flashable recoveries, and they wiped cache as well. I don't fully understand why myself. Maybe for the very purpose of clearing the recovery log? Maybe because we are taught to always clear the cache before flashing anything and it's just a habit?
ravilov said:
Question - why is it necessary to format /cache before flashing? I mean, the recovery log is in there (/cache/recovery/log).
Click to expand...
Click to collapse
I could access recovery. I just couldn't get past the boot logo. I did say "boot loop" instead of "boot logo" in the original post (I corrected that - my bad). Was this the source of your confusion?
yeahmann said:
I don't get it. A recovery that you can flash from recovery in case you can't get into recovery?
Click to expand...
Click to collapse

upndwn4par said:
Before I made this file I analyzed other zip flashable recoveries, and they wiped cache as well. I don't fully understand why myself. Maybe for the very purpose of clearing the recovery log? Maybe because we are taught to always clear the cache before flashing anything and it's just a habit?
Click to expand...
Click to collapse
Ah, I see.
upndwn4par said:
I could access recovery. I just couldn't get past the boot logo. I did say "boot loop" instead of "boot logo" in the original post (I corrected that - my bad). Was this the source of your confusion?
Click to expand...
Click to collapse
I think he was confused about why would you want to flash recovery if you already have a working recovery? And if you don't have a working recovery, a flashable recovery won't help. IE, he thought this is for emergency purposes, but in case your recovery is malfunctioning.

ravilov said:
Ah, I see.
I think he was confused about why would you want to flash recovery if you already have a working recovery? And if you don't have a working recovery, a flashable recovery won't help. IE, he thought this is for emergency purposes, but in case your recovery is malfunctioning.
Click to expand...
Click to collapse
Having a flashable recovery if your recovery works allows for easy switching. I'm not (yet) a touch recovery fan, but some roms require them.
I was trying to install a touch recovery when the install failed (bad download I think - I downloaded another copy and it installed fine). My phone would not boot past the logo, but I could boot to recovery. I pulled the battery and tried to reboot a few times, re-flashed the recovery, fixed permissions, etc. to no avail. I had no PC access, so I couldn't fastboot a recovery. So, I had no phone for a few hours. During that time I was wishing I had a recovery flashable recovery (if I hadn't recently deleted a copy of romracer's recovery from my phone I would have been good to go). I made one, pulled my sd card and loaded the file, replaced the sd card, booted to recovery, then flashed the recovery I made. The abridged version is the back story in the OP. Anyway, that brings us to the whole point of this thread.
Edit:
I think I set a record for most times using the word "recovery" in a single post.

Although I do appreciate your contributions... I refuse to do any flashing whatsoever unless I have PC access or it's already a dire emergency.
Nandroid -> Titanium Backup -> MyBackup -> Image SD Card (With all three backups) to desktop / laptop -> blast everything on phone to kingdom come -> begin whatever flashing that I probably shouldn't be doing...
Probably overkill, yes; but your remote flashing with no PC access? You sir, are a brave soul.

Normally I am almost as cautious as you. But I was at a really boring offsite meeting. But, I learned my lesson.
xdraconis said:
Although I do appreciate your contributions... I refuse to do any flashing whatsoever unless I have PC access or it's already a dire emergency.
Nandroid -> Titanium Backup -> MyBackup -> Image SD Card (With all three backups) to desktop / laptop -> blast everything on phone to kingdom come -> begin whatever flashing that I probably shouldn't be doing...
Probably overkill, yes; but your remote flashing with no PC access? You sir, are a brave soul.
Click to expand...
Click to collapse

[RECOVERY] TWRP 2.5.0.0 - r#3

Hey, I bring to you, TeamWin Recovery Project or commonly known as TWRP for your N5100, N5110 and N5120. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N51XX and Teamwin for creating this recovery. Flash with Odin or via a already installed custom recovery.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
N5100 / N5110
Release #3: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Release #3: ODIN
Stock Recovery: Soon enough
Changelog:
Code:
[I][U]Release #3[/U][/I]
Updated to TWRP 2.6 (re) [cant call it 2.6 as its not complete by its devs yet]
Cache wipe fixed
N5120 support
Backup compression fixed
Code:
[I][U]Release #2[/U][/I]
Updated to TWRP 2.6
Fixed partition names
Attempt to fix compression
[I][U]Release #1[/U][/I]
Fixed external sdcard
Added modem and efs backup
Removed touch event logging
1st stable release
[COLOR="Red"]<-- Experimentals -->[/COLOR]
[I][U]Experimental #7[/U][/I]
swap X/Y axis
flip Y axis
revert gerrit code review (teamwin-600)
[I][U]Experimental #6[/U][/I]
flipped X axis mapping
flipped Y axis mapping
[I][U]Experimental #5[/U][/I]
Boot fix for devices with install-recovery.sh still present in system
[I][U]Experimental #4[/U][/I]
Touch issues addressed (fail)
[I][U]Experimental #3[/U][/I]
Boot fix (again)
touch issue fix implemented from #2 (failed)
[I][U]Experimental #2[/U][/I]
Touch issues fixed (attempt)
[I][U]Experimental #1[/U][/I]
(info: no longer preview release (public))
display issue fixed

Thanks for your hard work sir trying this when i get home

Downloaded and flashed the newest TWRP. Visually it is perfect but the touch did not work properly. I succeeded in wiping my Note data by mistake due to the touch problems. Some of the targets work but some are mixed up. Sorry I can't get you a logcat. Thanks for getting us where we are though. I feel we are almost there. If someone with better adb skills can try it and get you more info think we will all appreciate it. As an aside I did get CWM EX#3 installed, I had a bad download the first time and that is why I didn't get a recovery img. I much prefer the TWRP if we can get the final bugs out.

Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools

emwno said:
Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools
Click to expand...
Click to collapse
good job may i ask if you have the partition table for the 5110 and the 5100? i posted in general the instructions on how to get it but no one has replied lol working on a little something for everyone, also the note10.1 currently has the same bugs as he was describing above with twrp

emwno said:
Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools
Click to expand...
Click to collapse
Emwno, your work on the CWM got everything started and resulted in a working CWM Recovery. I hope you continue to try to get the TWRP working since it has many fans. I set up my Note again and made a nandroid with the Ex#4 CWM which appears to be working well.
I believe I speak for many of us who thank you for your efforts.

beanstown106 said:
good job may i ask if you have the partition table for the 5110 and the 5100? i posted in general the instructions on how to get it but no one has replied lol working on a little something for everyone, also the note10.1 currently has the same bugs as he was describing above with twrp
Click to expand...
Click to collapse
looks like you got your answer.
rfb813 said:
Emwno, your work on the CWM got everything started and resulted in a working CWM Recovery. I hope you continue to try to get the TWRP working since it has many fans. I set up my Note again and made a nandroid with the Ex#4 CWM which appears to be working well.
I believe I speak for many of us who thank you for your efforts.
Click to expand...
Click to collapse
I dont really understand why those touch input issues occur. But yeah now that the n51xx has a wokring recovery. onto cm10.1

Thank you for sharing your hard work, glad to see progress being made.
Sent from my GT-N5110 using Xparent Skyblue Tapatalk 2

EDIT: Nevermind what i said previously. What i need you people to do is:
1. Take a look at the TWRP layout (Dont touch anything yet)
2. Now try tapping on the 'Install' icon and tell me which menu you end up in
3. Reboot to recovery
4. Finally try tapping the icon of the menu, where you were taken instead of 'Install'
5. Check if you now ended up in the 'Install' menu
Click to expand...
Click to collapse

So, found a way to get twrp to work, credits to dees_troy for pointing me in the right direction. Anyways for this to be done, ill be needing the device in hand (100/400) or a full time tester. So if your willing, take your pick

Uploading the New version of TWRP. Universal for 5110 and 5100 (excluded specifics). Try flashing that and let me know if touch works.
EDIT: new version online! test and report.

emwno said:
Uploading the New version of TWRP. Universal for 5110 and 5100 (excluded specifics). Try flashing that and let me know if touch works.
EDIT: new version online! test and report.
Click to expand...
Click to collapse
Sorry emwno,does not boot into recovery,stays stuck on the Samsung Note 8 screen so i flashed cwm recovery back on.

ktmman said:
Sorry emwno,does not boot into recovery,stays stuck on the Samsung Note 8 screen so i flashed cwm recovery back on.
Click to expand...
Click to collapse
State device. Ill try to make a new version when home

emwno said:
State device. Ill try to make a new version when home
Click to expand...
Click to collapse
5110

Uploading new build, if this one boots to recovery, it should most probably fix the touch issues.
EDIT: up

emwno said:
Uploading new build, if this one boots to recovery, it should most probably fix the touch issues.
EDIT: up
Click to expand...
Click to collapse
Flashed the newest TWRP and it booted into recovery but the touch issues are still there, When I touched install it went to wipe. The others did not respond to touch. I had to reflash CWM.
Thanks

Ill build a new version after today's paper. Swapping the touch mappings

I Think for MY Gtab 2 7". Someone had us Touch Several Specific Points In some sort of Diag area of TWRP to get mappIng data. And then took our output and fixed Accordingly. I'll see f i can dig up the Post.
Sent from my GT-N5110 using xda premium

I think ill just wait till I have the device my self. As I have 0-500 values I need to test to check which one will work for this device. (350/400)

I tried it today in my Note 8 Wifi and had the same touch problems... hope you can fix it soon, i really like your work

[Recovery] & [Root] [T211] CWM Recovery v6.0.4.9.KK Unofficial

READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
Updated to CWM v6.0.4.9.KK on 10-28-14. Now works properly with KitKat bootloader.
Now with SELinux enabled kernel for flashing roms that require it.
Click HERE for the latest version.
Compiled from source.
@ketut.kumajaya has provided us with a kernel for CWM recovery.
Here is CWM recovery for the T211.
Please report any bugs here in this thread.
It takes a few seconds longer for CWM to boot than the stock recovery, so be patient.
Credits go to:
@ketut.kumajaya for working kernels
@Jamison904 for giving us root
@hkjr for getting ketut to help
@k.aibutsu and @Unjustified Dev for there device source work
and of course Koush and the CyanogenMod team
Supplied in 3 formats:
Odin flashable tar.md5 (for first time installation)
Recovery flashable zip (requires a custom recovery to currently be installed)
.img file (for those who use Flashify or other direct methods).
Instructions for ODIN: (use T211.CWMv.....recovery.tar.zip)
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the highlight doesn't move on the recovery menu, the selection actually does change. Go ahead and hit Power to select. If the menu goes blank, just hit Volume Up or Down to get it to reappear.
It appears that the menu navigation issue only happens when you use the button combination to boot into recovery. If you use the Quick Boot app or "adb reboot recovery", it seems to work properly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If it doesn't boot into recovery:
Please reboot into android (hold power until it reboots) and send me the last_kmsg. See my thread about ADB in the General section for instructions.
To get the last_kmsg with adb use: adb shell cat /proc/last_kmsg > last_kmsg.txt
Stock T211 recovery also attached.
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
+++++++++++++++++++++++++++++++
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
+++++++++++++++++++++++++++++++
DOWNLOADS
Click HERE for the latest version.

Reserved

gr8nole said:
Here is an attempt to get CWM recovery working for the T211. Please test and report back.
Click to expand...
Click to collapse
Unfortunately, Kernel Panic.
It tested a guy from Russian forum 4PDA. See here: http://4pda/
Please tell me where is the log?
I can send it later if you need.

Updated to Test #2

Dasdranamin said:
Unfortunately, Kernel Panic.
It tested a guy from Russian forum 4PDA. See here: http://4pda/
Please tell me where is the log?
I can send it later if you need.
Click to expand...
Click to collapse
I added the adb command to get last_kmsg to the OP. You have to pull it immediately after rebooting after the failure (before any secondary reboots) or it will get overwritten.

gr8nole said:
I added the adb command to get last_kmsg to the OP. You have to pull it immediately after rebooting after the failure (before any secondary reboots) or it will get overwritten.
Click to expand...
Click to collapse
:good:
IT WORKS!!!
See http://4pda.ru
Can You make the TWRP too?

Dasdranamin said:
:good:
IT WORSKS!!!
See http://4pda.ru
Can You make the TWRP too?
Click to expand...
Click to collapse
Great, I will make TWRP once we get a few more confirmations that all is working properly. Thanks for testing.:good:

Here You can see the results http://4pda.ru
Sorry, on russian.
http://cs3-3.4pda.to/3636459.jpg
http://cs3-3.4pda.to/3636435.jpg

IT WORKS!!!:laugh:
PLEASE LINK DOWNLOAD BEST ROM FOR T211. :good:

vmollz said:
IT WORKS!!!:laugh:
Click to expand...
Click to collapse
Does this mean that we will be able to flash a zip file for root (of stock ROM, without using a custom ROM?).
If so, could someone pleae link to that zip file?
Thanks

Nice!
I already know ROMs are different for 211 and 210, but what about kernels? Do we need separate, specific kernels for SM-T211 devices, or just flash SM-T210 kernels?

tristan_2468 said:
Does this mean that we will be able to flash a zip file for root (of stock ROM, without using a custom ROM?).
If so, could someone pleae link to that zip file?
Thanks
Click to expand...
Click to collapse
Universal root zip added to OP (zip provided by @ketut.kumajaya).

toxicdog said:
Nice!
I already know ROMs are different for 211 and 210, but what about kernels? Do we need separate, specific kernels for SM-T211 devices, or just flash SM-T210 kernels?
Click to expand...
Click to collapse
@ketut.kumajaya has a custom kernel for T211 in his blackhawk kernel thread.

custom ROM

vmollz said:
custom ROM
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2447053
That's the only one.
Sent from my DROID RAZR MAXX HD

New version (v2) in the OP. This version corrects the touchscreen orientation. That is only important if you flash a zip with a touch interface (such as Aroma File Manager).

im still new with this tab. there is a universal root zip. does this means i dont have to use the other method of rooting by zidkijah?

StormTrooper89 said:
im still new with this tab. there is a universal root zip. does this means i dont have to use the other method of rooting by zidkijah?
Click to expand...
Click to collapse
That is correct...just install CWM, then flash the root zip.
Sent from my DROID RAZR MAXX HD

i have dloaded the file but when i try to search for it in ODIN it didnt detect the dloaded file. i even try rename the file but still odin doesnt show up the file. any tips?

StormTrooper89 said:
i have dloaded the file but when i try to search for it in ODIN it didnt detect the dloaded file. i even try rename the file but still odin doesnt show up the file. any tips?
Click to expand...
Click to collapse
Extract it from the zip. Odin should find the tar.md5 file.
Sent from my DROID RAZR MAXX HD

TWRP on Galaxy s I9000 ?

I would install KITKAT on my Galaxy S i9000 using the TWRP recovery.
In the list of devices on which you can mount the TWRP not indicated the Galaxy S I9000.
It 'an error or you can not?

1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!

Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I will choose the ROM later.
Now I have already choosed the procedure to save EFS files.
Now I'm choosing what type of recovery use.
I repeat: I would use TWRP but my smartphone does not appear in the list of supported devices.
On the contrary, in all the guides TWRP is indicated as an alternative to CWR.

Original TWRP is not available for i9000.
BUT: The CodeROM-Team managed to make it running onto i9000. Therefore, you need to extract TWRP from their ROM, convert it to an Imagefile and upload it with ODIN. This works!

Hello, I would like to also do this as stated in the OP. The image in the kernel.tar, that's what I have to flash the i9000 with Odin? Do I have twrp recovery then in the i9000?

Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?

bronxboy1 said:
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
Click to expand...
Click to collapse
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Fragone said:
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
Click to expand...
Click to collapse
> The phone does not boot in download mode either
Did not see that before. I never had such an issue. Try it again, but do not push the power button more than 10 seconds, else the phone reboots again and again.
Sometimes, Download mode works even thought you cannot see anything on screen. try to connect the device to your PC and launch ODIN, you'll see if it can connect.

Tnx for your reply Fragone. It took me a while, had to wait on a USB jig for me to get the phone in download mode.
Unfortunately I did format to f2fs, how did you get back to ext? As for the other files, I did get my hands on an original rom, but I have to go look for the files you mentioned and try it with those, as the stock rom does not boot either. If you have the links, I'd be much abliged. Right now I go to sleep, just got home from the graveyard shift.

So someone finally returned my i9000 to me after a few years of use and I'm looking to put a current ROM on it so I can use it as a test phone. I keep seeing TWRP as the custom recovery used for the new ROMs. And yet like umberto, I've found there's no official custom TWRP for this phone. I'm pretty familiar with using TWRP on all my other devices.
So back to the original question of this thread - is there a way to get TWRP on the phone? It looks like Fragone's suggestion isn't the right way to go? The only thing I could find in my thread searches was a suggestion to use Mackay's ROM to get 2.8.1.0 and then (theoretically) it's on there so you could move to other ROMs. Any help?
D

@umberto santulli @dnaod
On the i9000, kernel & recovery share the same image, thus the recovery cannot be flashed separately. Therefore there is no i9000 on the TWRP site.
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One

tetakpatak said:
@umberto santulli @dnaod
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
Click to expand...
Click to collapse
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.

dnaod said:
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
Click to expand...
Click to collapse
There should be no problem to change the ROM. Just mind that the kernel & recovery share the image. I was using Omni 4.4.4 by kasper_h and Mackay kernel with TWRP
tetakpatalked from Nexus 7 flo