G'day,
Ok, things are just not very clear. For example, I've read that Roger's Dream is a 32A ... and I've read that it is a 32B. I've read that I need a special kernel, and that it does not.
I've seen posts where users state that they just flashed, and all was fine! I've seen other posts, where the user flashing, says that they have a Dream, then they switch to Magic, realising they are calling their phone the wrong thing!
I've also found that only the Cyanogen 1.2 recovery image works with my phone, yet I see people claiming that they have 1.4 working... and again, others claiming the opposite!
Is there anyone that owns a Rogers Dream (NOT MAGIC!!), that can clarify the precise steps they used to get 4.19999 of CyanogenMod to work?
For example:
- did you use a recent recovery image (like CyanogenMod 1.4), and if so -- where did you get it?
- did you need to flash a modified kernel over 4.19999, to get it to work?
- what base image from HTC did you use, before flashing 4.19999?
It would be really cool if someone could post the precise, know to work steps. Note, I'm very hesitant to flash, using the old 1.2 recovery image I have, as 1/2 the options in that recovery image don't work!
It would be even cooler, if someone could post this info on the Cyanogen Wiki, for all to see.
(I should mention, that I've tried about 10 different recovery images, and only one worked. A 1.2 recovery image, which was from the "Rogers Root" thread. I've tried the Cyanogen 1.4 recovery image, and the -32A hacked recovery image. In all cases, the phone simply locks when I try to get to the recovery screen. I've seen other users state the same thing. When such conflicting information exists, it makes one nervous as to the validity of all "Do this to get CyanogenMod working" Rogers threads...)
BRad Barnett said:
G'day,
Ok, things are just not very clear. For example, I've read that Roger's Dream is a 32A ... and I've read that it is a 32B. I've read that I need a special kernel, and that it does not.
I've seen posts where users state that they just flashed, and all was fine! I've seen other posts, where the user flashing, says that they have a Dream, then they switch to Magic, realising they are calling their phone the wrong thing!
I've also found that only the Cyanogen 1.2 recovery image works with my phone, yet I see people claiming that they have 1.4 working... and again, others claiming the opposite!
Is there anyone that owns a Rogers Dream (NOT MAGIC!!), that can clarify the precise steps they used to get 4.19999 of CyanogenMod to work?
For example:
- did you use a recent recovery image (like CyanogenMod 1.4), and if so -- where did you get it?
- did you need to flash a modified kernel over 4.19999, to get it to work?
- what base image from HTC did you use, before flashing 4.19999?
It would be really cool if someone could post the precise, know to work steps. Note, I'm very hesitant to flash, using the old 1.2 recovery image I have, as 1/2 the options in that recovery image don't work!
It would be even cooler, if someone could post this info on the Cyanogen Wiki, for all to see.
(I should mention, that I've tried about 10 different recovery images, and only one worked. A 1.2 recovery image, which was from the "Rogers Root" thread. I've tried the Cyanogen 1.4 recovery image, and the -32A hacked recovery image. In all cases, the phone simply locks when I try to get to the recovery screen. I've seen other users state the same thing. When such conflicting information exists, it makes one nervous as to the validity of all "Do this to get CyanogenMod working" Rogers threads...)
Click to expand...
Click to collapse
i just followed his instructions in post #1 and it worked fine for me
btw I used Amon_RA's latest recovery image
Ok, first.. I do appreciate the response.
However, what I'm trying to do, is get rid of *all* ambiguity, here.
So, first, you can't have done what (I assume) Cyanogen said in his 'post #1', if you used a different recovery image!
Also, I'm not sure what post #1 you mean. Post #1 on this board, is an off topic discussion thread. If you mean on Cyanogen's site, that's probably changed since you flashed.
Did you flash with 4.19999? Are you running 4.19999? It's different than the current Cyanogen stable...
Again, thanks for the post, but I'm hoping we can get something clear, for all Rogers users....
Ok, I'm guessing you are talking about this recovery image?
http://forum.xda-developers.com/showthread.php?t=530492
Which version did you use? The confusion exists, because some posts claim that Rogers Dream is different than the T-Mobile dream, and that it is a 32A.. where the t-mobile is a 32B.
However, from my side, I've actually tried to flash *both* of those images. Both simply lock up on boot, for me.
Do you have a Dream, or a Magic? Again, I'm talking about Dream here...
Thanks
note.. I've been flashing recovery images using ADB, but in the thread I saw, where another Rogers Dream user could only get the 1.2 image working, he tried everything. The easy flash tool, using flash_boot from the Android shell, using ADB, and replacing the recovery image on the data partition too! Nothing worked!
note#2!
I've just downloaded both G and H recovery images, from the above post, again. Neither recovery image works. They both just lock up on the Rogers screen.
Note #3...
I've just tried this image (1.2.3):
http://forum.xda-developers.com/showthread.php?t=566669
Also a lockup on an attempt to access it, on boot.
I emailed the guy who wrote Flashrec, and asked him about the 32A/32B problem and here is his response:
On Tue, Oct 20, 2009 at 8:25 PM, <REDACTED> wrote:
> I am doing some research into rooting my Rogers HTC Dream phone.
>
> I have checked the HBOOT boot loader and it tells me I have a 32B handset,
> but your flashrec detects it as a 32A.
>
> Which method should I trust? How can I avoid bricking my phone?
>
> Additional info:
>
> Flash rec tells me: "Phone type is EBI1/32A"
>
> HBOOT tells me:
>
> * DREAM PVT 32B SHIP S-ON H
> * HBOOT-1.33.0009 (DREA21000)
> * CPLD-4
> * RADIO-3.22.20.17
> * May 12 2009, 17:05:58
>
What FlashRec really reports is "EBI1". Unfortunately there has been
some confusion about 32A/32B - the 32A/32B part is not actually what
matters for the kernel, but rather the EBI0/EBI1 part.
Most people are calling "EBI1" the wrong thing - "32A" - incorrectly,
so I made FlashRec report both ways of saying what's meant to be said.
Unfortunately, some of the 32A kernels floating around really do
*only* handle 32A phones. If you can find one that does not use
TigerTael's patches, but rather uses the HTC EBI1 patch, you should be
ok.
You can not use a "32B" kernel with your phone, since all of those are
EBI0. Some Rogers Dream owners have been flashing a EBI0 SPL/radio so
the normal ADP1/G1 kernels are usable, but I can't recommend that
route myself.
The EBI1 recovery image FlashRec picks automatically will work with
your phone, but you'll need to find a proper (EBI1, and not 32A only)
firmware. I don't know if any exist yet, though there's no good
reason for them not to.
--
http://zenthought.org/
Click to expand...
Click to collapse
Related
I rooted my MT3G early on using the goldcard method - it is currently running the RAv1.1.0h rom from the original rooting thread. It has the 1.33.2005 SPL and the 3.22.20.17 radio. In fastboot I can see that it the SPL is an HTC version (I think that is what PVT 32B ENG S-OFF H means, right?).
I'm having trouble moving to a 32B rom, and no matter what I try, I can't get the damn recovery image to switch from the current RAv1.2.1H to the G - which is (I assume) why I can't install any 32B roms.
Any foolproof way to change my recovery image from H to G? I've followed all the steps listed on how to do this in Fastboot and using ADB to switch it over, but no matter what I do, it has no problems booting correctly with an H recovery image, but not with a G.
Any 32B roms just makes the phone hang at the splashscreen, so I know it's a rom issue.
OR - Am I missing a step here - is there a different spl I need in order to get my MyTouch 3G to think it is a G edition again. OR easier yet, should I stop whining and just find a reliable 32A rom that works on it (assuming something without too much HERO stuff?).
YES - I searched everywhere, I spent countless hours on it, but I can't help feel I've missed something really stupid, so feel free to call me names and point out the obvious (just don't say "try Google).
Are you still able to use flashrec? If yes try to flash this one>> cm-recovery-1.4 works fine if you want 32B roms. Enom uploaded latest version yesterday.
http://forum.xda-developers.com/showthread.php?t=549754 nd if you want version prior to this then go to http://www.4shared.com/file/129108782/3953f016/HTC__crc1__Android_rooted_Rom_32B_TMobile.html
unzip and make sure to install one after the other. Large one first and rename as update ,put in your sd card. Once that is performed then go to the next small one about 14mb. Rename as update and put it in sdcard. Dont forget to delete the large one if already there.
Let us know how you go on.
No - Flashrec won't run since the rom I'm currently using has the exploit patched.
Good tip though, thanks! Any other thoughts on why I can't get the 1.2.1G recovery image on my phone? Or an alternative way to get it to install?
EDIT: Took a few steps back, installed the sappimg for the MT3G, then did flashrec and then did the update with the rom you posted. Thanks so much for the tip and inspiration!
Yes, well done.Thanks for letting us know.And yes flashrec wont work on these rom also. I tried many times to flash with RAv 1.2.1image but it seems it was not possible. I asked emon in his T Mobile rom thread where he gave me a tip as to how to go about RAv.... but that hasnt worked.
But there is a solution if al you want is to make 3 partitions.
I followed Paaragon method as described on http://forum.xda-developers.com/showthread.php?t=512873
and it worked. So try that.
I tried many different roms and finally settled on enomther's
because it is very fast, not too cluttered and just perfect for 32B boards. And further more, there isnt anything that doesnt function.
PS: I prefered the one prior to current as on 4shared. But thats personal.
unroot completly by re insttalling the saphimg and go with the oneclick root method from the unlocker thats what i did and TITS! perfict running hero and full 32 b envierment raido and roms ... be carefull with the 32 a 32 b mixup could be the end of your touch....
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'm a complete newbie. Most of you will have little patience for me but I'm hoping to find at least a couple of you willing to help me out. Here's my story. I thought it would be cool to by a used HTC Magic from Ebay to use with AT&T. The guy that sold it to me put Froyo on it and I was excited to have the latest Android on the phone.
I got it yesterday and the trouble started quasi immediately. I will post the exact things that happened as well as I can.
1. First the phone was rebooting on its own. It would make it as far as the home screen with the icons but if I tried to press anything, like contacts, it would reboot.
2. Then it eventually took me to the recovery screen where, after reading several threads, I downloaded the newest (not ROM, but whatever the first thing is on that page that you can update it).
3. Then the phone stopped rebooting itself but I couldn't get to the market or email because the dumbass that sold me the phone hadn't wiped his user info. So I googled again and was told to factory reset.
4. I tried factory reset 3 times and it did nothing.
5. Went back to the recovery page to see if that had anything that would help and I clicked Fix Permissions and let it run that.
6. Still no change when it came to wiping his user info.
7. Got frustrated and googled again. This time I saw a thread that said you should reboot using the up/down key and power. Did that.
Since then, I've had a blinking HTC green screen. At some point during this process I made it to what looks like a basic OS window from which I copied the following information:
sapphire pvt 32b eng s-off h
1.33.2005
radio-2.22.19.261
apr 20 2009, 15:30:43
hboot
What do you suggest I do now? I emailed the guy who sold me the phone because I figure if he put it on there, he can put it back. Or at least send me the files. Not sure he will care or want to help me. Besides, doesn't seem like he got it right.
I am willing to try to fix this myself but I don't want to start downloading files and flashing the phone only to destroy it. Guidance is needed.
Thank you in advance.
Seelier.
Metuchen, NJ
If the device actually booting then you should be alright, just sounds as if the guy who sold it to you flashed it with something crappy.
1.33.2005 is your SPL version, and that particular SPL version is what's referred to as an "engineering SPL" which allows you to flash roms and custom recoveries via fastboot (basically). For more info you can read here , but it doesn't overly concern you now.
To flash any roms yourself (more easily) you will need a custom recovery such as Amon_RA's Recovery, which you can download in this thread. Follow his instructions. You may already have this but you didn't say so.
Once you have done so, I suggest you install a ROM such as CyanogenMod, which you can get from here. Again, instructions on how-to flash it are in his thread. Essentially though, it is as follows:
- Put cyanogenmod rom on your SD card.
- Boot in to recovery screen (press the ON button whilst holding HOME)
- Wipe data/dalvik-cache
- Flash .zip from SD card & choose the file you put there
- Reboot the phone and wait patiently
Edit: Just to reassure, the things that tend to "brick" phones are flashing SPL and Radio updates, which you don't appear to need to do. Flashing roms very rarely causes devices to break, it is usually just the rom at fault.
Not Development related. Moved to General.
OP, next time you post make sure you post in the correct section or I'll close the thread.
Okay I'm lost, weary of trying things as I'm not 100% clear on alot of this stuff.
Here's what I did, I recently had tmo replace my original mt3g, sadly the replacement gave the version is older or whatever message. I've gone through the steps and now I'm stuck at the boot up splash screen. I'll post what i've done so far, hopefully someone can identify whats gone wrong and steer me
Ok I followed the instructions here:
h~p://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
h~p://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
h~p://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
That worked, the phone was rooted and booting.
I then installed the the AMON_RA recovery img and I've tried both flavors
recovery-RA-sapphire-v1.7.0H.img
recovery-RA-sapphire-v1.7.0G.img
I forget at this point, but I think the G didn't work for me, but i have H working.
From there I began following the instructions on cynogen mod to install...
h~p://forum.cyanogenmod.com/topic/394-cyanogenmod-5-for-dreammagic-mean-lean-pastry-machine-v508-06192010/
h~p://forum.cyanogenmod.com/topic/278-installation-support-line-cyanogenmod-5-for-dreammagic/
h~p://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Magic_%2832B%29
I booted the the recovery, wiped everything, installed the cm base, then gapps and powered down and powered on, stuck at splash...
I've tried a few variances and just to make sure, i went back to recovery and installed the Rom-RAv1.1.0H-signed-update.zip again to make sure it was working. It booted right up.
Ok so here is my phones info from the vol down + power hboot menu
sapphire pvt 32b eng s-off h
hboot-1.33.2005(sapp30000)
radio-3.22.20.17
apr 20 2009,15:30:43
I'm not sure of what else to include, my minds melted at this point.
It was so easy to root my old mt3g, this new model just makes me feel like an idiot.
*edit* Here is the info from my phones settings>about with the Rom-RAv1.1.0H-signed-update.zip loaded
Model: Ion
Firmware 1.5
Baseband 62.525.20.18h_3.22.20.17
kernel 2.6.27-cb85e129
[email protected] #3
Build #
cr843
Hmm
Did you root your phone using the MyTouch Rooting guide? Or the MyTouch 1.2 (has 3.5 mm headphone jack) guide? From what it sounds like you got the updated model of the MT3G.
If you used the Rooting guide for the old model and you have the new one, you will have issues. Heres the link:
h~p://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
If I'm right, you should have no issue re-rooting your phone.
Good luck, hope this helps.
<grin> that's another aspect of my mind melting yesterday, making sure i wasn't following instructions for the wrong version of the phone.
I have the original base model, no 3.5mm.
Tmo sent me the replacement phone about a month ago.
So that said, I think I followed the original versions instructions.
Flashing back to the old version
Rom-RAv1.1.0H-signed-update.zip
the phones worked fine all night and I got it doing the things i rooted for in the first place, sharing my cells inet to my laptop etc. so I can live with this until the weekend I suppose but still want to figure out why i couldn't get cynogen mod 5 running.
Okay i have an idea what might be going on, just my guess at this point.
I think i have mix matched mt3g-a and mt3g-b files.
Here's my thinking...
recovery-RA-sapphire-v1.7.0H.img - works
recovery-RA-sapphire-v1.7.0G.img - doesn't work, sits at splash screen
Rom-RAv1.1.0H-signed-update.zip - works, but shows up in settings>about Model = ION. I think Ion is the mt3g-a flavor...
I tried today to use flashrec, the first backup of my recovery failed. tried again it reported success. closed app opened and it gave me the option to flash the cyno recovery or restor mine, i flashed the CM and when i rebooted to the recovery it would just sit there at the splash screen. i could still boot normally and into the fastboot menu... I then went and downloaded the CM 5.08 install from a mirror.
I also tried the the newest cm v6 rc2, and update-cm-4.2.15.1-signed.zip
All stuck at splash on boot.
Fixed and working, I think it was my radio. I had a mirror post over ta the CM forums, and I was pointed to the correct radio and after flashing the radio and the g version of the recovery it came up, then flashed CM and Gapps and it worked...
I was also told to update my spl, but havn't done that part yet.
*edit* username is globeadue there, post should come up with a username search
Hello...
Fairly new here...
Also new to this rooting/rom business...
but, to the point.
I have a Rogers Magic 32A, with the stock Rogers rom.
my fastboot specs are
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76. 0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
I am using the universal androot app, and running ROM Manager.
Whenever I boot into recovery, it either freezes after a few seconds, or resets the phone back to the first splash screen, and continues to work as normal (no bricking or any of that jazz.)
So anyway, my question is...
Does anyone know why it's doing this?
I got it to flash Cyanogenmod 6.0 once, but it didn't actually install.
Do I need a different radio and SPL?
I've tried searching, and I found nothing... but if there is already a thread with this issue, I'll gladly revert to that, and delete this thread.
TL;DR
-Phone is involuntarily restarting when I go into recovery mode
-Running stock Rogers rom, ROM manager, rooted with universal androot app
-New to android customization
-Am I doing anything wrong?
Thanks for reading.
I have the same problem!!
What I can do to fix it?
I'm really scared ...
the problem likely is you are loading the ebi1 recovery (magic 32a running 3.x radio) on you "hero like" magic (magic 32a running 6.x radio)
The hero recovery will work but you may find few roms.
I'd reccomend these rooting instructions
The process will work from the top I believe but since you ran androot after placing the files onto the phone you can skip to where I run exploid (with the seceetlol password) and run 'su' instead of exploid.
Once you have a 3.x radio with working rom and recovery if you want to checkout rom manager you can hopefully with less issues and if an issue happens you can always flash a recovery via fastboot.
I did end up fixing my issue.
Great Big Dog on the androidforums helped me out...
I tried to look for my thread that I posted on the androidforums, but I guess it got deleted...
pretty much... I followed GBD's quick root guide for the post 911 update for rogers magics, with a tiny bit of a switch for flashing the amonRA rom.
I can't remember exactly what it was, and I really wish that thread didn't get deleted.
And I can't link in any posts, so I can't really help you out.
I usually always just suggest installing a fresh RUU, especially if you don't know what you're doing... like me.
you can probably find one on the htc website.