{
"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?
Related
[REF]Difference between SPL 2.20.000, 2.21.0000 & 2.26.0000 (Do you have 2.28.0000?)
If somebody wants to try it, here are the SPL updates stand alone:
-----------------------------------------------------
ELFIN SPL ONLY, DON'T TRY ON ELF.
-----------------------------------------------------
NEW VERSION UPDATED!!! SPL 2.26.0000 (hacked for CID UNLOCKing) by htctouchp
Confirmed post working here
SPL 2.26.0000 (Original)
SPL 2.21.0000 (Original)
SPL 2.20.0000 (Original)
SPL 2.20.0000 (hacked for CID UNLOCKing) by djvw
----------------------------------------------------------------------
NEW!!! ALL OF THEM one package here SPL_UPDATES
----------------------------------------------------------------------
It's an update so if you have a successful flash, u will not loose your data.
LAST TEST RESULTS: (More info @ post 72 and post 73)
{
"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"
}
If you want to share a different SPL Version, try this (THX @ kokotas):
Code:
pmemdump.exe 0x8c000000 1048576 SPL.nb
or run the included bat file.I think it's going to work!
DumpSPL.zip
Code:
NOTE: I WILL NOT TAKE RESPONSABILITY for dead devices, i did it
because i have my original ROM in case of everything comes wrong, but the
device its working ok with IPL 2.20.0002 and SPL 2.26.0000.
Flashing original SPL turns CID LOCK again your device.
-------------------------------------------------------------------------------------------------------
EDIT 04-07-08: PATCHED SPL 2.26.000 ADDED AND TESTED
I'll try to see whats the difference following the relevant thread SPL effects on ROM. Of course everyone can do that and feedback!
BTW, nice subject chosen CyZeeK!
Regards!
kokotas said:
I'll try to see whats the difference following the relevant thread SPL effects on ROM. Of course everyone can do that and feedback!
BTW, nice subject chosen CyZeeK!
Regards!
Click to expand...
Click to collapse
Thanx!.
Im updated the thread adding the 2.21.0000 and 2.20.0000 versions too.
I descarted GXMark because after serveral tests it gave me the same mark for every SPL version.
Well i did a benchmark using GAPI Benchmark on a cooked lite rom and tested 3 times on every SPL version.
So this are the results:
CONTINUE...
...more results
Now im trying SPB Benchmark, i will post results asap.
I have SPL 2.28.0000...
prieditis said:
I have SPL 2.28.0000...
Click to expand...
Click to collapse
I have a little question,
If I lash the highest versions, can I change the room any time I want or I have to do one more time the CID unlock...
thx a lot and sorry about my English.
Silly question:
How do one verify the SPL version AFTER flashing? I don't see the SPL version listed under Settings;About or Settings;DeviceInfo.
I do see a ELF_USPL_v1.n on my RUU directory, where I have my flash image.
Can I tell the version on that file?
First of all, Great work CyZeeK! Now we only need someone to patch the 2.26.0000 SPL for better performance
eXPerience1983 said:
I have a little question,
If I flash the highest versions, can I change the rom any time I want or I have to do one more time the CID unlock...
thx a lot and sorry about my English.
Click to expand...
Click to collapse
Of course CID unlocking is needed every time you "overwrite" the patched SPL, either you upgrade or you downgrade SPL!
Regards!
mr_ding said:
Silly question:
How do one verify the SPL version AFTER flashing? I don't see the SPL version listed under Settings;About or Settings;DeviceInfo.
Click to expand...
Click to collapse
Enter bootloader
mr_ding said:
I do see a ELF_USPL_v1.n on my RUU directory, where I have my flash image.
Can I tell the version on that file?
Click to expand...
Click to collapse
If you open it with a hex editor you'll see the version even though it's a patched SPL.
Regards!
kokotas said:
First of all, Great work CyZeeK! Now we only need someone to patch the 2.26.0000 SPL for better performance
Please try to dump it and post it here for the test!!!
Grab the attached zip, extract it on your pc, connect your Elfin to the pc and either type in cmd:
Code:
pmemdump.exe 0x8c000000 1048576 SPL.nb
or run the included bat file.I think it's going to work!
If it doesn't we need someone to help with the correct address!
Of course CID unlocking is needed every time you "overwrite" the patched SPL, either you upgrade or you downgrade SPL!
Regards!
Click to expand...
Click to collapse
Thnx bud. and thx to share how to dump the SPL, because i seen many other versions, good stuff for the people who want to share that versions.
I noticed a little boost in Elfin performance with SPL 2.26.0000 and it's true that you have to CID unlock again if u want to up ROM from SPL 2.26.0000
The newest version of SPL is 2.28.0000 and you cannot CID unlock from SPL 2.28.0000, is it?
Ryu Kenshin said:
I noticed a little boost in Elfin performance with SPL 2.26.0000 and it's true that you have to CID unlock again if u want to up ROM from SPL 2.26.0000
The newest version of SPL is 2.28.0000 and you cannot CID unlock from SPL 2.28.0000, is it?
Click to expand...
Click to collapse
Theorically you can, but i can't proof it because i don't have that version.
Please correct me if I am wrong; I am now using SPL 2.20.0000 to flash ROMs, and according to the test result in this thread, if now I switch to SPL 2.26.0000, and flash the same ROM as what I do in SPL 2.20.0000, and I may gain some performance due to the SPL difference ?
chihliouma said:
Please correct me if I am wrong; I am now using SPL 2.20.0000 to flash ROMs, and according to the test result in this thread, if now I switch to SPL 2.26.0000, and flash the same ROM as what I do in SPL 2.20.0000, and I may gain some performance due to the SPL difference ?
Click to expand...
Click to collapse
I am assuming that is the case. I'll try flashing 2.26. Thanks Cyzeek!
EDIT: So far so good! Haven't really noticed any speed changes from 2.21... but I got a baby on my lap so I can't really analyze it at the moment
didnt anybody try to hack the 2.26.0000 version for CID unlocking as yet?
Hey guys is it ok to add these SPL files to the ROM Builder in the htcrt.exe tool when we make our backup ROMs? Or will it brick the device?
I was thinking of making a new backup of my Rogers Elfin with the 2.26 SPL -- all in one ROM.
htctouchp said:
didnt anybody try to hack the 2.26.0000 version for CID unlocking as yet?
Click to expand...
Click to collapse
You mean 2.26.0000 version is NOT yet CID unlocking ? then how to use this SPL for flashing ROMs ?
chihliouma said:
You mean 2.26.0000 version is NOT yet CID unlocking ? then how to use this SPL for flashing ROMs ?
Click to expand...
Click to collapse
this SPL can not be used to flash ROMs as yet. u've to go back to 2.20.0000 SPL for flashing the ROM.
htctouchp said:
this SPL can not be used to flash ROMs as yet. u've to go back to 2.20.0000 SPL for flashing the ROM.
Click to expand...
Click to collapse
Then I am confused. I thought I may use 2.26.0000 to flash any ROM (and gain some performance) just the same as what I've done by using 2.20.000 to flash ROM. So how can I get the performance gain of 2.26.0000 at this moment ? Just run the RUU file inside or what ? But if I want to flash to other ROMs, I need to run the RUU file of 2.20.0000 again in order to switch back as what you said ?
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
[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.
Hi i'm going to get chevronwp7 when the tokens come out again as the unlocking problems here don't work on my phone and i'm wondering can I use homebrew? apps if I use chevronwp7?
I'm new to this stuff
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
GoodDayToDie said:
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
Click to expand...
Click to collapse
Ok thanks and HTC HD7
The HD7 actually can be interop-unlocked, but you probably need to downgrade its firmware (if you look under Settings -> About -> More info, check the Firmware version number. If the third cluster of digits is greater than 50000, you'll need to downgrade). HTC "fixed" the driver we were using to make registry modifications, including interop-unlock, some months back.
The HD7 can also run (many!) custom ROMs, if you decide to go that route. You'll probably need to downgrade the bootloader, also called the SPL (look for the bootloader version, if it's greater than 3.1.x you'll need to downgrade, if it's greater than 5.0 you'll need a couple cheap pieces of equipment to do it). Custom ROMs are typically "fully unlocked" and can run anything, even including some software ported from WinMo 6.5.
GoodDayToDie said:
The HD7 actually can be interop-unlocked, but you probably need to downgrade its firmware (if you look under Settings -> About -> More info, check the Firmware version number. If the third cluster of digits is greater than 50000, you'll need to downgrade). HTC "fixed" the driver we were using to make registry modifications, including interop-unlock, some months back.
The HD7 can also run (many!) custom ROMs, if you decide to go that route. You'll probably need to downgrade the bootloader, also called the SPL (look for the bootloader version, if it's greater than 3.1.x you'll need to downgrade, if it's greater than 5.0 you'll need a couple cheap pieces of equipment to do it). Custom ROMs are typically "fully unlocked" and can run anything, even including some software ported from WinMo 6.5.
Click to expand...
Click to collapse
?? How do you down grade firmware ??
Either roll back to an old backup, or re-flash the phone with an older ROM. The first option loses any data changed or added since the backup was made, though, and the second option wipes it all (hard reset).
In theory it should be possible to downgrade just the firmware (not the entire ROM) without wiping the phone, but if anybody has found a way to do so, I don't know of it. That doesn't mean much though; I'm not terribly knowledgeable around flashing the phone.
sinister1 said:
?? How do you down grade firmware ??
Click to expand...
Click to collapse
Did you ever find a Mango Verizon Spark stock rom and try reloading?
LiFePo4 said:
Did you ever find a Mango Verizon Spark stock rom and try reloading?
Click to expand...
Click to collapse
No I have not.
sinister1 said:
No I have not.
Click to expand...
Click to collapse
I was digging around XDA to find one to have on hand "just in case". I came across this thread;
http://forum.xda-developers.com/showthread.php?t=1254384
Went to this link;
http://www.filefactory.com/f/0dacfac3a33cc378/
And from reading the thread this is the one people used early on to upgrade VZW Trophys to Mango;
RUU_Spark_W_S_VERIZON_WWE_2.01.605.04_2K_new_partition_...
What confuses me is the other ones; are they NoDo original (the 1.xx ones)? And the second one could be the Mango one that also pushed the HTC Gen 1 drivers (which are fine) since it is slightly larger file size and has Radio in the file name...
GDTD - ideas?
You could try but I don't know.
EDIT: Read this post! The one file above is the one. It looks like from the date in this thread the one with Radio in it is the Gen2 drivers (don't want that). This thread also explains the other ones (1.xx).
http://forum.xda-developers.com/showthread.php?t=1427904
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
{
"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"
}
Andy8888 said:
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
Click to expand...
Click to collapse
Sinister1 and I are both on VZW Trophy (CDMA) phones and AKAIK no one has done a homebrew or custom ROM, so we are sort of screwed. We have Stock ROMs; that's all that's out there. DFT at one point said they were working on custom CDMA ROMs for the Sprint HTC Arrive and VZW HTC Trophy but they really have no way to test or use it so why would they.
---------- Post added at 09:08 PM ---------- Previous post was at 08:45 PM ----------
I edited post 9 so make sure to read it again if you haven't. The stock NoDo and Mango ROMs are there and I explained how to look for them.
im kind of confused. i want to roll back to the stock rom of my hd7 and these ospl, hspl is confusing (probably because im noob to this).anyway, i do have the stock rom by anzar and i want to flash my hd7 the stock rom, but the confusion worries me. the reason why i want to downgrade is my phone is kinda laggy now and always hard resets by itself.done all the ts provided to me by the htc tech rep and none of them fixed the problem. im thinking of flashing the stock rom and upgrade to mango from there (leaving out internet sharing since i dont need it and the device's mac address changes which i dont want my phone to do)
can i flash my hd7 (tmous) with the rom from anzr without downgading bootloader, spl's etc?
OS Version: 7.10.7720.68
firmware revision number: 2250.21.51004.531
hardware revision number: 0002
radio software version: 5.70.09.02a_22.51.50.21u
radio hardware version: a.12.0.d4
bootloader version: 5.10.2250.0(132968)
chip soc version: 2.2.5.0
thanks in advance for any reply or comment regarding this post
Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
Here is a picture of my HBoot
{
"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 was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,
Halim2k said:
Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
I was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,
Click to expand...
Click to collapse
That's tough to answer without testing. It "SHOULD" be safe but without testing there's no way to know for sure.. the drivers that come with your hboot may or may not mesh well with the roms since they are typically based off aT&T or Telus Roms.
Strange... Two posts about this phone within 24 hours. As exad said, it SHOULD work, but nothing is guaranteed. If you would be our guinea pig, then it would help out numerous other people. If you don't feel comfortable doing that, then it's totally understandable.
Yrah and that makes it three posts within a week. I wonder if it's just been released recently.
Sent from my Evita
---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------
Here's that other thread I was talking about before, this guy says he was able to flash our ROMs onto his Evita UTL.
http://forum.xda-developers.com/showthread.php?p=43237946
Sent from my Evita
It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.
Halim2k said:
It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.
Click to expand...
Click to collapse
For the 3.18 software on our phones, it bricks if you RUU while S-ON with 11111111 or 22222222 as the CID so just be mindful of this as i imagine the latest RUU for your device, if you find one, will probably behave similarly.
Just out of interest, I had a look around. On the RUU collection thread there is a HTC GCC (Gulf Cooperation Council) RUU section which seems to fit your device with a CID of HTC__J15.
Please listen to Exad and be careful, because running an RUU with the wrong setup on your phone can definitely brick it.
EDIT: it looks like the RUU listed for your phone on the link above is lower than your current firmware configuration. Interestingly enough though, it seems to share the 1.14 hboot that our device had, which is positive.
Sent from my Evita
Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.
Halim2k said:
Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.
Click to expand...
Click to collapse
Correct! Once you're S-OFF you shouldn't have any problems RUUing at all. If you don't mind, I'd love if you update this post regarding stability of our Roms on your phone after you've had a chance to try one for a couple days.
Sure, I'll update the post tomorrow.
What's revone s-off? There's only one working s-off method for the XL and it's called Facepalm, it can be found here.
Sent from my Evita
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.
Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.
Click to expand...
Click to collapse
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.
Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Click to expand...
Click to collapse
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
So true! I suppose I didn't stress this enough. Especially since JET tool does purposefully brick the phone in order to write an older Hboot. Though, theoretically even if it did brick, it should not be so far as the unbrick evita thread wouldn't be able to restore it. This of course does not make it any less dangerous. Just saying.
OP does seem to be knowledgeable, which is the only reason I am pointing out these more advanced methods that may work.
I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.
exad said:
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.
Click to expand...
Click to collapse
I red JET tool thread, and for sure it will hard brick my phone.
timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, I tried revone as I was almost 99% sure it's safe, as it's not envolving any HBoot flashing.
twistedddx said:
I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.
Click to expand...
Click to collapse
Thanks for the info.
I spent the last 2 days searching and reading about this variant, and you are right.
This one has TD-LTE support, and it is different than any other variant, and of course we can't cross flashing boot image.
That is why I think 4G LTE will not work with cooked ROMs.
Also without a proper backup, there no way to go back to stock firmware, as this firmware version which is "1.01.401.03" is the initial release.
Now my most important concern is to find stock RUU or OTA for this variant, which I really appreciate any help about it.
I would ask tour carrier about it. They should have an ruu or ota. If you can extract the radio you should be able to run our roms
Sent from my One X using xda app-developers app
Just some more random info. The source for this device and software version was released in March by HTC. HTC dont have a habit of releasing source prior to the release of the device.
When it first got released it caught my eye because of the software version not matching the existing pattern and the T in the model.
Maybe you can find someone with a bit of spare time to compare what can be found in the kernel for differences to the evita_ul.
http://dl4.htc.com/RomCode/Source_and_Binaries/evitautl-jb-crc-3.4.10-cl141628-1.zip
Also seems like a prerelease 1.00.401.01 existed.
mid is reported in other forums as PJ8350000
@guys
Need ur help in restoring my bricked phone! HTC EVA_UTL, i did was s-off and then tried to flash the "RUU_Evita_UL_Vodafone_DE_1.82.162.4_Radio_0.17a.32.09.04_T_10.85.32.16L_release_260067_signed" thru SDCARD method and when it asked me to confirm to update by pressing the volume up button, i did! and it just satrted flashing the first part and then went dead!
so i would like to know if there's a way to fix it by copying it from other same model phone or any thing?
pls inform?
WBR
ReyTech.