Bricked G4 Wizard... - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Hey guys...I believe my G4 device is bricked yet still recoverable.
I was flashing the htc 8125 update today to my wizard from the vanilla WM6 ROM. (Yes I want to go back to originial WM5).
I'm still quite new to this whole flashing scene, but that's besides the point.
I tried using the EXE of this ROM:
RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe
and after that didn't work I believed that maybe I should try using shelltool, which I used for the Vanilla WM6 ROM.
It went for about 35 minutes...then I decided to pull the cable. Shelltool said it completed the flash..so I hard reset the device. It didn't get past the cingular splash screen.
Only until later did I start believing that this was a G3 only ROM.
I'm still unsure whether it was g3 or g4, but my device is a G4.
I believe i can still get into bootloader(the 3 color screen I believe it is), but can't connect to the USB to flash any other ROM, or so I believe.
When I plug in the USB the device shows that it is connected, yet the computer doesn't do anything.
I have no idea, i've been searching google, searching XDA with google, maybe just not using the right words.
the device
SPL/SPL is 2.25.0001
GSM 02.25.11
OS(Believe it is displaying the OS it was supposed to be AFTER flash): 2.25.11.1
Can anyone direct me down the right path?
EDIT:WOOPS....WRONG FORUM..
Totally didn't see the specific G4 forum

figured it out myself on accident.
Thanks for everyone's help!

Related

8125 ROM Upgrade Problems

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.

Another one bites the dust....

Well after months of flashing successfully I have finally managed to brick my phone. Totally bricked. Won't power on, no lights, nada. Dead as. And I can't think how I managed to achieve it!
I'd been having problems getting my bluetooth GPS receiver working, and after having no luck with any of the WM6 ROMS I decided to go back to the original T-Mobile ROM. I have a G3 device and I can't remember the IPL/SPL settings now but it was Olip unlocked and I'd been flashing whatever ROM I liked for months. I always had problems with using the update tools and had to use the RUU_MUN tool - this was the only one that ever worked for me.
I thought I'd be fine with downgrading - just a case of flashing the old ROM, but even the RUU_MUN tool failed me on that one - just kept saying the image I was using was invalid or something, even in bootloader mode. So I decided to go back to button ROM and then up again. Got button ROM on OK, but then after that I couldn't flash anything else, couldn't boot into bootloader or anything. I thought a hard reset would cure it. No. I took the battery out and it has never worked since - no lights no reset nothing. I've used a meter to test the battery and it's almost fully charged. I've taken the battery out for a couple of hours and then put back in, nothing.
It's totally dead. Really annoyed with myself for not understanding as much as I thought I did.
curlsaloud said:
Well after months of flashing successfully I have finally managed to brick my phone. Totally bricked. Won't power on, no lights, nada. Dead as. And I can't think how I managed to achieve it!
I'd been having problems getting my GPS receiver working, and after having no luck with any of the WM5 ROMS I decided to go back to the original T-Mobile ROM. I have a G3 device and I can't remember the IPL/SPL settings now but it was Olip unlocked and I'd been flashing whatever ROM I liked for months. I always had problems with using the update tools and had to use the RUU_MUN tool - this was the only one that ever worked for me.
I thought I'd be fine with downgrading - just a case of flashing the old ROM, but even the RUU_MUN tool failed me on that one - just kept saying the image I was using was invalid or something, even in bootloader mode. So I decided to go back to button ROM and then up again. Got button ROM on OK, but then after that I couldn't flash anything else, couldn't boot into bootloader or anything. I thought a hard reset would cure it. No. I took the battery out and it has never worked since - no lights no reset nothing. I've used a meter to test the battery and it's almost fully charged. I've taken the battery out for a couple of hours and then put back in, nothing.
It's totally dead. Really annoyed with myself for not understanding as much as I thought I did.
Click to expand...
Click to collapse
Its a clear cut case of misunderstanding ,Are you sure it was A G3 device ? whereas ! I believe it must be a G4,thats why you applied it with HardSPL patched IPL 2.21.0001 and SPL 2.21.olip. You kept on flashing new Wm6 Roms,coz,due to the HardSPL,as new wm6 Roms don't include any IPL/SPL in them,they are safe for G4 devices.
Well,in the same misunderstanding,thinking it to be a G3 device,you flashed 'Button's Rom' which includes IPL/SPL meant for a G3 device to your G4 phone.....
"BRICK"
zabardast_1 said:
Its a clear cut case of misunderstanding ,Are you sure it was A G3 device ? whereas ! I believe it must be a G4,thats why you applied it with HardSPL patched IPL 2.21.0001 and SPL 2.21.olip. You kept on flashing new Wm6 Roms,coz,due to the HardSPL,as new wm6 Roms don't include any IPL/SPL in them,they are safe for G4 devices.
Well,in the same misunderstanding,thinking it to be a G3 device,you flashed 'Button's Rom' which includes IPL/SPL meant for a G3 device to your G4 phone.....
"BRICK"
Click to expand...
Click to collapse
Pretty sure it was a G3 - the IPL/SPL numbers were something like 2.26 not 2.26.000x. Seems irrelevent now I have a doorstop for a phone
curlsaloud said:
Pretty sure it was a G3 - the IPL/SPL numbers were something like 2.26 not 2.26.000x. Seems irrelevent now I have a doorstop for a phone
Click to expand...
Click to collapse
Anyhow ! I don't understand the fact that how come flashing Button's cud Brick a G3 device ? YES ! its certain that if flashed to a G4,it'll Brick,but never heard a G3 getting Bricked by Button's or there might be some other Hardware failure the phone is dead,can't say about it !
Why did you say it had IPL/SPL 'olip' something in your first post ?
Anyways ! you are the better judge of your phone
This'll teach me for not making decent notes. You're quite right I did indeed have a G4 device and I've made a juvenille schoolboy type error of flashing a G3 ROM. I feel really stupid. I've only just found my sketchy notes from when I unlocked it - it was 6 months ago so I kind of forgot. Ooops. What a noob. Oh well, I'll have to get a new phone now
curlsaloud said:
This'll teach me for not making decent notes. You're quite right I did indeed have a G4 device and I've made a juvenille schoolboy type error of flashing a G3 ROM. I feel really stupid. I've only just found my sketchy notes from when I unlocked it - it was 6 months ago so I kind of forgot. Ooops. What a noob. Oh well, I'll have to get a new phone now
Click to expand...
Click to collapse
Well,learned the lesson Hard way !!!
Yes indeed. Never flash a ROM when you're not sure what you're doing

8125 bootloader stuck

ok, im inbetween a newb and a full out destructive force to any type of moddable device and im having a little bit of trouble with my cingular 8125. ive had this phone for a few months and i am having the hardest time dealing with the rom on the phone now. ill give a quick breifing on it:
got it with original cingular rom, not sure what spl or ipl on it but the first thing i did was unlock it by myself, cid and sim unlocked, and then updated to a jaguar wm 6.1 rom which worked fine. decided i was going to unfortunately sell this phone so i decided to upgrade it one more time to see if i really wanted to sell it, i then bought the upgrade to go past my 2.21 ipl and spl. i got my unlocker and followed my instructions and got a brick. but not a full brick. its stuck in the bootloader screen. after reading countless threads, i learned that i should be able to just still update a rom to the phone with no problems which actually works, but as soon as a rom completes it goes right back to my bootloader screen so help me! please cuz now thats its a challenge again, i want the phone! plus all my info is on the phone still back up
Flash the official stock ROM first, then use Button's ROM to downgrade your IPL and SPL before unlocking CID.
post the present IPL/SPL it displays now.Which rom you are trying to flash now ?
ok when i try to put the most current 8125 rom on my phone (2.25.blah) it tells me that its not the same phone which is weird but thats preventing me from putting the original rom on the phone. however if i try and put the buton rom on the phone now, it will go through completely and say it put it on the phone, but when it restart, its right back to the bootload screen...
and im running IPL 2.21.0001 and SPL 2.21 with a previous installation of a jaguar rom, dont know exactly which one, but i know it was a jaguar rom. but right before i tried to upgrade the updater, i went back to my default WM5 rom so i guess it was te basic 2.21 rom on the phone with WM5
dimedash12 said:
ok when i try to put the most current 8125 rom on my phone (2.25.blah) it tells me that its not the same phone which is weird but thats preventing me from putting the original rom on the phone. however if i try and put the buton rom on the phone now, it will go through completely and say it put it on the phone, but when it restart, its right back to the bootload screen...
and im running IPL 2.21.0001 and SPL 2.21 with a previous installation of a jaguar rom, dont know exactly which one, but i know it was a jaguar rom. but right before i tried to upgrade the updater, i went back to my default WM5 rom so i guess it was te basic 2.21 rom on the phone with WM5
Click to expand...
Click to collapse
WEIRD !
You got mixed Bootloaders of G3 And G4,IPL 2.21.0001 is G4 and SPL 2.21 is G3,as you posted,well,can't say which was original,only you can tell,but some how its mixed Bootloaders,in this situation no Rom will flash,its a 'Brick'.
If as Zabardast says its bricked then you have three options:
1. Get a new Wizard
2. Get a new Wizard Motherboard
3. Get a Wizard with broken LCD from eBay and replace its LCD with your current one and Enjoy!!! (Cheapest)
lol this is tough! but no worries, ill be back with some other pda at some point and time and then ill try and take this phone apart! but the weird thing about my wizard is that this only happened when i tried to update the phone with the CID unlock program that you have to pay for!
lol it was perfectly fine until i tried to do it! oh well, back to my crappy p168!
May be that CID Unlock program was not meant to be for a G3 and you were updating a G3 so it mixed you IPL/SPL and caused a kinda BRICK. So please be careful before doing flashing things because if you dont be carefull then your PPC may become a heavy paper weight, and a costy one too. LOL. TC
kitty4uhig said:
Farming for eq2 plat isn't easy, but you can buy eq2 plat, guides, accounts & items on sale. We have revolutionized the exchange of money to eq2 plat. Purchase eq2 plat& power up your character ot the next level. Our world class customer service will make sure you are more than satisfied with every purchase. Feel free to contact our 24 hour live support with any questions you may have. Shop now and play as a VIP!
Click to expand...
Click to collapse
Stop this nonsense immediately,otherwise it'll be reported and you'll be banned.Its spam !!!
try this: http://forum.xda-developers.com/showthread.php?t=276963
Cingular 8125 problems
Ok guys i am really pissed i have been looking for three days and cant find it, first off my IPL is at 1.01 and the SPL is at 2.25 and i cant fix it i wanted to install the original 2.25 again and start from scratch but can not find the damn thing so if anyone has it can u just upload it fo me and give me a link that i can get it at please i am sick and tired of waitnin i really like this phone and i dont want to risk bricking it thanks.
Ok, grimgod, aggression is reaaaallly ugly and no freakin one will help with that sh!t attitude (pardon the language, mods). The senior members do everything they can to help the noobs. Have you tried reading the flashing guide, wiki, or tutorial? I'd bet even money you haven't. Have you CID unlocked? Did you flash the button rom twice ( as the guide suggested to get ipl/spl both 2.xx)? Did you flash the official tmo rom (found im the flashing guide)? Have you done anything other than sit on your hands and wait for it to be handed to you? READ AND SEARCH!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=310831 <HERE!!!!!!!!!! Should I flash your device, too?
Similar issue... need some Wizard Expertise
I picked up a coworkers old Cingular 8125 that he'd had in a drawer for about a year. Battery was right dead so the phone wouldn't boot. I charged the battery on an external charger for a few minutes, put it back into the phone, and plugged it in to the charger until the LED went green indicating a full charge.
When I power up I see the T-Mobile splash screen (light gray background, some square dots, and the "T-Mobile" logo). And there it stays indefinitely.
Tried a hard reset (Comm Mgr + Voice Cmd + Soft Reset), and it said "Press Send to restore factory default". Pressed the green dialer key (I assume that's send), and it says Format FAT partition, FAT partition complete, and then returns to the same T-Mobile splash screen and hangs there.
So then I tried putting it into Boot Loader manually (Power On + Camera). No problem, shows IPL 2.26 and SPL 2.26. Plug it into the computer USB port (running XP Pro), and then the USB connection shows on the phone. Attempted to flash the Wizard Love ROM to get this thing back to square-one. Error 260. Attempted to flash the T-Mobile stock ROM. Error 260.
Between each flash attempt, I'm pulling the battery out and starting fresh. I think I've followed all the steps I'm finding in multiple threads. But for some reason I'm not able to get this thing to communicate via USB. All RUU's give an Error 260. Am I missing something?
Forgot to mention I'm following the steps outlined in this thread from Dr P. To the letter!
Also did a little reading up on using the MTTY method in this thread by Drug_Store. Thought maybe the existing ROM might be intact, and I might be able get it to a 256MB MiniSD, then write the backup ROM from SD in boot loader. Well, for some reason I don't even see the USB connection option when I use the MTTY - can't ever get to a point where I can issue commands. Again, I think I'm following the instruction. But still no juice.
Nudge, nudge. I'd donate for a solution that works... otherwise I have to keep letting my 10 year old play The Quest on my phone.

Do I have a bricked Wizard??

Hi, I was trying to flash/upgrade my Wizard to WM6.1 (was able to do it once over the weekend). But got over-confident and was trying to do it second time (ofcourse use some other cooked rom) but during the upgrade, my kid pulled out the wire from the computer.
If that was not enough, in a panic mode, i actuall did a reset on the wizard. Now it wont even start (no lights light up nor I get the 3 color screen = bootloader.).
The time when my kid pulled up the USB cable, I was "upgrading" to 2.26 after having successully downgraded to 1.xx ..
I fear I have bricked my wizard...is there anything I can try before having to spend 40-50 buck and get to cell repair estimate? I tried hard-reset (Camera + Power On), (Green + Red button + Power), Communication Button + Voice Button + Power but nothing happens.....
Sorry but i guess your Wizard is a brick, the only solution is that you get a new motherboard or a new Wizard. Feel Sorry to say that but still dont go on my advice let some other senior member say something too. Maybe there is a way i dont know and anybody else does.
did you have a full battery?do you think your battery drained through the process?try charging the battery in some other way or try another battery...if that doesn't do the trick....you need a new motherboard.....
G3 phones are very stubborn devices,its very hard to 'Brick' it ! They don't get Bricked in this way ,unless you really do stupid thing and flash a Rom with G4 IPL/SPL.
Here,you have a dead battery,just try to charge it fully ,somehow, or borrow another battery from a friend,or if you prefer,buy a new one,as it comes with little charge to start and boot up the phone and even sometimes flash a rom.
Apart from this,I don't believe its Bricked,G3 doesn't get bricked like that,by being interrupted in the middle of flashing or resetting it.
zabardast i think he was upgrading the bootloader...that kills it right?
xardas_90 said:
zabardast i think he was upgrading the bootloader...that kills it right?
Click to expand...
Click to collapse
What I believe he means he was upgrading to IPL/SPL 2.26 by flashing T-mobile,after downgrading to 1.xx by Button's Rom,while flashing,it got interrupted and in panic he reset the device,now can't power Up the device.
Well,interrupted during flash or resetting doesn't brick a phone.
secondly,Bootloaders IPL/SPL are automatically downgraded/upgraded by flashing a Rom with IPL/SPL when flashed.
Unless,as I posted above, if he has flashed G4 IPL/SPL or a G4 Rom with IPL/SPL,it wud certainly brick a G3 device.But as he said he was upgrading to 2.26,means,he was flashing T-mobile,so I believe,it cannot be bricked this way
OOOPS!
On second thought,did he mention its a G3,well,what if its a G4!!!
and he flashed Button's Rom............. GONER!
I assumed its a G3,coz he posted ipl/spl 1.xx and 2.26 and he already got it upgraded.
hi thanks for all the info.
Before the upgrade I verified it have more than 60% battery (arround 80%). I had got a new battery and charged it 100% overnight before i tried the first upgrade.
Its a G3 phone (It showed 2.2x a did not have following .000 which show for G4).
I had downgraded using the Button ROM and was upgrading the rom using WST write ROM.
So is there still a chance..
I can try and see if anyone's got a HTC Wizard within my friends/around and try to charge the battery in their phone....just to make sure its fully charged
try this. http://forum.xda-developers.com/showthread.php?t=276963
I have repair my wizard with this manual.
zabardast_1 said:
OOOPS!
On second thought,did he mention its a G3,well,what if its a G4!!!
and he flashed Button's Rom............. GONER!
I assumed its a G3,coz he posted ipl/spl 1.xx and 2.26 and he already got it upgraded.
Click to expand...
Click to collapse
I wonderfully and utterly stupidly did exactly that !!! I wrote a G4 rom on G3 Wizard !! It turned on once after the procedure and wm6 loaded all the "extras" and then re-booted... into complete darkness !! Now it's completely dead nothing turns on, not even the green charging light. I left it for a couple of months and the red light come on briefly... but that's all. Now it stops the papers from flying off my desk .... it's my funeral and I'll cry if I want to (
I honestly feel sry for it,but may I ask which was the rom which you say is G4,which you flashed ? coz all official roms are suitable to flash to both devices and custom build roms do not contain IPL/SPL in them,which cud harm any device,its really questionable as which was this rom which bricked a G3 phone,if you are sure your phone is a G3. YES! its certain that if a G4 phone is flashed with a G3 specific rom,it'll get bricked,was your G3 or G4 ?
zabardast_1 said:
I honestly feel sry for it,but may I ask which was the rom which you say is G4,which you flashed ? coz all official roms are suitable to flash to both devices and custom build roms do not contain IPL/SPL in them,which cud harm any device,its really questionable as which was this rom which bricked a G3 phone,if you are sure your phone is a G3. YES! its certain that if a G4 phone is flashed with a G3 specific rom,it'll get bricked,was your G3 or G4 ?
Click to expand...
Click to collapse
I confirm my Wizard is a G3 device and the rom I accidentally wrote over it was a G4 rom (I since deleted it from my computer to ensure I would not repeat the mistake) ....
So, there are G4 specific ROMs floating around out there? Now that doesnt make a whole lotta sense. I thought that all carrier ROMs where G3 (and to an extent G4 safe), and that all cooked ROMs where G3 and G4 safe because they dont contain IPL/SPL?
ashasaur said:
So, there are G4 specific ROMs floating around out there? Now that doesnt make a whole lotta sense. I thought that all carrier ROMs where G3 (and to an extent G4 safe), and that all cooked ROMs where G3 and G4 safe because they dont contain IPL/SPL?
Click to expand...
Click to collapse
After G4 came out, the providers started releasing ROM packages with two bootloaders and a new RUU that would detect the device DOC generation and flash accordingly. If you extract an 'official' ROM you'll find IPL_1, SPL_1, IPL_2, SPL_2, etc... which means G3 and G4 respectively and therefore safe to flash to any Wizard in the market (minding the CID status of course)
As for G4 only roms i believe that might be a few around that were cooked in a time when the "G4 safe" concept wasn't yet implemented and when one would flash a complete ROM and upgrade IPL/SPL at the same time.
Nowadays, since Wizard official development has ended, almost everyone has a 'high' bootloader and only needs to change the OS version/flavor thus the absence of IPL/SPL in a released cooked ROM
Hope it's clear
cheers
mestrini said:
After G4 came out, the providers started releasing ROM packages with two bootloaders and a new RUU that would detect the device DOC generation and flash accordingly. If you extract an 'official' ROM you'll find IPL_1, SPL_1, IPL_2, SPL_2, etc... which means G3 and G4 respectively and therefore safe to flash to any Wizard in the market (minding the CID status of course)
As for G4 only roms i believe that might be a few around that were cooked in a time when the "G4 safe" concept wasn't yet implemented and when one would flash a complete ROM and upgrade IPL/SPL at the same time.
Nowadays, since Wizard official development has ended, almost everyone has a 'high' bootloader and only needs to change the OS version/flavor thus the absence of IPL/SPL in a released cooked ROM
Hope it's clear
cheers
Click to expand...
Click to collapse
This, however does not solve my "totally dead" G3 Wizard, I suppose it must go to a service lab after all.....
Simply
gizmofan777 said:
This, however does not solve my "totally dead" G3 Wizard, I suppose it must go to a service lab after all.....
Click to expand...
Click to collapse
Does your wizard starts? YES- it can enter to bootloader? Yes - its not bricked...
Does your wizard starts? NO- Maybe a dead battery... Does your wizard shut off and conected to the wall charger shows a Led RED? this two are......
BRICKED PHONE!!!!!
Thats all...
+ Que PPC said:
Does your wizard starts? YES- it can enter to bootloader? Yes - its not bricked...
Does your wizard starts? NO- Maybe a dead battery... Does your wizard shut off and conected to the wall charger shows a Led RED? this two are......
BRICKED PHONE!!!!!
Thats all...
Click to expand...
Click to collapse
Battery OK, red light briefly once then never again, no other activity - patient is brain dead.... it's "el bricko phone" !!
Bricko Phone?????????
gizmofan777 said:
Battery OK, red light briefly once then never again, no other activity - patient is brain dead.... it's "el bricko phone" !!
Click to expand...
Click to collapse
Hahahaha "A silence minute for it's soul please"
Father, embrace with your arms this soul of a dead wizard and let it rest in peace in the Pocket Heaven Amen.
More Respect please HAHAHAHA
what a funny men!!!!
I bricked my phone too!
Hi there! I think I have the same problem. My phone is a G4 and it won't boot to bootloader mode nor charge in a wall charger. I had my phone unloacked and during the process, my phone shut down. Now it's dead. Is there a go around for this problem? Thanks.
Hey Guys,
I've got a similar thing, think I might have flashed a G4 file to a G3 Wizard.
I have, by following through the "Let's Revive A Wizard" thread (http://forum.xda-developers.com/showthread.php?t=274766) been able to get the thing to boot into the bootloader screen and show IPL 1.05 : SPL 2.26.clip I think from memory and then flashed the 02 ROM but then it just boots back to the bootloader.
I also tried an SD backup from my other G3 and followed that through but nothing.
I think there is a way to revive using the methods shown, but there appears to be no more help relating to it and I'm out of ideas myself.
If anyone has a IPL & SPL file for 2.26 can they post it for me to try.
Thanks.
Ian

Wizard stuck on three-colour screen IPL/SPL after attempt to unlock

I have a wizard (wiza110) running wm5 and i wanted to upgrade it. It was the first time i was trying such thing. I was following these instructions http://wiki.xda-developers.com/index.php?pagename=Wizard%20Windows%20Mobile%206%20for%20newbies. My device is g3. My first attempt was with Button Rom, everything was fine until 99%... i think it was error 302 or something. I took off the battery and plugged it again several times but nothing came out. I had the three-colour screen.
Then I tried The Xda_MiniS_LaunchROM_v154102.exe, still nothing, lokiwiz also...
Last attempt was with wizard Love. USB appears but the ruu can't see the device and stops the process
Any ideas?
i think the device was sim-unlocked...
Flash back to the original rom, charge the battery to 100%. Make a guest connection to windows and start reading this thread from the beginning
do you have a link for the original rom? the thing is that ipl is 1.05 and spl is 2.25
aposperitis said:
do you have a link for the original rom? the thing is that ipl is 1.05 and spl is 2.25
Click to expand...
Click to collapse
Based on my experience and what I've read here, I'm guessing that your original rom had ipl and spl both 2.25. When you installed the button rom, it updated the ipl but nothing else. Just a guess, but that's what happened to me the first time on my G3. I just re-flashed button rom and continued from there. You should try to find the original rom for whatever kind of phone you have (I mean, the rom from the service provider like Orange, AT&T, etc). Their latest rom might not be 2.25. For example, my phone originally came from T-Mobile. I have the T-Mobile rom that is I think 2.26. I keep it handy, but have only reflashed back to that rom once when my extended rom got messed up.
Read the link suggested above. Good stuff. It is possible to flash a phone that is stuck on the tri-color screen, but it might not work the first try.
Same thing here, just youre getting further
I have ipl and spl on 2.26 received it this way. It's G3. I've been a week looking through the forums. Trying to avoid posting here. But damn it. I can't seem to get anything right. I previously had the G1 and Juno, Flashing was a breeze. But here i feel lost.
Basically my problem is i can't get it to downgrade. upgrade. CID unlock, With neither Lokiwiz or WST. A pain. And really NO RUU runs past the 0% it reboots my phone to boot loader image and USB shows but it reads that it can't find my phone anymore. It's been charged to 100%. Deleted TEMP folder. Was guest under activesync. Changed my USB cables 10 times. It's frustrating. Please. Any suggestions??

Categories

Resources