Related
after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!
......
noone?????
The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)
Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...
Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .
i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck
There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL
It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?
another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL
When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.
I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.
The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!
Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.
It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.
Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."
The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!
Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.
Hi you guys!
I hope you can help me...
Had a Magic with:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0014 (SAP10000)
CPLD-12
RADIO-3.22.23.18
Sep 2 2009,17:42:56
I tried to change my Perfected SPL by following the "How To: Root Your MyTouch 3G (GoldCard Method)" from The Unlockr, since others methods didn't work for my Perfected SPL! I updated to 1.33.2010, it was the only SappIMG that worked, and followed the goldcard-method to the end.
Problem:
When I turn on my phone, the HTC screen loads, the new Android logo appears, and I get “SIM card is locked”.. I type in my normal Pin-code, and immedealy after gets a “Sorry! Process system is not responding”-message! I can choose between: Force Close & Wait, but under that window another window is open. It says: "Sorry! The process android.process.media has stopped unexpectedly. Please try again". No matter what I press or do it reboots over and over again, but always gives me those "Sorry!" screens!
I am desperate, because I was so close for making my phone Rooted, so I could install a Hero ROM!
What should I do? Is there a way to go directly on loading a ROM now, or a way to get a working phone? Please help me!
- Martin
so try and take the sim lock of the card and when its install put sim lock back on
I think something has given me other clues!
I tried to take out my SD-card (not the Gold-card), and I was able skip the activation and get to my Home-screen!
I tried to plug in my SD-card while having it turned on, and it accepted the SD-card. However, when i try to use camera/video/loading music from the SD card, i get a "Sorry! process com.android.camera etc" note.
I am not able to plug in the SD-card before booting the phone. I tried to plug in my Goldcard, start the phone, and it worked. But the notificationbar told me it was destroyed, as expected!
Well, I have got a rooted phone, with half of my apps not working! I was going to install a hero ROM! Could I install that directly now?
TheUnlockr says in "How to load a custom ROM/Hero ROM" that: This method requires that you used OUR super easy 1 click method of rooting on your MyTouch or G1 BEFORE doing this procedure!
Does that mean I should unroot - root - and load a Hero ROM?
hey, how did u skip the registration?...i dont have service anymore but i still want to use the phone for other things..thank you in advance
SOLVED!
Everything is solved!
For those interested:
I took out my SD-card, and I was able skip the activation just by pushing SKIP all the way to my Home-screen!
I tried to plug in my SD-card while having it turned on, and it accepted the SD-card. I couldn't get on to my Google Account and I thought it would be best to get back to cupcake 1.5 - then root - and then load a rom!
Downloaded the "RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver" and got it back to cupcake by pluging out my SD card. I got the same problems on the homescreen - forceclosing programs and no Google account login. Market won't load without Google Account and I needed a file explorer to be able to work with flash recovery. Sent the Linda.apk to my mail, went on WIFI, downloaded it, extracted, and followed the rest of TheUnlockrs guides to get a Hero ROM! IT ROCKS, FINALLY FREEDOM!
bg80018: I am afraid that I didn't do anything clever except for pluging out my SDcard! When it was in there was nothing I could do.. I am not an expert, but perhaps another clean install of your ROM would help? (experts, stop me if i am wrong ) well, I will check the next week if anyone needs questions answered, otherwise I am going to play with my phone for the rest of my life now!
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.
another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.
cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.
@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.
cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)
cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18
Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.
Thanks a lot!
That solved it.
Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.
So i hope this is the right place to ask. I updated the radio to 6.xx and the spl to 1.33.0013 and now i cant boot my custom rom or access the recovery screen, but i can access fastboot. Ive tryed flashing a new radio, recovery etc from the sdk cmd promt and no luck, keeps saying remote: not allow. IS there anything i can do from the fastboot to get my phone back. Sorry if this is realy noobish. Ive searched for 3 days and i've had no luck. PLEASE HELP ME
Sapphire pvt 32a sip s-on g
hboot-1.33.0013 (sapp31000)
CPLD-13
Radio-6.35.10.18
oct 21 2009,22:33:27
You are ok untill now..You have not bricked your phone....you can still recover it using fast boot or recovery...
serach for the correct topic on this fourm...you will surely get info
Ive tryed everything in fastboot and i cant get into recovery. If i could i would have fixed it by now
Tried Goldcard method as well?
I cant do a goldcard again. I cant access the operating system. I cant access the recovery screen. Al i can do is access fastboot. And from there i just get remote: not allow when i try to modify things. I just need a BIG reset button on this phone. Im hitting my head so hard against the wall trying to figure this out. I try to read up but everywhere you go its something different and its all soooooooo confusing. No one makes nay sense
If this is a bad place to ask this, please tell me. My head hurts and im very frustrated because i followed someones write up step by step and i got screwed over. I know it can be fixed!
OK dude, just breathe. By looking at your SPL you've got the myTouch 1.2 (the one with the 3.5mm jack) so you've got o use the goldcard method which is done through hboot and fastboot, if you can get one you can get the other. Let me get to a computer and we'll fix your problem. In the mean time post back and let me know your still here.
Sent from my HTC Magic using XDA App
You need to fastboot an engineering spl first.
I believe 1.33.2010 should do it.
Flash back to the operator's ROM and start all over again; safest approach if you are having a difficult time understanding how to troublshoot your problem.
I try to load a new sippimg.img ( from my understanding that a new spl) And everytime i load it, it says model id wrong and fails to load.
And in fast boot i cant load anything new cause i get the remote: not allow.
How am i suppose to create a gold card another gold card without having access to the phones main operating system?
I just went to http://forum.xda-developers.com/showthread.php?t=529019 and followed that and wasnt able to load the recovery image cause because remote: not allow. So im stuck
Try using this.
Sent from my HTC Magic using XDA App
I cant create a new gold card, i cant access the phone I created one before but it still gives me a the wrong mode ID code. And i cant do adb because i cant turn on USB debugging since i cant access the phone.
I followed the steps in the link. I loaded the sappimg.img and it loaded it but didnt ask to confirm the install, but it did show a loading bar and when it was completed it never said anything about restarting or anything. It just detected it, loaded it and then nothing. So after that i tryed to load the spl, radio and recovery and it still gave me remote: not allow.
It seems my gold card somehow undid its self. I need to figure out how to make one without being able to access the actual phone options. I realy do appreciate you guys helping!!!! If this gets fixed ill kiss all of you. JK!
How long have you had your phone?
3 days But i didnt buy through t-mobile, so no warranty for me
The only other option I can think of is to see if a friend with the same phone can let you borrow his. Luckily the stuff you need to do isn't phone specific, it's only specific to the SD card, so you can remake it with another phone and then use it to finish your's.
I believe the CID that you get (that ridiculously long number you have to copy) is specific to the SD card. I just swapped the goldcard I made for my phone into my wife's and the CID remained the same. Just not sure if using a different model phone will work.
You don't happen to have the CID still do you?
DonJuan692006 said:
The only other option I can think of is to see if a friend with the same phone can let you borrow his. Luckily the stuff you need to do isn't phone specific, it's only specific to the SD card, so you can remake it with another phone and then use it to finish your's.
I believe the CID that you get (that ridiculously long number you have to copy) is specific to the SD card. I just swapped the goldcard I made for my phone into my wife's and the CID remained the same. Just not sure if using a different model phone will work.
You don't happen to have the CID still do you?
Click to expand...
Click to collapse
I still have all the emails for when i originally made a gold card and the goldcard.img.
You can try doing the steps in Hex Editor, where you copy the lines from the goldcard image over to your SD card again. Then try flashing the sappimg again and see what you get.
On it! :cross fingers:
I did all the Hex editor stuff. And i still get Wong model ID when i try to install a new sappimg.img. I tried several times and double checked the hex editor.
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!