Database Users

Problem with Flashing T-mobile Mytouch 1.2 (Hboot)

I get this error while trying to Fastboot my phone
error: cannot load 'recovery-RA-sapphire-v1.7.0G-cyan.img'
don't know what i'm doing wrong.. any help?
Also, the radio and .hb0 flashed over fine.. it's just not loading the Recovery .img

You flashed the stock SPL, correct? (1.33.0013)

er0c said:
I get this error while trying to Fastboot my phone
error: cannot load 'recovery-RA-sapphire-v1.7.0G-cyan.img'
don't know what i'm doing wrong.. any help?
Also, the radio and .hb0 flashed over fine.. it's just not loading the Recovery .img
Click to expand...
Click to collapse
First of all, why did I find this in the Development section? Development is for DEVELOPMENT. Moved to General. Next time I'll close it.
Secondly, make sure that you are still using the engineering spl (1.33.2010).
Alternatively try a different recovery such as clockwork or an older version of Amon_Ra.
sgrichard said:
You flashed the stock SPL, correct? (1.33.0013)
Click to expand...
Click to collapse
If he flashed 1.33.0013 then he would would not be able to flash the recovery from bootloader. The OP needs 1.33.2010 to flash anything without root access.

[Resolved] PLEASE help. G2 bricked!

Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

MobileWon said:
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Every phone i have had from the g1, mytouch 3g, vibrant, and now g2 it never fails to amaze me how people who dont know what they are doing manage to brick their phone in under a day. PROTIP READ learn what you are doing before you go in doing it so you dont screw yourself.

If you have the hboot menu and you seem to have s-off so you can restore official htc rom or a custom rom
Sent from my HTC Vision using XDA App

Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash

Hot_Hands said:
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Click to expand...
Click to collapse
Yup, exacly what he said.. also, I don't think editing the statusbar from a stock is possible because its odexed, correct me if I am wrong though.. unless you really know what you're doing.. so now after flashing recovery, try again with a nandroid if you have yours if not with fastludeh's stock odex or deodex rom if you want to keep it stock.
Sent from my HTC Vision

You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend

Hot_Hands said:
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Click to expand...
Click to collapse
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
Nope. Just put it on your SD and flash from recovery.

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
No, you do not need to rename it.
Sent from my HTC Vision using XDA App

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
EDIT: Oh wait, it says SHIP S-OFF, shouldn't it say ENG S-OFF if you had the ENG boot loader? Did you even flash the new HBOOT?

KoolKidsKlub said:
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
Click to expand...
Click to collapse
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.

ianmcquinn said:
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
Click to expand...
Click to collapse
Yeah I just noticed that and edited my post about 1-2 minutes ago.

Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.

The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.

MobileWon said:
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
Click to expand...
Click to collapse
Yeah ummm you might be screwed, we assumed that you flashed the engineering HBOOT, and only with the engineering HBOOT can you use fastboot to save your self and it seems like you don't have it. I'm not sure what to do now, I think some one said that you might have to flash the stock ROM but I'm not sure how. Wait around for some other guys to help you out, they know more than me with this stuff.

Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Ok, I have the stock rom already. How do I flash a RUU? Or can you give me a link?

Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
EDIT: And if you do have to flash an RUU, could you please explain how? I would like to know how just in case I screw something up(which I probably won't because I have been on my computer searching the forum, asking for help and to double check that what I have learned is correct and what to do if something bad happens for the past week or two) and I can also use the information to help other users.

KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
That was a warning because if you had S-Off and root it would put S-On and remove root. It was an issue because for a while it was impossible to root the DZ's 1.72 RUU but this has since been worked around and doesn't apply to the G2.

Ok, guys Im not an idiot. I previously had a HD2 and had no problems...just rushing to get my phone right before I go out of town for the weekend. So, whatever I have to do to get it right.

KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
You might be right.
Ok,... So you have gone into your Hboot screen, select fastboot, then it says Fastboot on the screen yeah? Do:
fastboot devices
in cmd, do you get anything?

Downgrading from .97 to .76 bootloader, what's the trick?

I am currently s-off via UnrEVOked. I want to go from .97 to .76 to get fastboot.
Is it as simple as flashing the file from recovery?
1) Do I need to clear cache/dalvik?
2) Do I need to re-flash the ROM/radio/PRI/NV?
3) Any other implications or dangers of doing this?
I'd appreciate any info.

