Small Custom Recoveries?

[marquisg]

Alright, half of you may press the back button when you see what kind of phone I have but I hope that you don't...
I'm a customer of T-Mobile and of course, I got jipped into getting a CLIQ XT. My phone is about 8 months old, and I've been trying to put a ROM on it since I first got it. But with my luck, I would get stuck with bad blocks.. So during recent attempts to flash a recovery, i found out that i can flash recoveries, they just have to be small. like 3 MB or less, too bad that j_rodd and clockwork recoveries are over 3 MB and won't flash. so i need a smaller recovery that's compatible with the CLIQ XT but also small enough for me to flash..

any ideas?

[rockettpc]

Bad blocks are bad man... I had seen that once before on a friends XT and he basically had to go get a new phone. The hdd is probably damaged...

cliq XT (MB501)
CM7 RC2
www.rockettpc.com

[Double0EK]

No he's right. If someone can make a really small recovery.img it is possible to get it to work again. The sector of the device that has the bad blocks is what's causing us not being able to flash a recovery because they are too big in size..if someone can create a small enough recovery it just mite work.

Sent from my CM7'd Cliq using Tapatalk

[blackwing182]

well i found this on xda Here is Guide: How to repair bad block and reset call timer - xda-developers aparetly this guy fixed badblocks on his phone! you ac try this out if you want! to,

[41rw4lk]

Just a random thought, I don't know if it is feasible or if it would even work, but what about logging the output of a failed flash. Then using that log of bad blocks to go back and flag them to be skipped, or not used.
Remember back in the old windows days when you could do a scandisk and it would mark bad sectors so that no info would be written to those blocks? Anyways, I'm certain that I'm out of my league here, but it was just a thought.

[marquisg]

Just a random thought, I don't know if it is feasible or if it would even work, but what about logging the output of a failed flash. Then using that log of bad blocks to go back and flag them to be skipped, or not used.
Remember back in the old windows days when you could do a scandisk and it would mark bad sectors so that no info would be written to those blocks? Anyways, I'm certain that I'm out of my league here, but it was just a thought.

i wish i knew what you were talking about haha, but i got the jest of what your trying to say, that wouldn't make more space though, those bad blocks would still occupy the same space whether skipped or not used. so cliq xt users with bad blocks still need a smaller recovery.

^correct me if i'm wrong.

well i found this on xda Here is Guide: How to repair bad block and reset call timer - xda-developers aparetly this guy fixed badblocks on his phone! you ac try this out if you want! to,

well i read the post and did some research and it seems like that method is for windows mobile enabled htc phones..i couldnt find anything that relates to the cliq xt. but thanks anyways!

sorry it took so long to get back to this btw.

[adlx]

Alright, half of you may press the back button when you see what kind of phone I have but I hope that you don't...
I'm a customer of T-Mobile and of course, I got jipped into getting a CLIQ XT. My phone is about 8 months old, and I've been trying to put a ROM on it since I first got it. But with my luck, I would get stuck with bad blocks.. So during recent attempts to flash a recovery, i found out that i can flash recoveries, they just have to be small. like 3 MB or less, too bad that j_rodd and clockwork recoveries are over 3 MB and won't flash. so i need a smaller recovery that's compatible with the CLIQ XT but also small enough for me to flash..

any ideas?

Have you tried latest CWM made by J_r0dd? http://t.co/ggtmEfk

[marquisg]

Have you tried latest CWM made by J_r0dd? http://t.co/ggtmEfk

i just did, and it was still too big to flash to my phone .. i really appreciate it though.

just for anyone out there that might want this info: this is what i get when i tried to flash j_r0dd's latest CWM
# flash_image recovery /sdcard/3201cwm.xt.img
flash_image recovery /sdcard/3201cwm.xt.img
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00100000
mtd: not writing bad block at 0x00120000
mtd: not writing bad block at 0x00140000
mtd: not writing bad block at 0x00160000
mtd: not writing bad block at 0x00180000
mtd: not writing bad block at 0x001a0000
mtd: not writing bad block at 0x001c0000
error closing recovery: No space left on device

