Help with my P4351 - Wing, P4350 ROM development

Hello friends, I need your help, to be trying
P4351 upgrade my cable took off from there, it is
nailed to the first screen (not the system starts
OS), just let me enter the Tricolor screen,
I tried many roms (both P4350, P4351 as)
with officials, as cooked, and give me error, with
the original Sell tells me Invalid ID, and the
The rom cooked tells me is corrupted, being that before
allow me to update with any rom.
My IPL is 4.24.0002
My SPL is 4.14.0000
For more information: my phone was bought in Paraguay.
I've tested with the official rom T-Mobile.
Anyone can help me?
thanks.

matuzalen said:
Hello friends, I need your help, to be trying
P4351 upgrade my cable took off from there, it is
nailed to the first screen (not the system starts
OS), just let me enter the Tricolor screen,
I tried many roms (both P4350, P4351 as)
with officials, as cooked, and give me error, with
the original Sell tells me Invalid ID, and the
The rom cooked tells me is corrupted, being that before
allow me to update with any rom.
My IPL is 4.24.0002
My SPL is 4.14.0000
For more information: my phone was bought in Paraguay.
I've tested with the official rom T-Mobile.
Anyone can help me?
thanks.
Click to expand...
Click to collapse
Oki, maybe i can help you.
Did your DROP your phone recently?
cause that's what happened to me, and it broke my camera button. so my device was forced to go to the bootloader screen (aka RGB screen).

mrbayn said:
Oki, maybe i can help you.
Did your DROP your phone recently?
cause that's what happened to me, and it broke my camera button. so my device was forced to go to the bootloader screen (aka RGB screen).
Click to expand...
Click to collapse
No, not been dropped, the problem arose because I took the
cable during the update.

Okay. On the RGB screen plug in your usb and run then run this:
http://www.mediafire.com/?yj1oz2m3mzm
Let me know how it does from here. If this works then i'll guide you the rest of the way.

I have tried with the file that I've been, but still
jumping the same error, ERROR [294] invalid vender ID, the update runs to the 1% and the phone is restarted and returned to the initial state.
Also thank you very much for your help!

First thing - Is your phone a Herald?
Because my last bit of advice was for the Wing..
Try to find your original ROM for your device.
The service provider that you have your cell pone through should have that stock ROM/Update.
Then make sure you're at the RGB screen when running the stock ROM.

Tribulattifather said:
First thing - Is your phone a Herald?
Because my last bit of advice was for the Wing..
Try to find your original ROM for your device.
The service provider that you have your cell pone through should have that stock ROM/Update.
Then make sure you're at the RGB screen when running the stock ROM.
Click to expand...
Click to collapse
Hi friend, my phone is Herald (HERA110), and it's runing on the screen RGB

1) Download THIS.
2) Flash with the above while on the RGB screen.
3) Run the HardSPL package.
4) Get back to RGB screen.
5) Flash any custom ROM for your device
^>^

I tried and nothing happened, I digue giving the same error, and
Phone will not start, and do not know what else to do, because I
the steps you give me the bottom of the letter or even so
does not work. You may no longer serve?

Related

MDA_C hangs at 99% ce rom upgrade and splash screen