If it fails to boot up after you downgrade, you'll probably have to reflash the ROM.

Noxious Ninja said:
If it fails to boot up after you downgrade, you'll probably have to reflash the ROM.
Click to expand...
Click to collapse
1) What is the likelihood of my device not booting, based on what you have seen from people's actual experience?
2) If my device boots okay, then nothing else to worry about?
3) If my device does fail to boot, will I be able to boot into recovery? Will a nandroid restore suffice?
Thank you.

Not reflash the ROM, just the kernel should suffice.

InfectedMushroom said:
Not reflash the ROM, just the kernel should suffice.
Click to expand...
Click to collapse
For my knowledge, why is flashing the kernel necessary at all? If HBoot is a different part of the phone (sort of like a bootstrap), shouldn't the OS/ROM/kernel/radio/etc. not be touched at all?
Thank you.

Snovvman-
Search for hboot in "EVO android development" section. I think Caulkin started that thread. It has the .76 hboot version with installation instructions. I would also recommend updating your recovery if you haven't already. I have AmonRA v2.2.1 with hboot .76 on my EVO. Amon's recovery has some cool features. Good luck dude.
Sent from my PC36100 using XDA App

ElectronBlue said:
Snovvman-
Search for hboot in "EVO android development" section. I think Caulkin started that thread. It has the .76 hboot version with installation instructions. I would also recommend updating your recovery if you haven't already. I have AmonRA v2.2.1 with hboot .76 on my EVO. Amon's recovery has some cool features. Good luck dude.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I have the files from that thread (actually on my subscribed list), I actually have all the HBoot versions at the ready. I am currently using CW 2.6.0.1 for now and I like it okay. There are even a couple of threads to help people with 2.x Hboot to go back to .76. Reading through them, they just don't exactly apply to what I'm wanting to do. I'm simply gathering some data before diving in.
Edit: I started the thread because I have read in different places where either 1) no additional flash is needed, 2) must re-flash radio/PRI/NV/etc., 3) must reflash ROM, or 4) may need to reflash kernel.
I not only want to know what one actually must do, but why...

My experience with downgrading my hboot went like this. After I applied the 76 hboot and tried to boot up, it would loop me back to the boot loader. After I went to recovery through the boot loader I flashed a new rom and got out of the boot loader loop. If you downgrade, you WILL get in that loop unless the method has changed and you will have to reflash a kernel or the whole rom.

jxr94 said:
My experience with downgrading my hboot went like this. After I applied the 76 hboot and tried to boot up, it would loop me back to the boot loader. After I went to recovery through the boot loader I flashed a new rom and got out of the boot loader loop. If you downgrade, you WILL get in that loop unless the method has changed and you will have to reflash a kernel or the whole rom.
Click to expand...
Click to collapse
Thanks. From what version did you downgrade? I presume the radio/PRI/etc. stayed intact?

There is a thread about this. Search!!
From what I can remember, the older hboot doesn't work properly with the newer nand chips, specifically those with 40000 byte erase blocks possibly present in rev 0004. Flashing an old hboot onto one of these results in a bricked evo.
http://forum.xda-developers.com/showthread.php?t=883548
ymmv

gpz1100 said:
There is a thread about this. Search!!
From what I can remember, the older hboot doesn't work properly with the newer nand chips, specifically those with 40000 byte erase blocks possibly present in rev 0004. Flashing an old hboot onto one of these results in a bricked evo.
http://forum.xda-developers.com/showthread.php?t=883548
ymmv
Click to expand...
Click to collapse
Thanks. As I indicated in a previous post in this thread, I am aware of the post you cited, as well as another. They are actually both in my subscribed list. I have the 20K partition. I started this thread because those threads describe steps to go from 2.x Hboot to .76, not .97 to .76. I have yet to see a specific case where somone went from .97 to .76. I wanted to know if going from .97 would be less problematic than from 2.x.

