Related
Hey guys, before anything please let me thank you for this amazing site. You have made a complete n00b to a power-user in 2 days flat. Please do allow me to tell you my story. 2 Days ago I got this thing called O2 XDA IIs (HTC Blueangel) and I got it for around 300US$ (Unlocked/New) was not so fond of Windows devices so intended to sell it off asap and get some other phone, was just doing a little R&D on the net to see what all is available for this thing. When I came across to your site, here's when I got so intregued by the capabilities of this thing.
First I intalled the latest ROM for my device, after getting little confidence I installed WM5 with my fingers crossed. Its all done now but have a few things to ask you guys.
1. When you mentioned about the EXTROM you said that you'll have to copy the files on the StorageCard\ExtRom when all I did was copy nk.nbf into the folder called WM5_Pack_V3 and ran the installer. I did run the batch file to get the oper_code from the DeviceData file. It was all done, I was really scared but now am worried did I do the right thing?
The Device Information TAB shows
ROM Version : 5.03.02WWE
ROM Date : 03/02/05
Radio Version : 1.12.00
Protocol Ver : 1337.42
ExtRom Ver : TuMa v1.3
2. It took me long enough to install this what all tweaks should I do to it so that it stays at the maximum bug-free current stage. (Hope you get me)
3. I need the starting screen to display something other then those scary 3 colored lines
Some things that I noticed after upgrading:
1. WM5 It's a little slow, but definately much better looking and show-off value.
2. I have a Wi-Fi enabled ADSL router at home by which I connect the O2 and other devices its working fine on.
Any help/suggestions/comments are welcome.
A brief intro for me would be have worked as a beta tester for many symbian application providers, was a complete S60 geek and am majorly into bikes & bike photography
Nothing said yet?
Im not sure I understand that whole Extrom deal, but what I can say is that the files that were in the extrom folder inside the upgrade pack must be put in the storage card in the same folder, but that is only if you want MMS and have a camera, if not, then there is nothing to do, unless you edit the Cfg.txt to load all your apps and settings after a hard reset. I guess that if you are able to use the device, you did everything ok as far as the flashing goes. it is a little slow, but its come a long way from the first versions, those were slow as hell, thanks to Mamaich and Tuatara and everyone else this version is running great!
as for the 3 color bar start up screen, there is nothing you can do about it...
Yeah I really forgot to thank Mamaich and Tuatara for their awesome work, now I am really scared as I dont like the slow response and am unable to downgrade. ActiveSync shuts down whenever I try to run the MaUpgradenoID.exe file activesync stops and it is giving errors in connecting, gets DC frequently. And moreover the Manufacturer supplied upgrade is also not working it gives a CountryCode error. Am really confused and scared now what to do?
Well I did not get any help but with loads of tinkering I got the thing done, I wanted to know why was WM5 so slow, otherwise the interface is loads better then the current CE I am using.
I have the Cingular version SX66 Blue Angel. I was able to update it without any problems. Usually speed is very different with those who flush the registry and with those who don't. Make sure you flush your registry after you completed the update.
Mine is faster and way more stable than the other version I had on it. Remember to follow all instructions exactly. if there is a link you need to check and make sure you do the format, change the ram size on the device, then upgrade.
There are no instructions on how to flush the registry can you enlighten me on this?
manav said:
There are no instructions on how to flush the registry can you enlighten me on this?
Click to expand...
Click to collapse
During the flashing process, the wiki instructs the user to do a hard reset
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM5_HardReset
You should answer NO, YES, YES to the boot questions.
Hmm yeah, I did do that. And just am in the process of downgrading from the buggy WM5. It doesn't work out for me.
and THAT'S where I got problems!
in the manual, it says I have to download my latest favorite ROM version, and FROM that file i should copy the nk.nbf the "DOWNGRADE TO WM2003SE" folder..and that's what seems impossible to me, since the Rom-update i downloaded is an .exe application, and not a .zip or .rar archive..
so how should i get the nk.nbf file out of the Rom-update .exe file..?
help
well some were in the same documentaion it should also say use rar or zip to unpack it (being the exe file).
Pls spend some time in wiki you might find some other answers
yeah i had tried that already back then butthat didn't work either..when i try that it still just starts running the program.. :?
Try these instructions with your exe file:
http://forum.xda-developers.com/viewtopic.php?p=233903#233903
I recently attempted to update the ROM in my Cingular 8125. The process stopped at 95% and I received an "Internal Error". Now, when I turn on the phone, it gets as far as the color RUU screen, and nothing else.
How can I find out if I can repair this situation myself or if I need to take it back to Cingular.
Hopefully you'll give Cingular a little more info regarding this than you gave us.
My psychic advisor is STILL on vacation so I can be of very little help to you, sorry!
What ROM were you running before and what ROM were you trying to flash it with? Did you CID unlock before you flashed?
Sorry - When I posted the 1st message, I was in a hurry...
I am not sure what ROM version was on the device before I attempted to update (I know, I should have paid attention, but I was not). The phone was new from Cingular and I had not done anything else to it besides load a couple of apps (Skype & Agile).
I attempted to run the file RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe that I downloaded from the HTC site. The update go to 95% and I received the error "ERROR [326]: INVALID COMMAND" - This NBF file cannot be used for your PDA Phone. Please check your NBF file." (I have attached a screenshot of the error to this post).
I am not sure what to do at this point.
Thanks,
Chris
Some folks at the Cingular forum are having the same issue with no solution offered.
I'd suggest putting the device into bootloader mode (Holding Record and Camera buttons while soft reseting) and then reflashing. Make sure not to launch any programs while flashing. I also don't touch the device at all as I've noticed the USB connection might slightly disconnect.
Good luck and let us know what happens.
I just tried reloading from the bootloader screen - no luck. Exact same error at 95%. Would it work to try to reload an original earlier ROM? If so, how would I go about trying that?
Chris
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I have re-downloaded the ROM file from the Cingular site (actually it just redirects to the HTC site). Same problem. I cannot get to the point to even shut down any programs because the phone OS does not even load at this point. When I do a soft reset, I get the following (sorry for the blurry image - as you can see my good phone with the good camera is dead...)
I had a similar problem. I posted the fix on another thread and ppl said i was wrong, this wasnt it...but heres what worked for me.
Are you using a usb port on the front of the computer? if so, try pluggin into the ports on the back of your computer. I tried flashing the official rom from cingular a few times using front port and it stopped at the exact same % each time. got the same thing as you, colored bars.
Someone had mentioned to me that front usb ports don't work as well as back ones. give it a try. good luck
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Thanks to everyone for their input. From the suggestions above, I have tried various USB ports on my laptop and I always get to the same point. I have also called HTC tech support and they are pretty sure I have bricked my phone. I talked to Cingular and they have agreed to replace it. I have also researched the G4 chip issues (looked at the post: http://forum.xda-developers.com/viewtopic.php?t=56408).
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
xtreme23 said:
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Click to expand...
Click to collapse
I second this observation! :shock:
This makes a major difference on wether or not you can even upgrade.
Search for G4 issues.
The .0001 in the IPS/SPL number will tell you which one you have.
The way I understand it is:
2.25 - G3
2.25.0001 - G4
I think this is the proper way to identify it.
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Chris, LokiwizMSL ( http://forum.xda-developers.com/viewtopic.php?t=50768 ) can SIM Unlock your device. Be sure to read the instructions.
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
slapper said:
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
Click to expand...
Click to collapse
If you installed an unofficial ROM then they are correct. You should never admit that you used a ROM that was not provided by HTC.
There are warnings all over this site about VOIDing your warranty.
Since you used the Official Update they are wrong.
Same problem with official Cingular 8125 ROM
I tried to flash the official Cingular ROM from the HTC site here:
http://www.htcamerica.net/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
I got the same error at 95%:
"Error [326]: INVALID COMMAND This NBF file cannot be used for your PDA Phone. Please check your NBF file."
When I reset the phone I get the RGB bootloader screen and nothing else.
My phone is a G4 and was running ROM version 2.25.11.1 WWE before. The reason I tried to apply this ROM is because there was apparently no Extended ROM. None of the customization cabs executed on a hard reset. Also, in Device Information, there was no "ExtROM" listed.
This is the second phone that this has happened on. I thought the first time was just a fluke thing and I had a bad phone. But now I think there is an issue with this ROM.
Anyone have any idea what is going on here with this ROM? Does the fact that there was no Extended ROM have anything to do with this ROM not flashing properly?
Is there anything else to try or do I need to try to return the phone (AGAIN)?
how to fix the problem
read this thread carefully. The upgrade problem seems to be occuring on G4 chipped Wizards with the most current IPL/SPL.
http://forum.xda-developers.com/viewtopic.php?t=56088
take the official update. run it, when it finishes extracting look for the extracted NBF file in your
C:\Documents and Settings\yourusernamehere\Local Settings\Temp\the newest directory just made
find the NK.NBF file
extract it using the tutorial in the post above you will be flashing with the official cingular components sans IPL/SPL.
flash it and your are back up and running
I would have posted this earlier but i had to make sure it worked and was repeatable.
I think the problem with the new update is the new IPL/SPL version checking. It seems that if the patcher sees the same version already running it will give you that error at 95%. I've seen it on 3 phones already and I have been able to fix them by doing what i've told you above. You are already in bootloader mode and your phone is ready to accept a new rom anyways. My solution may not be the best for your phone and take no responsibilites but you are already desperate and need a fix. Good Luck!
Thanks for the reply, evilito. Since I hadn't gotten any replies for a few days, I decided to go ahead and try to exchange the phone at the Cingular store. They were baffled that this was the second phone I had returned for the exact same problem, but gave me a new phone anyway. I wish now that I had waited so that I could try evilito's solution to see if it works. As it is now, I am too scared to try any flashing on this new phone after my results with the first two. I would really hate to have to try to return a third phone
Can anyone else verify that there is a problem with the latest Cingular ROM when flashing a G4? Or did I really have two bad phones?
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Thats good to know, I thought that when we unlocked it and updated the ROM we lost Warentee Support. Where can you get the official Cingular 2.25 ROM. I am still on 2.17.
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
I am super new to this. I have 2 att tilts I followed a guide on this site and flashed them both to windows 6.5. both seemed to be working fine. My wifes had no sound though. So I searched and realized hers had an older radio than mine. I followed another guide here to update her radio. (I picked the same one as mine 1.65.21.18) I tried the sim card first and nothing happened so I tried it via sync. It got to 99% and errored. I followed the on screen commands and the second time I got 0% and errored. Now the phone is stuck in the multi color boot screen and nothing I do fixes it. I have tried searching and cant fix it. I dont know what mtty is. Please help!!!
fragnbastich said:
I am super new to this. I have 2 att tilts I followed a guide on this site and flashed them both to windows 6.5. both seemed to be working fine. My wifes had no sound though. So I searched and realized hers had an older radio than mine. I followed another guide here to update her radio. (I picked the same one as mine 1.65.21.18) I tried the sim card first and nothing happened so I tried it via sync. It got to 99% and errored. I followed the on screen commands and the second time I got 0% and errored. Now the phone is stuck in the multi color boot screen and nothing I do fixes it. I have tried searching and cant fix it. I dont know what mtty is. Please help!!!
Click to expand...
Click to collapse
to fixing bricked kaisers with MTTY commands looks at http://forum.xda-developers.com/showthread.php?t=371154&page=5
Thanks. I'll check this out.
Once again it says run mtty. What is mtty? is it a program? if so can I get a link? i googled mtty and there is a download but im afraid it might be a virus so if anybody here has a safe link id appreciate it...
fragnbastich said:
Once again it says run mtty. What is mtty? is it a program? if so can I get a link? i googled mtty and there is a download but im afraid it might be a virus so if anybody here has a safe link id appreciate it...
Click to expand...
Click to collapse
MTTY is a program command ....here use it
Thanks for the program, when I open it and go to usb and type command boot i get
Cmd>boot
Command error !!!
I also have ruunbh in top corner I followed the link on the tutorial to download an original kaiser rom but there were none....
ok I typed
set 16 0
then
task 8
My phone rebooted to windows 6.5 but still has wrong radio. I am afraid to try and change radio. is there a link to a step by step procedure that works. did i pick the wrong radio?
TPC_Kaiser_Titanium_Ultimate_28002 is rom
Kaiser_Radio_only_1.65.21.18 is the radio that i tried to do last time...
r-1.27.14.09 is radio it has now...
http://blog.contriving.net/2009/06/18/upgrading-your-att-tilt-to-windows-mobile-6-5-tutorial/
is the tutorial i followed to flash rom. I am not sure if i installed Hard SPL i followed that tutorial. I did jumpspl 1.56...
fragnbastich said:
ok I typed
set 16 0
then
task 8
My phone rebooted to windows 6.5 but still has wrong radio. I am afraid to try and change radio. is there a link to a step by step procedure that works. did i pick the wrong radio?
TPC_Kaiser_Titanium_Ultimate_28002 is rom
Kaiser_Radio_only_1.65.21.18 is the radio that i tried to do last time...
r-1.27.14.09 is radio it has now...
http://blog.contriving.net/2009/06/18/upgrading-your-att-tilt-to-windows-mobile-6-5-tutorial/
is the tutorial i followed to flash rom. I am not sure if i installed Hard SPL i followed that tutorial. I did jumpspl 1.56...
Click to expand...
Click to collapse
If you are not sure how to use MTTY, please don't use it. This is a powerful tool and if its not used correctly you can definitely bricked your device. Try to read first of what you do.
I have spent hours reading and searching posts the last couple of days. If you have a helpful answer for me feel free to post it! I followed the tuorials exactly. Not to mention I already DID USE MTTY and it worked! Now I need to change the radio... All I need to know is if I need to run hard spl first or jump spl? The tutorial I followed just had me run jump....
PS. I don't need to become an expert I am only updating to sell these phones on ebay. You get more for them with windows 6.5. Once I get them working I am selling them and will never use these tools again. I switched from ATT to Virginusa and an android phone...
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks