Database Users

Wrote the CLoader_usb.nb file on my Qtek 1010 and it's dead

Hello All,
I was wondering if any of you were able to recover from this particular error:
I have a Qtek 1010 which I upgraded to ROM 3.16 and RS 3.19. I was really curious about ROM 3.15.15 as I had heard so much about it on the forums so I got my hands on a copy and tried to upgrade.
First, the Upgrade utility refused to work because I was trying to flash an older ROM with and already existing newer ROM. So I resorted to the Bootloader way. I backed up the existing Bootloader and ROM Image and wrote the 3.15.15 ROM back onto the SD Card. Unfortunately, I wrote the CLoader_usb.nb that came with the Upgrade Utility back onto the SD card. I booted up and flashed the ROM with the SD card, did a cold boot and nothing happens.
I charged the phone until the LED was a steady green and tried again. Nothing. I did note that I get a quick red LED flash whenever I press the Cold Boot button the second time, for example: press [red flash], press [no flash], press [red flash], etc.
If anyone has ever come across this problem and managed to undo it, please let me know.
Anyway, I guess it was my own fault, but it was not too clear on the website how to rewrite the bootloader because the example graphic says 5-15.nb0. So all you guys out there who are just getting into flashing you ROM the bootloader way, make sure you use the Boot Image that you backed up and not any other (unless you have a new Boot Image that you want to upload)
See you guys around.

I have exactly the same thing. See here: http://xda-developers.com/phpBB/viewtopic.php?t=3284
Have you found a solution yet?

CLoader_usb.nb does not contain a bootloader, so if you wrote that over the bootloader, you probably have permanently damaged your device.
you would have to look into this for a possible solution http://xda-developers.com/jtag/

Your guys' XDA are dead. How could your guys wrote "CLoader_usb.nb" to overwrite to bootloader!
Only hardware solution could bring the life back (I can help)!
If your phone is still on warranty, you could send back to them to repair or replace!
Please note, flashing is dangerous for newbie!

I'm about to fix my xda...