I went from .97 to .76 with no problems other than the expected bootloop. I just reflashed my kernel and was good to go. No need to reflash the rom.

snovvman said:
Thanks. As I indicated in a previous post in this thread, I am aware of the post you cited, as well as another. They are actually both in my subscribed list. I have the 20K partition. I started this thread because those threads describe steps to go from 2.x Hboot to .76, not .97 to .76. I have yet to see a specific case where somone went from .97 to .76. I wanted to know if going from .97 would be less problematic than from 2.x.
Click to expand...
Click to collapse
That used to be the only method of unlocking the NAND, you are safe. If you haven't done it yet then the best way to do it is through the bootloader though.

InfectedMushroom said:
I went from .97 to .76 with no problems other than the expected bootloop. I just reflashed my kernel and was good to go. No need to reflash the rom.
Click to expand...
Click to collapse
Thank you.
xHausx said:
That used to be the only method of unlocking the NAND, you are safe. If you haven't done it yet then the best way to do it is through the bootloader though.
Click to expand...
Click to collapse
xHausx: Do you mean to do that by renaming the .76 Hboot to PCIMG36 and boot into the bootloader to let it flash?
Again, just for my education, why is this better than flashing through recovery?
Cheers.

snovvman said:
xHausx: Do you mean to do that by renaming the .76 Hboot to PCIMG36 and boot into the bootloader to let it flash?
Again, just for my education, why is this better than flashing through recovery?
Cheers.
Click to expand...
Click to collapse
You will need it packaged as a PC36IMG to work, I went ahead and attached one with it if you still need it.
As a rule of thumb flashing from the bootloader is always safer than from the recovery. Odds are if the bootloader can't flash properly your phone would already be a brick, so you know it will be good. Although with something like the bootloader the recovery may actually call on the bootloader to do the actual flashing but you never know.

xHausx said:
You will need it packaged as a PC36IMG to work, I went ahead and attached one with it if you still need it.
As a rule of thumb flashing from the bootloader is always safer than from the recovery. Odds are if the bootloader can't flash properly your phone would already be a brick, so you know it will be good. Although with something like the bootloader the recovery may actually call on the bootloader to do the actual flashing but you never know.
Click to expand...
Click to collapse
Thank you for taking the time to make and upload the zip sir.

going to run over my friend's mytouch

So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith

smithisize said:
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
Click to expand...
Click to collapse
doubt its bricked...(its not bricked if you can get to the bootloader
what h-boot version do you have?
use the PD15IMG.zip to restore your phone

VibrantOwnr said:
what h-boot version do you have?
Click to expand...
Click to collapse
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..

smithisize said:
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
Click to expand...
Click to collapse
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)

VibrantOwnr said:
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
Click to expand...
Click to collapse
ROM Manager didn't work (again, couldn't obtain permissions).
So, I'm going to flash the ROM, hope for the best, then if $*&^ hits the fan, I'll result to flashing a diff bootloader.
Thanks for your advice, didn't think about flashing a diff booloader... used to my Cappy xD
Regards
Smith

have you tried using TrueBlue's recovery .zip it was the only way I could get either of my phones to take 3.0.0.6
HERE is the thread for it

Well, I flashed regardless of the 3006 req, and it went fine... Whatever lol.
thanks for the help and suggestions
Regards
Smith

[Q] Rooted MT4G with grankin's gfree. Confused about needing bootloader.

