6.0 flash that isn't resulting with 6.0 - 8125, K-JAM, P4300, MDA Vario ROM Development

I've searched but not found this issue.
Correct me please if I've missed it.
I've successfully installed 3 different ROM's on my MDA. It is a G3 version.
The boot screens all show whatever that ROM has as it's screen so I know the install is working. but once I get the phone booted up and the first time 'Customization' goes through, none of the included apps are there and it's basically still T-mobile. Also, not one ROM actually updated the phone to a 6.0 or 6.1. It still shows 5.whatever. I'd be more specific, but it's currently installing a ROM yet again just to test an idea I had.
If this fails, I'm stumped.
Any takers on this?

free bawlin
You cannot be new to forums in general if you're here. The same rules apply on ALL forums.. do some research for your $100 device. First of the First, in giant bold sticky letters, UNLOCK SUPER-CID!!!

Yes the same rules do apply on all forums.
That said, consider I didn't wander in with the typical statement of "HAI GUISE SOME1'S MDA LOOKED COOLER CAN YOU MAKEMINE THAT WAY K THNX BYE"
I've been reading to roughly 6 hours of reviews and guides both here and elsewhere. I've come to this site for advice concerning my Dash numerous time before, but as I had nothing to contribute and my answers were already existing, I never registered until recently. Remember, post count doesnt show experience.
Now on the other hand I apologize for not going in to detail completely. Yes I used the Button ROM. After downgrading, I used the lokiwiz batch file to both SIM and CID unlock my device. I followed the Dr. Puttingham guide to the letter. I know because I missed one minor detail and spent 45 minutes going back over everything carefully before I realized that when extracted, everything in lokiwiz didn't go to the right location.
I then upgraded back to the 2.26 IPL and SPL as was recommended.
So, going by the various guides posted, I've done everything asked to be done of a G3 MDA.
With this out of the way, does anyone have a valid reply that may be helpful?

Use WST-Wizard Service Tool
http://forum.xda-developers.com/showthread.php?t=329170
To check the real situation for your device, please be aware that only with IPL/SPL 1.xx you are able to unlock your CID, with WST
Also only G3 devices can be unlocked with WST

I had just stumbled across the WST this morning but have not yet had a chance to use it as I'm at work now.
Very much appreciated.
So I'm guessing my best bet at this point would be to downgrade yet again. Well this should be fun. I'll get to work on that as soon as I get home and update in case someone else has this issue.

@ drkangel650
My reply was more than valid. Post count doesnt explain anything, not reading the stickies hudreds of thousands of people have does!
If you know forum rules, then you don't read. If you would have done the correct reading as you say for hours like this, how are you only NOW getting the WST when it's at the top stickied in multiple threads for your EXACT problem. You would have read that you can easily use that program in 2 mins have it sim and cid unlocked.
You have not correctly completed the procedure obviously, if you did the roms would flash. The only thing that would make your phone back back to original rom would be being CID-locked. Hit the threads roonie!

I'm not here to argue. My splash screen shows wat it should for the ROM selected and installed and the lokiwiz said it had performed both the SIM and CID unlock. This is only my second modification on a phone.
The information here is great, but I will say that to someone not familiar with this, it's a bit difficult. Many of the tutorials cross reference so it is very easy to miss something. Many different programs doing the same thing are mentioned so for me not to see the WST being used for the CID unlock is understandable especially when there are programs made specifically for CID unlocking. I chose the straight forward route.
My Dash only had one minor issue in updating the ROM and that was an oversight on my half.
I have yet to cross someone who gets the ROM splash screen but not the ROM itself.
I'm not asking for your pitty or a handout, I'm simply asking for a step in the right direction. Thanks to Pisca for delivering the sort of help I've learned to expect from here in reading in the past.

ok,there's no point in arguing,this is a development forum and its full of very rich info and guidance,but it believes that you first 'Seek & search',the best place to get all the info is 'xda-wiki',
ok,that was good you read through the guides and procedure,but missing an important step,creates many problems,so its advisable to re-read and follow it correctly.
This forum also demands politeness and respect for seniors.
BA_Flash_GOD advised you in a simple way,that all the problem is that your phone must be CID unlocked (SuperCID),now,there was no need to lecture him for this.
Anyway! as advised by Pisca and I also believe,your phone is still CID unlocked,use WST (Wizard Service Tool) and hit 'CID Action' button to verify the CID lock/unlock status.
Yes if its still CID locked,you need to downgrade to IPL/SPL 1.xx to CID unlock,only then it'll upgrade to wm6.
Or,read this guide to do the procedure correctly :-
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies

Thanks for your help yet again. I followed the guide exactly. WST is even showing me that my device is in fact CID Unlocked. I made a point to check it prior to finally flashing my selected ROM.
Finally wrapped up, got nervous when It asked me to calibrate the screen and all looked the same but I held hope. Finally done and sure enough, Windows Mobile Version 5.0
OS 5.1.195
Full T-Mobile software.
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies
That's the guide I used as was suggested. Button ROM, check. IPL was dropped and SPL stayed the same.
Ran Lokiwiz. Both with SIM and CID it rebooted as it said.
Reran the Button ROM, both IPL and SPL were dropped.
Used WST just to verify it was CID unlocked as so far it had been the same as what I'd done before. This time it showed it was in fact unlocked.
ran the Tmobile ROM to up the IPL and SPL back to the 2.26 level.
The only thing not done was the 3.08 flash as it said it were optional and with it supposedly being more difficult to downgrade, I chose not to at the time.
I then flashed the XM6r5 ROM.
And here I am looking at the basic Tmobile ROM I started with.
I thank you all for your help But I'm really at an ends. I followed the guide to the very letter (Except the optional flash) and nothing but null results.
and to prove I'm not insane....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This may sound like an odd question: where did you ge the the 2.26 rom? I hope not from Tmobile. Because that one relocks your device.
About CID unlocking the phone:
As I remember (this was mothes ago) You have to run it twice (once for SIM, reset; once for CID, reset ) Sounds redundant I know< but you also need to exit the unlocker everytime you do that. also Unplug the phone evrytime... By saying reset I mean exit the scenario (at least you don't hae to rese the pc)
Are you using Vista or XP? If you are on vista can you dual boot to XP?
I see that you are a polite individual Just slightly confused by this ridiculous way to unlock the phone. I was too, but as soon as I left it alone for a while, and came back to the directions with a fresh head, I got it to work.
excuse the spelling mistakes I'm using an unfamiliar keyboard

I am currently using XP and as I wasn't sure (and activesync just doesn't like me) I ended up unplugging the device each time just from habbit.
Goin by what you said, I think the hold up was that Last ROM used to updated back to the 2.26 IPL and SPL. But if the T-Mobile ROM relocks (which makes sense now that I think of it) why would it be listed in the tutorial?
lol anyways I'll post the link to the one I used in just a moment.
EDIT
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
That's the link I used from the tutorial guide.
Much thanks yet again.

NO! the official T-mobile rom you downloaded doesn't relocks,its perfect and being flashed by all,there's perhaps some other hold up,that doesn't let it flash or upgrade.
YES! WST confirms its CID unlocked, I think you might be having connectivity problem,you don't require Activesync for flashing, infact its automatically shut off by the RUU as soon as it starts to flash.
To check the connectivity,get the phone into Bootloaders (multicolor screen),hook up the phone with pc via usb cable and check small usb appear at the bottom of the bootloader screen,if its there,then its good to go and flash,butif its not there than,its connectivity problem.
Secondly,close all running programs in the back ground,especially Anti virus and Firewall and don't do any surfing or use net,just leave the mouse,let it flash and complete and make sure battery is full,many flashing error occur due to weak or battery not having enough juice in it.
Anyways! download T-mobile 2.26 rom from this link:-
http://www.sendspace.com/file/zj8f21
Hope,it'll work

Well the good news is at least I have all these ROM's saved now so it won't take quite as long
In about 9 hours I'll be home and able to do this again. If anyone else has any input, I'll add that to the list for tonight lol.
Thanks again guys.

S.V.I said:
This may sound like an odd question: where did you ge the the 2.26 rom? I hope not from Tmobile. Because that one relocks your device.
Click to expand...
Click to collapse
Is this true...?
Some of the Roms I've build where based on the original T-Mobile 2.26 Rom.
I also flashed this to my device(s) many many times (including the 2.x IPL/SPL) after they were CID Unlocked (with LokiWiz) but my devices were never CID locked again...

it is only of you downloaded the rom from the tmobile website with their ruu.

