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 have sold my phone and I am currently using CM6 RC3
The buyer want me to install the stock 2.2
can someone please provide me with the Download to stock 2.2, and the instructions, Just flash over cm6?
Thanks
You could download the FRF91 system image (link in my signature) and flash it using fastboot...
1. reboot into bootloader
2. extract the downloaded zip
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot flash boot boot.img
6. fastboot flash recovery recovery.img
Your radio and hboot can remain unchanged (they are stock anyways)
thanks alot of your help:
I am not fimilar with using fastboot
is there a way to use recovery and flash from zip file, that is how I have been trying out different roms
I think ROM Manager has the stock rom available. That would be the easiest way.
I rooted my phone after the update. I had BHT tools which I liked pre update. I also installed safe boot then did the forever root. This all worked great. Then I installed Liberty which I did not like. I uninstalled it and bricked my phone. I then did the targa to try to get back the stock. The phone is working but I have to reboot it into recovery then use the start from there. My bionic still says my flash is not working. What do I need to do now?
Reboot the phone in fastboot and flash the device_tree.bin and it will fix that error.
"fastboot flash devtree device_tree.bin" from a command prompt in the same directory where the fastboot.exe and dll files are with the device_tree.bin file.
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse