.. now is there anyone that tried to root this again? Ive looked through alot of threads on here and people saying yeah this method will work for perfect spl etc.. but they are from taiwan or india or someother place that bought a perfect spl phone.. to me that doesnt apply to us Canadians who upgrade with the official htc rom update... so thats why i started a new thread. i see last night there are a couple new vids on theunlockr.com on 1click root access just waiting to see if someone that has the updated rogers rom has tried any ways to root again... what happens anyways if you try and root with hboot-1.33.0010 (sapp50000)
just wondering if it fails so you reboot and no luck or does it brick
ROGERS Actively disableing ANDROID features
When I first started trying to root my android, it was because I many apps were not working and I wanted to beable to mess around with the android os (cupcake?)
But the phone would not boot using fastboot, it would freeze on the ROGERS splash screen.
I must have tried 7 various imgs made by various people, none seemed to work, the phone always froze on the ROGERS screen.
Then I noticed Rogers website had a new release...
Rogers is intentionally altering their hboot to disable system changes.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireles...rs_WWE_2.17.631.2_release_signed_NoDriver.exe
That update makes further changes to the hboot, incrementing the version to HBOOT-1.33.0010 (SAPP50000)
After updating FASTBOOT returns
downloading 'boot.img'... FAILED (remote: not allow)
every previous attempt with the firmware my magic shipped with returned
>fastboot boot recovery-new.img
downloading 'boot.img'... OKAY
booting... OKAY
looks like they don't support the openness android is supposed to be...
corporate tools...
However, their update tool, available at the link above avoids all of the work on the pc side, one exe updages the firmware. if someone could use that exe, watch what it is saying to the android and how it bypasses the security features of the phone...
But until then, CANADIAN ROGERS users may never get root access.
Related
Hey everyone,
it so happened yesterday that after successfully toying around with some pre-made ROMs I tried to flash my Magic with the Google I/O Device recovery and apparently bricked it in the process. But let me start at the beginning.
What I had running fine was Anrdoid 2.0 for the 32A from here. Under the hood I was running Amon_RAs recovery "recovery-RA-sapphire-v1.5.1H.img" from here and my SPL was the Engineering SPL 1.33.2010 from here. Everything was working fine so far and I was happy toying around with the Android 2.0 goodness.
However, ultimately I wanted to deploy my custom built of Android 1.6 from the source repository. Therefore my first step was to make sure that the vanilla Android 1.6 without modifications works on the device. What I did is I went to the HTC developer site for the Google I/O Device here and downloaded the system image for Android 1.6, called "signed-google_ion-img-14721.zip". I fastbooted system, boot and (the empty) userdata that were in that package, to not much avail. The device would be stuck at the Vodafone splash (mine is a Vodafone branded 32A). I made sure to wipe everything and fastbooted those again, just to make sure. Again no results. Then I wanted to fastboot the whole package instead of the individual imgs with "fastboot update <file> -w". The consistency check then told me:
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
I happily got SPL .2005 from the above link, and installed through the Amon's recovery image. Just in case I tried to boot the device, but it didn't do much. So I went ahead and tried to fastboot update the package again. It then told me:
checking version-baseband... FAILED
Device version-baseband is '3.22.20.17'.
Update requires '2.22.19.26I'.
I was a little sceptical but went back to the HTC developer site and downloaded the radio that it cried for, named "ota-radio-2_22_19_26I.zip". I installed that again through Amon's recovery image (which is awesome btw, thank you very much!). It seemed rather successful but after a reboot the device would still not boot, nothing new to me. However, when I wanted to enter fastboot (back key), HBOOT (vol down key) or recovery (home key), nothing would happen anymore, it was just stuck at the red Vodafone splash and fastboot which would usually spring open right away would just trigger the regular boot.
I went through dozens of forum posts where people describe the same problem and it appears that no one found a solution so far. When I press the ball it comes up with a black screen and a blue LED. It also happily charges when I connect it to a charger or USB, but that is about as much as I can do. Plugging/unplugging a million times and trying different combinations of button presses and battery insert/removals didn't bring it back to life, either. The device is not connecting over USB (not as an Android or unknown device or anything) so that adb or fastboot are useless.
Have I bricked my phone? Does anyone have a solution? Please take the time to read the whole post before replying because I took the time to describe my problem and the steps I took in detail.
I'm also curious what exactly went wrong, can someone enlighten me? From what I could tell the HTC developer device (Google I/O) is a 32A so the hardware should be identical. What was my mistake?
I'd appreciate any input you guys might have!
I am sorry about your brick.. But Google I/O device is not a 32a device, it's 32b The link below explains the issue in details.. Thanks to Xanadux (if i got it right.. )
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire
And it looks like it got bricked after the Radio update.. which could be because there was something specific hardcoded for Vodefone or supported by the device hardware, and when you flashed the Google IO Radio Image (which has a differeng GSM freq. as you can see from http://developer.htc.com/google-io-device.html) it bricked..
I hope someone comes up with a solution.. I was planning to flash my Google IO device with the HTC Magic Radio flash, I guess it's not the best idea..
Hm now that you say it, it seems quite obvious that the "Google" I/O Device would be a 32B, which is "Google" branded. Mh. Oh well, I guess for some reason I didn't see it. Well, it would of course be great if someone would come up with a solution, but at least I know now what I did wrong. Thanks for the hint about the different frequencies!
Same boat....
2of11 said:
Hey everyone,
it so happened yesterday that after successfully toying around with some pre-made ROMs I tried to flash my Magic with the Google I/O Device recovery and apparently bricked it in the process. But let me start at the beginning.
What I had running fine was Anrdoid 2.0 for the 32A from here. Under the hood I was running Amon_RAs recovery "recovery-RA-sapphire-v1.5.1H.img" from here and my SPL was the Engineering SPL 1.33.2010 from here. Everything was working fine so far and I was happy toying around with the Android 2.0 goodness.
However, ultimately I wanted to deploy my custom built of Android 1.6 from the source repository. Therefore my first step was to make sure that the vanilla Android 1.6 without modifications works on the device. What I did is I went to the HTC developer site for the Google I/O Device here and downloaded the system image for Android 1.6, called "signed-google_ion-img-14721.zip". I fastbooted system, boot and (the empty) userdata that were in that package, to not much avail. The device would be stuck at the Vodafone splash (mine is a Vodafone branded 32A). I made sure to wipe everything and fastbooted those again, just to make sure. Again no results. Then I wanted to fastboot the whole package instead of the individual imgs with "fastboot update <file> -w". The consistency check then told me:
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
I happily got SPL .2005 from the above link, and installed through the Amon's recovery image. Just in case I tried to boot the device, but it didn't do much. So I went ahead and tried to fastboot update the package again. It then told me:
checking version-baseband... FAILED
Device version-baseband is '3.22.20.17'.
Update requires '2.22.19.26I'.
I was a little sceptical but went back to the HTC developer site and downloaded the radio that it cried for, named "ota-radio-2_22_19_26I.zip". I installed that again through Amon's recovery image (which is awesome btw, thank you very much!). It seemed rather successful but after a reboot the device would still not boot, nothing new to me. However, when I wanted to enter fastboot (back key), HBOOT (vol down key) or recovery (home key), nothing would happen anymore, it was just stuck at the red Vodafone splash and fastboot which would usually spring open right away would just trigger the regular boot.
I went through dozens of forum posts where people describe the same problem and it appears that no one found a solution so far. When I press the ball it comes up with a black screen and a blue LED. It also happily charges when I connect it to a charger or USB, but that is about as much as I can do. Plugging/unplugging a million times and trying different combinations of button presses and battery insert/removals didn't bring it back to life, either. The device is not connecting over USB (not as an Android or unknown device or anything) so that adb or fastboot are useless.
Have I bricked my phone? Does anyone have a solution? Please take the time to read the whole post before replying because I took the time to describe my problem and the steps I took in detail.
I'm also curious what exactly went wrong, can someone enlighten me? From what I could tell the HTC developer device (Google I/O) is a 32A so the hardware should be identical. What was my mistake?
I'd appreciate any input you guys might have!
Click to expand...
Click to collapse
Unfortunately me and you are in the same boat, I was trying to do the same to the same by flashing my spl 2010 to 2005 and just like that im stuck at boot logo with no access at all. . . tried all kinds of button, it still vibrates when you press power but thats all the love im getting from this magic.. . .by the way, it this is what i think it is.. . this will be brick # 2... . .f*ckin ey right?? . .well lets hope some genius come up with some crazy azz solution.. . ..
Another Bricke HTC Magic
Same problem than 2of11, I also flashed the wrong radio image. Did you get any solution?
Cheers, there is always a reason to buy a new better phone.. but wich one will it be?
Sorry, but I did not find a solution, the phone stayed bricked and was then changed.
Hello,
I have a PVT 32B (HTC Magic Vodafone) and just updated the RADIO to the same version as I had before, just because HTC says it. now I wanted to flash the image with
Code:
$ fastboot update signed-google_ion-img-14721.zip
and got
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2010
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking product... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
So I searched for one of these bootloader versions and ended up at this post, which tells me to be careful I think my phone still works, because it booted correctly after RADIO update. Is it save to update the bootloader and load the image from htc.developers if I have a 32B? And if so are the "SPLs" from the post (#529019) of Amon_RA good for me, or where can I get the appropriate HBOOT version?
white_gecko said:
Hello,
Is it save to update the bootloader and load the image from htc.developers if I have a 32B? And if so are the "SPLs" from the post (#529019) of Amon_RA good for me, or where can I get the appropriate HBOOT version?
Click to expand...
Click to collapse
So I was also working with a Vodafone Magic, but if I remember this correctly, mine was a 32A, where as the Google I/O device is a 32B. So maybe the hardware changed over time? In any case, be VERY careful and have someone confirm that you are indeed handling the same kind of device as the Google I/O. There should be a "Google" branding on the back of 32B devices, but I haven't been toying around with this for a while and may provide outdated information. Have you checked this link?
Code:
wiki.xda-developers.com/index.php?pagename=HTC_Sapphire
For what it's worth, I was able to use the Engineering SPLs that were posted here:
Code:
forum.xda-developers.com/showthread.php?t=529019
without any trouble. Keep in mind that maybe we are talking about different devices, though.
Hope that helps.
Yes I'm sure, that I have a 32B and in Wikipedia article to "HTC Magic" I've read, that the I/O has also the 32B. But could there also be other differences, which could cause that I brick the phone?
the en.wikipedia "Htc_magic" said:
* Two different hardware platforms exist for this phone (they require different boot images and wireless LAN kernel modules):
- The PVT32A, with a Qualcomm MSM7200A ARM11 processor and 288 MB RAM,
- The PVT32B, with a Qualcomm MSM7201A ARM11 processor, and 192MB RAM.
The only models that use the 32B platform are the original T-Mobile myTouch 3G (v1.2 of this phone, released in Feb 2010, switched to the 32A), the Vodafone Magic and the Google Ion developer phone.
Click to expand...
Click to collapse
Now I have installed a different Image so I'm not in such big temptation to update the HBOOT, but I would also like to try the developer images.
Well the good news, guys, is that the G1/dream has been de-bricked successfully, and due to the similarity of the hardware it's a safe bet that the mytouch/magic is not far off. The bad news is that it will likely require someone who has specialized equipment who knows what they are doing.
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?
Let me explain to you the whole story. I obviously know im going to get flamed for this one. I will give you the short short version
I had a rooted MT3G fender with this Rom installed
http:/forum.xda-developers.com/showthread.php?t=669911
It worked all good until i started messing with stuff. I wanted this rom installed
http:/forum.xda-developers.com/showthread.php?t=673394
Since it said 32a and MT3G fender is 32a i assumed that it will install and no problems. So i used the gold card to change radio and spl to the 3.22 series. only to find out that they dont work for my phone. based on this post
"You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY." -crypysmoker-
[THUNK AND FIXED] Rooting Mytouch Fender LE 32a/ Mytouch 1.2 DONT!!
http:/forum.xda-developers.com/showthread.php?t=622530
So now im thinking great i didnt catch that so let me just move back to where i was before. using the last section of that previous thread to install the stock radio and spl. i have done this already and know it works. so i install the stock radio and spl and the custom recovery. Boot up into recovery and restore nandroid. everything is going ok utill.....it locks up in a boot loop. i then boot back up into recovery and erase data. after that i tryed another nandroid restore and to my wonderful surprise i now lost the ability to mount the sdcard. i restarted and tryed many different cards and all failed. I then boot up into hboot restore with the goldcard and it then locks up at system.
Great now im looking for something to fix this whole mess. after that i try to reinstall the original spl and radio. I then have an error "signature verify failed." Now im thinking WTF!!!!!
I then find a thread about the RUU and how to turn off "S-on" if i install this official HTC app. However come to find out its the asia version. WONDERFUL FOR ME!!! I then found the Official T-mobile MT3G RUU, installed it and now i have a fastboot installed with a memchip with a red circle around it, not the 3 skate droids, and cant boot into HBOOT ,with the volume down button. All that i see is "RUU USB." I have adb but now get the error "remote not allowed." it used to be "signature verify failed." i have no recovery, no HBOOT, just fast boot with RUU USB.
How to i fix this mess up and get back to this?
T-Mobile MyTouch 3g Fender Edition Stock ROM with ROOT!
http:/forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
This is what i have and show
Sapphire pvt 32a ship s-on G
Hboot-1.33.0013 (sapp31000)
cpld-13
radio-2.22.23.02
oct 21 2009,22:33:27
RUU USB
This is definitely a snowball effect right here.
Oh also i cant go and exchange the MT3g fender because im past my 14 days and i already did it on the first day. LOL
I actually am stuck on the same screen with the same phone. I hope someone has been able to get this fixed
Damn, not trying to be mean, but you screwed up a lot.
I have the same version device as you, and I upgraded my radio/SPL. and did a lot of stuff, i semi-bricked it, but i got it working again. I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Try following this theunlockr[DOT]com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The problem is that the phone is stuck in a bit of an interesting state. You can't flash from an RUU at this point because the engineering SPL used to root the phone is version 2.53.x, while the RUU's ROM is 2.10.x. You also cannot flash any images to the phone because the SPL is locked (S-ON). So the only way to fix the phone at this point would be to somehow get an HTC-signed 2.53+ ROM for the SAPP31000 (mytouch 3g 1.2/fender) or find a way to unlock the SPL. I had a nice chat with some of the Modaco guys and we went through a lot of options with none of them working. The phone's basically in a bit of a chicken vs. egg state. So personally, I will be building a serial cable to manually unlock the SPL so that I can flash images back on manually.
So, while I wish it was as easy as just re-flashing the phone, you can't do that with a locked SPL and no HBOOT mode available. Onward to a serial/TTL cable advendure!
Once I get the parts in to build it, I'll follow up here with my results
shintokun said:
I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Click to expand...
Click to collapse
Ok. So I have a Rogers Dream. I rooted it and flashed to cyan froyo. All was well. Long story short I need to send the phone back to rogers. I tried the first unrooting procedure I found and am stuck now. I tried the Dream/G1 unrooting method. I am now stuck with a T-Mobile G1 bootloader and cannot load any images from here.
I have spent the last 2 days seraching every rogers unrooting thread I could find with no success.
I am looking to get back to the rogers 911 update so I can send the phone back.
I hate to post when i'm sure it has been covered. But any help would be awesome. Any info you need I can provide asap
Sounds like you tried to install a T-Mobile ROM in a Rogers phone. You would have to use a gold card to make that work, but you would be left with a tmo branded phone. Try searching Rogers' site for their latest full ruu, probably the one with the 911 patch.
I have that. But I need to be able to boot up fully to run that. I have the t-mobile bootloader.. and thats it
You will need to reflash the T-Mobile rom with a goldcard until it will boot, root it via telnet after signing into Google (via a wifi hack?) then install 1.33.2003 spl, that will let you use fastboot to install 1.33.2005 and thus the rogers rom.
Hope the defect isn't going to interfere with this..
Ok. Now I just read a procedure on creating a gold card. This requires a running phone? This phone.. does not run. I can get into the bootloader and thats about all.
You can see if you can boot and wipe from recovery. If then android boots you may be able to skip the gold card.
However you are I assume stuck on HBOOT-0.95.0000
If you download the rogers nbh, rename it to DREAIMG.nbh, place it on the root of your SD and try to flash by turning the phone on holding camera, you will likely receive an error (if not it will flash the Rogers rom)
If you get the error you will need to flash rc29 the only DREAIMG.nbh known to work, the problem is its signed for the us T-Mobile region and you have a phone for the rogers Canada region.. the way to skip the region check is you make a goldcard and use that to flash the nbh.
This requires you to know the Cid of an SD card.. and the easiest way to find that is a working android / winmo phone (does not need to be the broken phone, you can make the goldcard on a friends phone and use it in yours). This is because most USB sdcard readers don't provide access to the cid.
With the goldcard you can try to flash rc29 again, hopefully boot android, root it like a T-Mobile phone, reinstall (carefully) dangerspl allowing you to at last safely flash the rogers rom.
Short of time travel and preventing your past self from installing a T-Mobile stock rom on a Rogers phone.. I'm short on alternative ideas.
I am stuck with HBOOT-1.33.0009
The RC29 DREAIMG.nbh wont flash.
skylinegts said:
I am stuck with HBOOT-1.33.0009
The RC29 DREAIMG.nbh wont flash.
Click to expand...
Click to collapse
That is not the T-Mobile bootloader.. that is an older rogers one (and other HTC branded dreams)
And here is the rogers unroot instructions
http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
And on the topic what isn't working that you are thinking the phone requires to be returned?
that worked! thanks!