Related
Hi,
I'm kinda stuck here and maybe someone know what I'm missing here.
I downloaded the 2.8.7.102 WWE Rom and installed it without any problems. I used aWizard to backup the OS and reverted back to the Qtek_9100_RUU_Prodigy_10107105_Qtek_WWE Rom and modified the Extended_ROM to my likings. I tried to use aWizard to restore the 2.8.7.102 OS for several times now (without problems or errors) but it always hangs at the splashscreen so I have to restore a RUU Rom again to get my device to boot again.
What am I doing wrong?
Is what I want possible?
Thanks in advance on any help
Cheers,
Cacti
le_cactus said:
Hi,
I'm kinda stuck here and maybe someone know what I'm missing here.
I downloaded the 2.8.7.102 WWE Rom and installed it without any problems. I used aWizard to backup the OS and reverted back to the Qtek_9100_RUU_Prodigy_10107105_Qtek_WWE Rom and modified the Extended_ROM to my likings. I tried to use aWizard to restore the 2.8.7.102 OS for several times now (without problems or errors) but it always hangs at the splashscreen so I have to restore a RUU Rom again to get my device to boot again.
What am I doing wrong?
Is what I want possible?
Thanks in advance on any help
Cheers,
Cacti
Click to expand...
Click to collapse
I have tested what you want to do in my Wizard and success without any problem.
Please make sure you have unlock CID using 'u' and enabel RAPI using 'e' option.
Hey Cactus,
Did you get an error while flashing your device or is it when you are restarting it after flashing?
Have seen it with mine that during the first steps of the flash I got this error but when I flashed it on another computer everything went fine.
Cheers,
Drifter
Drifter dude!!! Whazup
No errors when I run the RUU Rom and no errors when I use aWizard. But it hangs at the splash screen.
I did enable RAPI and I CID unlocked it also (although I'm sure you only need to do that once) but still no go. I reverted back to the RUU_Prodigy_1060204_105_11210_TMO_UK_Ship OS.
I can't stand that it's not working so I ran the RUU with the test ROM again and used aWizard to extract the OS rom again. You never know, it may have gone wrong the first time, but still no go. I was able to restore it's Radio Rom fine but not the OS part. Bummer!
Oh well, seems I need to be patient and wait till someone figures out how to unlock the locked Extended_ROM from newer roms.
Cheers
Cacti
le_cactus said:
Hi,
I'm kinda stuck here and maybe someone know what I'm missing here.
I downloaded the 2.8.7.102 WWE Rom and installed it without any problems. I used aWizard to backup the OS and reverted back to the Qtek_9100_RUU_Prodigy_10107105_Qtek_WWE Rom and modified the Extended_ROM to my likings. I tried to use aWizard to restore the 2.8.7.102 OS for several times now (without problems or errors) but it always hangs at the splashscreen so I have to restore a RUU Rom again to get my device to boot again.
What am I doing wrong?
Is what I want possible?
Thanks in advance on any help
Cheers,
Cacti
Click to expand...
Click to collapse
sorry you're having problems. The silver lining is that you can revert back from the 2.8.7.102 rom. Now, I feel comfortable trying 2.8.7.102, since i can go back.
Sorry Cactus, cant help you with this one.
If you have removed CID and simlock you shouldn't have any problems updating the firmware.
Did you try the update with another computer with a clean ActiveSync?
Someone else with a suggestion about this problem?
How do I delete this post?!
* UPDATE: Either I'm just really tired or I am going blind. I fixed my problem, but now I cant seem to be able to find a way to delete this post...
I got my Cingular 8125 about a week ago, it's been a dream! I LOVE THIS THING!
Tonight I decided to update the ROM. I got it with 1.8 or something really old like that so I thought updating would be a good idea. I went to the HTC site an downloaded the latest ROM (2.25).
As I am a mac user, I fired up the old PC and updated. But before I did, I installed SPB Backup on the 8125 and backed everything up to my miniSD. Update went fine. Worked like a charm. I went to restore my files and thats where it all went to hell!!!
I made the mistake of restoring ALL of my files and settings. It seemed fine when it was done. the 8125 asked for my password, and as I finished typing it in, the 8125 rebooted without notice. The Cingular screen came up, loaded fine. Then the Windows Pocket PC screen came up and then the top bar with icons came up. That was it. Now it just sits there, nothing else loads. I can put it on stand by. But nothing else happens. No today screen, no phone, no signal, nothing.
I tried to connect it back to my PC but ActiveSync cant mount it. I tried the Wizard ROM update installer, but it said that the device couldn't be found. I tried connecting it to my Mac with Missing Sync. It asked for a password, which it has never done before (which seemed promising) but after I typed it in, again, no device was found.
Now the poor thing is just sitting there on my desk
Is there anything I can do to get it up and running again? Is there a way I can get one of my machines to recognize it and wipe it clean so I can start fresh???
Please help! I bought this phone refurbished, so I dont know if I will be able to get it replaced. Any help would be greatly appreciated!!!
Was this device CID unlocked? Did you try going to the bootloader mode (Hold camera down and press reset while holding camera button, rainbow screen should appear) and then flashing it with your desire ROM?
If it still don't work, you might need an SD backup image of a rom. I've been trying to look for one but the only think I found is an image of a dutch language ROM. If I do get one I'll give you a PM.
Clem
clemsyn said:
Was this device CID unlocked? Did you try going to the bootloader mode (Hold camera down and press reset while holding camera button, rainbow screen should appear) and then flashing it with your desire ROM?
If it still don't work, you might need an SD backup image of a rom. I've been trying to look for one but the only think I found is an image of a dutch language ROM. If I do get one I'll give you a PM.
Clem
Click to expand...
Click to collapse
Hey thanks Clem! I did solve my problem, but now I have a new one. I HATE 2.25!!!
So if you do get your hands on an older ROM, I would be forever greatful!
Thanks for responding!
Here is the link for the 1.8 Cingular ROM
ftp://xda:[email protected]/Wizard/Roms/Cingular/Cingular_RUU_1.8.11.1.WWE.ship.exe
I hope this works for you.
You think you can save that 2.25 image to your SD card coz I've been looking for an SD image this is ths instructions...that is if you don't mind.
ftp://xda:[email protected]/Wizard/DumpROM/How_to_DumpROM.txt
and here are the files needed
ftp://xda:[email protected]/Wizard/DumpROM/ntrw_189.exe
ftp://xda:[email protected]/Wizard/DumpROM/psdread.exe
ftp://xda:[email protected]/Wizard/DumpROM/romupdate_115.exe
This will also create you a backup of 2.25.
Thanks
clemsyn said:
Here is the link for the 1.8 Cingular ROM
ftp://xda:[email protected]/Wizard/Roms/Cingular/Cingular_RUU_1.8.11.1.WWE.ship.exe
I hope this works for you.
You think you can save that 2.25 image to your SD card coz I've been looking for an SD image this is ths instructions...that is if you don't mind.
ftp://xda:[email protected]/Wizard/DumpROM/How_to_DumpROM.txt
and here are the files needed
ftp://xda:[email protected]/Wizard/DumpROM/ntrw_189.exe
ftp://xda:[email protected]/Wizard/DumpROM/psdread.exe
ftp://xda:[email protected]/Wizard/DumpROM/romupdate_115.exe
This will also create you a backup of 2.25.
Thanks
Click to expand...
Click to collapse
THANKS CLEMSYN! I'll give them a try! YOU ROCK!
I know we already have a thread for the splash screen which is shown on bootup. Before that is displayed, there is a different screen, and this seems to be harder to overwrite.
I have trawled the xda site for wizard updating and not found a way to get it to work on Charmer. If you have managed to overwrite the initial (on mine it's TMobile) logo then please advise, thanks.
Me too in the same boat. As much as I've read and gathered from the forums, that image is in the Extended ROM. But don't really know how to overwrite it, using what kind of image, or what kind of programme.
Advice, someone???
Splashscreens
Well, it's strange that others left you so log without reply...
Easy solution:
1) download http://rapidshare.com/files/30404684/splash.zip.html
2) unzip
3) create splash.bmp, 320 height 240 width
4) flash it...
enjoy.
Didn't work for me
Thanks for this. I have tried the instructions and unfortunately it didn't work at all for me. I get an error as follows:
hm, looks like error
try to run enablerapi.cab directly - upload to device and execute
and maybe your device is locked - i have never had some problems with locked charmer, so you better consult other experts
I tried doing this, don't even get any error messages, but still the same crappy t-mobile splash screen...
dunno what to do..
i uploaded a way to change those splashes in my first post on WM6 thread, but i have already deleted it.
Hello,
I've tried to update my phone using the shelltool method and my phone crashed during the update.
Now it can't boot. it's freezed on the splash screen.
I've tried to put the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE rom and it does nothing.
I have a G3 device, the IPL/SPL is now 1.01
Thanks in advance for your help
Flash back to official carrier ROM.
I have already tried using the bootloader method. it tells me that the device is not compatible
Try it doing the storage card method.
I also tried and it tells me I don't have the right
Before the first update, I have made a backup of the OS ROM but the file format is NBA. Is there a solution to reuse my original ROM?
In Addition to the SD method, the bootloader is password protected
Try reflashing the ROM you were flashing in the first post using the RUU in bootloader mode. You shouldn't need to use the shelltool to flash that one. Then when you get that flashed on there do your CID unlock. After that you should be able to flash any ROM you want.
I've tried tu put Button's ROM using the RUU in bootloader mode and its still blocked
Try flashing the wizard love rom then. I'm not sure where it is at the moment, but you can find it on here somewhere.
I also tried this ROM
I have made some research.
At the beginning (when my first upgrade crashed) someone on a chat told me to do a doctest.
No the problem is that the memory is damaged.
When I try a hard reset, I have the message "format is failed"
Any idea?
You've got me on this one, I don't think I've run across anyone else ever having this problem. By the way, did you remove any miniSD card that you had in the phone before flashing? Having one in there while flashing tends to cause people problems.
Also, I just realized that you said that you used sheeltool to flash the first time when you flashed the button rom and that it changed your IPL/SPL to 1.01. Flashing using shelltool won't change your IPL/SPL, it skips those files if they are added to a rom since they are the files that will destroy a G4 device. So, if it did change them then that's where you did something wrong. Why don't you start over and explain exactly what you did on the first flash with the button rom and see if we can't figure it out from there.
OK I'll explain from the beginning
Before beginning the flash, I have made a backup of the ROMs (OS, Radio and Ext) with aWizard.
I wanted to put a french WM6 ROM. In the the tuto, it was told to use shelltool to do this. For an unknown reason, the phone crashed. So I had to reboot the phone because it was freezed and after this point it did'nt boot.
I went on a chat to get help and someone told me to start the bootloader and with mtty enter the command doctest (I think he's a joker becose today I saw this command is very dangerous).
When I saw this command doesn't work I discovered this forum and tried 2 of the 3 methods to unbrick a phone in the wiki.
I can't use the SD one because the boot loader is password protected.
I also discovered today that the IMEI number doesn't correspond to the label on the phone.
Here is my story .
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
raskell said:
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
Click to expand...
Click to collapse
I'can't use imei check because my imei is invalid
Why do you think your IMEI is invalid? If the only reason is that it shows a different one on the box than it shows in aWizard or whatever program you're using, don't worry about it because that seems to happen quite a bit. Usually it's because it got put in the wrong box. Anyway, you're in luck, I have a program that I believe I downloaded off of XDA which is a version of the IMEI-checks unlocker with the master unlocker code for all wizards.
Well, I was going to upload that tool for you but after trying 6 times to upload it and it failing each time I figured that maybe I should wait a little bit and try again later.
I think the IMEI is different because the one given from imei-checks is different from the one on the label back the battery.
Also, when I tried to order an UNL file with the IMEI given by the unlocker, they told me its a wrong number
Lets try this again.
Still failing to upload. I'm not sure why, but I'll try yet again later.
I sent you in PM the address of my ftp server
I am new to completely flashing a custom ROM. I've been trying to flash a new ROM on my tilt, with the latest AT&T updates(ROM 1.62.502.0 Radio 1.27.14.09). Each time I try to flash a custom ROM I get Error 262 Update Error. The progress bar never gets past 0%. I've tried multiple PCs and tried reinstalling ActiveSync. Am I missing something, or do I have to do something first before being able to flash the new ROM?
Any help is greatly appreciated!
Steve
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
I am about 100% sure you searched, didn't you?
Here, baby boy, let me spoon feed you and you can ask your mommy if she can whipe your drool:
http://www.digwin.com/view/schaps-wm6-pro-roms-update-error-262
bapssystupr3m3 said:
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
Click to expand...
Click to collapse
I have searched the forums over the past week or so. The solutions suggested such as soft reset, hard reset, reinstall activesync, switch USB ports, etc have not done anything. I also came across this thread:
http://forum.xda-developers.com/showthread.php?t=370205
which would suggest that I there is an incompatibility. I was hoping someone could point me in the direction of which radio version etc I would need to update to in order to update to a WM 6.1 ROM.
edit:yes I have run CID unlock.
Steve
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
_Alex_ said:
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
Click to expand...
Click to collapse
Thanks Alex! Tri-Color mode worked!
Steve
My error 262 fixed
I don't know if this is the best place to put this, but I didn't want to open a new thread.
I too had been getting repeated error 262. And I spent a couple of hours searching for answers, and while there have been many questions raised on this subject, there have been few clear solutions (and certainly none that worked for me).
I have the HTC branded Kaiser installing from Vista. (By the way I am new to this, but as I had such a hard time working this out, I thought I should at least post what worked for me.) I unlocked the CID with pof's Hard-spl v1 tool. Then (as I want to stay with Mobile 6.1) I upgraded the hard spl to v3.28 by JockyW. I then downloaded a number of Roms I wanted to try. That is where the trouble started.
Each ROM I tried would get past the tri-color screen with no problem. Then it would hang at the 0% until finally showing the error 262. A soft reset would reload my previous rom unchanged. I tried many things: removing all USB's, firewall, virus protection, hard reset, reboot windows, every suggestion I could find (and understand).
While the hard spl I had should have worked, I thought I should try version 3.29. When trying to upgrade to that I had a similar problem with error 260 this time. Looking over spl update instructions I realized I had forgotten to uncheck "disable usb connections" in "Activesync" at the proper stage. Once that was unchecked, the new spl loaded. After that I was able to load the cooked roms with no problem.
It appears there was something wrong with the HardSPL v3.28 I was using or in how I installed it. The tricolor screen was showing 3.28. In any case, after I reinstalled a new hard spl (this time 3.29), I had no more error 262.
A bit long-winded, but hopefully this might help someone else.