Rooted with the "check this out even if" thread. Worked fine, found out that gfree doesn't root, but that visionary is what actually roots you when using it for teh second time after gfree turns radio security off. (had su denied in terminal a few times after gfree until I ran visionary and rebooted twice- it finally took)
So a big thanks to everyone.
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended.
Now, which is it? I don't want one of these
http://forum.xda-developers.com/showthread.php?t=1028615
where I read that there's people who flash one rom a single time like royalginger 1.6, then want to goto CM7.02 or vice versa, and that's all it takes to get in some boot loop. Now it might be that they're not wiping everything they should wipe, or wipe once instead of twice (which shouldnt be necessary), but it still makes you wonder.
Should I flash the 085 bootloader? Running fine on RG1.6, but may try CM 7.02 or RG2.0 when it's out of testing...
Thanks

acsi007 said:
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended
Click to expand...
Click to collapse
The engineering bootloader is not required, but some of us do recommend it. IF you should have something go south you can flash recovery images, sections of the ROM, erase sections of the ROM, clear stuff. It helps if you should run into a problem. Their have been a few threads that people would of bricked their devices if they didn't have it.
The final choice is up to you. But if it were my phone i'd do it. If you are worried about the code you have to punch in to unlock it, just double and triple check it.

hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
anything else i cant do without H085?

acsi007 said:
hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
Click to expand...
Click to collapse
You cannot flash specific sections of the ROM if something should go south. You cannot flash recovery images via the HBoot, and you cannot flash splash images.
acsi007 said:
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
Click to expand...
Click to collapse
fastboot = hBoot = Engineering Screen.
Basically it what allows you to flash items via the Engineering screen. You cannot mount sections of the ROMs, nor can you clear stuff out if you should so choose.
acsi007 said:
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
Click to expand...
Click to collapse
You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method.
basically the .85 HBoot a BIG tool to help you not brick your device.

thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....

acsi007 said:
thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
Click to expand...
Click to collapse
when we are talking about booting into Recovery, or the Engineering screen. Fastboot, hBoot, and Engineering screen are all pretty much one in the same. Just like some people call softdrinks, "pop", "soda", or "coke". It's terminology. the reason for the "Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it." Is even though are in a "bootloader" screen the phone must pick up and recognize that you want to use fastboot. so sometimes, not typical though, you must select the "fastboot option".
acsi007 said:
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
Click to expand...
Click to collapse
Correct there have been several threads popping up that are pointing to people have bricked their devices by flashing the PD15IMG in the Engineering screen but they are using the wrong recovery image. It always said something to the degree of "fail -PU". One guy was able to fix his by flashing the 2.5 recovery image from the Engineering screen then flashing the PD15IMG.
acsi007 said:
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....
Click to expand...
Click to collapse
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.

neidlinger said:
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.
Click to expand...
Click to collapse
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?

acsi007 said:
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?
Click to expand...
Click to collapse
i think we are on two different wave lengths.
one of the first Clockwork recoverys that came out where for 2.2 style ROMs, where store information in an EXT3 format. When Google released 2.3 we needed a new recovery image to flash the EXT4 design that the 2.3 ROMs bring. 3.0.0.5 will only handle 2.2 ROMs 3.0.0.6 and 3.0.2.4 will do both.
The problem lies in the fact that EXT3 and EXT4 ROMs store and handle information differently.
using the recovery image while trying to load the PD15IMG will cause the load to fail.
Now if you have the engineering screen loaded you can manually load the 2.5.1.4 recovery image via the Engineering screen then flash the PD15IMG and all should be good.
But this is only if you need to revert back to 100% stock.

we're not on 2 wavelengths, i'm just talking like an inebriated baby on no sleep!
thanks for the patience you display toward everyone, all the while having a guide which spells all this stuff out...
so the file system rules, and since 2.3's obvious big upgrade was the F/S, it borked previous recoveries.
so i'm on CWM3024, the latest, which i installed via rommanager, and it flashed it, and i nandroid backed up.
so im set for ext3 and ext4 incl pd15img, (which is ext3). right?
also, flashing pd15img- that reverts the bootloader from 085 to 086 again?

Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.

kmdub said:
Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.
Click to expand...
Click to collapse
then i'm out....