Okay, now I do understand what you mean, I heard this "problem" before
But to be honest, sometimes when I flashed a completely STOCK T-Mobile Rom with their RUU (their complete executable) this wasn't the deal.
Take the following Rom as example: http://rapidshare.com/files/20139766/MDA_Vario_1060202_103_11210_TMNL_Ship_-_STOCK_ROM.exe
It's a stock T-Mobile Rom.....after flashing this on a CID Unlocked device I didn't have to CID Unlock it again...to be honest, I only ran LokiWiz 1 time on my 1st Wizard about 5 minutes after opening the box...and believe me.....I flashed thousands of times since then

I guess I was the lucky one who got the tmobile update with a written CID block

S.V.I said:
I guess I was the lucky one who got the tmobile update with a written CID block
Click to expand...
Click to collapse
LOL .

What version of WST do you have? You shouldn't use the latest beta. If the old version of WST will failt, too, try aWizard...
And... don't look at your splashes, they say nothing about your ROM

utak3r said:
What version of WST do you have? You shouldn't use the latest beta. If the old version of WST will failt, too, try aWizard...
And... don't look at your splashes, they say nothing about your ROM
Click to expand...
Click to collapse
The 1st 2 splashscreens not, the 3rd one (welcomehead.96.png) is cooked into the Rom, so the (3rd) splashscreen does say something about the Rom

Related

Rom install issues

