Related
Hi, I am going to sell my Milestone soon and need to prepare it for that.
Basically, I want to keep the current rom (CM) and the updates / scripts I flashed through Androidiani OR.
But, I obviously want to remove my data, google account, and purchased apps.
How do I achieve that? Thanks!
Just flash the non service 2.2.1 sbf of your region from and-developers.
Edit : i didnt read properly. Just wipe data in AOR.
Sent from my Milestone using Tapatalk
sileshn said:
Just flash the non service 2.2.1 sbf of your region from and-developers.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Thanks for the instant reply, but how will that help?
I want to leave the custom rom (CyanogenMod) on the phone (including all the updates flashed via OR).
Won't your suggestion just restore it to factory default?
xploited said:
Thanks for the instant reply, but how will that help?
I want to leave the custom rom (CyanogenMod) on the phone (including all the updates flashed via OR).
Won't your suggestion just restore it to factory default?
Click to expand...
Click to collapse
Yes. But your CM7 will stay. Take a nandroid and try wiping all in AOR.
To make things more clear, CM7 makes changes to your system partition. All your apps and google details are stored in the data partition. So wiping your data will not effect the system partition.
In case you were using apps2ext, make sure you format your ext partition as well.
Sent from my Milestone using Tapatalk
Thanks, will try that.
How I can back to stock rom?
my model is xt862 i guess (from verizon)
what did you use to flash in the first place? Koush's bootstrap, hashcodes bootstrap or safestrap? Also, youre in portugal, correct? are you sure its a xt862 or is it the xt860?
Fastboot http://goo.gl/g033Z
Isn't there a factory restore option in the boot menu to accomplish something similar? I have to do this soon to accept the upcoming OTA update...
Sent from my DROID3 using XDA App
Phibernaut said:
Isn't there a factory restore option in the boot menu to accomplish something similar? I have to do this soon to accept the upcoming OTA update...
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Factory reset doesn't restore your stock rom, it just removes all user data like apps sms phone book etc. Anything done as a root user is on /system is untouched by factory reset. Once you start messing around with root factory reset becomes a misnomer. To restore your stock rom you need to use the fastboot files. Its a sticky in the dev section, assuming you are using xt862. For xt860 you can't restore to bell stock rom, but you can use the brazil stock to get close.
xt860, android 2.3.5, Monster rom
I bought from verizon soo ...its unlocked...and already come with another recovery
like if I turn on the phone it will pause on CWR =/, I need to restart on CWR to boot again fine...
Îf I put it charging, it will boot on CWR
i think your best bet is to sbf to 5.6.890 using RSD. boot the phone with m+pwr choose AP fastboot and use RSD to sbf the phone. if you are using the regular koush cwm and flash the 5.6.890 + root from http://hash-of-codes.blogspot.com it may work, but if youre on 5.5.959 then you may bootloop or worse (i really dont know on that one)
how I can see what cwr or bootstrap I have?
Sent from my DROID3 using XDA App
A friend of mine has Droid 3 on Verizon. I'm want to know what I need to do to flash a recovery on it so I can backup and flash roms on it. I'm not sure if I need a custom bootloader for it aswell. I found this thread with recovery as a sticky but it doesn't have much explanations in it. I also see you guys don't have a sticky with a guide anywhere besides just the one click root.
Can anyone point me in a direction?
Thank you.
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
slayer621 said:
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
So how do I install this safe strap and where do I get it. I assume this will also let me flash a custom recovery like CWM?
Everything you need to know on installing safestrap can be found here
There are 2 versions. One is the standard version in the link, the other is a "tweaked" version found on the forums here. While the tweaked version has a few extra features, from what I've read, it can be a bit unstable. Use the version provided in the link.
Yeah what he said ^^^ then once u have the safestrap you just download the rom u want and flash it and your good to go
Sent from my XT883 using Tapatalk
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
obsanity said:
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
Click to expand...
Click to collapse
The 1st system gets renamed to systemorig and is otherwise left untouched. /reinstall gets renamed to /system and becomes your safe mode system. Im not 100% on hijack but as I understand it, it quite literally hijacks the boot sequence at a certain point by killing all the processes and inserting its own in order to give us a custom recovery
Sent from my XT860 using xda premium
OK. So why not just backup the original system and overwrite it? If the partition gets renamed why is there a need to keep it? Wouldn't deleting it give more room for roms? Is there even enough room for 2 partitions on the emmc?
The whole idea was that you keep your original system intact so you can still receive OTA updates. I've never had an issue with not having enough room for roms. They are only about 150 MB.
Many of us actually use this to dual boot. The common way is to have a stable rom on your /systemorig and test new roms on safe system.
There is a plain old bootstrap that installs regular old cwr and just overwrites /system. Everything should be compatible with it. I think I have a copy of it in my dropbox
The main reason for using safestrap(in my view) is that when you're messing around in safemode its next to impossible to brick your phone so bad you can't access recovery, since when it first boots it still boots from /system, and then redirects to the safe system. You should never have to fastboot flash your phone
Sent from my XT860 using xda premium
So can you dual boot? And how do you boot into your orig 1st system? Don't you have to toggle the safe mode each time? Also, how much total room is there on emmc on D3?
try here :
http://forum.xda-developers.com/showthread.php?t=1436380
The internal SD memory is roughly 11GB. The phone stores which system was last booted and then you can backup and restore between them though the SafeStrap pre-boot recovery. Once you try it, it's really simple and effective. I was hesitant to leave old faithful bootstrap, but now that I'm on safestrap, I wonder why I ever hesitated.
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Also, do I download ver 1.09 which says Droid 4? I have a Droid 3.
obsanity said:
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Click to expand...
Click to collapse
It creates a backup of /system and /data when you switch between safe and non safe. And I think also /cache. However as I mentioned before it renames /system to systemorig.
Sent from my XT860 using xda premium
It runs off the /preinstall partition IIRC. You should/can DL the original from Hash's blog or get Rick's tweaked version from the Dev section.
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
obsanity said:
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
Click to expand...
Click to collapse
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Endoroid said:
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I just did it on his phone. All worked OK. Thanks for all your help. I'm used to the nexus devices which are much easier and straightforward. I installed nightly CM9 from hashcode. I'm not sure what works yet. Is there a better version of CM9 besides that one? He really wants ICS and CM.
All of the ICS roms are currently limited in the same way: no HW codecs, bluetooth on but not connected = loss of audio, etc. There's a thread here in the general section that compares all of the ICS roms. I would advise looking through it and deciding which one suits you best.
EDIT: to answer your question, the may 7 build of Hashcode's CM9 is a good build. They just brought back the theme engine so that opens up possibilities.
Sent from my DROID3 using xda premium
Sent from my LG-F180K using XDA Free mobile app
My device galaxy s3 19305 lte is brick. It won't boot up even after I flash the original firmware from sammobile. So I was told that the bootloader is damage. I probably damage it when I was trying to root. The phone only boot and get stuck in the Samsung logo. Please please can anyone point me to a thread where I can repairs the bootloader? Thanks
Da Legend said:
Sent from my LG-F180K using XDA Free mobile app
My device galaxy s3 19305 lte is brick. It won't boot up even after I flash the original firmware from sammobile. So I was told that the bootloader is damage. I probably damage it when I was trying to root. The phone only boot and get stuck in the Samsung logo. Please please can anyone point me to a thread where I can repairs the bootloader? Thanks
Click to expand...
Click to collapse
did you try a dalvik wipe? sometimes it helps
I think you need to flash twpr (you can find it on this forum) then a full wipe, after that, try another rom (i'm using for now a 4.4.4 rom, but tried several 5.02 rom's. Was working fine only a irri noise when i was caling with somebody, think my mic is broken)I would say, try also to use odin multiflasher to reset all settings of your phone, start new from the begin, It can be a nasty problem but good to fix.
killerbee_67 said:
did you try a dalvik wipe? sometimes it helps
I think you need to flash twpr (you can find it on this forum) then a full wipe, after that, try another rom (i'm using for now a 4.4.4 rom, but tried several 5.02 rom's. Was working fine only a irri noise when i was caling with somebody, think my mic is broken)I would say, try also to use odin multiflasher to reset all settings of your phone, start new from the begin, It can be a nasty problem but good to fix.
Click to expand...
Click to collapse
I did the dalvik wipe. And I have twpr installed. The device is running 4.3 and I can't flash other rims coz i'm not rooted. Or can I?
Sent from my LG-F180K using XDA Free mobile app
Flash kitkat official stock rom with Odin .
Did many times. No luck
Sent from my LG-F180K using XDA Free mobile app
Da Legend said:
I did the dalvik wipe. And I have twpr installed. The device is running 4.3 and I can't flash other rims coz i'm not rooted. Or can I?
Sent from my LG-F180K using XDA Free mobile app
Click to expand...
Click to collapse
If you have TWRP, you can flash anything. Root permissions apply inside the rom, not inside a custom recovery.
If you're on the recovery, you can flash anything (that your recovery allows).
inside TWRP, find a way to wipe everything except EFS. Format /system , /cache , /data and /data/media if it shows.
daedric said:
If you have TWRP, you can flash anything. Root permissions apply inside the rom, not inside a custom recovery.
If you're on the recovery, you can flash anything (that your recovery allows).
inside TWRP, find a way to wipe everything except EFS. Format /system , /cache , /data and /data/media if it shows.
Click to expand...
Click to collapse
Are you saying that I can even upgrade my device to 4.4 kitkat? Please i just want to be sure. And does it mean that i9305 comes with an unlock boot loader?. Please please reply.
Sent from my LG-F180K using XDA Free mobile app
Da Legend said:
Are you saying that I can even upgrade my device to 4.4 kitkat? Please i just want to be sure. And does it mean that i9305 comes with an unlock boot loader?. Please please reply.
Sent from my LG-F180K using XDA Free mobile app
Click to expand...
Click to collapse
yes it should be possible to instal kitkat or lollipop, did that several times, but you have to be sure you're going to use the right rom's (9305 or LTE) if you don't you divice can be bricked.
Are you sure your samsung has root? please download en install root checker from the playstore, this will tell you if your samsung has root!!
i ran this rom a few days (again ihave a personal problem with my mic, on lollipop there is a noise, on kitkat or older roms not) can't find what couses the problem, sadly....
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3042318 link isn't availleble
follow the instructions correctly and it should work
killerbee_67 said:
yes it should be possible to instal kitkat or lollipop, did that several times, but you have to be sure you're going to use the right rom's (9305 or LTE) if you don't you divice can be bricked.
Are you sure your samsung has root? please download en install root checker from the playstore, this will tell you if your samsung has root!!
i ran this rom a few days (again ihave a personal problem with my mic, on lollipop there is a noise, on kitkat or older roms not) can't find what couses the problem, sadly....
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3042318
follow the instructions correctly and it should work
Click to expand...
Click to collapse
My device doesn't have root!! But i have twrp installed. I was told that I can flash from the custom recovery without root! Please reply
Sent from my LG-F180K using XDA Free mobile app
Da Legend said:
My device doesn't have root!! But i have twrp installed. I was told that I can flash from the custom recovery without root! Please reply
Sent from my LG-F180K using XDA Free mobile app
Click to expand...
Click to collapse
With custom rom's better always look for root on your device.
you need this:
http://download.chainfire.eu/232/CF-Root/CF-Auto-Root/CF-Auto-Root-m3-m3zh-gti9305.zip
http://techerrata.com/file/twrp2/i9305/openrecovery-twrp-2.7.0.0-i9305.tarhttp://techerrata.com/file/twrp2/i9305/openrecovery-twrp-2.7.0.0-i9305.tar
Rom: https://www.androidfilehost.com/?fid=95916177934540052 this is a lollipop good working rom
on this url: you find info for using odin to flash the proper software on your gt-i9305!
http://www.droidviews.com/root-and-install-twrp-on-galaxy-s3-gt-i9305-lte/
read carefully and do exaxt the same thing.......suc6
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Try a factory image?
sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Junk ROM anyway.. Lol
simms22 said:
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
Click to expand...
Click to collapse
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Did you downgrade the bootloader back to 5.1.1?
Evolution_Tech said:
Did you downgrade the bootloader back to 5.1.1?
Click to expand...
Click to collapse
Yes, manually first and when it wouldnt* boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Edit: maybe if I downgrade down to 5.0.1? Then reroot and recovery?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
Yes, manually first and when it would boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
rootSU said:
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
Click to expand...
Click to collapse
I reread the thread like 3x.
And it was mentioned that another user used NRT to downgrade successfully.
I thought the same thing, but didn't try it till I read that thread till 4am. This morning decided to take the plunge.
I was thinking also, if I just reflash bootloader and radio and put M back on, then just try manually flashing 5.1?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i did flash the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
oh, and i meant you no disrespect. while it doesnt include everyone, most people using toolkits around here are noobs. and they are the ones that usually get stuck. so, i apologize
simms22 said:
i did flaah the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
Click to expand...
Click to collapse
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Disregard
sookieball said:
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
moddified bootloader? huh? there is a modified kernel thats not supposed to force encryption. i did flash it, even though i am encrypted(by choice).
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
simms22 said:
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
Click to expand...
Click to collapse
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
no, it shouldnt unless you accidentally did it yourself. ive seen people do that too often. if you go into the wipe menu, be sure to go into advanced options, where you can pick what you want wiped.or itll wipe everything.
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
fingers crossed
What cracks me up the most is people that posses limited knowledge about fastboot flashing partition images are just seemingly willy nilly flashing images not really fully understanding what they are doing/flashing. We all have to learn somehow but I wouldn't do it at the expense of flashing a boot loader. If anything went wrong during a boatloader flash you would definitely have an unrecoverable hard brick.
Moral of the story.... People, read the how to's and SLOW down... Think about what you are doing. After reading the above replies its clear to me that people are getting a bit confused with a boot.img and a bootloader.img. its OK guys. Just be careful