Database Info

6.0 flash that isn't resulting with 6.0

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

SPLs for DREA100 & DREA110 (Orig, Eng, Hard) [updated 2009-05-12]

{
"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"
}
SPLs for DREA100 & DREA110
About SPLs
This thread contains information and downloads for SPLs for the HTC Dream (aka T-Mobile G1 and ADP1). What is a SPL? The SPL, or Second Program Loader, in conjunction with the IPL comprise a device's bootloader. Aside from bootstrapping Android, the bootloader also fulfills various diagnostic functions. One of these functions is the manipulation of data in the device's internal flash ram. Depending on the SPL installed, the user can apply a signed NBH file, flash nand images, and more. Note that the SPL is installed and operates independently of the Android build that runs atop it.
Currently there are three SPLs available. The G1 variant is the SPL that is installed in stock T-Mobile G1 phones. The Engineering variant is found in the Android Dev Phone 1. Finally, the HardSPL is a modification of the Engineering variant by cmonex, with additional hacker-friendly functionality. HardSPL is the recommended SPL.
Installation
The SPLs are packaged in the familiar update.zip format and install from the recovery console in the same fashion as other update files.
0. This is only verified to work for DREA100 and DREA110 devices. If you have a US or EU G1, it is most likely compatible. To check, boot into the SPL and confirm that the first word is DREA100 or DREA110. Please do not attempt to flash a SPL onto a Dream that does not fit that description!
1. If you are installing onto a G1, your G1 must already have been "rooted" or otherwise have test-keys installed. ADP1 is exempt from this.
2. Download the desired SPL zip file (attached below), rename it to update.zip and copy it to the root of your sdcard. As usual, remember to use a USB cable with a ferrite core and dismount your USB drive before disconnecting.
3. Reboot the phone into recovery console and flash the update with Alt+S.
4. To confirm it has installed properly, power on the G1 with BACK + END to enter the bootloader. When you are done, press CALL + MENU + END to leave the bootloader.
5. To revert a G1 to its factory original SPL, simply apply the G1 Original SPL file.
HardSPL (recommended)
VER: HSPL10.95.3000
ZIP: splhard1_update_signed.zip
MD5: 6502af25b9e9fbe1322cc405559af1ca
HardSPL is a modification of the Engineering SPL by cmonex. In addition to the functionality of the Engineering SPL, HardSPL also allows NBH files to be used without matching the CID (carrier ID) check. At the current time the main benefit of this is to allow European G1s flash American NBH files and vice versa. All other features and attributes of the Engineering SPL (such as the ability to flash the mtds from nand backup images) are present. Using the Nandroid backup scripts to create nand backups for this purpose is recommended.
Click to expand...
Click to collapse
Engineering SPL
VER: HBOOT-0.95.3000
ZIP: EngBootloader_v2_NoSigCheck.zip
MD5: 8008e01cb2c35e06b704e4dfb624ce4e
The Engineering SPL is a custom SPL installed in devices intended for Android development. It has existed since before the launch of the G1 and is now available to the general public as preinstalled on the Android Dev Phone 1, the official development device sold by Brightstar Corp. This SPL, in addition to flashing signed NBH files, can also flash nand dumps through the use of the fastboot protocol (as defined in the legacy bootloader documentation). This is a convenient way to flash the mtd partitions and can be greatly useful in the event that an undesirable build of Android is advertently or inadvertently installed.
This SPL was first originally dumped from a G1 which dream_kill received as a replacement from T-Mobile by cmonex and JesusFreke. The file was released by Disconnect on his webpage.
Click to expand...
Click to collapse
G1 Original SPL
VER: HBOOT-0.95.0000
ZIP: G1OrigBootloader_nocheck.zip
MD5: ae58b427b797707c453f3b3fa9d13c76
This is the original SPL which is installed in a stock G1. It is easily distinguished by the "trademark" red-green-blue bootloader screen which appears in many HTC phones. This SPL does not support the fastboot protocol and thus will not allow the user to flash nand backup images.
Before the leak of the TC4-RC29 and TC5-RC7 signed NBH images, users running stock RC30 and RC8 were unable to downgrade and install modified Android builds. On January 1st, 2008, xda-dev user chavonbravo leaked the aforementioned files, which allowed users to downgrade G1s through the original SPL. This SPL was dumped by damien667.
Click to expand...
Click to collapse
Download

awesome. anyone wanna try it first? I hope this gives us access to the bootloader?
anyway Dream_kill is probably one of the luckiest guy to recieve one as a replacement from tmobile. He should buy the lottery. lol

I just did it....no problems yet......
The update went really really quick.....
Woohooo...No problems! I see android skateboarding!
Thanks alot dream_kill, cmonex and JesusFreke,you guys are awesome!

mack said:
awesome. anyone wanna try it first? I hope this gives us access to the bootloader?
anyway Dream_kill is probably one of the luckiest guy to recieve one as a replacement from tmobile. He should buy the lottery. lol
Click to expand...
Click to collapse
I've tried it. It works. . Read the warning though, if something goes wrong during the flash, you'll probably have a brick.

Whatcha think, another couple of weeks before us unlucky ppl that got the official rc30 can have at least root? haha, thanks google you guys finally came to our rescue. and t-mobile thanks for your mistake!

I am still helpless!
Was Busy around some Issue Developers G1 is a Welcome though but would be Happy if they had allowed Official RC30 to Developers Edition after voiding Warranty also. Hey Google Are you Listening
Edited: on 1-1-2008 New year gift
Thanks ti RC29-NBH file I have root now on OTA RC30 and now converted phone to ADP1