So I have followed the guides, two of them conflicting each other (one tells me Wizard Love while other says Button)
So I pick wizard love because I did the factory update a few years back to 2.25
use loki3
run tmobile 2.26 and it fails
run the 3.08 and it works
try to install TNT roms... all get stuck at 99% except one but the rom doesn't work because I am still on windows 5.1
Now on my third attempt it gets stuck at bootloader. Can't get the phone to turn back on to normal mode just to use it and forget about trying these roms
Any ideas?
Got button to work some how
Now I am at IPL 1.01 and SPL 3.08
Hopefully I can redo everything and get 6.1 to work
It tells me my CID/SIM but no where does anyone tell me where I need to insert this ID code at.
ID code? What do you mean by that?
I ment CID, it was telling me the CID like if I needed to enter some sort of menu and run it
Running t-mobile rom again, hopefully this works
You sure that it wasnt asking for a SIM unlock code? OR was it giving you a "data crashes" message?
Nope neither of those.
Anyways
Tmobile screen pops up now with 2.26/2.26
In regards to installing new roms, do I just launch ROMUpdateUtility or Do I need to do a CID unlock again?
Also saw there is 3.08/3.08 available, Update before or after upgrading the wm6.1 rom?
Well, lemme ask you this, what is your device? Is it a G3 or a G4, if G3, then sure, update your IPL/SPL after you upgrade. If it is a G4 however, FOR THE LOVE OF TUNA DO NOT upgrade your IPL/SPL or you will have a brick on your hands. And also, if you have used HardSPL, then no, you do not have to CID unlock your device again. Personally, I just use the SoftSPL method each time I load a ROM. If your device is a G4, I have made a guide in the G4 section that should help you. Its got screenshots and such aswell.
G3
Yay somehow it worked this time, 6.1 is nice
I did softspl
3.08 worth it?
If you device is G3 - FORGET HARDSPL
You mention that you have IPL 1.xx and SPL 3.xx
get WST - Wizard Service Tool and follow the instructions to cid unlock you device, unfortunately you cannot unlock your SIM with the SPl that you have for now
After that flash a carrier ROm to align your IPL/SPL to 2.xx
Ohh it now displays 2.26 on both IPL/SPL
From what I read, 3.08 is mainly for the european radio brand in terms of what the focus on it was for
<---AT&T
Hopefully this will be my last month with this company, figured I try some things out before I put the phone away or give it away to a friend.
Ok, you have a G3 device
Get WST: http://forum.xda-developers.com/showthread.php?t=329170
Install in your PC (XP not Vista), check the situation about your CID and SIM
If you have CID unlock = SUpercid you can flash any ROm you want, if not you must downgrade to IPL/SPL 1.xx (Button Rom)
WST Unlock only works with IPL/SPL 1.xx
Note that SIM can only be unlocked with your SPL as 1.xx
go on run, type msconfig and open that, close all microsoft services and install,
Ckamc said:
Ohh it now displays 2.26 on both IPL/SPL
From what I read, 3.08 is mainly for the european radio brand in terms of what the focus on it was for
<---AT&T
Hopefully this will be my last month with this company, figured I try some things out before I put the phone away or give it away to a friend.
Click to expand...
Click to collapse
DUDE! I'm your friend you can give it to me
Or you could use tmobile with that phone (or any other company that uses sim chips for service) .
Once you have it completely unlocked (cid/sim) you can take it traveling to other countries and use their prepaid sim cards... This is an open phone. dont get rid of it.
on second thought, I will buy it from you if you dont see a reason why you would keep it. I could use a backup to test my cooking on PM me
HAHAHAHA
S.V.I said:
DUDE! I'm your friend you can give it to me
Or you could use tmobile with that phone (or any other company that uses sim chips for service) .
Once you have it completely unlocked (cid/sim) you can take it traveling to other countries and use their prepaid sim cards... This is an open phone. dont get rid of it.
on second thought, I will buy it from you if you dont see a reason why you would keep it. I could use a backup to test my cooking on PM me
Click to expand...
Click to collapse
You know when an oportunittie comes huh!
I can buy it too but its more glad to see a wizard function well with 6.1
hope you can unlock and upgrade... if not... READ a lot.
Losing Mind (again)
OK, here we go.
First off, I am in no way new to Flashing or the logistics behind it. I am sure this is just something that I cant find by searching. But my problem is this.
I have a G3 TMOBILE USA MDA (Wizard). I have used the lokiwiz2 unlock software several times and according to the program I am SUPERCID unlocked. I am able to flash ROMS all day long. I get no error about loading. What is happening is that I almost always end up with the same default ROM after the FLASH is completed. I am now sitting with the Button ROM on the unit. I assume if the Button ROM loads, then I should be CID Unlocked otr it would not load (or is this my mistake in thinking?)
As my MDA sits now, I have the Beer Mug Displayed, IPL 1.05
SPL 2.26 GSM 01.12.10 OS 1.5.4.2
Now, if I go and try to Flash to one of the Two ROMS I want to go to
TMOUS_MDA_5.2.1629_Wing_Port_1.1 (Boring ROM) or I try with SNN 3.1 it will run the procedure perfectly, and I will end up with a Barebones version of Windows Mobile 5.0. This is wild.
Has anyone seen this happen and is laughing and going "Been there, here is the problem,,) or do I need to discuss this in more detail.
Im wondering if the ROM Upgrade Software is grabbing a ROM from elsewhere on my Hard Drive and is installing it from cache or something like that. Is there another version of the OS Upgrader that allows me to tell it exactly what ROM I want installed, instead of just installing whatever it wants.
Thanks for the help, after two days of searching and looking around, I can deal with amteur hour emabreesment, just HELP!!
My xv6800 and my 8125 was a breeze compared to this nitemare. (BTW, I also flashed this 2 years ago with the TMOBILE USA Official Release, no issue)
wyreless
Well,these are symptoms of CID not unlocked.Button's Rom flashed doesn't mean its CID unlocked,its a patched IPL/SPL rom simply to downgrade to IPL/SPL 1.xx for CID unlocking.
Simply,download WST_4.2.2 and run it to verify the CID lock/unlock status of the phone and do the right thing onwards.
Thank You Zabardast for the quick and to the point answer.
I was thinking in the back of my head it was a CID issue. It was just that everything seemed to be "moving right along". I sthere an easier or better Unlocking soiftware then lokwhiz for the Wizard Series, specifically my USA Tmobile MDA?
Well,if you have Button's Rom running successfully,so its IPL/SPL must be 1.xx already,there shudn't be any problem to use lokiwiz02b to CID unlock the phone,you can even use WST_4.2.2 tool also to easily CID unlock the phone.
There's no other method known to get CID unlocked a wizard freely,unless you are ready to pay to IMEI company to get a unlock code
hey alll..ok i screwed up
i downloaded Charecters ROM..i used WST and it showed that my device is G3 and its CID locked..well i just started the Flashing and it stuck at 99%
now it wont load any ROM and just as i came from school..its not evening starting..its not evening charging..please help any one
for one to flash a rom you must CID unlock it first...

RhodiumW WU Radio Unlocked for US SIMs

