Related
Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Drunknasty said:
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Click to expand...
Click to collapse
if your device is G3, unlocking is required to flash any rom, before upgrade your device, it is recommended to flash an official WM5.0 rom (in your case T-Mobile rom) with IPL and SPL 2.xx then flash again.
in general there are many probabilities for your issue.
((Where is TNT1.1?? did you mean 1.0?? ))
My Bad meant 1.0
So to get it straight.... I will need to unlock my phone each time?
Oh and to correct myself again, when flashing with the T-mobile ROM it says UPGRADE ONLY. And the read me file says its the wrong RUU. But it is the same file from Tmobile I used when I first got the phone. But I will try again.
Are there any other suggestions?
You need to read the "how to flash" sticky.
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Try another ROM.
Sounds like you need the "Wizard Love" rom. I dont have the link handy but I am sure someone else does.
Drunknasty said:
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Click to expand...
Click to collapse
Already got it. Thanks I am trying to load it now. But the only thing is that the last time it failed and I can understand what the error says. I know the number is 300 but can read the language.
But I will let you guys know when this load completes.
Thanks again for all the assistance.
No worky worky. The load completed and then boots the splash screen shows and then stays there.
Any ideas?
Try to remove the battery and let it out for at least half an hour. Then put it back in and see what it does then.
I thought the same thing too. So when it got done last night, out of frustration, I removed the battery and left it there to wait on when I get off work today. I will report back on what happens.
Again I would like to thank you guys for helping me. I really do appreciate it!
STEP 1 install the original manufacturer ROM
T-mobile UK
http://www.tm-phonedownloads.com/download_manager_mda_vario.html
T-mobile US
http://www.t-mobile.com/wmupgrade/
Search for the original rom for any other
instructions on how to use the original rom can be found here
http://support.t-mobile.com/knowbase/root/public/tm23294.htm?&A2L.SERVICE=AboutUpgrading
Put it in the bootloader mode.. ( three color screens )
hope this helps..
cheers
Praneet
Ok I did that and it gave me ERROR 296: UPGRADE ONLY
Then it tells me that the NBF file cannot be used for my PDA Phone. Please get newer NBF file.
Is there any way I can get the Tmobile splash and IPL\SPL number back to original, it doesnt need to boot all the way into WCE but atleast show the same numbers and splash during boot up?
Or any other way to get this thing to work?
Thanks guys
BTW it is a HTC Wizard from T-mobile.
If you are getting an error 300 you need a newer rom update utility, and regardless if your phone is a G3 or G4 it needs to be unlocked before you flash any rom.. LOAD a OFFICIAL cingular ROM onto your device before going any further, then unlock your phone either via www.imei-check.com or through some of the tools offered here...
Which one should I down load from Cingular? Even though I have a Tmobile phone?
what ipl and spl are you using and what radio are you using. Just post all the numbers from the bootloader
As soon as I get home, I will post them.
Thanks
Ipl 1.01
Spl 3.08
Thanks
Drunknasty said:
Ipl 1.01
Spl 3.08
Thanks
Click to expand...
Click to collapse
uh oh. someone tell me if I'm wrong, but I think this is bad. it's the result of flashing a g4 with g3 or the other way around... keep searching, and good luck.
flash the original t-mobile rom. your phone doesn't appear to be unlocked. good luck
Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Hi,
Please consider a new battery.
As strange as it may sound, one of my MDA Pro's had similar symptoms with battery at 70%. Replacing the battery with a new one fixed it right away.
The symptoms were:
- less network signal
- random turning off of radio
- could not access phone settings
- radio crash when trying GPRS connection
Also, on my other MDA Pro, I had problems like this, but they were caused by radio ROM 1.18. I changed to 1.15 and everything is fine since.
It seems that aging batteries are a major problem for weird issues. Just buy a new one at ebay and dont start flashing as a fool, cause you can risk a brick.
Cheers,
vma
My battery is actually new... just bought it 2 weeks ago.. and I tried the phone with both my new and old batt. still no luck -_-
I can't flash any radio rom now... is my Uni certified dead?
Any help would be great.. thanks
Try charging the battery first in another universal if possible, if battery is ok, put it in and try again, read Wiki and check if you can go to boot loader mode, check whether pc recognising the Uni once on etc.,
Read everything and the computer recognised my Uni ... tried MTTY tools to reset all the DOC partition in my Uni yet no way to reflash my radio rom again
I think as long as PC is recognising, dont consider it as DEAD. Its very much alive and keep hopes.
as I read through this forum, Radio ROM flashing is the most risky thing and often takes longer.
If you are not already considering, try only flashing radio rom and do not club with extrom etc, try redownloading the ROM or try a different version from a different link, unless you are particular about the one you are trying.
Always use the original USB cable supplied with the Uni.
Enter BootLoader mode by pressing and holding the power button and backlight button whilst performing a reset with the stylus. Connect Unit to PC to the USB port directly and not through a USB HUB.
Start flash again..
All the best
ronaldphl said:
Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Click to expand...
Click to collapse
From the problem behavior it seems your device got GSM locked, I'm afraid it's permanent. But at least try ...
1. Remove the SIM card
2. Must upgrade the bootloaded to 1.01 if it's a G3 (and not upgraded already).
3. Run the Buzz's CID unlocker tool and flash the radio (version 0.00) provided with the tool.
4. Do the HR and check the status
First of all please be gentle! I am a complete novice and this is my first post. I have a Touch Pro on a Vodafone contract. I downloaded the recent ROM software upgrade from the Vodafone web site and began the transfer to my phone having followed all the advice. However, the download got stuck at 12% and no matter how many times I start over again it will not go past that point. Worst still the phone is now locked on a red/green/blue/white screen with the message "Upgrade ROM code error Please try again". the error message on the Vodafone software download is No 302. I have tried Vodafone technical help but as I was due for a new phone anyway they have sent me a Touch Pro 2 but don't seem to want to help me resolving the problem with my "old" phone. It is only 5 months old (replacement insurance phone) and in good condition but useless if it can't be made to work.
Can anyone help with simple instructions on how to download a ROM that will work. If not does anyone want to make me an offer for the phone? Currently locked on Vodafone but I am sure you guys out there have the skill to resolve that one.
Many thanks,
Hollybeau
So, they aren't asking you to send it back, I take it? If that's the case, then the first thing I would try would be to flash with the stock rom, if you can find it (not the upgrade that quit on you). If that doesn't work, then just try to flash hard spl. If hard spl goes through ok, you're golden and can flash any raphael rom you want. If it doesn't, the phone is probably toast. You got a new one, so just use the old one as artwork.
Thanks Farmer Ted,
Unfortunately I do not know the orginal stock ROM. It is not on the Vodafone web site and the HTC site keeps telling me that all the likely candidates are "not suitable" ( I assume this is beacuse it is some sort of Vodafone variant). I am afraid that "flash hardspl" means nothing to me - I told you I was a novice! Can you direct me to what and where please.
What bugs me is that here is a phone worth £200? but for a problem caused by Vodafone's buggy software upgrade.
Hollybeau
Start Here.
Best way to find everything you want to know about flashing ROMs.
Lol.
Hard SPL is a bootloader that allows you to flash any rom you want (not just vodaphone). It also has over-write protection, so if you get into the situation you're currently in, the phone won't be bricked. If you can flash it (make sure you flash the gsm version in the raph rom forum), you are fine and dandy.
If you can't find the stock rom online, you may be able to flash the upgraded rom off of your sd card (I believe this will work with a stock rom and stock spl, but am not 100% sure). Re-name the .nbh image file to RAPHIMG.nbh. Format your sd card (1-2 gb works best) to FAT32, and put the image on the root of the card. Go into bootloader (well, you're already there, you may not need to) by holding volume down and soft resetting. Hold vol. down until the tri-color screen appears. At the prompt, press the power button, and let the flash run its course. Soft reset when it says that the update was a success. Let the phone boot up until it gets to the the alignment screen, the hard reset and boot it up.
If you don't have an .nbh file, and instead have a .exe file from vodaphone/htc, then you should be able to extract the contents with either winrar or 7-zip (google) to get at the .nbh image file. I've done this before, and it works fine.
Many thanks to all who have replied. I have fixed the problem. It turns out that it was the download to my PC that was at fault. I downloaded the Vodafone software to my lap top and ran it from there and it has recovered the phone. I now have a spare, and working, Touch Pro. I may try the HardSPL and other ROMS just to use the phone as a test bed. Alternatively, anyone out there want to make me an offer?
Hollybeau
Hollybeau said:
Alternatively, anyone out there want to make me an offer?
Click to expand...
Click to collapse
Ask in market place and you will probably get some takers
WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.