Big question... does this change your build type?

neoobs said:
Big question... does this change your build type?
Click to expand...
Click to collapse
...kernel version now says...
2.6.25-01843-gfea26b0
[email protected] #21
build number says
kila-user 1.0 tc4-rc30 116143 ota-rel-keys,release-keys
...didn't check what they were beforehand.

neoobs said:
Big question... does this change your build type?
Click to expand...
Click to collapse
This only affects your bootloader (specifically the second program loader). The software stack above that (kernel and userland) is unaffected.

Great news...can't wait till someone figures out a way to get this on RC30(stock).

jashsu said:
This only affects your bootloader (specifically the second program loader). The software stack above that (kernel and userland) is unaffected.
Click to expand...
Click to collapse
you really never know... for all we know it gathers that info from the bootloader.

Could this update be applied to a phone running the TC5-RC8 (JesusFreke version) Since this update only affects the bootloader I should be fine?

hey JF, if I install the engineering bootloader, can i put the stock bootloader back?

korndub said:
hey JF, if I install the engineering bootloader, can i put the stock bootloader back?
Click to expand...
Click to collapse
I'd like to know the same...

Done. Worked ok. Now the main question.
After I installed developer boot loader, do that means now what even if i'll install Official RC30 now, I still will have ability to reflash my system with modified.
The answers is 100% yes for me. But just to be 101% sure i am askin it.
Also. When I am booting with Camera+Power and getting those geeks on skateboards. It's said "no image" which image it's searching for? Where it's should be placed? Anything else what I could do from this "booting" mode?

And another question. Google should have it's own version of OS (/system) for developers phone, beside of "official rc30 for t-mobile, which have root blocked" is this native version published anythere?

To do anything with it you need the fastboot tool (built as part of the source tree). There is a cheat sheet up at www.gotontheinter.net that talks about how to use it.
As to the google official build... source.android.com. Although they are talking about adding a way for devs to install the closed source google apps.

what is the benefit of having this over the modified RC30?

In addition to, not instead of.
It lets you (safely) work on the kernel or platform. That is all really.

so if im not a developer there is no real benefit for me to upgrade to this version?

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.

[Q] RUU error 131

I want to send back my phone to htc because my earpiece is not working correclty. I rooted my phone with AlpharevX method. I wanted to go back to S-ON and stock rom so i dont void my warranty. I flashed 0.98 bootloader and the i run RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed but it stoped updating the phone and gave me ERROR 131. It changed bootloader and radio but my phone has no rom inside. What should i do now?
{
"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"
}

Wooow there is a big mess here!
First your phone is branded. You have to use the proper RUU. European won't do. Not true
Second you have used a leaked RUU firmware, posted by mdeejay so you should have used misc_version.
Third now you stuck without root so you have to use htcdev.com
Sent from my HTC Desire S

I thought my phone was not branded.... I should have checked that beforehand. I called HTC and they have the ruu for my phone but they wont give it to me... I'll try to find it elsewhere... not even htc has it on their site. If i get the old RUU will it flash the old bootloader and old radio? or im stuck on the new ones?

Sorry
I have checked and your CID is included in the European RUU. But still you have used the wrong RUU because 2.10.401.9 contains only the CID for Russia. The last GB RUU for the rest of the European region is 2.10.401.8
Anyway now even if you can get back the old 0.98 hboot you cannot use Revolutionary, because you need USB Debugging and an booted OS for it. With the Stock recovery you cannot use the misc_version. I am afraid the only way is htcdev.com flash a custom recovery, use the misc_version, relock the bootloader then go back to stock with a proper RUU. I hope they will acknowledge that your problem is hardware related and has nothing to do with the unlocked bootloader. But you can avoid that if you use older RUU (1.28 or 1.47) there is no Locked/Relocked line there

I run RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 everything went ok, phone booted. Ready to ship to HTC for repair! Thanks amidabuddha

ignited said:
i checked the EU ICS update and has my cid in there.... i flashed it and it updated ok... now it is booting....
Click to expand...
Click to collapse
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.

amidabuddha said:
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.
Click to expand...
Click to collapse
The ICS RUU is not official either?

ignited said:
The ICS RUU is not official either?
Click to expand...
Click to collapse
Well it is semi-official, so to say But should keep the warranty on the hardware.
Also the OTA way that I was thinking about has a 50 % chance to work, because it includes a modification of a signed by HTC zip.
So in any case the ICS RUU is the better option compared to htcdev.com unlock in terms of warranty. And the easier as well.
Good luck with the repair and sorry if I confused you somehow with my posts.

HTC INCREDIBLE S 710e
I follow the instructions to downgrade and s off my htc incredible s710e from this page.
http://forum.xda-developers.com/showthread.php?t=2118187
everything going quite right but during RUU installing i got an error message which says that this RUU is not suitable for you please select suitable RUU for your handset.
Igot RUU from this page.
http://d-h.st/vgw
now i want a Suitable RUU for my HTC.
HTC INCREDIBLE S 710e
HBOOT-2.02.002
RADIO-3831.18.00.11_M
eMMC_boot
May 22 2012
Android 4.0.4 (Ice Cream Sandwich)
Full HTC Sense 3.6 Interface
Multi-language (WWE)
softwre # 4.10.707.1
serial # ht23xtd11136
IMEI # 359836048384758

Wrong forum.This is Desire S.And delete serial and IMEI

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.