[SIZE=+1]WU means Worldphone Unlocked, look out for the WU on all radio firmwares to indicate whether it's been patched as unlocked or not! (WV = locked)[/SIZE]
[SIZE=+2]YOU MUST BE SECURITY UNLOCKED IN ORDER TO USE THIS!!![/SIZE][SIZE=+2] - if you are not Security unlocked, you will get a Flash Write Error.[/SIZE]
[SIZE=+2]Flashing one of these radios will enable you to use a US SIM card in your device - if you flash a non-supported (non-patched) radio over this, you will lose the ability.[/SIZE]
[SIZE=+2]DOWNLOAD BELOW[/SIZE]
[SIZE=+2]1) 2.32.00WU (Sprint stock edited)[/size]Mirror1 Mirror2[size=+2]RECOMMENDED FOR ALL DEVICES REGARDLESS OF PROVIDER
2) 2.23.00WU (Verizon stock edited)
3) 1.96.10WU (Sprint stock edited)http://www.4shared.com/file/O3JH-MZK/RhodiumW_WU_196.html
4) 2.05.00WU (USCC test edited)NOT RECOMMENDED[/SIZE]
Not Found
The requested URL /RhodiumW/RhodiumW_WU.exe was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Either im too quick to the draw or its not on the server yet but...
Sorry my bad.
corrected the link now.
IMEI??
For the TP2 Sprint? Tried doing the *#06# but nothing happened.
Is it the one located under settings/ Device Info? Or the MEID on the back of the phone?
Maybe the website needs to reflect the correct info so other users are not confused as I am. Saw the same question at PPCG...
Thanks
You have been stuck. Congrats on a job well done!
HERE'S ALL THE IMPORTANT NOTES:
1. you must be security unlocked to flash this
2. the patch will not stick if you flash another radio but we'll release patched versions for other radios from time to time (for newest radios).
3. when you flashed the radio, you need to make sure to be in GSM mode (SIM inserted of course ), and if automatic network selection doesn't work, use manual selection in phone/options to register on the network.
ENJOY
racolon said:
For the TP2 Sprint? Tried doing the *#06# but nothing happened.
Is it the one located under settings/ Device Info? Or the MEID on the back of the phone?
Maybe the website needs to reflect the correct info so other users are not confused as I am. Saw the same question at PPCG...
Thanks
Click to expand...
Click to collapse
only works if you're in GSM mode... look on the label under the battery or in Device Information
cmonex said:
HERE'S ALL THE IMPORTANT NOTES:
1. you must be security unlocked to flash this
2. the patch will not stick if you flash another radio but we'll release patched versions for other radios from time to time (for newest radios).
3. when you flashed the radio, you need to make sure to be in GSM mode (SIM inserted of course ), and if automatic network selection doesn't work, use manual selection in phone/options to register on the network.
ENJOY
Click to expand...
Click to collapse
i wasn't in gsm mode and once i flashed the radio, it went to 100% errored out and now i have an error message behind my bootloader screen that i can barely read. It says ........code error please try again. what should i do?
Young_e said:
i wasn't in gsm mode and once i flashed the radio, it went to 100% errored out and now i have an error message behind my bootloader screen that i can barely read. It says ........code error please try again. what should i do?
Click to expand...
Click to collapse
learn to read... it does say "it won't work if you're not security unlocked"
when they were handing out brains, what were you doing? having a piss?
Olipro said:
learn to read... it does say "it won't work if you're not security unlocked"
when they were handing out brains, what were you doing? having a piss?
Click to expand...
Click to collapse
why so much disrespect? I already security unlocked my device that wasn't my problem. I thought i had an issue because i flash the radio without being in GSM mode and She posted the iformation about that after i already downloaded the radio and flashed it. i just flashed a rom and it seemed to fix the problem. I had no idea you we so evil olipro that was definitely uncalled for
Can't we all just get along?
thanks again for your work olipro & cmonex!
Olipro said:
learn to read... it does say "it won't work if you're not security unlocked"
when they were handing out brains, what were you doing? having a piss?
Click to expand...
Click to collapse
over 1800 posts and you speak to ppl like that? i know it can be hard dealing with noobs but that was uncalled for.
Young_e said:
why so much disrespect? I already security unlocked my device that wasn't my problem. I thought i had an issue because i flash the radio without being in GSM mode and She posted the iformation about that after i already downloaded the radio and flashed it. i just flashed a rom and it seemed to fix the problem. I had no idea you we so evil olipro that was definitely uncalled for
Click to expand...
Click to collapse
oh grow a sense of humor for christs sake, if I was intending to disrespect you, there'd be worse flying your way, the regulars will assure you of that.
anyway, I can assure you, if it failed to flash, then you're not security unlocked (if we assume you didn't knock the cable out)
Olipro said:
learn to read... it does say "it won't work if you're not security unlocked"
when they were handing out brains, what were you doing? having a piss?
Click to expand...
Click to collapse
+5400 points for this lol almost fell off my chair
Olipro,
I went to the unlocker website entered my IMEI and paid via PayPal Transaction
ID: 9BN694576Y515383Y.
I tried running the unlocker and skipped step 1 since I had already done the HSPL. Went to step 2 and gave me the "This program has encountered an error" Report to MS or Dont Send the report" I chose "dont send the report" and the program closed.
I am in GSM Mode and with the SIM inserted.
Am I missing a step? Thanks!!!
Edit: The problems above occured in an XP machine. So I went to my Vista machine and it all seem to have worked there (the unlocker part). I try to stay away from Vista when flashing but for some odd reason it worked there and not on XP. Now I will try to flash the radio. Thanks!
Olipro said:
oh grow a sense of humor for christs sake, if I was intending to disrespect you, there'd be worse flying your way, the regulars will assure you of that.
anyway, I can assure you, if it failed to flash, then you're not security unlocked (if we assume you didn't knock the cable out)
Click to expand...
Click to collapse
im no noob by any means neccesary i am usually on ppcgeeks. But i made my donation and flashed the RhodiumWUnlocker that was e-mailed to me. Doesn't that security unlock the device?? Also can i run the radio with the sim card that sprint provided or do i need an at&t or t-mobile sim card??
Olipro said:
oh grow a sense of humor for christs sake, if I was intending to disrespect you, there'd be worse flying your way, the regulars will assure you of that.
anyway, I can assure you, if it failed to flash, then you're not security unlocked (if we assume you didn't knock the cable out)
Click to expand...
Click to collapse
It's true people, you should see him in the kitchen. Brutal.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just want some clarification before I try to install this if that's OK. I have a Sprint TP2 and I've installed the unlocker. I've successfully flashed the ROM so I know I'm good there. So just to make sure, I can install this radio and everything should keep working fine, and I should be able to use US SIM cards? Sorry if this seems like a dumb question.