Hi all,
Have purchased a German MDA_C and flashed it to the latest dutch WWE rom (1.13). I use the NOID updater and get an error message at 99% of the update.
After this my MDA hangs at the splash screen (but showing updated rom and radio versions).
Doing a lot of soft and hard resets I managed to get by the splash screen 1 time...
Tried a lot of different rom versions but each time I get the same problem
I've read that the SPLASH screen problem is more or less common but I wasn't able to find a solution on the forum.
Now I made one stupid mistake... I did not backup the original rom...
Any suggestions how to get up and running?
Thanks in advance...
BuDDaH
The very first boot takes a long time, 15 mins for some! If you're not waiting for around 15 mins ....
Thanks for this valuable information kta.
This time I waited 1 hour after upgrading just to be sure.
same result. flashing stops at 99% of the CE Rom.
Hard reset shows splash screen with version numbers (radio 1.13 rom 1.13 wwe) and then just hangs.
From bad to worse
So I had a MDA_C that did not boot further than the splash screen.
Updated using the MaUpgradeUt_noID.exe. Thought I'd give the SD way a try since I already tried about 6 different roms all with the same result.
First I made a backup to SD card of what was in my MDA using romupdate.exe
extracted the file to my HD.
After extracting (and securing the device ID) I tried rebooting my MDA.
Now things got worse!!! instead of the splashscreen I now have the BLACK SCREEN......
Have tried resetting and hard resetting dozens of times (more like a thousand times) and only occasionaly the splash screen comes up. :roll:
But over the last couple of days I only managed to get the bootloader 1 time (and at that time there was no SD card inside) :shock:
this is behaviour I haven't read about on the forum.
Guess I will have to get it serviced.
Is there anyone on the board that has an address in the Netherlands that can flash or repair my mda? Not sure T-Mobile NL services German devices...
Thanks!
Not dead yet?
Here's some more info.
My 'almost dead' Magician is showing signs of life.
I had the BLACK SCREEN.... (first couple of lines of pixels were not black)
After thousands of hard and soft resets (soft resets seemed to have the best results) I managed to get into the bootloader!! Flashed with an older rom and at least I'm getting the splash screen again. (but still getting an error at 99% of update of the CE rom).
I'm updating using the exe in bootloader mode btw....
Since there's always an error at 99% when I use the exe method and the device is not booting I thought about giving the SD method a shot.
My device didn's show the SD option but fortunately tadzio explained about the MBR (didn't even know a SD card had one!!! :lol:
http://forum.xda-developers.com/viewtopic.php?t=32849
When I decode a nbf file using nbfdec.exe and flashing afterwards I get a message that my ROM is to small.
Size is same as nbf file.
How do I correctly decode a nbf file?
Thanks for the help.
BuDDaH
Don't use a nbf, get a dumped or bs rom from the ftp & follow instructions with copying bytes etc.
M
Ok OLTP I'll skip the nbf decoding route.
Think one of the problems is the way the newer roms are encoded.....
Saw you're using a 1.13 bigstorage rom?
That one is not on the ftp is it?
Modified your own rom image?
Hi BuDDaH,
I downloaded at the Dutch TMO site the shipped-rom, unzipped the exe file & decoded the nk.nbf nbfdec. In this nk.nb1 I altered the usual BS bit patterns and re-encoded the nk.nb1, again with nbfdec, to the nk.nbf. After that it was just running, the extracted, upgrade program & it worked like the usual shipped-rom upgrade. you might have to use the maupgrade_noid version, sometimes twice.
This method is better described in the thread about upgrading to radio 1.13 which you can add along the road as well.
So yes I made it myself, not so fond of using other people's rom unless I have to. Please don't let anyone be offended by this, cause a replaced bit can cause serious harm, like I encountered myself, with my own corrupted rom-dump.
Good luck, M
Just wanted to update you all on the latest status.
I managed to flash a german rom (as I've got a German device) although I always get an error message at 99%.....
Fist it just stuck on the splash screen but this somehow deteriorated. Now I get a black screen covering about 5/6th of the screen. the first 1/6th shows a part of the splash screen. No backlight and it hangs.
No more bootloader so I need to have it serviced (anybody knows what the techies do with such a device?)....
Now the question remains where.
T-Mobile NL refuses to service it since the IMEI is unknown to their system
T-mobile Germany doesn't have a service center but only takes repairs through a T-Punkt shop..
Any ideas?
Thanks,
BuDDaH
Latest update...
I sent it in for repair and it turns out that the ROM is damaged and the phone needs a mainboard replacement..... which costs about the same as a new unit...
Anyone got a spare one laying around for me?
So much for my Magician!
Cheers,
BuDDaH....
Sorry to hear...did you try another SD card?
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Hey BuddaH,
There enough people interested in the parts here at the forum, so there's a tiny brightside on your adventure :-(, man i do feel sorry for you.
Regards, M
Yup, i need some parts also
BuDDaH said:
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Click to expand...
Click to collapse
You probably ran the battery down. I don't think it charges unless the ROM is working. That is why it is highly recommended that you start with a full charge before commencing a ROM update.
Hi Stevedebbi,
Even in my situation the it still seemed possible to charge the battery (at least the red light went out and the battery got hot).
Sent my device to apexlaptops.co.uk cause they claimed they reflash...
Got the reply back that they couldn't get it too bootloader mode and were unable to repair. (guess they could not do some JTAG debugging).
I may be able to buy a working device that's damaged on the outside....

Wont Boot

I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Drunknasty said:
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Click to expand...
Click to collapse
if your device is G3, unlocking is required to flash any rom, before upgrade your device, it is recommended to flash an official WM5.0 rom (in your case T-Mobile rom) with IPL and SPL 2.xx then flash again.
in general there are many probabilities for your issue.
((Where is TNT1.1?? did you mean 1.0?? ))
My Bad meant 1.0
So to get it straight.... I will need to unlock my phone each time?
Oh and to correct myself again, when flashing with the T-mobile ROM it says UPGRADE ONLY. And the read me file says its the wrong RUU. But it is the same file from Tmobile I used when I first got the phone. But I will try again.
Are there any other suggestions?
You need to read the "how to flash" sticky.
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Try another ROM.
Sounds like you need the "Wizard Love" rom. I dont have the link handy but I am sure someone else does.
Drunknasty said:
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Click to expand...
Click to collapse
Already got it. Thanks I am trying to load it now. But the only thing is that the last time it failed and I can understand what the error says. I know the number is 300 but can read the language.
But I will let you guys know when this load completes.
Thanks again for all the assistance.
No worky worky. The load completed and then boots the splash screen shows and then stays there.
Any ideas?
Try to remove the battery and let it out for at least half an hour. Then put it back in and see what it does then.
I thought the same thing too. So when it got done last night, out of frustration, I removed the battery and left it there to wait on when I get off work today. I will report back on what happens.
Again I would like to thank you guys for helping me. I really do appreciate it!
STEP 1 install the original manufacturer ROM
T-mobile UK
http://www.tm-phonedownloads.com/download_manager_mda_vario.html
T-mobile US
http://www.t-mobile.com/wmupgrade/
Search for the original rom for any other
instructions on how to use the original rom can be found here
http://support.t-mobile.com/knowbase/root/public/tm23294.htm?&A2L.SERVICE=AboutUpgrading
Put it in the bootloader mode.. ( three color screens )
hope this helps..
cheers
Praneet
Ok I did that and it gave me ERROR 296: UPGRADE ONLY
Then it tells me that the NBF file cannot be used for my PDA Phone. Please get newer NBF file.
Is there any way I can get the Tmobile splash and IPL\SPL number back to original, it doesnt need to boot all the way into WCE but atleast show the same numbers and splash during boot up?
Or any other way to get this thing to work?
Thanks guys
BTW it is a HTC Wizard from T-mobile.
If you are getting an error 300 you need a newer rom update utility, and regardless if your phone is a G3 or G4 it needs to be unlocked before you flash any rom.. LOAD a OFFICIAL cingular ROM onto your device before going any further, then unlock your phone either via www.imei-check.com or through some of the tools offered here...
Which one should I down load from Cingular? Even though I have a Tmobile phone?
what ipl and spl are you using and what radio are you using. Just post all the numbers from the bootloader
As soon as I get home, I will post them.
Thanks
Ipl 1.01
Spl 3.08
Thanks
Drunknasty said:
Ipl 1.01
Spl 3.08
Thanks
Click to expand...
Click to collapse
uh oh. someone tell me if I'm wrong, but I think this is bad. it's the result of flashing a g4 with g3 or the other way around... keep searching, and good luck.
flash the original t-mobile rom. your phone doesn't appear to be unlocked. good luck

Flash without hardspl

I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK
Did you try going to tri-color first then flashing a stock tilt rom?
Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.
both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!
I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK

Have I bricked my Kaiser

Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
But doesn't the SPL have to be either Hardspl or jumpSPL.
I have tried to do the rom update again but sticks on 0% and gives error 262
Alemaker said:
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
Click to expand...
Click to collapse
Not advisable if he has the default SPL still though which by the number appearing at the tri col screen it appears to be the case.
Try doing a hard reset and see if it boots into the original ROM then at least you will find out if it is bricked or not, however, i'm not sure it will work based on the fact you got part way through in the first place.
Hold down the keys directly next to the Send and End (green and Red) Hold in the stylus and keep them all held untill you get a screen telling you to press the green (send) key.
Tried the hard reset, takes me back into the bootloader. Any other ideas?
Hmm... ok then.... you are pretty much looking at a very expensive paperweight at this moment in time then.
Look at this thread...it "may" (i'm not promising anything but it may point you in the right direction) help you out. Let us know how it goes.
http://forum.xda-developers.com/showthread.php?t=361612&highlight=bricked
cmcmill01 said:
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
Click to expand...
Click to collapse
Hate to joint the parade, but the exact same thing happened here - 18% now stuck at 1.93.0000
For anyone else reading this BEFORE flashing a new ROM please read, read and read again EVERYTHING related to flashing on this site, wikis and wherever else you can get info.
Another idea for you. Search around here for how to flash from an SD card that may solve the issue out for you. As previously noted though....READ READ READ and be 110% certain you understand what you are doing before you do anything.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=stuck+bootloader
details some info for a Wizard, should it be the same for a Kaiser?
Will Mtty get me any further?
MTTY will at least give you a USB connection to the device it is worth a shot given your current situation.
There is hope!
I did a clean reboot of my PC and disabled my antivirus (avast) and was able to sucessfully reflash the new 1.62 rom (released from ATT site today).
Thanks will try the new 1.62 rom.
What commands can you use with MTTY?
tried the At&t rom gives me an error on the vendor id. Will try a HTC rom
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
If you are stuck in boot loader & would like some help via MSN Messenger, please PM me or look for me on MSM messenger at [email protected]. I will be available to help later this evening or tomorrow morning.
I have most of the files to fix these issues & can use MSN fileshare folders to help you.
Good chance that you can be up again in a matter of minutes
cmcmill01 said:
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
Click to expand...
Click to collapse
Invalid Vendor I.D. is cuz it's locked.
Had the exact issue myself and found a ATT ROM that will boot. It saved me bigtime, so I saved it. It's in one of the posts on one of the threads but I have the actual ROM, it'll overide that lock.- PM me if ya need it.
Got the same solution, Holy S**t about to have a heart attack. Tried nearly ever ROM out there, it was the Asia one that got me going.
Lesson learned: make sure you Hardspl after jumpspl.
Thanks for all the help folks
Glad ya got it fixed. One quick question?
Is your original ROM ATT or HTC ?
It is a HTC ROM. Done My Hardspl and got Sleuth v3.0 on it already
Happy days

Screen stuck on red green blue and white

First of all please be gentle! I am a complete novice and this is my first post. I have a Touch Pro on a Vodafone contract. I downloaded the recent ROM software upgrade from the Vodafone web site and began the transfer to my phone having followed all the advice. However, the download got stuck at 12% and no matter how many times I start over again it will not go past that point. Worst still the phone is now locked on a red/green/blue/white screen with the message "Upgrade ROM code error Please try again". the error message on the Vodafone software download is No 302. I have tried Vodafone technical help but as I was due for a new phone anyway they have sent me a Touch Pro 2 but don't seem to want to help me resolving the problem with my "old" phone. It is only 5 months old (replacement insurance phone) and in good condition but useless if it can't be made to work.
Can anyone help with simple instructions on how to download a ROM that will work. If not does anyone want to make me an offer for the phone? Currently locked on Vodafone but I am sure you guys out there have the skill to resolve that one.
Many thanks,
Hollybeau
So, they aren't asking you to send it back, I take it? If that's the case, then the first thing I would try would be to flash with the stock rom, if you can find it (not the upgrade that quit on you). If that doesn't work, then just try to flash hard spl. If hard spl goes through ok, you're golden and can flash any raphael rom you want. If it doesn't, the phone is probably toast. You got a new one, so just use the old one as artwork.
Thanks Farmer Ted,
Unfortunately I do not know the orginal stock ROM. It is not on the Vodafone web site and the HTC site keeps telling me that all the likely candidates are "not suitable" ( I assume this is beacuse it is some sort of Vodafone variant). I am afraid that "flash hardspl" means nothing to me - I told you I was a novice! Can you direct me to what and where please.
What bugs me is that here is a phone worth £200? but for a problem caused by Vodafone's buggy software upgrade.
Hollybeau
Start Here.
Best way to find everything you want to know about flashing ROMs.
Lol.
Hard SPL is a bootloader that allows you to flash any rom you want (not just vodaphone). It also has over-write protection, so if you get into the situation you're currently in, the phone won't be bricked. If you can flash it (make sure you flash the gsm version in the raph rom forum), you are fine and dandy.
If you can't find the stock rom online, you may be able to flash the upgraded rom off of your sd card (I believe this will work with a stock rom and stock spl, but am not 100% sure). Re-name the .nbh image file to RAPHIMG.nbh. Format your sd card (1-2 gb works best) to FAT32, and put the image on the root of the card. Go into bootloader (well, you're already there, you may not need to) by holding volume down and soft resetting. Hold vol. down until the tri-color screen appears. At the prompt, press the power button, and let the flash run its course. Soft reset when it says that the update was a success. Let the phone boot up until it gets to the the alignment screen, the hard reset and boot it up.
If you don't have an .nbh file, and instead have a .exe file from vodaphone/htc, then you should be able to extract the contents with either winrar or 7-zip (google) to get at the .nbh image file. I've done this before, and it works fine.
Many thanks to all who have replied. I have fixed the problem. It turns out that it was the download to my PC that was at fault. I downloaded the Vodafone software to my lap top and ran it from there and it has recovered the phone. I now have a spare, and working, Touch Pro. I may try the HardSPL and other ROMS just to use the phone as a test bed. Alternatively, anyone out there want to make me an offer?
Hollybeau
Hollybeau said:
Alternatively, anyone out there want to make me an offer?
Click to expand...
Click to collapse
Ask in market place and you will probably get some takers

Categories

Resources