Help
I posted this in PPCGEEKS
I have a NZ Telecom Apache that would only upgrade with the telecom AKU202 kit.
Others (ppckitchen tetc) said "wrong rom for this device" and I wanted more so I used the "bootloaderfix" and it upgraded my bootloader from version 1.00 to 1.02.
Now I can't flash any roms -they all say they are "wrong rom for this device".
Is there anything i can do or is this now a brick?
Related
i'm trying to upgrade a second hand bought qtek s100 (presumably a magician). i hoped it would be a piece of cake, being a qtek device (thus sim and cid lock free). the simlock part is correct, any sim will work. but the cid lock free part does not hold. i tried several rom upgrades from the shipped rom section on the xda server:
nl113 rom (i think this is the tmobile rom)
the uk wwe 112 rom
the wwe 112 rom
the wwe 113 rom
and so on.
i also tried the xda unlock tool, hoping that i made a mistake and that something was still locked. after running it, it told me that unlocking worked (but it was already simunlocked to begin with). but still afterwards, running any of the above roms still didn't work. still country error.
with all the roms i get an country 112 error. even with the original qtek roms? i tried both the uk and wwe rom (not quite sure if this is a native dutch s100 or an expansys (uk) s100). did not matter, both didn't work. never had so much problems with my mda vario.
current rom is radio version 1.05.00
protocol version 1337.39
rom version 1.06.00wwe
extromversion 1.06.154wwe
maybe someone can shed some light why my qtek s100 does not take any of the shipped qtek wwe roms?
many thanks for reading my thread (and hoping for your suggestions)
solved it. just needed to run the MaUpgradeUt_noID.exe. then it stated the current rom and so on, after which it gave an country error while putting it into bootloader menu. then i ran MaUpgradeUt_noID.exe again while the qtek was still in bootloader menu, now the summary sheet stated blank at the rom version and so on. now it was able to upgrade correctly. for those like me who have the same problem, just run MaUpgradeUt_noID.exe twice and immediately after the first attempt!
Hi All
I had a problem with my TyTN II camera it was showing horizontal and vertical lines. So i sent it for repair and they replaced the camera.
It looks like they have reflashed my device to a different boot loader and changed the CID to a HTC test device. This is a full production release device that I bought from Expansys UK
Once I noticed a problem when I tried installing TomTom from the CD. It gave me an error. "Unable to install application. Please update your device ROM to the required version before trying again." I checked Model No in Device Information > Identity and it shows "Kaiser" I am not too sure but I thought this was KAIS130 before I sent it for repair, can someone confirm what it shows on your TyTN II.
I then tried to flash the HTC WWE shipped ROM and it gave me invalid vender ID.
Went in to bootloader and noticed at the top of the screen it shows "Security Unlocked" see attached image I have never seen this before what does this mean.
mtty commands shows.
info 2
HTCSTEST1234 ‹q:HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300TS13HTCE
Cmd>
What does this security unlocked mean?
Will bootloader which is security unlocked be any use to the ROM cookers on here?
Should I complain and send the unit back to get reflased?
Just Flash HardSPL which can be found in the sticky's in Kaiser Uprading and your good to flash any rom you like!
That is what i was planning to do use HardSPL.
But will this mean i will not have a shipped ROM matching my CID if things go wrong in the future.
Can some one please confirm what model it shows on a TyTN II on Settings > System > Device Information > Identity
on mine (ITA version) Model is Kaiser.
If something goes wrong at this point you can just flashg back to the old SPL using the custom wrapper. Before you flash any ROM your best bet is to instal HardSPL your just asking for trouble if you don't period.
Dils, were you able to fixed your tomtom problem? If not, i suggest you send it back to HTC service center so they can fix your problem.
Hi mates. i was using tnt series wm6 rom. and i just tried to upgrade to faria's rom using shell tool. and after non successful upgrading now. when i start my wizard it stuck on boot screen. with this info.
ipl : 3.08
spl: 3.08
Gsm : 2.19.11
OS : 2.18.0.0
i tried a alot installing original t-mobile shipped rom but it says the update utility is not for your device.
i tried a lot installing other roms using shell tool. but all return this screen. so please let me know. how i will completly flash this thing..
Kind Regards
Tell us smth more
Are you using Windows Vista on your PC.
If you do, do some search around to find how to update from Vista in Bootloader Mode, as Vista can not talk to the phone on that state
Aldo
thanks bro., i am using wondows xp. and i tried all shipped original t-mobile roms. and all i got this message" the update utility is not for your device" i think this error is due to i upgraded my ipl and spl to 3.08. before i have 2.26
i also tested with wizard service tool. and its also not detecting the device in boot loader mode.
so please let me know. what i will do. and which rom i will try to fix that issue.
ruk_design said:
thanks bro., i am using wondows xp. and i tried all shipped original t-mobile roms. and all i got this message" the update utility is not for your device" i think this error is due to i upgraded my ipl and spl to 3.08. before i have 2.26
i also tested with wizard service tool. and its also not detecting the device in boot loader mode.
so please let me know. what i will do. and which rom i will try to fix that issue.
Click to expand...
Click to collapse
My friend have you already done the reviving techniques included in this tut?:
http://forum.xda-developers.com/showthread.php?t=298613
G3 or G4 device?
For the last couple days I've been trying to reflash a TP2 I have lying around, and I've run into a host of problems. The most current problem is that while flashing from the SD the update will complete the bootloader, splash 1 and splash 2 and then fail at the Radio. I am stumped.
After the fail I've used mtty to reset the RUUNBH flag, and then tried again.
I've tried the factory signed roms for sprint and verizon with no difference. This device is security unlocked, but does not have HSPL (nor can I get HSPL to load via USB, and can not find an SD solution).
This hardware is an unbranded pre-production device (RHOD400), currently running SPL 0.63
Any ideas would be appreciated.
--fail screen--
00018003
RHODIMG.nbh - FAIL
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
RADIO -FAIL
OS -
Update Terminate
UPDATE FAIL
I've tried flashing a few different radios, but haven't had any success as of yet.
The Sprint, Verizon, and Telus shipped signed roms all get to the radio portion of the flash and fail.
Running the manual HSPL flash gets the device to show the percent complete screen, but it never goes beyond 0%.
Any direction would be appreciated. I'd love to get this unbranded device working again.
ur phone has to be HARD-SPL'd before flashing a radio i thought? if ur running SPL0.xx then i dont think it will work...
So I have been spying here on xda a few months now since I got my trophy off ebay. There are custom roms here that I wanted to try so I followed guides to RSPL and HSPL. So I HSPL'd my trophy and installed ansars unbranded trophy rom with 1.09 this worked and got my bootloader replaced by 1.09 instead of HSPL.
Then I had problems with the marketplace giving me errors so I had to revert back to my original rom which was DE so I flashed it straight to the phone without HSPL. Now the rom installed fine, only my bootloader now says:
Ç ÊÀ-|Eï SS-BC (4K)
SPL-1.9.2250.0(109882)
MicroP(LED) 0x09
TOUCH A19v10,20)
What I believe is that Ç ÊÀ-|Eï should say PC40100.
Now I cannot install the stock rom or any other rom, or even hspl as it gives out vender/model id error. I have tried goldcard with the trophy but it gets stuck at "checking".
Can anyone help me?
Willing to donate to the person who can help me.
The only fix I know of for that state is to install a stock bootloader update. You might be able to find one in the CAB list thread on the dev&hacking sub-forum, or you may just need to wait. I've only seen it reported once before, but an official bootloader update fixed it (of course, you'll need to downgrade the bootloader again).