New to ROM update, need help

Hi all,
I have read alot of your articles to update to WM 6.5. I have a Palm Treo 750I downloaded the CeetahUnlocker.exe and the Cheeimg.nbh. I ran the CeetahUnlocker.exe and clicked on the "Flash SPL" which after my second try worked fine. My phone boots with the Palm logo and not the AT&T logo it initially had. The other thing when I hold the media key and do a soft reset the phone enters the Bootloader program, therefore I think the "Flash SPL" went okay. The problem I am having is that the second step "Unlock Radio" does not work that is a ERROR message happens after the phone goes into the Bootloader mode. Can you guys tell me If my phone was unlocked to use my local carrier do I have to unlock the radio ect. Please help as this is becoming very fustrating.
thank you in advance
Anthony
Come on guys... anyone, someone pls help...
Hi, u just need to use the Athena_unlocker at that point to unlock ur carrier and thats it
I bought my phone unlock so do I still need to do this. Their are 2 Carrier in my country and I can use the simm card of anyone of them...
If your phone was unlocked, then you don't need to do it again. Flashing ROMs using Hard SPL will not change its status in that regard.
Can you tell me then the steps for updtaing to WM 6.5 please
Assuming you have correctly run the HardSPL, there are many threads in this section that describe how to flash a ROM, so there's no reason to re-hash the instructions yet again here.
Pick your preferred version of WM6.5 (keeping in mind they all still have major bugs) and flash it. If you don't like it, then keep trying until you find one you like.
The WM6.1 ROM is the most stable and bug free however, just as an FYI. The WM6.5 ROMs are fun to play with, but I wouldn't recommend them as a permanent install for most people unless the known bugs don't affect functions you regularly use.

[Q] Why can't Mobilicity (MPL100) with SPL 1.24 accept HARDSPL?

