Hi,
I was just wondering if it's possible to flash system.img from the Android 1.6 SDK (well can be 1.5 as well ) to the HTC Magic and if so will it work (map buttons, light indicators etc.)?
Would you also need to flash the boot and recovery then?
And at last would it all be possible with a stock SPL?
Thanks.
Related
I have a black G1 with a 32b board,I found a rom online that was for the rogers dream,I didn't think it would flash the recovery image too,so I flashed it thinking if it didn't work I would be able to just flash to a different rom. That didn't work. it boots up as a rogers dream,and is fully working,but I can't flash back to anything else because it's a stock recovery image,and even though I had the engineering spl,it messed that up too,it still shows the skateboarding androids,but with a cyan stripe at the top of the screen and it won't even flash the htc images for the dev phone,or the normal rc29 DREAIMG.nbh. anyone have any ideas? fastboot tells me remote not allow,bootloader to the DREAIMG.nbh says either main version old,or model id mismatch,most of the time it's the main version thing though,and the recovery thing tells me no signature found if I try to flash the htc images and verification failed if I try to flash anything else that i've tried. anyone have any ideas? it was the 911 mandatory update from rogers that was supposed to also add sense if that helps anyone any.
1) THERE IS NO SUCH THING AS A 32A DREAM!!!!
32A means SOME HTC MAGIC, and ALL HTC HERO.
ALL DREAM 100% WORLDWIDE are 32B
*** NO EXCEPTIONS.
2) You need to provide more information: WHAT did you flash to the device.... SPECIFICALLY. And HOW DOES EVERYTHING IDENTIFY ITSELF, i.e. SPL, BASEBAND, KERNEL, etc., does the "su" command work?
3) I have ZERO expectations for you. Anyone with a screen name of "msnuser" is not worthy of android.
it's the rom from comment 102 on this page:androidforums.com/rogers/38624-rogers-update-911-fix-rogers-htc-dream-magic-ready-3.html the rom says on the recovery screen dream PVT-32A and it used to be PVT-32B. Not sure how it worked or how it booted,but the phone says it has 87mb free on the internal storage and it runs a lot quicker than it did on any rom I've ever used before,I just miss my rooted apps. I traded phones with my brother because he never uses rooted apps anyway,he was running stock tmobile firmware and was glad to have a faster os.
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?
I have a Rogers Dream 32B. Radio 3.x (this is EBI1, correct?).
I was following the instructions on the CM wiki to root my phone and install CM 5. I can't link outside as a new user, but the article titles on CM wiki are "Full Update Guide - Rogers Dream 911 Patched" and "Upgrading From CM 4.2 or other rooted ROMS to 5.0.x(Dream/Sapphire)"
I used fastboot to install Amon_Ra's recovery, which is the first note. But after that I'm not exactly sure what I did to brick my phone.
Stalls at the Rogers splash screen. I can access the bootloader with the 3 androids on skateboards by holding down Camera + Power. I can also issue fastboot commands. I can also boot into recovery by holding down Home + Power. I haven't tried doing anything in recovery other than having it power off the phone, but I can see it says I have Amon_Ra's recovery version. I can't issue adb commands to the phone, which is step 4 in the tutorial - copying the ROM and google apps files to the SD card.
If I do a reset in recovery, will that help me at all? Or is there something else I can try?
plasticjar said:
I have a Rogers Dream 32B. Radio 3.x (this is EBI1, correct?).
I was following the instructions on the CM wiki to root my phone and install CM 5. I can't link outside as a new user, but the article titles on CM wiki are "Full Update Guide - Rogers Dream 911 Patched" and "Upgrading From CM 4.2 or other rooted ROMS to 5.0.x(Dream/Sapphire)"
I used fastboot to install Amon_Ra's recovery, which is the first note. But after that I'm not exactly sure what I did to brick my phone.
Stalls at the Rogers splash screen. I can access the bootloader with the 3 androids on skateboards by holding down Camera + Power. I can also issue fastboot commands. I can also boot into recovery by holding down Home + Power. I haven't tried doing anything in recovery other than having it power off the phone, but I can see it says I have Amon_Ra's recovery version. I can't issue adb commands to the phone, which is step 4 in the tutorial - copying the ROM and google apps files to the SD card.
If I do a reset in recovery, will that help me at all? Or is there something else I can try?
Click to expand...
Click to collapse
You're not bricked.
Couple of options:
1) Go into fastboot and flash a COMPATIBLE recovery.img. You installed an EBI0 recovery image, you need an EBI1.
2) Go into fastboot and flash an EBI0 radio (version starts with a "2").
I suggest option 2, since it will improve your compatibility with custom ROMs. It is also MUCH SAFER to have a 2.x radio since it is compatible with ALL SPLs ("1.x" and "3.x" are each only compatible with *some* SPLs.)
lbcoder said:
You're not bricked.
Couple of options:
1) Go into fastboot and flash a COMPATIBLE recovery.img. You installed an EBI0 recovery image, you need an EBI1.
2) Go into fastboot and flash an EBI0 radio (version starts with a "2").
I suggest option 2, since it will improve your compatibility with custom ROMs. It is also MUCH SAFER to have a 2.x radio since it is compatible with ALL SPLs ("1.x" and "3.x" are each only compatible with *some* SPLs.)
Click to expand...
Click to collapse
Thanks for your help lbcoder.
EDIT: Actually, I installed the correct recovery image! I have RA-dream-v1.7.0R, which is the one for EBI1.
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.
plasticjar said:
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.
Click to expand...
Click to collapse
I use the same combination, Rogers Dream on AT&T. Started off with the EBI1 kernel and 3.x radio, but after a while went to EBI0 and tried both current 2.x radios. I found no noticeable difference in reception or speed with any combination.
plasticjar said:
Thanks for your help lbcoder.
EDIT: Actually, I installed the correct recovery image! I have RA-dream-v1.7.0R, which is the one for EBI1.
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.
Click to expand...
Click to collapse
No, it won't affect your radio frequencies.
Your phone is basically TWO COMPUTERS. One is the "radio" computer, the other is the "application" computer. Each of these runs their own operating system. You'll just be running your radio computer on an operating system that is *more compatible* with the typical ROMs that you might find for similar hardware.
Can anyone tell me if there's a way to flash a new radio with android already flashed.
i would like to know that too >.<
probably via the bootloader? or do we really have to flashback to winmo first Oo
1. Power off your device.
2. Hold Volume Down key and power on the device till u get the tricolour screen.
3. Flash your Preferred Radio Rom
Where can you download these radio roms? And once you flash those roms do you still keep your Android rom that you have installed before you flash the radio rom?
benmeilink said:
Where can you download these radio roms? And once you flash those roms do you still keep your Android rom that you have installed before you flash the radio rom?
Click to expand...
Click to collapse
you will still have your android without any changes
Once you are in the tricolour screen you just flash with customRUU? Because customRUU wont find any information concerning the radio that is already installed..?
benmeilink said:
Once you are in the tricolour screen you just flash with customRUU? Because customRUU wont find any information concerning the radio that is already installed..?
Click to expand...
Click to collapse
two days ago i flashed the most recent radio on my android hd2.
went without problems, just like max_ray said, boot into bootloader/tricolourscreen and then flash with RUU.
just do it, it works ^^
I have been playing around with different Android and WP7 builds on the HD2. I recently had one android NAND flash that failed during the process. I was able to recover the HD2 no problem.
However when I do flash any WM6.5 ROM or use the ROM update utility the standard HTC logo that is present when showing the percentage of the ROM update is missing.
I am wondering if this has happened to anybody else as well.
Thanks,
Aaron
AllTheWay said:
I have been playing around with different Android and WP7 builds on the HD2. I recently had one android NAND flash that failed during the process. I was able to recover the HD2 no problem.
However when I do flash any WM6.5 ROM or use the ROM update utility the standard HTC logo that is present when showing the percentage of the ROM update is missing.
I am wondering if this has happened to anybody else as well.
Thanks,
Aaron
Click to expand...
Click to collapse
Hasn't really happenned to me, But I'm interested into how would it even happen.
You mean you get a white screen with a green bar in the middle (shows process ? ).