[GROGG]

i just did, and it was still too big to flash to my phone .. i really appreciate it though.

just for anyone out there that might want this info: this is what i get when i tried to flash j_r0dd's latest CWM
# flash_image recovery /sdcard/3201cwm.xt.img
flash_image recovery /sdcard/3201cwm.xt.img
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00100000
mtd: not writing bad block at 0x00120000
mtd: not writing bad block at 0x00140000
mtd: not writing bad block at 0x00160000
mtd: not writing bad block at 0x00180000
mtd: not writing bad block at 0x001a0000
mtd: not writing bad block at 0x001c0000
error closing recovery: No space left on device

I don't have a solution for your bad blocks, but I do know that your recovery needs to be named "recovery.img"...

[marquisg]

I don't have a solution for your bad blocks, but I do know that your recovery needs to be named "recovery.img"...

i tried it as recovery.img the first time it did it, then i changed it back to it's original name just for the hell of it and neither of them worked, sorry for the confusion, but thanks anyways.

[bestialbub]

umm, could be me, but your pasted error indicates your problem is at the beginning, not the end of the memory space you're trying to write to.

doesn't look too promising searching for smaller recoveries to flash to that space. the space indicated for your recovery needs to be re-addressed to begin later in that space before a smaller recovery will work if it can work at all.

[MENTION=1829471]marquis[/MENTION]qg thats my GUESS as i don't know as much about memory addressing as i'd like.. yet.

[marquisg]

umm, could be me, but your pasted error indicates your problem is at the beginning, not the end of the memory space you're trying to write to.

doesn't look too promising searching for smaller recoveries to flash to that space. the space indicated for your recovery needs to be re-addressed to begin later in that space before a smaller recovery will work if it can work at all.

[MENTION=1829471]marquis[/MENTION]qg thats my GUESS as i don't know as much about memory addressing as i'd like.. yet.

i'm not exactly memory addressing "literate" either. so could you explain a little more? or explain how to re-address the blocks?

this is what i get when i flash a small recovery. i dont get an error after all the bad blocks saying that the device is out of space..

# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00100000
mtd: not writing bad block at 0x00120000
mtd: not writing bad block at 0x00140000
mtd: not writing bad block at 0x00160000
mtd: not writing bad block at 0x00180000
mtd: not writing bad block at 0x001a0000
mtd: not writing bad block at 0x001c0000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00100000
mtd: not writing bad block at 0x00120000
mtd: not writing bad block at 0x00140000
mtd: not writing bad block at 0x00160000
mtd: not writing bad block at 0x00180000
mtd: not writing bad block at 0x001a0000
mtd: not writing bad block at 0x001c0000
#

but when i try and boot into recovery mode, i get stuck on the recovery screen with all the bad blocks listed. and i didnt take this into consideration because when earlier when i go into the default cliq xt recovery it lists the bad blocks also for a few seconds, then launches the recovery.

[Double0EK]

I used Root Explorer to check the size of my recovery.img. It shows 2.42mb so maybe something that size would work? I really want to get my XT up to parr with my Cliq..I haven't been trying tho because I don't want to brick it..I haven't tried manually moving a custom recovery with RE...maybe that will work? Has anyone tried?

Sent from my CM7'd Cliq using Tapatalk

[marquisg]

I used Root Explorer to check the size of my recovery.img. It shows 2.42mb so maybe something that size would work? I really want to get my XT up to parr with my Cliq..I haven't been trying tho because I don't want to brick it..I haven't tried manually moving a custom recovery with RE...maybe that will work? Has anyone tried?

Sent from my CM7'd Cliq using Tapatalk

is the recovery thats 2.42mb for your cliq or cliq xt?
and what do you mean move it with root explorer? move it to where?

[Double0EK]

That size (2.42mb) is the size of the factory recovery.img for my XT. And the question was: Has anyone moved a custom recovery.img using RootExplorer after deleting the factory recovery.img? And was it successful? The recovery sizes that I've tried were too big in size and would not flash (bad blocks).

Sent from my CM7'd Cliq using Tapatalk