Related
I bricked my first phone in January after a month of reading and then following the wrong instructions -- now I am quite hesitant to do things.
On my second phone, I followed the rooting rogers dream full guide at:
[http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod] This worked, although it seemed to have almost as much lag as the rogers rom.
I did a nandroid restore back to my original rogers rom which I had backed up per the instructions in the above guide. This confirmed that I was not seeing much decrease in lag using cyanogenmod.
I want to try going to the 2.22.19.26I radio and use non EBI1 ROMs.
From reading I think I need to use amon-ra recovery with no R on the end.
The radio,recovery and rom should all be non - EBI1.
In my reading, I haven't seen instructions to do what I am looking for.
I have put some commands together below.
Will this work or brick my phone?
It probably is missing some things. For example see step 6.
=============================
1.
start up recovery : Shut down your phone and, while holding the Camera button on the side of the phone, turn it on
again. [Amon_RAs Rogers Dream Recovery (recovery-RA-dream-v1.5.2R.img)]
2.
enter fastboot: press Send to go into fastboot mode.
3.
fastboot devices (to make sure that fastboot "sees" your device)
4.
fastboot flash radio radio.img [from givemeroot.zip]
5.
fastboot erase system -w
6.
is this needed?
fastboot erase boot
7.
fastboot erase recovery
8.
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
9.
fastboot flash system system.img [htc_system_img_14721.zip, stock android 1.6 will get rid of EBI1 kernel patch]
At this point it shoule be a working phone with 2.x radio and stock HTC Android 1.6.
10.
powerdown phone
11.
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Now the phone will be:
Device: Rogers HTC Dream phone
recovery-RA-dream-v1.6.2
Engineering SPL - HBOOT version is 1.33.2005
Radio - 2.22.19.26I
ROM cm-4.2.x
checksums:
givemeroot.zip md5: 4a58a5702fdf899547011888d9cc066f
recovery-RA-dream-v1.6.2.img - MD5Sum: de9a2562ed8b7ef3b8dab4ecf369fd13
htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d)
=============================
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
beav_35 said:
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
Click to expand...
Click to collapse
yea, I did this 2 weeks ago.
I followed this:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
only do it in reverse, as in install the 2.x radio instead and install the ebi0 recovery instead. Then boot into recovery and flash a rom (i would suggest superD rather than cyano because you wont have to also flash the google apps)
troubles...
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
pictures
Additional info:
pictures of my screens are attached.
david1212 said:
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
Click to expand...
Click to collapse
You for got to flash the base rom or a modified rom. You stopped at the system img so you don't have anythig to boot to. Flash the 1.6 base and you should be good to go.
I don't understand.
I thought that the system.img that I got from the htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d) is the base android 1.6. I thought this is a full base 1.6 system.
What am I missing?
In recovery just flash the rom you want to use, then it should boot properly.
OK. I applied update-cm-4.2.14.1-signed.zip from recovery and it boots up to CM now.
Thanks.
Great!! Glad you got it working.
BTW There's a newer version of CyanogenMod out.
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Yes you can use SuperD. Make a nandroid backup, wipe, then flash the update.zip. No need to flash the system.img. There is also a EBI1 port for SuperD so you could have used it before too.
david1212 said:
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Click to expand...
Click to collapse
you know that you could have used ALL the roms on ebi1 anyway
you just flash a kernel after you flash the rom
It takes literally 2 minutes to make your own kernels with
http://faruq.yandao.com/magicport/
insert rom boot.img (just extract rom to get this), and out comes a kernel !
good news
I am glad I did this.
The phone works better. I don't lose data connection like I did before. The battery life is better.
Now I will make guesses.
The radio works better - has better signal. At my desk, cell reception is not very good. Now the battery is run down less with better connection strength.
My config is now:
-Device: Rogers HTC Dream phone
-Provider: Bell Mobility Canada
-recovery-RA-dream-v1.6.2 [non EBI1]
-spl: 1.33.2005 DREA21000 aka danger spl from rogers_root_unzipme.zip (md5sum: d522e09be7ddec00ef2354533c14cd2f).
-Radio: 2.22.19.26I
-ROM: SuperD 1.9.3 [non EBI1]
questions about downgrading from rogers radio
HI, i'm on a rogers dream using cyan 6.1 and ebi1 kernel. if i downgrade to the 2.22 radio will i have to sign the rogers waiver to get service? i've also heard that the edge network slows down considerably. if there are problems will i be able to go back to the rogers radio?
thanks.
jeremy boyd
Yes, Rogers will disable your data if you don't have the 3.22.26.17 radio unless you sign the waiver. 2.xx is not a downgrade, its a different type of radio. You can always go back to the old radio just make sure your recovery and kernel match your radio.
If you want try this radio. Your phone will be much faster.
http://forum.xda-developers.com/showthread.php?t=831139
I read recently that to flash the danger spl with the least amount of risk it should be done using fastboot. I have fastboot up and running but I am a little confused on using the commands. Can anyone help explain this to me?
You need to boot the phone into the bootloader (spl), open a command prompt on your computer, and cd to where the fastboot binary is.
From here the commands all start with "fastboot." So to erase a partition from the spl, you would enter "fastboot erase recovery" and substitute recovery for whatever you wanna erase. The partitions on the Dream are: system, boot, cache, misc, userdata, and recovery.
To flash a partition you would enter "fastboot flash [partition] [.img file name]"
The .img file has to be in the same folder as the fastboot binary.
Example: "fastboot flash recovery recovery-AmonRa-1.6.2.img"
This is, of course, just about fastboot itself. I have no idea how to flash the spl from fastboot; I didn't even think it could be done. I would suggest using fastboot to flash a custom recovery, and using the recovery partition to flash the spl zip file.
Interesting
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?
Jaylen said:
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?
Click to expand...
Click to collapse
You don't flash zip files through fastboot, extract it and flash the .img file directly, but yes, that command is correct.
fastboot flash radio yourfile.img
fastboot flash hboot yourfile.img
then reboot with:
fastboot reboot-bootloader
You'll probably want a recovery .img handy as well, in case you can't get into recovery after flashing. You can flash that with (predictably):
fastboot flash recovery yourfile.img
If anything goes wrong during the radio or hboot flash, DO NOT POWER OFF OR RESTART!! Come back here and get advice. If you reboot the phone without a valid radio or hboot, you will brick.
Remember there's always a risk involved with flashing these sensitive parts of the system.. if you brick it, I was never here
Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?
The new radio is your choice really.. It's not made a lot of difference to me and you shouldn't have any problems just flashing the spl on top of 26i.
Jaylen said:
Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?
Click to expand...
Click to collapse
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.
lbcoder said:
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.
Click to expand...
Click to collapse
Thats what I thought. After reading your thread I flashed the engineering SPL using recovery and now I plan on using fastboot to install the danger SPL. Is it alright to reboot and use recovery to flash a ROM after the SPL is finished or should I just keep using fastboot?
hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?
1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.
blackknightavalon said:
1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.
Click to expand...
Click to collapse
Have you read anything in this thread or any of the awesome work by ezterry over the past few weeks? FLASHING THE SPL THROUGH RECOVERY CAUSED ALL THE BRICKS.
Anyone looking at this thread for help should ignore this and use the fastboot method detailed above.
Jaylen said:
hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?
Click to expand...
Click to collapse
Er.. I've not come across that one before..
Yeah I just put it on hold for the night. It seems that fastboot only flashes to these partitions, system, boot, cache, misc, userdata, and recovery. I'm wondering if the SPL is stored in one of these. I found an ancient JesusFreke thread where he was talking about it being in misc, but I wasn't just gonna go flashing away at random partitions lol...
Ok, I was looking at the commands in fastboot by typing "fastboot ?" in the command prompt and I notice that it says you can flash update.zip files from fastboot. I'm wondering if I rename the original Danger SPL zip file to update.zip and try to flash it this way through fastboot if it will work. Kind of nervous to try it though, what do you guys think?
Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.
FaJu said:
Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.
Click to expand...
Click to collapse
The running spl is in RAM. No need to worry about this.
@Jaylen: That's an interesting one about the partition not being available. I'll look into that -- it could potentially throw a wrench into things.
I don't think its fastboot error or anything, I'm a little bit new at this but I'm pretty sure I set it up correctly. I can see my device in the command prompt, could I have missed a step? @ lbcoder What do you think about flashing the SPL as an update.zip package through fastboot?
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx
yogi2010 said:
hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx
Click to expand...
Click to collapse
You'll need that file to run in ADB mode.
Has anyone who has a CDMA Hero been able to flash a recovery image through fastboot? I have never been able to and I either flash it with the OS running or when booted into recovery.
unCoRrUpTeD said:
Has anyone who has a CDMA Hero been able to flash a recovery image through fastboot? I have never been able to and I either flash it with the OS running or when booted into recovery.
Click to expand...
Click to collapse
I have done it on my g1 but you'll need the eng spl to unlock the fastboot flash commands. So yes it is possible.
ASimmons said:
I have done it on my g1 but you'll need the eng spl to unlock the fastboot flash commands. So yes it is possible.
Click to expand...
Click to collapse
I knew it had to be something because on the G1 you can do fastboot shell and a whole lot of other stuff that we can't do.
unCoRrUpTeD said:
I knew it had to be something because on the G1 you can do fastboot shell and a whole lot of other stuff that we can't do.
Click to expand...
Click to collapse
If you flash the eng spl with s-off that floating around here you'll have all the fastboot commands unlocked. this will allow you to flash stuff from fastboot... and as far as I've heard pretty much makes your phone un-brickable (save flashing a bad radio since this boots even before the spl) basically you can only soft brick your phone... so you just go to the fastboot and fastboot flash a new recovery, rom, kernel.... yadda and your back.
This seems to be where you see people say that there stuck on fastboot but can't do anything, if you have the eng spl your golden if not your in trouble.
The rooting for the g1, as a remember it made you flash the danger spl which I think was similar to the eng spl. Its been a while so I could be wrong on that but thats how I remember it.
After many searches to no avail, I figured I'd open a thread and see what's going on.
I recently purchased a Nexus One that was rooted and had an unlocked bootloader. The hboot is 0.33.2012 with radio 5.12.00.00
I am trying to convert back to stock so I can access Gingerbread when it goes OTA. I have tried 20 times now to use the PASSIMG.zip method of reverting and every single time, some text loads very fast, and the last thing I see is something along the lines of:
"Loading... [nv.img]"
Is there anyone that can suggest an easy fix? I have tired using FRG33 and FRF91, but both will not work. With my luck, I'm just doing something nubish. Any help would be greatly appreciated.
Well this should work : I replied to you via the twitters - but I'll post this here for posterity.
@du57in Ok I'll bite. I restored my N1 to stock due to wifi issues yesterday. Download FRG83 from here http://tinyurl.com/26jy7tt
@du57in Step 2: follow the steps in this thread http://tinyurl.com/2dlmzsl using the FRG83 from the first link
@du57in You're going to want to use the first FRG83 listed in bold MD5: a801dcc43e9244d323e57bbd5705eaea
Here's my summary:
Download that original signed HTC FRG83 image
setup fastboot if you haven't already
unzip it
Plug in Nexus One with USB to computer (enable usb and debug modes)
$ adb reboot bootloader
(which will boot into the bootloader)
Confirm fastboot connection
$ fastboot devices
$ fastboot erase userdata
- did not work for me, I went into the bootloader recovery and wiped the data on my device instead
$ fastboot erase cache
Go to the directory that you stored your unzipped files.
$ fastboot flash userdata userdata.img
(I actually skipped this one, but you might want to flash it since you're coming from a custom rom)
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot reboot
OK, I'm working on that and I will update with what happens.
Goodluck with fastboot. Theres always the throwing it against the wall method if fastboot fails.
Fastboot never fails. NEVER
7on said:
Well this should work : I replied to you via the twitters - but I'll post this here for posterity.
@du57in Ok I'll bite. I restored my N1 to stock due to wifi issues yesterday. Download FRG83 from here http://tinyurl.com/26jy7tt
@du57in Step 2: follow the steps in this thread http://tinyurl.com/2dlmzsl using the FRG83 from the first link
@du57in You're going to want to use the first FRG83 listed in bold MD5: a801dcc43e9244d323e57bbd5705eaea
Here's my summary:
Download that original signed HTC FRG83 image
setup fastboot if you haven't already
unzip it
Plug in Nexus One with USB to computer (enable usb and debug modes)
$ adb reboot bootloader
(which will boot into the bootloader)
Confirm fastboot connection
$ fastboot devices
$ fastboot erase userdata
- did not work for me, I went into the bootloader recovery and wiped the data on my device instead
$ fastboot erase cache
Go to the directory that you stored your unzipped files.
$ fastboot flash userdata userdata.img
(I actually skipped this one, but you might want to flash it since you're coming from a custom rom)
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot reboot
Click to expand...
Click to collapse
This will not revert your recovery to stock. The OTA will still fail.
mortzz said:
This will not revert your recovery to stock. The OTA will still fail.
Click to expand...
Click to collapse
Yes it will, smart ass
Make sure your downloads aren't corrupt. That was my noobish mistake just yesterday haha
Rusty! said:
Yes it will, smart ass
Click to expand...
Click to collapse
+1, I believe recovery will be reflashed after the next reboot.
get the ota or not be sure that it will be available online for rooted users
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I got a old g1 today it looks like it may need a new battery will have to get one before I flash.
It has CM 5 on it. It looks like before I flash any new roms I may need to update the hboot or radio ?
hboot
1.33.2005
cpld-4
radio
2.22.23.02
that's what there at now thanks. All the roms I looked at dont support 1.33.205 or am I wrong I would like to go to cm 7 what do I need to do?
All ways safe to double check before I start flashing thanks much
i flashed recovery 2.5.07
I tryed a rom that side it would support my hboot
it just got stuck at g1 screen did not make it to spash used recovery to flash back to cm 5 any suggestions
id suggest using amonra's recovery for the g1, in my opinion its the best to date. also consider upgrading your radio/spl. the extra 14mb of ram is huge for the g1 and most new roms require it. all the info to do this can be found in the forum, but if you need further help feel free to ask.
demkantor said:
id suggest using amonra's recovery for the g1, in my opinion its the best to date. also consider upgrading your radio/spl. the extra 14mb of ram is huge for the g1 and most new roms require it. all the info to do this can be found in the forum, but if you need further help feel free to ask.
Click to expand...
Click to collapse
Ok i figured I just use fastboot? I have a little fear of bricking it. Can you link a good guide flashing radio and hboot I have seen 3 or 4
well im in the process of writing a fastboot guide for the vision in another forumHERE although it is not finished.
the commands are the same just dont use the links to get the recovery, radio etc from that thread :good:
get the recovery image from amonra
and follow my 4ext recovery instructions
next will be flashing the radio and spl
this is a .zip and and you will need to extract the images
once you have everything ready to roar here are the fastboot commands:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
you can just copy and paste each line one after another in cmd
and for more info go HERE
good luck, between my guide and ezterys you should have more than enough info, of course feel free to ask more questions
demkantor said:
well im in the process of writing a fastboot guide for the vision in another forumHERE although it is not finished.
the commands are the same just dont use the links to get the recovery, radio etc from that thread :good:
get the recovery image from amonra
and follow my 4ext recovery instructions
next will be flashing the radio and spl
this is a .zip and and you will need to extract the images
once you have everything ready to roar here are the fastboot commands:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
you can just copy and paste each line one after another in cmd
and for more info go HERE
good luck, between my guide and ezterys you should have more than enough info, of course feel free to ask more questions
Click to expand...
Click to collapse
thanks much dont need a guild as I have fastboot set up all ready in a dir just looking for files to flash the links and guids were very old dating from 2009-2011 I was lost thanks much
great, then all the files needed are in my last post. just be sure to flash in that order as the .13d spl is not compatible with your current radio, and as a heads up once you change to this hboot you will no longer be able to use most fastboot commands as this is a hacked bootloader and isn't perfect in that sense. erasing partitions will still work just fine though
Sent from my HTC Vision using xda premium
All is well now thanks much thats why I love fast boot.