MDA-II upgrade problems (Noob) - MDA II, XDA II, 2060 ROM Development

Rom: 1.60.00 Ger
Datum (Date): 12/03/03
Radio: 1.06.01
Protokol: 1337.16
ExtRom: 1.60.08
---
At StartupScreen:
R 1.06.01
G 1337.16
D 1.60.00Ger
I have this T-Mobile Edition and try to upgrade this MDA with:
C_ShekharAKU3.5c.R40.P24_public
C_ShekharAKU7.0c.R40.P24_public
(Downloaded as recommandet here)
After doubleclick
Code:
HimaUpgradeUt.exe
the program start, but after a while it says, there is a error/problem, i should retry.
When I start to try something with the "bootloader" (on-switch, Action-button, reset) he explain me, i can´t install this version, cause the langua.
So pls. help a noob (first-timer of rom-modification), maybe u have a help-page in german too (Or step by step), cause all what i found at your wiki confuse me too much, cause i never heard somethin about this all - even how the extract a .nbf-file.
Thx for help

llbasha's guide
==================================================
6 steps to successfull Himalaya/WM2k5 upgrade.
==================================================
Note:
The Radio_.nbf is an optional component,
not included in this archive.
Get your favourite Radio ROM at http://buzzdev.net
====================================================================
1. Start your device in bootloader mode by pressing and holding down:
DPad + PowerButton + ResetButton
After a second release ResetButton, then release the rest of them.
Your screen will show word "Serial" at the top.
You are in bootloader mode now.
2. Place your device in the cradle, ensuring that the cradle
is plugged directly into a USB port on your PC and not to a hub
and that the power supply is connected to the cradle.
It is also a good idea to disable any screensavers on your desktop PC.
Once your device is cradled, the text on the screen will change to "USB".
3. Run HimaUpgradeUt_noid.exe
4. Sit back and wait for the Congratulations screen to be displayed
on your PC. Your device will still be displaying 'Upgrading radio stack, please wait',
but as long as the PC says it is done, then its all OK.
5. Detach your device from the cradle.
6. Now you have to hardreset your device.
Press ResetButton and hold down CameraButton + RecordButton.
Hold them pressed until the "Boot Options" menu appears on the screen.
Select the options as follows:
(for selecting use RecordButton, change values with CameraButton)
Enable KITL -> NO
Clean Registry Hive -> YES
Format Storage -> YES
When done, press DPad and wait until OS starts.