Moderator, please do not delete/lock this topic, I know that there is a separate one for HardSPL however considering how many people with Mobilicity HTC Snap are encountering the same problem I think that we deserve a place to discuss this particular issue.
Here is how it goes for me:
1) Attempted creating a GOLDCARD (just in case, to avoid bricking my device which happened to other ppl here). Not possible, the new PSAS does not allow creating a Maple goldcard with a Maple device (why?). I created one for G1 from their website but I wouldn't risk using it unless I really have to.
2) Followed all the instructions for HardSPL using 1.17. Everything went well until the point where it asks to confirm USB Connectivity. The update utility was not able to find the device. I disconnected and reconnected it. Windows 7 installed a new driver. Then I ran ROMUpdateUtility again. This time it found the device but the screen was a bit weird (flashing from image empty to image version 1.0.00). Anyway, I proceeded and it finished with 100%. Then it restarted the device. In the bootloader the SPL is still 1.24 like everybody else is experiencing, no changes.
3) Repeated using 1.19 . Exactly the same results.
Questions: is it possible that this has something to view with the custom Mobilicity ROM (which is nowhere to be found on the HTC website)? May be JumpSPL only works with Generic/T-Mobile WinMo ROMs?
Given how many people here are having bricked devices and HTC/Mobilicity don't care to release the shipped ROM, would it be reasonable for us (as a group) to ask the PSAS guys to make a page like http: //psas.revskills.de/?q=goldcard for the Maple? My understanding is that if you have a goldcard you can load a ROM which doesn't match your CID, i.e. people with bricked Mobilicity devices will be able to load the Wind ROM and still have a usable HTC Snap 3G.
I second that!
Yes, Mobilicity users need some fix to this problem. Is there a workaround that will allow installing the Wind Mobile one (which is the exact exact same but sold as Maple instead of Snap) since the Mobilicity Snap is the like the only phone on htc canada's website with no ROM download.
But don't you need to HardSPL your device before you can install the Wind ROM?
I have broke it!
How can I can resurrect?

Demo htc one a9

I have a question about making a demo htc one a9 into a working normal phone.
I found this
http://forum.xda-developers.com/one-...etail-t3269515
and many other guides about how to do that.
The general problem for me is that I simply cannot access the developer options
(or to be more exact, turn them on from the right corner of the dev options menu...everything but "running services" is gray and can't be clicked).
Is there a way to turn them on so I can turn OEM uncloking on to unlock bootloader via HTC support
as it seems that it's the only option to access fastboot to install twrp and root this device etc.??
Thanks in advance.
I'm not exactly sure, but I believe the demo HTC One A9 is running a different software altogether. I think you have to run an RUU to bring it to a non demo phone, although like I said,I'm not sure, I've never done it before
I now tried installing a new RUU to the phone, but the problem is that no version seems to suit it!
I always get the fail message when trying the SD card method.
"10 RU_MODELID_FAIL modelid in android-info mismatched" (x3 times)
What does this mean? do I still have the wrong RUU? I tried many from here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344, including all the european versions I could find.
(Including the one where CID HTC__002 is shown).
EDIT:
As I can't use fastboot I tried finding out CID and MID using adb shell resulting:
CID = HTC__002
MID = just no answer here...
In the phones identity it says the Model number is same as the phones name (HTC One A9).
Phone number is unknown, IMSI is unavailable, bluetooth adress is unavailable...
Kernel version 3.10.73-perf-gb10289f
Baseband version [email protected]_29.05_F
Build number 1.10.401.7 CL635503 release-keys
Software number 1.10.401.7
Android 6.0, HTC Sense 7.0_g
Maybe a stupid question, but did you try typing 10 times on the build nr in the info and software section to get the developer option running?
Sent from my HTC One A9 using XDA-Developers mobile app
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just there where build nummer is written.
Sent from my HTC One A9 using XDA-Developers mobile app
Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.
chargoal said:
Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.
Click to expand...
Click to collapse
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.
CSnowRules said:
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.
Click to expand...
Click to collapse
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.
chargoal said:
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.
Click to expand...
Click to collapse
As far as I know, the only way to make the phone as if it were a stock retail device is by going s-off to change the CID. I haven't heard of Sunshine failing. It does checks to make sure it will work and doesn't charge you unless it will.
You can s-off, change CID, flash appropriate RUU, then s-on and have a completely stock, retail-converted device.
I wouldn't go back s-on if the phone is for your personal use.
Refer to the convert to unlocked thread.

Categories

Resources