Ok, i have another thread going which appears to have gone cold.
Can someone (expert) tell me is my MDA Vario T-mobile device dead?
Here are the details:
Currently, it will flash with any rom, 100% and reboot.
It will not load in to Win mobile, it gets stuck on boot screen.
It will flash with original Vendor rom, 100% reboot and get stuck on boot screen, although the boot screen is not a T-mobile one, its a custom one, i.e. button or Mr clean, leading me to beleive the flashing didnt work correctly.
Currently i have followed all the guids on how to get these back and alive, i.e. Active sync wsecomm set to untick USB connections, tried original rom, nothing will allow this device to get in to windows.
The device WILL go to Tri colour screen (boot loader) and allow flashing.
ALL the experts say as it can go to Tri colour screen the device is not dead, so can anyone confirm?
I am willing to paypal anyone who can get this device running.
currently:
Tmob Aku 2.3
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.24.10.1
So, anyone care to enlight me, and please dont come back with Hard reset, Format fails.....
Whoops ignore me, you seem to have a G3 device, NOT a G4. My bad. /me deletes info relating to G4's.
You might like to re-read the flashing howto:
http://forum.xda-developers.com/showthread.php?t=298613
Info on original (vendor's) ROMs you tried, and you flash it using its EXE or other tools?
Flashing method
.exe and noid update tool.
Both the same result 100% flashed, stuck on boot.
It appears to me that when i flash with Button or Mr Clean, the initial boot screen changes between beer glass and Mr clean, however when i flash with T-mob official, it goes 100% through but does not change the boot screen.
All of them get stuck and dont get past boot screen......
lokidan said:
.exe and noid update tool.
Both the same result 100% flashed, stuck on boot.
It appears to me that when i flash with Button or Mr Clean, the initial boot screen changes between beer glass and Mr clean, however when i flash with T-mob official, it goes 100% through but does not change the boot screen.
All of them get stuck and dont get past boot screen......
Click to expand...
Click to collapse
If you can get into bootloader you are NOT bricked.
However you will never get your phone recovered unless you do what was told to you in your other thread. You MUST flash a rom that matches your devices CID--if you are unsure AND your phone was bought from your carrier, go to your carrier's website and download from there. You MUST flash this from the bootloader. Try a different computer if the one you have been using isn't getting you anywhere. Only you have the ability to get the information and correct rom for your device. Your unlock process did not complete successfully and you are getting no where fast. Until you get your phone in a usable state no one is going to be able to help you any more than the others that have already tried.
If it were only one device I would say you have a hardware issue. Since the same issue is happening on 2 devices for you it is more than likely something that you are or are not doing. Providing your devices were G3's when you started and you didn't flash G3 bootloaders into G4 devices these phones can be recovered.
lokidan said:
Currently, it will flash with any rom, 100% and reboot.
It will not load in to Win mobile, it gets stuck on boot screen.
Click to expand...
Click to collapse
The fact that it flashes is good, you can get to bootloader you are not bricked.
The symptoms you describe are indicative of a CID locked device trying to recover a bad flash with custom roms.
The fact that your phone freezes at boot screen is that you have had a previous bad flash.
lokidan said:
It will flash with original Vendor rom, 100% reboot and get stuck on boot screen, although the boot screen is not a T-mobile one, its a custom one, i.e. button or Mr clean, leading me to beleive the flashing didnt work correctly.
Click to expand...
Click to collapse
you are correct the flash is not working correctly. You MUST flash an official ROM from the carrier that your phones are CID locked to in order to "fix" the flashing issue.
Custom roms require that you have a full carrier rom flashed prior to flashing them, you will have issues if you do not have a successfully flashed Official rom prior to attempting a custom rom flash. Official roms require that if you are not CID unlocked that your CID matches that of the rom.
lokidan said:
currently:
Tmob Aku 2.3
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.24.10.1
Click to expand...
Click to collapse
Any idea what it was before you started your upgrade/flash attempts originally?
currently
Zzan, thanks for your reply.
My only issue flashing the original roms is this, it flashed to 100% complete, rebooted and still got stuck on boot screen.
Now i tried Very first rom that was on this device which i believe was this:
RUU_Prodigy_1060204_105_11210_TMO_UK_Ship
Result: 100% --> reboot --> stuck on boot screen.
NExt:
RUU_Prodigy_2210206_22102109_021911_TMO_UK_WWE_Ship
Result: 100% --> reboot --> stuck on boot screen.
So as you see, i am trying to flash with original roms....
Everyone says, as long as you can get to boot loader (tri colour) these devices are not bricked, so i can , so why wont the these devices go back to Tmo original....
Now, i am happy to give you any info you need.
Thanks.
This will work if the phone never gets past bootloader screen even after flashing:
http://forum.xda-developers.com/showthread.php?t=276963
CID unlocked
Dont think you can use the r2sd all command with mtty as this requires the device to be unlocked, clearly mine isnt because i get security failure.
Is it worth using th emeicheck website?
lokidan said:
Dont think you can use the r2sd all command with mtty as this requires the device to be unlocked, clearly mine isnt because i get security failure.
Is it worth using th emeicheck website?
Click to expand...
Click to collapse
it may be your only option From post 16 in the thread mentioned above it seems that their unlock process starts from the bootloader. You may need to talk to some people on the G4 forums to see exactly how this process works to determine if it has a chance for you.
It doesn't appear that anyone that has posted to that thread tried to unlock through their site once they were already stuck at the boot screens.
Good Luck. I hope this works for you.
Related
I just tried using ShellTool to install the flash Xplore onto my phone, it's a G4, CID locked. But, when ShellTool reported that it was done, I went to unplug my phone and hard reset it, but I accidentally held one wrong button, and put it into bootloader mode. Then, I realized what I had done, then hard restarted it the right way, and now all that comes up is the initial boot screen, with the new OS listed as 10.2.0.8, but it just stays there.
What do you think?
i think if you can get your wizard into bootloader then you dont have a brick. Please try to put your phone into bootloader mode then flash wizard love or your carriers rom. Then you can attempt shell tool again
Doesn't the phone have to be CID unlocked to flash the Love ROM with RUU? I have Wizard Love 2.26 10.2 WWE Novii CF2, will that work with my G4 device since it is CID locked?
My device is cid-locked G4 and wizard love worked fine flashing from RUU, so did my carriers rom.
http://forum.xda-developers.com/showthread.php?t=298613
here is a tutorial that may help you.
Good luck.
Sorry for asking but ive checked the search and i cant seem to find it. Im looking for the original ROM 1.5 i think it was for the wizard...my phone wont do anything but go to the bootloader screen even after ive flashed it to 2.6 so im thinking i need to do the original ROM...anyways does anyone know where i can find it and download it? thanks for any help guys
oh i flashed it to what i think was 2.0...still the same bootloader problem but now it says IPL 1.01 and SPL 1.01...but still stuck at the bootlader screen...
Flash button rom:
http://forum.xda-developers.com/showthread.php?t=298613
i did that and now its still stuck at the bootloader screen with IPL 2.26 and SPL 2.26...somethings not right about my cell phone or something...any other ideas anybody?
XxShibbyxX said:
i did that and now its still stuck at the bootloader screen with IPL 2.26 and SPL 2.26...somethings not right about my cell phone or something...any other ideas anybody?
Click to expand...
Click to collapse
Have you read and followed this and the steps it points you to?
http://forum.xda-developers.com/showthread.php?t=298613
I assume you have a G3 since you are flashing these other roms, and based on the IPL/SPL numbers you are giving. You need to give us specifics of what you have done, what happened at each step and where you are at now. Details are a good thing, as its hard to diagnose with just bits of the information. At one point you say 2.6 (no idea what that is) then you say you are stuck at 1.01, and now you say 2.26. So please tell us (in gory detail!) what all you have done...
If you follow all the steps in the thread above you will get CID Unlocked, but at the point where you are now, you need to flash YOUR PROVIDER's original rom to get back to a known state. Then try doing the CID Unlock.
alright i was using molskis 3.0 and for some reason sometimes my phone would not dial or connect so i restart it once every few days...well i did a simple restart and when my phone turned back on it was on the bootloader screen with IPL and SPL of 2.26...i figured i would have to flash the rom again or go to an earlier one...so i get home and try to flash molskis 3.0 again...right after it finishes and restarts itself it comes up with the bootloader screen again...now at this point im thinking i might have to do an earlier one like the original t-mobile rom and so i tried that...same problem stuck at the bootloader screen but with IPL and SPL of 1.01...so i post and then vippie tells me to download the button rom...i try that and no luck still the same problem and i followed those steps exactly and no luck...so now my phones just sitting on my nightstand charging with a bootloader screen and nothing else and the IPL and SPL says 2.26...could it be internal damage or what? i like my phone and dont wanna have to spend the money on a new one but at this point im thinking i might have to...thanks mfrazzz for offering your help...i know i seem like a noob and i really suck at punctuation but im not stupid so anything you guys tell me to do in detail i will be able to try
I don't follow you anymore.... you got IPL/SPL 1.01 and tried to flash button rom, after this your IPL/SPL is 2.26? Impossible....
Sometimes it won't go past bootloader no matter what you do... do this to revive:
http://forum.xda-developers.com/showthread.php?t=276963
Hi all, I'm a newbie. I did research but still couldn't find an answer, hope some experts can help me out. Thank you so much.
I'm trying to flash my 8125 and the software asked me for the SPL version of bootloader. Anybody know how can I find out the bootloader SPL version for my phone 8125 (or Pocket PC in general) any help would be really appreciated! Thanks in advance.
what rom is currently in it? is it stock? for instance, my MDA from tmo now has a stock rom (long, depressing story, don't ask) and the ipl/spl if memory serves correctly is 2.26
It shows on your initial boot screen in red letters (at least my tmo rom is in red). I'm NOT sure if the bootloader should have a seperate number but if not...simply soft reset your phone and as it boots look at the first screen to pop up and write down those numbers.
Wish I could help you more.
Another easy way is to get WST (check my signature) and read the "Device Info" as it will tell you what Bootloaders you have, the Gx type and much more
@ kadin27
what sw asks for the bootloader version before flashing?
kadin27 said:
Hi all, I'm a newbie. I did research but still couldn't find an answer, hope some experts can help me out. Thank you so much.
I'm trying to flash my 8125 and the software asked me for the SPL version of bootloader. Anybody know how can I find out the bootloader SPL version for my phone 8125 (or Pocket PC in general) any help would be really appreciated! Thanks in advance.
Click to expand...
Click to collapse
what software your talking about,with which you are trying to flash your device ?
windows mobile OS are packed into a package called 'Roms',which have the OS,OEM drivers,extended rom(contains applications) and Romupdateutility (RUU)which flashes the OS to the device,.When flashing it won't ask for any SPL version,but if the rom is a stock rom (official rom) with a higher Os version than already installed,will flash automatically without any verification of os ipl/spl.or if older than the present rom will not flash and stops with an Error code and it's explanation.
If you are trying to flash a non official custom build rom on a locked device it will also stop flashing with an Error code,or sometimes it seems it has flashed and ruu confirms on the pc 'Congratulations you have successfully upgraded'but when it reboots the previus OS loads up.But to flash a custom build ron,it's mandatory to have your phone CID unlocked,custom roms cannot be flashed to a cid locked devices.
SO,what are you using and what ERROR CODE it displays ?
Secondly, IPL/SPL versions are displayed when you power on or reboot the device on the initial first splash screen in red at the top of the screen.
OR as already suggested by mestrini download WST tool and run to check IPL/SPL and all other info about your device.
IPl/SPL are infect called the 'Bootloaders'
I have a 8125 G4 sim unlocked w lokiwiz and a flashed WMSE5_rev4 with soft spl, well the problem that i have now is that i recentley tried to flash a new wm6 rom without hard spl ( yeah i know stupid) And now i am stuck on tri color boatloader screen no matter if i turn it off or not still goes back to the same thing. and yes the rom that i was flashing was g safe, i think were i messed up is not CID unlocking it with hard spl?when i tried to flash the new rom it went all the way to 100% and then gave error after that. NO activesync connection right now
questions
1- DID I BRICK IT
2- is there a way to recover this device
nothing at all?
AHHH man exactly the same thing just happened to me please some one help us and tell us there us a way to fix it
Download the official carrier's Rom and flash in the tricolor screen or you can even try with wizard_love rom,it usually works with a G4 device.Activesync will not connect in bootloaders (tricolor screen).If you had not got your phone 'HardSPL' then always do the flashing through 'SoftSPL',cuz after flashing with 'SoftSPL',it only patches or tricks the device to think its CID unlock,which is temporary and as soon as you Soft Reset the phone,it goes back to its original ipl/spl and into cid locked situation,therefore,each time to flash,it has to be used again.
Cheers!
I lost some of my brain cells and flashed my Rhod400 TP2 with an incompatible radio. Now the phone boots to the splash screen without any rom or radio info displayed. It will not go past the splash screen. I performed a task29 via mtty and reflashed the phone to a stock rom/radio, however, the phone is still stuck. Someone told me to relock the phone and reflash to stock. That made things worse because I cannot unlock it anymore Is there any way to get the correct radio back on the phone and make it boot? I've tried several roms, but they fail. The only rom which flashes successfully is the stock OS rom.
Help!
I'm sorry to say that I think your phone is permanently bricked now. If you flash the wrong type of ROM, then you can just put the phone in bootloader and flash a new one. But I don't recall anyone who flashed the wrong type of radio (assuming it was a GSM one on your CDMA phone) getting out of it
Enter Bootloader mode???
Hi, the big question...
Can you enter the Bootloader mode?
When no power on the phone hold down the volume-down key and the power key as seen in this YOUTUBE Movie.
If you can enter it you can flash any radio from THIS THREAD
Simply plug in your USB cable when in Bootloader mode and you'll see after a few seconds USB on the screen.
If this does work then you're lucky and then we can look for an solution (if you don't find it yourself).
I'll keep my finger crossed for you
Hi. Yes, I can get to the bootloader. This is how I've been flashing the phone since it died. I also used it to do a task29. The phone is CDMA with USCC. The link bigchrizzieboy posted is for gsm radios.. I assume since the phone has been relocked to SPL 0.70, then it will not accept a new radio rom. The problem is that I can't seem to unlock the phone anymore. I originally unlocked the spl with the latest HardSPL v1.10R3.100 version. It fails now that the phone is dead. It enters the rom loading screen, but just sits at 0% until the battery drains (1 hr).
drexful said:
Hi. Yes, I can get to the bootloader. This is how I've been flashing the phone since it died. I also used it to do a task29. The phone is CDMA with USCC. The link bigchrizzieboy posted is for gsm radios.. I assume since the phone has been relocked to SPL 0.70, then it will not accept a new radio rom. The problem is that I can't seem to unlock the phone anymore. I originally unlocked the spl with the latest HardSPL v1.10R3.100 version. It fails now that the phone is dead. It enters the rom loading screen, but just sits at 0% until the battery drains (1 hr).
Click to expand...
Click to collapse
same with me mines sits at 0% i tried everything and still samething
get your phone replaced under warranty. and don't tell them that you tried to replace radio. or just call your insurance company to get the phone replaced.
drexful said:
Hi. Yes, I can get to the bootloader. This is how I've been flashing the phone since it died. I also used it to do a task29. The phone is CDMA with USCC. The link bigchrizzieboy posted is for gsm radios.. I assume since the phone has been relocked to SPL 0.70, then it will not accept a new radio rom. The problem is that I can't seem to unlock the phone anymore. I originally unlocked the spl with the latest HardSPL v1.10R3.100 version. It fails now that the phone is dead. It enters the rom loading screen, but just sits at 0% until the battery drains (1 hr).
Click to expand...
Click to collapse
u do notice this is gsm section? maybe the radio & ROMs you are flashing are GSM not cdma