Hi to all. I know this has been asked several times about properly restoring a corrupted xda.
My device specs: wallaby 5.17, 64MB asian edition, last working rom is 4.00.11 eng wm2003 (which changed my model no. from pw10a1 to pw10b1, i don't know why and how).
I have a 64MB sd card and a 6-in-1 card reader.
When I reverted my rom version to d xda-developers rom 1.2 using the exe path, the flashing process suddenly stopped, it instructed me to remove my xda from the cradle, do a soft reset, and then execute the flashing again. After doing that, my screen just shows two black horizontal bars and it's background is a series of thick white horizontal lines. I can still go to the wallaby bootloader screen (which shows gsm ok).
My questions are:
1. Can I still revive my xda to a woking one? How? I wish you could guide me in a detailed way here. I tried reading the readme txt files on the xdatools installation directory but I can't seem to figure it out.
2. How can I change my model no. again to pw10a1? I need to change this back since asian rom upgrades checks this and if it's different it reports an error and does not continue the upgrade process.
Thanks so much for the time reading my problem and another thanks for those who'll lend a helping hand. Good day.

Since you have a 64 MB SD card and card reader I suggest you re-flash your ROM using the boot-loader method.

Thanks Qman.
But the method or procedure of reflashing using the bootloader method is quite ambiguous to me. It would greatly help me if there's a detailed and complete step by step instruction on how this is done.
I'm quite new at flahing roms using the bootloader. Any help to enlighten me on this is greatly apprceciated.

Help!! My xda is DEAD!!!

Hi guys i really hope u guys can help me with my DEAD xda. The problem with it now is it does start or on at all after i tried to downgrade the bootloader from 6.22 to 5.15 using the sd card method. Here is a detailed description of what i did....
First i downloaded the Updated wallaby patch tool for bootloader 6.22 from 1 of the links i found on this forum then i wrote it to a sd card using xdarit.exe It worked fine and patched my bootloader 6.22 so i could access the extra functions... Then i removed the sd card and went on to write the 5.15 bootloader file to it using the xdarit also... i selected at least 5.17 for the header cos my currect bootloader was still 6.22 (Maybe this is the cause of the whole problem?) and i went on to write the file to the sd card... after that i insert it back to my xda and select restore sd and was prompted with an invalid rom image but i selected continue since i thought i didn't write any rom images to the sd card and so the invalid rom image error.. after that i was greeted with a bootloader image heading and i pressed action to start the overwriting of the bootloader... All went well and the checksum was ok... Lastly i was asked to cold reset the xda and my xda never went back on again.... The most i could do was to get the xda to a blank white screen doing a conbinations of holding power, resetting and hard resetting.... Can you guys help me? I know i'm in deep ****.....

Man!
Well I've never messed with the boot loader as far as down nor upgrade but I think you should have used XDATools instead of XDARit to do the job.
Anyhow take a look at the below thread you might finds some useful info. there:
XDATools thread:
http://xda-developers.com/forum/viewtopic.php?t=2189
Download:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
HTH

Jaron said:
Hi guys i really hope u guys can help me with my DEAD xda. The problem with it now is it does start or on at all after i tried to downgrade the bootloader from 6.22 to 5.15 using the sd card method. Here is a detailed description of what i did....
The most i could do was to get the xda to a blank white screen doing a conbinations of holding power, resetting and hard resetting.... Can you guys help me? I know i'm in deep ****.....
Click to expand...
Click to collapse
You phone is dead, only hardware solution could help you!.

U mean changing the whole damn xda? [/b]

Jaron said:
U mean changing the whole damn xda? [/b]
Click to expand...
Click to collapse
yes!
if you don't have working OS or working bootloader, only hardware solution could help you!

Hey Jaron
Send your xda to cgigate.
He can repair it for you (of course u have to pay him).
He just fix my own one and I am waiting for the returned MDA.
BTW, I've done the same silly thing that you did.
Hope it's help.

Semi Dead SX56 Stefan, please help!!!!!!!!!!!!!!!!!!!!!!!

Hi,
I'm relatively new at this, so please I apolgize if I make dumb questions and /or statements. I have a Wallaby that just won't get pass the boot screen. My screen has a white bacakground and has the following message:
"Welcome to
T-Mobile
G324e4
R6.25.02
4.01.16"
I have already tried flashing a cooked rom by using XDATools; however, I can't get the rom into the SD card. The OSImageTool.exe doesn't show my SD cards at all, so I can't dump the rom to the SD card.
I've also tried docking the unit, but it just won't sync with my pc.
It may be irrelevant, but I have the BootLoader 5.15 on my Wallaby.
I have read several posts regarding similar issues, but nothing I've seen has worked yet. I need some help sometime soon. Thanks

Have you tried using a card reader/writer on your pc for transferring rom image?

Yup.
Actually, my laptop has an integrated SD card reader on it (I am beginning to think this may be the real issue - compatibility, etc). Keep the suggestions coming though.
Thanks for the help, but... and still in trouble :?

Have aou tried another hard reset of the device? Maybe it helps to start the ROM....
Integrated SD-Card Reader / writer do make often problems with the XDA-Tools. Best (and i think only solution) would be buying an external Card-Reader/Writer (should be available for about 10 Euro...) or borrow one.
Then you're able ro reflash your device using a SD-Card.
2nd Chance you have is making an SD-Card dump of the OS of any other XDA. And then reflash your device with this Backup.....
I don't think there is any other possibility....
Stefan

LumpiStefan,
I did try hard resetting the device several times, but nothing happened. I will try to get another card reader and go about it that way.
By the way, I did think about getting the rom from someone else, but I don't know anyone in this city with an XDA.
All in all, thanks for confirming my theory of compatibility issues. I will give that a shot...
I'll write again to tell the story of the final outcome... "Will it live to see another day, receive another call? Or will it just become another victim lost in the valley of the Death?" :lol:
Stay tunned...

egsthunder1 and LumpiStefan,
I have this exact same problem. This phone sat on my desk for several months, I powered it up and charged it everyonce in a while. Now I wanted to give it to my daughter and it just sits trying to boot up. I let it charge for several day, soft and hard resets. I used the boot loader from a second device to dump its Tmobile official ROM to SD. I then Flashed the frozen device with the SD card. It was uploading for a while, said the flash was successful. I then did a hard reset and the same "welcome to Tmobile screen with G324e4, R6.25.02, 4.01.16. Both devices had a 6.22 bootloader.
Any help would be great. There was nothing done to this device other than sittng on a desk, draining to zero, charging and then a lockup.
Thanks for any and all help.
Paul.

Hey guys, I've been having this problems for years and I've been waiting for someone to find a solution but I guess no one has the answer. egsthunder1, what rom are you currently using? I'm guessing 2003? I suggest you re-flash your rom back to 2002, I think ROM Kitchen carries the 2002 one for the T-Mobile or whatever service you're using. Just cook the rom, download it, upload it into your SD card, and use the bootloader to download the rom from the SD. It works for me if you're willing to use your PPC again w/o 2003.

Back from the grave!!!
Well,
After seeing the light , my phone turned away from it and decided that it wanted to stay in the world of the living once more.
I was right in my assertions (and Lumpi verified that), the integrated card reader on my laptop was the reason why I couldn't flash the rom into an SD card. So I borrowed one from a friend, and presto!!!
My Wallaby now runs on 2002 since I cannot get 2003 SE (from the kitchen) to get past the boot screen, just like XDAPDA88 said it would. It was twice the work, but in the end it paid off.
I guess it is for the better since 2002 was far more stable than 2003 SE ever was (at least in my experience with the Wallaby). However, I now have a BA, and I couldn't be happier (at least until I get my hands on the Universal, then I will truly be happy
Thanks to all of you for your input.

[Q] Restoring to Factory Settings

Hey guys,
So my HD2 recently started having the same issue a lot of you guys are having with the touchscreen just dying or being very unreliable. This past week I've had trouble getting past the lock screen and today it takes me half an hour to a full hour of attempts to make it past the lock. Once I do, however, the screen works fine until it's locked again.
I'm about two weeks away from warranty ending, so I want to get this bad boy sent in ASAP. A year ago I flashed a custom ROM onto the phone and haven't modified it until this morning when I installed MAGLDR 1.13 and NAND Android ROM. The new ROM worked great but didn't resolve the touchscreen issue at all.
What I want to do is completely restore the phone to how I bought it from T-Mobile US a year ago. I don't want the replacement voided because of the custom ROM, though it clearly has nothing to do with the error.
Not being very technically proficient with this stuff (aside form the dozens of hours I've spent reading up), what is the best way to go about this?
So far I tried doing a Hard Reset manually via the VolUpDown/EndCall button boot, but that just booted me into NANDroid after the reset. I tried downloading WinMo from the T-Mo site, but it's asking for a phone identification number I can't access because of the lack of touchscreen access.
Any help/advice you guys can offer would be really appreciated. Thanks in advance!

You can get the IMEI number from behind the battery to download the rom from t-mobile.
This was explained to me by another member here
Right click the ROM file you download from the T-mobile site and rename the .exe to a .zip and then you can explore the file to find the RUU_signed.nbh file. You want to copy the RUU_signed.nbh file to the root of your SD card (make sure it has been formated to FAT32) and rename the file to LEOIMG.nbh. then place the SD card in the HD2. Boot the HD2 imto bootloader and as soon as you see searching on the screen let the volume down button go. It should ask if you want to flash the imageand you will have to press the end button to confirm and it will flash the ROM.

bnd10706 said:
You can get the IMEI number from behind the battery to download the rom from t-mobile.
This was explained to me by another member here
Right click the ROM file you download from the T-mobile site and rename the .exe to a .zip and then you can explore the file to find the RUU_signed.nbh file. You want to copy the RUU_signed.nbh file to the root of your SD card (make sure it has been formated to FAT32) and rename the file to LEOIMG.nbh. then place the SD card in the HD2. Boot the HD2 imto bootloader and as soon as you see searching on the screen let the volume down button go. It should ask if you want to flash the imageand you will have to press the end button to confirm and it will flash the ROM.
Click to expand...
Click to collapse
I seriously owe you a beer, this solution worked flawlessly. Thank you!!

Hi ... this is exactly what i need to do, but my problem is I don't have my SD card in my phone anymore. I forgot my phone at home ... and this is my go to phone when I forget things!!! I flashed the phone, and now it's not going to work the way that I need to without the card. Anyway of reseting the phone?? Please help!

Flash over usb, then use hspl 4 to set stock spl.

samsamuel said:
Flash over usb, then use hspl 4 to set stock spl.
Click to expand...
Click to collapse
How exactly do i get hspl 4?
It's been a long time since i flashed anything and played around with my phone.

look at the links in my sig, you want the one that says HSPL4

samsamuel said:
look at the links in my sig, you want the one that says HSPL4
Click to expand...
Click to collapse
ok... thanks so much for that...
what about some instructions?

phoneoff-power+voldown-releasepowerkeepholdingvoldown-stripedscreen-insert usb-whenserialchangestousbinsertusb-runhspl4(rightclickrunasadministrator)-choose2.08.0000or3.03.0000asyoulike-whenphonerebootsimmediatelyholdvoldowntoreenterbootloader(stripedscreen)-waitforserial-->USB-runthestockromupdateyoudownloaded.
or, simplified
bootloader - run hspl4 - set desired spl - bootloader - flash stock rom - sit back all smug.