wow - ma, thx; perfectly :d:
It worked, no i have a version of 7.04.c, i guess win 6.0
---
Just few problems left:
1.) fixed
2.) Is there a german version anywhere???
3.) edit: my mistake; fixed
4.) I read, there is no problem of downgrade it (no, i don´t want), but from where i should get the german version for downgrading)
5.) My mda was without simlock (I could use every phonecard), i hope i still can ))
Edit2
6.) I have the program PowerLOC Destinator (a Navigation Program); when i would start, he tell´s me: Invalid PocketWizard Setup package
I guess Navigator is not made for win 6, cause the programm is the original sd-card
7.) At settings i can "switch" wlan; I guess this is just from the OS, cause as i know, a standart mda2 doesn´t have wlan
Background: A guy from phonecompany told me, that t-mobile, switched off the wlan-function, so that i customers doesn´tt know, that his pda can wlan (Branding of t-mobile); but the hardware is inside the pda; They made it at vario 2 and mda pro
Edit3:
Next Problem:
When i connect now the craddle with the mda, i get following error msg.
-Generic RNDIS (PROTOTYPE--Remember to change idVendor-
And ActivSync is not connecting
I duno, how to fix
ActiveSync 4.5 doesn´t work on my w2k-pc, and my mda sais he needs 4.5
With 4.2 and down, i can´tt connect the mda
Anyway, thx, thxy, thx, this was really a good describtion

Related

WALLABY BOOTLOADER V5.15

Hello, I have upgraded my Siemens SX56, to 2003,I had couple of problems with this Upgrade, I restar my computer but now my phone got 4 colors screen "Whit, Red, Green, and Blue" with the title Wallaby Bootloader V5.15 and at the bottom GSM OK, What should I do. Thanks.
Just make a soft reset wqithout pressing the power button....
HTH
Stefan
Thanks, but, how put in my phone?
Soft reset is placing stylus in the hole on bottom left of xda, if that doesnt work you will need to reflash your xda using sd card method.
Sorry.Now, I save, the file in sd card, this is corret? and then?
You have to use xdatools to write the .nbf file to sd card, choose your nbf file as source and choose the sd card as destination, do not use the browse button in the destination box, use the drop down to the left of it, this will show your sd card, once it is written you need to put it in your xda, then enter bootloader mode, it will ask if you wish to continue the flash, press the action key and it will flash the rom, make sure your xda is charged.
Ok, thanks again, now my phone, coming up, but only see on window the screen pocket pc 2002 "Tap the screen to set up your Pocket PC" but when I tap noting, ActiveSync is connected and up date mi pocket, I supposed, I see in my computer and synchronized all. I try again to upgrade and I receive this.
your current device information:
Model : PW10A1
ROM Version : 3.17
Language : English
Your upgraded image information:
Model : PW10B1
ROM Version : A.30
Language : English
Please download the compatible utility and try again.
How make now?....thank you againt.
Sorry, now I restart in the battery on/off switch side and coming up and work, but, is possible upgrade this version?
ROM Version: 3.17.03 ENG
Rom date: 05/15/03
Radio version: A.33.02
Protocol version: 1.3.3
One more question, this phone is only 900/1900 MHz Dual Band, is possible open to 1900?
Tanks

Where i can get this files for KITL mode

According to the http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i need to have "any valid signed dlls from a hermes/tytn device. You will need to copy that file 3 times and rename them to stk_service.dll, ril.dll and rilgsm.dll".
Please help me to find this files.
[email protected] said:
According to the http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i need to have "any valid signed dlls from a hermes/tytn device. You will need to copy that file 3 times and rename them to stk_service.dll, ril.dll and rilgsm.dll".
Please help me to find this files.
Click to expand...
Click to collapse
It's this "file"...not "files". Grab a Hermes. Copy a valid dll three times. Rename each copy. Do the kitl thing.
Ninja1
Could you please clearify what do you mean by.
Grab Hermes.
Copy a valid dll three times. Rename each copy. Do the kitl thing.
Another problem is that i have bricked HTC Tytn.
Help me please.
Another problem is, where i can get Full Version of Microsoft Plaform CE 5.0.
[email protected] said:
Help me please.
Another problem is, where i can get Full Version of Microsoft Plaform CE 5.0.
Click to expand...
Click to collapse
http://www.microsoft.com/downloads/...50-D311-4F67-9FB3-23E8B8944F3E&displaylang=en
if you try this method, you dont need valid rills.dll,
Here you are just creating dummy rills. This method will take some 2-3hours to compile but it should get you out of the sh!t if you have no valid files..
this quote taken from JBO
"I've unbrick my phone!! Type 2 i think (stuck on windows screen).
I've used the superdave's method with Platform Builder. So, the steps:
- Download Windows CE 5.0 Trial Edition. It's a 2.6Mb file but others components will be downloaded during install (around 2 Gb for me, so be patient!). Choose to install ARMV4I processor platform (not the x86 selected by default).
- Run Platform Builder, File menu -> New Platform
Select "SAMSUNG SMDK2410: ARMV4I"
- Build OS menu -> check "Copy files to release directory after build"
- Build OS menu -> check "Make run-time image after build"
- Build OS menu -> click "Build and Sysgen"
One more time, be patient, tyhe compilation may take 20min.
After compilation successfull:
- Build OS menu -> Open Release Directory.
Copy 3 DLL's from this directory and paste in another (i.e. your Desktop). Rename them as stk_service.dll, ril.dll and rilgsm.dll
Copy the renamed DLL's back in the Release Directory
- Target menu -> Release Directory Modules -> Add the 3 DLL's
- Run your Hermes in KITL debug mode (COM MANAGER + POWER + RESET)
- In Platform Builder, Target menu -> Attach device
- Wait that the phone starts (may take 10min)
- You are in Windows Mobile !!
I had copy SSPL_HERM.exe to my MicroSD card before the operation. For that, I've used the SDcard adapter shipped with my MicroSD card and connect on a colleague PC with a 7-in-1 card reader.
So, once my phone was started, i've clicked SSPL_HERM, and after, I've followed the procedure for the pof' UNLOCKER v3.
Then flash a new ROM
So, for all who have an Hermes stuck on the windows screen, follow this method and unbrick it in 30min !!
Have a good day
PS: sorry for my approximative english!"
Mal..
malrose - thanks for your detail instructions.
I will try do this tomorrow.
i'm sorry, but this is very unclear to me...
Or, this KITL mode... I've never seen one on my phone so far, just can not activate it at all!
Anyone, please report, is KITL mode possible at all on DoCoMo and Softbank japanese ROMs...
Also, when one enters KITL mode using "healty" phone, what's displayed on screen?!?
sorry again.
Zgembo said:
i'm sorry, but this is very unclear to me...
Or, this KITL mode... I've never seen one on my phone so far, just can not activate it at all!
Anyone, please report, is KITL mode possible at all on DoCoMo and Softbank japanese ROMs...
Also, when one enters KITL mode using "healty" phone, what's displayed on screen?!?
sorry again.
Click to expand...
Click to collapse
Not all roms have kitl enabled. Press either power+comm+reset or comm+ok+reset..
I have just installed Microsoft CE 5.0.
Now try to do all you says.
KITL assistence needed
Hi,
I allready posted this in the Bricked Hermes Thread, but that thread is getting a bit busy
When trying the method of Superdave as described in http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i get:
3195 PID:39ceb52 TID:39ceb2e !ERROR: NK!SC_CreateLocalView: failed opening "\windows\wince.nls"; error=2. Expect boot failure!
3198 PID:39ceb52 TID:39ceb2e !ERROR: NK!SC_CreateLocalView: make sure "wince.nls" is present in your image.
3201 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3202 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=03f8e83c(coredll.dll+0x0002e83c) RA=03f8e814(coredll.dll+0x0002e814) BVA=04000000 FSR=00000007
3206 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3208 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=03f8e83c(coredll.dll+0x0002e83c) RA=03f8e814(coredll.dll+0x0002e814) BVA=04000000 FSR=00000007
3464 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3466 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=80016e5c(NK.EXE+0x00016e5c) RA=80016e3c(NK.EXE+0x00016e3c) BVA=03f31528 FSR=00000007
Any ideas of fixing this?
Ooohhh yeahhhhhhhhhhhhhh.
HTC Tytn was recovered.
Thank all for help.
This method realy works, when devices hang on Windows Mobile Screen.
hi
i try to open microsoft window ce 5.0 through my pc but it shows error and can't open
i also download .net framework but same problem shows
any solution that how to use this software
malrose said:
Not all roms have kitl enabled. Press either power+comm+reset or comm+ok+reset..
Click to expand...
Click to collapse
Where can I find a ROM that has KITL enebled. I've tried two different, none has.
So how can I use this method if my hermes is not kitl enabled? In fact I have two dead hermes devices and I cannot enter in KITL mode on none of them. To flash other roms is impossible... as I'm writing this I'm installing on my pc the Win Ce platform builder and I really really hope not to waste time in trying this recovery method for two hermeses wich cannot start in kitl mode.
how to enable KTL MODE i can not enter this mode i tried
how to enable KTL MODE i can not enter this mode i tried
COMM manger - softreset
and
Comm manger - ok - soft reset
Comm manger - ok - power - softreset
all this is not work to me
why or how to enable this mode on my phone

[solved] What should I do now? Error while ROM flashing

Hi,
I'm trying to flash my Wizard (T-Mobile Mda Vario to be exact) to WM6 ("SNN Edition Version 3.0 LITE"). And I'm stuck
Before I touched anything that was what I got:
IPL: 2.21.0001
SPL: 2.21.0001
GSM: 02.19.11
OS: 2.21.26
// Just after I got my Wizard I have used lokiwiz03a to be able to use it with my Orange SIM card, but after that I have hard reseted it.
Here's what I have done:
- I'm using a Windows XP computer
1. I took off the SIM card and SD card.
2. Turned on my Wizard and connected it via USB to computer (with the latest ActiveSync - don't know the version but I've just downloaded it from Microsoft site).
3. It has synchronized.
- my battery was 85% full
4. I've downloaded "Wizard Service Tool" and clicked the wide button on the top "Enable RAPI..." or something like that (at the black screen on the left it said that I should click this button before doing anything else with this program). Then I clicked "Device Info" to be sure that I have a G4 Wizard.
5. I have unplugged the Wizard's USB (I don't really know why, but I've been nervous).
6. Then plugged it again and waited until the ActiveSync has synchronized.
7. I've used HardSPL as told in "Wizard Windows Mobile 6 for newbies" - everything came fine. I got the white screen and after my device has restarted I had:
IPL 2.21.0001
SPL 2.21.olip
// I don't remember what OS version was, and I got no GSM line
8. I waited for ActiveSync to synchronize and then ran ROMUpdateUtility_Wizard_NoID.exe (from "SNN Edition Version 3.0 LITE" - http://forum.xda-developers.com/showthread.php?t=383524).
9. I did what the program had told me to do (it has been the same as HardSPL).
10. In one of the final steps (after clicking "UPDATE") it hadn't written any information about "Image Version" and "Language" in "To" section but I didn't take this as an issue and clicked "next".
11. I got the progress bar, my Wizard's screen went black.
12. Finally, on the PC I got the information saying that it can't accomplish the upgrade and I should get a newer version of RUU or something like that (I freaked out and closed that window without making a screen shoot). I didn't get even 1% (I had 0) but I've seen the progress bar.
What I have now on my Wizard are three colored bars on my screen. In the top right corner it's written "RUU", in the bottom left "USB". I also have "IPL 2.21.0001" and "SPL 2.21.olip" written on the bars.
Please tell me what should I do now?
Should I unplug my Wizard's USB from PC?
Should I click any button on my Wizard?
Do I already have a brick or is there a chance for me?
Please help.
Thanks in advance,
Alex(ander)
From the "Wizard Windows Mobile 6 for newbies" guide, download the Mun RUU and use that. Extract it somewhere and paste the nk.nbf file from the ROM you wish to use and it should be ok. If you reset your wizard it will boot in WM normally. There's nothing wrong with it.
Thank you very much. You gave me hope
I'll do what you've said when I calm down.
EDIT//
Man, that's great. I have the WM6
Thanks a lot again
You are welcome. Glad everything worked out well.

S200 stops at rainbowscreen

Ive got a "bricked" S200 G4 (I think)
Text in rainbow screen is
"ILP 2.20.0001
SLP 2.10.0001"
I dont know if the difference here matters.
Tried to upgrade with different ROMs, but no luck, upgrade stops in the process, different % every time.
But the latest Speedking 2 ROM I managed to install. Hopefully I softbooted and got the same rainbow screen.
Any advice?
Why didn't you hardspl your prophet ??
I did, but maybe wrong hardSPL? It is a jungle here, hard to find the right info I need because its so much.
hpn said:
I did, but maybe wrong hardSPL? It is a jungle here, hard to find the right info I need because its so much.
Click to expand...
Click to collapse
1. not 100% of our Prophet can be hardspl done ( like mine )
2. if so, just go straight ahean with my lazt_tool, too easy though....
3. hardspl is just a flashing process but only spend a couple of minutes unlike rom flashing, (from 5 - 10 minute.)
all you have to read in the sticky post on the top pf this forum
I recommend youto read post 1 of this thread....
http://forum.xda-developers.com/showthread.php?t=353547 as follow....
20080601added:
[size=+2]Lazy_Tool (thks YOUZII) is for flashing all nk.nbf, in win-xp PCs, ........[/size]
WANNA GO OLDER ROMS? READ THIS POST THOROUGHLY ^_^ )
P.S. You can just change / replace the nk.nbf inside the Lazy_Tool folder if you wish to flash other roms....
20080529 added:
Cloudyfa's 19213 clean rom + Lazy_Tool, simple, fast, error free, a new upgrade tool.
[size=+3] Additional RECOVERY steps for 3 colors screen boot-up after flashing...[/size]
a. Force Bootloader Mode MANUALLY (see below Point 4 for How To ), Then flash PVtemp or NVID for prophet( P.S. the boot up screen will be changed to Qtek...),
b. ( Optional) Use Lazy_Tool to upgrade to WM6.1 (default rom is Cloudyfa's 19213-clean, you may change if you want...)....^_^,
Click to expand...
Click to collapse
20080423 added: Alternative "Lazy_Tool"
some hints ~~
if error persists while upgrading with this tool,
Please ask yourself...
I. did I softreset yet? did I make the Prophet recovery? (remove battery and sim card),
II. will the USB port of my PC currently too heavy loaded?
III. did I restart my PC yet?
IV. any connection related software other than activesync is running?
V. did I try the rear panel USB ports?
V.I is my PC currently too busy?
VI. did I try other USB cable yet?
VII. did I try the force bootloader manually before upgrade?
VIII. Did I hardreset my prophet after new flash(if everything had done but no help~~~~ ) ^_^
**************************************
2008-02-18 added ***
NVID for prophet,
Click to expand...
Click to collapse
HARDspl
(OLD method is at the bottom of this post)
1: "DON'T PANIC",
2: 99.9999% CAN BE RECOVERED BY
DOWNGRADE TO WM5 WITH entering BOOT_LOADER MODE + flashing the PVtemp (old method step 1).
3: IF USB CONNECTION ERRORS, TRY REMOVE BATTERY FOR 1 MINUTE and try again.
4: FORCE BOOTLOADER MODE MANUALLY HOW TO = ....
4a. keep pressing the Commgr button and
4b. in the same time keep picking/sticking the bottom softreset button with stylus for one second,
4c. [size=+2][highlight] THEN ONLY ONLY RELEASE THE STYLUS[/highlight][/size] and wait for the screen
TO CHANGE to the three color screen (bootloader mode),
4d. then release all and go to step 10 below..... !!!
Click to expand...
Click to collapse
(remember to download and prepare all files you needed first, or you may have errors while in the upgrade process)
Click to expand...
Click to collapse
5. Execute the Rom Upgrade Utility (ROMUpdateUtility_NV_G3.exe ( or G4), in the
HardSPL folder that you had downloaded, all activities will only take 2-3 minutes to go and
nothing will be seen in the Prophet screen.
(P.S. if connection Error, NO PANIC, soft reset OR remove battery for half a minute and try again. )
6. after the flash completed, it will restart automatically.
7. done!! in your prophet, nothing will be changed VISIBLY EXCEPT the digits IN the reboot screen !!!!!
and while booting now YOU MUSTBE ABLE TO SEE information like: 2.G3.4PDA (FOR G3 PROPHET) or 2.G4.4PDA (FOR G4 PROPHET)
Prophet Hard SPL isn't yet completed until the SPL shows
"2.G3.4PDA" or "2.G4.4PDA". ^_^ !!!​
Alternate way to Flashing / upgrading your Prophet to WM6,
a. ENTER BOOTLOADER (see how to at the upper part of this post) [size=+2]OR [/size]
b. DO THE JUMPSPL...(step 8-9 BELOW) [size=+2](you can force to bootloader mode instead of step 8 to 9)[/size]
8. copy the 3 files from the jumpspl.zip to the root directory of your Prophet and then unplug / disconnect Prophet,
9. Execute the SPL.lnk IN THE DEVICE (using the Total Commander is recommended), then you see Prophet in all bright or white screen,
10. Plug back to the USB port ( connect to rear USB panel of the computer - recommended) to the device,
11. Execute the Rom Upgrade Utility to upgrade to your chosen rom
(or put your NK.NBF to the unzipped WM6_Update_Utility folder), all activities will
only take 3-5 minutes, nothing will be seen in the Prophet screen.
12. Finally, after 100%, be patient, just wait, and Prophet will reboot automatically.
13. OF COURSE, after it auto-restart, [size=+2]better one more time HARD-RESET[/size],
ALL will be OKOKOK !!!
[size=+3]Tradition (OLD) method[/size].... (for ROM with OS.nb ),
1. Connect to PC, activesync now OK, Flash with [size=+2]PVtemp[/size] or NVID for prophet for step 1
WHEN FINISH,
2. TOUCH NOTHING, HANDS-UP !!! leave it alone, just don't touch your prophet...... ( WM5 wwe flashing now finished)
3. [size=+2]ACTIVE SYNC WILL POPS UP soon, JUST DON'T TOUCH IT (disregard it) [/size],
4. THEN RUN UPGRADE.BAT from PC to flash to WM6 (should be included in your old ROM package with OS.nb )
5. follow the on screen steps and YOU WILL GET WHAT YOU HAD EXPECTED THEN~~~~~
[size=+2]PLEASE REPLY IF YOU THINK HELPFUL ABOUT THIS MESSAGE !! ^_^ ​[/size]
Click to expand...
Click to collapse
I`m running Mac, with XP under Parallels. Upgrading Trinity is no problem on his config. But your reciepe include running command window. I cannot connect to the prophet from command window.
Trying to solve this somehow. Thanks for the link.

delete the original rom?

Hello everyone,
is that it will do some days I want to restart my qtek 2020 v0.6. It was purchased and screen
Black bootloader mode with serial or USB v0.6. I tried hard reset but nothing is there.
When I run the rom flash main with HimaUpgradeUt_noID.exe or HimaUpgradeUt.exe
it refuses to nk.nbf, it makes me country id error 120 or error 112 connection error.
But against n I've no problem for the Roma Radio_.nbf and ms_.nbf the flash is going well until the end.
With mtty.exe I could write the original rom on the sd card and I put on my pc with ntrw_494.exe.
The Roma PPE cause a password to open with ER2003edit.
I wanted to start the application xdadev_all_unlock-v1.6_138.exe or xdadev_all_unlock May-v1.5.exe my pc tells me that this is not a valid win32 application.
As against this for me xda2unlock.exe met:
XDA Developers XDA2UNLOCK tool v1.2 XDA Developers XDA2UNLOCK tool v1.2
This program will extract the unlock code from your XDA II. This program will extract the unlock code from your XDA II.
For this to be possible, a few steps are necessary: For this to be possible, a few steps are necessary:
1. 1. The XDA II needs to be put in bootloader mode. The XDA II needs to be put in bootloader mode.
NOTE: THIS WILL WIPE ALL YOUR DATA SO FIRST BACK-UP! NOTE: THIS WILL WIPE ALL YOUR DATA SO FIRST BACK-UP!
You enter the bootloader by holding the Power button and the Action button You enter the bootloader by holding the Power button and the Action button
while pressing the stylus in the reset hole on the bottom. while pressing the stylus in the reset hole on the bottom.
In the bootloader mode, the display will be gray and say Serial at the top. In the bootloader mode, the display will be gray and say Serial at the top.
2. 2. Next put the device in the USB cradle. Next put the device in the USB cradle. The display will now say USB The display will now say USB
and the first time Windows will detect a new device. and the first time Windows will detect a new device.
3. 3. Disable USB in Active Sync in 'File -> Connection Settings' Disable USB in Active Sync in 'File -> Connection Settings'
Now the device is ready to extract the unlock code. Now the device is ready to extract the unlock code.
Type YES when you have completed the above steps and want to continue: yes Type YES when you have completed the above steps and want to continue: yes
Communication port opened. Communication port opened.
waiting for radio bootloader waiting for radio bootloader
reading first block... reading first block ...
reading second block... reading second block ...
The phone seems unlocked already! Seems unlocked the phone already!
Do not forget to enable USB in Active Sync again! Do not forget to enable USB in Active Sync again!
Press enter to close.... Press enter to close ....
For truly all information of PDA on the origin of the country id and that exact version
there is the device data.txt but for creation must be initiated HimaGetDeviceData.exe that tells me that this is not
win 32 application invalid.
And finally, after searching hard I tried with hex editor on the original rom, change the first line, but there is nothing ...
That is my question is how empty the memory of the PDA to install a new (windows) to
it can restart normally?
norinsimpel,
I really tried to read and unterstand your post, but you mixed up languages, your own post and parts of a program manual, so that it is all FUBAR.
Could you please edit it, e.g. in this way:
1. The problem in French
2. The problem in English
3. Description of your device, the ROM you have now, the ROM you want to flash.
I´m shure this would make it much easier to help you...
sorry for the language.
I am belgium, and I use google to translate.
I have a qtek 2020 bootloader V1.06
I do not know the original rom, It does not light.
I can not use HimaGetDeviceData.exe with devicedata.txt to know the exact rom
because it does not turn

Categories

Resources