Greetings,
my sisters qtek 8500 suddenly started to freeze after the PIN code, at the startupslash screen and it doesn't go any further. therefore my intention was to reinstall it, via a new and better rom, but unfortunately the phone isn't Super CID, and so that my screen doesn't work (although active sync does recognize the phone and it is possible to explore the files) it is impossible to do it via this itsutl thing (I tried it and it always throws out the same kind of error - "ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence". it obviously is because of me being unable to access the screen.
so that it is impossible to install a newer ROM and I cannot hard reset the device (not able to go the clear storage and moreover somehow the hard reset via pressing both soft buttons doesn't work either), I wanted to ask whether someone has somewhere around lying a link for the old qtek 8500 ROM 1.02.252.1 ? I could try to install it once again on the phone and hope that it could fix this issue. or maybe any other ideas what to do? I would really appreciate it.
As far as i know you don't have to do anything on the phone itself when you use the update utility provided with the ROM.
You could give the last official Qtek ROM a try, you can download it via the Wikipedia topic from this forum (sticky) or the qtek support site:
http://www.qtek.nl/8500_updates.asp
(sorry....in dutch...but doesn't matter for the ROM, it's the last download link on the page)
Hope it works,
Karin
I had tried out this ROM already several times, and it still gives the "INVALID VENDER ID" error at the 4%, it's a bit weird, because it is the official ROM, but still - no idea, why.
hoping that someone has the old ROM
How to flash:
1) make an application unlock
1.5) make a SuperCID (optional)
2) copy content of SSPL folder (in the archive) to the root of your device
3) run SPL.lnk
4) run ROM Update Utility.exe (from RUU directory in the archive) on your PC
5) follow the instructions
6) wait until flash process will be completed
steps from 2 to 4
of course, I do know how to do it, have done it many times on my ppc, but the thing is - I cannot make it Super CID, because of being unable to access my screen. therefore I am searching for a rom , for which I do not need a Super CID.
How about just do a hard reset?
Turn the device off. Press and hold both the left and right soft keys while powering the phone on. You will get a request to enter 0 to continue, pressing 0 will perform a hard reset.
that's another weird thing - it doesn't work. I am sure I am doing it correctly with holding the soft keys and turning it on, but still it doesn't work with these hard resets. I'm really confused, googled it up a much and found none else with such a problem.
maybe you got an idea how to make a hard reset without the clear storage or holding these soft keys or is it simply impossible?
it's actually a bit more weird - while I am performing everything for a hard reset (both soft keys and turning on) it goes into the boatloader screen
somehow got it into a hard reset, now waiting how it will react.
FINALLY it worked - everything is okey, you can lock this thread.
fyi on factory reset
the correct way to factory reset is to press and release the power button, then press the 2 dash keys, hold until instructions appear then press 0
Related
My brand new XDA II seems to be a brick now.
- Got haret 0.3.3 from http://zap.eltrast.ru/en/hobby.html
- installed it in /Storage
- made a backup for all my data
- ran it
- established a network connection from my desktop via ppp (synce)
- got no response from my device anymore
Matthias
I assume you have tried a hard reset or removed the battery and then reinserted it. It looks like that program, whatever it is, works on Axim and it seems to poke into memory. Let us know what happens after hard reset.
Working again
Here comes the good news:
After removing the battery and letting the device sit for half an hour it is booting again.
Power button, soft reset, hard reset and bootloader key sequence (power + reset + action) did not do anything before.
I had a look into the code of haret on http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/haret/. During the procedure described above it tries to read some processor registers. Obviously it needs to set other registers before reading. This might have locked up the processor.
We probably should update http://wiki.xda-developers.com/wiki/HimalayaDevelopment with a warning about this issue.
Matthias
debrick
Hi,
Thanks for your update. I didn't have a chance yet to try it, but really bricking a device sounds like a low probability. If you can build HaRET from source, maybe you can find out which setting it is that hangs it.
I updated the wiki, but you can do that too if you want. Everyone can edit pages. When you are in edit mode, format info is at the bottom.
I had this state too a few days ago, I think I typed a bug, which severly overwrote some wrong memory area's. causing the device to not even 'cold-boot'. and also needed the battery to be removed before it became operational again.
this is probably because the 'cold-boot' of the himalaya is not that cold, it needs software to be triggered, that detects if the power button is pressed while booting into CE. this requires at least a bit of the system to be working properly.
Got it working
I managed to run the tool. Did not try much yet, but it didn't crash. see http://wiki.xda-developers.com/wiki/HaRET
Tried to upgrade the ROM on an M1000 to 2003 SE from a 1.600 version and wound up with the following symptoms.
Only able to see the bootloader (v1.06, but computer recognises the device when in the USB cradle)
HimaUpgradeUT will run as far as the screen saying what ROM it's replacing (though it says that there is nothing on the device itself). Then when I press "next" it just hangs on the erasing ROM 0% screen until I get an Error 112.
Tried using two different computers and still get the same error.
Tried different HimaUpgradeUTs and still get the same error.
Tried hard resets, soft resets, reinstalling ActiveSync, disabling ActiveSync etc.
Going insane and need suggestions. Help!
I think your best bet is to revert to the original ROM. I thought it was on this forum, but I just looked and can't find it, but...
http://www2.orange.co.uk/servlet/Sa...096364420640&product=Feature&t=Product#answer
Should get you to the ROM download page on ORANGE UK, where you have a choice of with and without MMS ROM images.
If you can get your 'phone back - that might be a start.
Richard
Edit - just tried the link and it isn't that good. Go to 'Your phones features'.
Sadly I've already tried that. But it won't accept anything. Thanks for the suggestion though.
I at a loss as to what exactly the problem is. I've checked the log file from the HimaUpdateUT file and it keeps trying to erase the original ROM but can't. Which is weird because there doesn't seem to be anything on the device. I wish there was better logging by the program.
I'm starting to consider exploring Bootloader commands to see what I can find.
did you put your device in BOOTLOADER MODE?
PROCEDURE: PRESS ON/OFF POWER BUTTON-SOFTRESET BUTTON-NAV PAD
Yep. In fact I can't get it out of bootloader mode. Have hard reset it several times.
Hi,
do you have SD card???
buzz
Ironically I just ordered one before I fried the device. I guess using it to transfer the ROM image is a possibility. It looks difficult though.
http://forum.xda-developers.com/showthread.php?t=298967
I have tried *everything* to get this working man and I'm no firmware hacker but I can follow directions and have had plenty of experience flashing G3 devices.
Basically when I do the flash (starting from the latest T-Mobile or aku rom) I get trapped on the boot screen with the T-Mobile or aku background and the following:
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
To get back I of course put the phone into "rainbow" mode by pressing camera while I boot up the device and reload either the T-Mobile rom or the akus rom. They go right in and I try again without success doing something a little different.
Things I've tried that were mentioned in other forum posts:
I've tried a number of times from more than one PC running Windows XP.
I've tried redownloading the rom and replacing the one that came with it.
I've tried waiting extra long between installed the EnableRAPI and other cab file.
tried with radio on and off (I assume this meant just disabling the phone in the connection manager?)
Things I've tried on my own account:
Doing it with and without the sim card installed
Trying multiple hard resets
Tried installing EnableRAPI but not the other one (some instructions left that peice out).
So basically i've spent a good 8 total hours on this (of course in the background of other activities) and tried load, fixed an reloading at least 15-20 times without success. The rest of the time has been spent searching the forums because I do not want to be the guy who swears at the creator or complains about it when they are doing something wrong. I see my problem (freezing at the boot screen) a number of places in the forum but never seems to be an educated person explaining what they tried.
So I've come to the conclusion that maybe it doesn't work on all phones or I'm doing something really stupid but apparently common and not easily figured out by myself (thinking too hard about it?)
im assuming you are using Shell Tool made by MuN
here is my advice:
-flash the wizard rom (i was unable to flash any other Rom until i got the wizard love in it)
-make sure you enable both cabs (rapi and the other one)
-turn on figth mode (i know you did this step and i can see that you are following all the instruction but hey we are almost out of options )
-close any antivirus or firewall (probably you did this too)
-do not have any other application running in the background
just so you know i was unabe to flash the xplore core 2.0n, i had to flash it at least 3 times going back to the wizard love (i guess this is something like hit-or -miss thing)
-try the wizard love and then flash the Rom that you want you should be able to flash it.
hope i helped in any way.
THANKS -
I've always flipped back to the TMobile a bit faster than maybe I should have. I guess the question is, if I keep trying it should work? Has anyone just determined that on certain new G4's that this option isn't valid?
I think I'm going to try the following:
Rainbow Mode USB Connection
T-Mobile original rom
Hard Reset
Wizard Love Rom
Hard Reset
Guest Sync
Copy Files
unplug USB
Enable Rapi and Other file (don't know why I can't remember the damn name)
Wait 2 minutes
Soft Reset
ShellTool Load all options except "OK"
Guest Sync
Hard Reset
Pray......
It if doesn't work I'm going to revert back to wizard love and redo the above 3 times.
At that point I'm calling it quits....
happyware said:
I've always flipped back to the TMobile a bit faster than maybe I should have. I guess the question is, if I keep trying it should work? Has anyone just determined that on certain new G4's that this option isn't valid?
I think I'm going to try the following:
Rainbow Mode USB Connection
T-Mobile original rom
Hard Reset
Wizard Love Rom
Hard Reset
Guest Sync
Copy Files
unplug USB
Enable Rapi and Other file (don't know why I can't remember the damn name)
Wait 2 minutes
Soft Reset
ShellTool Load all options except "OK"
Guest Sync
Hard Reset
Pray......
It if doesn't work I'm going to revert back to wizard love and redo the above 3 times.
At that point I'm calling it quits....
Click to expand...
Click to collapse
i would guest sync first and then shell tool load all options (dont know if this would make a difference but it a possiblity) then flash, then hard reset and before all this PRAY LOL....
dont quit i know you probably are frustated but there is gotta be a way to do it.
ill search around to see if i find something.
I thought the problem was for G3 devices
Though the shelltool was made for G4 devices, I use it on my G3. I have ended with the same problem. I couldn't upgrade to PDAVIET 4, Underground, Faria's The Real Thing.
But I do know that you can get PDAVIET 3, mUn aRTM, and Xplore 1.1 to work. There might be more but I don't know. I also use the same methods that all of you have.
Also, the ones that worked only worked when i used EnableRAPI.cab not the certspcs.cab file. Maybe the same will work for you.
I also requested mUn for his code and will try to edit it to be able to add other parts of the ROM (extended and splash).
Sick of ROMs
I been trying so many variants of CrossBOW WM6 for my G4 Wizard but sick of it, they never work out. Only successful was the WM5 Wizard love ROM, wut could be the issue?
Happyware, when you are running the shell tool, how long does it run? On most of the roms I've tried, the shell tool runs at least 8 minutes. I had a problem with an email application on my PC that was checking for email every 5 minutes and was causing the shell tool to end prematurely. After I temporarily killed the email app, the shell tool was able to finish and I had a good flash.
BTW, here's the scenario I always follow when flashing a new rom:
Temporarily kill my email application
Make USB connection to Activesync
Revert to Cingular stock rom or wizard love rom
Copy cert_spcs.cab and enablerapi.cab to the my documents folder on wizard
Install both cabs to main memory, wait 2 minutes, soft reset
Turn on flight mode
Start shell tool
Shell tool runs for approx. 8 minutes
Hard Reset
I don't know what it's doing after the hard reset, but it takes approx. 2-3 minutes to load the first time.
^^Exactly.....thats why I messed up my 1st 4 flashes because I wasnt patient.....after u do a hard reset for some reason that 1st time it takes forever for the rom to load up but it does. Also I agree w/ using wizard love, I couldnt flash anything until I that rom loaded up now I flash 1st time every time.
G4 No Luck either
Same as Happyware here.. No luck flashing my rig. with the Wizard_Love_2.26.10.2_WWE_Novii_CF2 ROM. The shell prog. cant even tell if its CID lucked or Unlucked.
blversion 2.26.10.2
device WIZARD
entrycount 5
flags 17
flags2 12
hdrcrc 0x0ab4e5ff
language WWE
magic HTC
operator
rest2
version 2.26.10.2
9b000000 00a00000 9cabd734 Extension Rom
80040000 03900000 f46dd463 OS
96000000 00280000 6b60114a GSM
92000000 00030000 19375118 Splash Screen
9d000000 00010000 093cf0a5 HTC Logo
Followed all instructions and did the steps twice. No luck Any ideas?
mdhensley5 said:
Happyware, when you are running the shell tool, how long does it run? On most of the roms I've tried, the shell tool runs at least 8 minutes. I had a problem with an email application on my PC that was checking for email every 5 minutes and was causing the shell tool to end prematurely. After I temporarily killed the email app, the shell tool was able to finish and I had a good flash.
BTW, here's the scenario I always follow when flashing a new rom:
Temporarily kill my email application
Make USB connection to Activesync
Revert to Cingular stock rom or wizard love rom
Copy cert_spcs.cab and enablerapi.cab to the my documents folder on wizard
Install both cabs to main memory, wait 2 minutes, soft reset
Turn on flight mode
Start shell tool
Shell tool runs for approx. 8 minutes
Hard Reset
I don't know what it's doing after the hard reset, but it takes approx. 2-3 minutes to load the first time.
Click to expand...
Click to collapse
Flight mode "ON" ????? Thought the instructions said OFF
I think it might relate to specific phone models
I tried many times and got into the exact same situation as Happyware. The phone just freezes at the bootloader stage with the following info:
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
I am pretty sure I followed every steps in the instruction as I spent the last 6 hrs playing with it to no avail. Is there anyone could help? Appreciate it.
I spent some time with it last night and this morning and this is what I've come up with.
I have the T-mobile MDA G4 Wizard. The Faria ROM included in the all-in-one kit simply would not flash to my device. After 2 minutes the flash would stop abruptly as if it had finished, when it simply couldn't have gone that quickly.
I tried several times, following each step exactly as I should have. It simply wouldn't work. When I hard reset the device after flashing, I was stuck on the same screen as the rest of you.
I then went back to the original T-Mobile ROM and then tried flashing with Orwell (wi6ard) and it flashed in 8 minutes and my phone APPEARS to be working normally. I haven't tried making any calls since I don't get reception in my home on any of my 4 phones (Wizard, Herald, and 2 RAZRs).
So I would recommend if you are having the same problem, you might try a different ROM.
bluebari said:
I spent some time with it last night and this morning and this is what I've come up with.
I have the T-mobile MDA G4 Wizard. The Faria ROM included in the all-in-one kit simply would not flash to my device. After 2 minutes the flash would stop abruptly as if it had finished, when it simply couldn't have gone that quickly.
I tried several times, following each step exactly as I should have. It simply wouldn't work. When I hard reset the device after flashing, I was stuck on the same screen as the rest of you.
I then went back to the original T-Mobile ROM and then tried flashing with Orwell (wi6ard) and it flashed in 8 minutes and my phone APPEARS to be working normally. I haven't tried making any calls since I don't get reception in my home on any of my 4 phones (Wizard, Herald, and 2 RAZRs).
So I would recommend if you are having the same problem, you might try a different ROM.
Click to expand...
Click to collapse
I have to agree with you... After several tries with the same ROM (Orwell´s) I decided to use WM6 Reloaded 1.5 and it worked just fine with my G4.
Now... Im having some issues (lol) with a strange behavior thingy. My phone turns itself on and dials random numbers (specially letters U Y T D A). Made a soft reset already, no-go. Hard reset, no-go. Flashed back to 2.26 and to WM6, no go
I wonder if its a virus stored in my 2GB Ultra II miniSD card Ive read a lot about AV SW been a scam in WM OS. I gotta try an antivirus b4 getting into wrong conclusion. I dont think its a HW issue.
If anyone has any ideas on this, please let me know... Or if theres a separate thread on this...
UPDATE REGARDING FLASHING OF HARDSPL - Specifically the error message "we have detected that you appear to already have unlocked another device"
- contact with the creators of HSPL has been established.
- If you have EVER used HardSPL before (on any phone BUT the one you're trying to flash) you will need to request another "license"
- OliNex will provide up to 2 or 3 licenses, but more than that is deemed commercial and you will have to purchase them thereafter.
- If you are sure you have NEVER flashed HardSPL before, then please standby until I get more information from OliNex, regarding steps we can take to resolve any conflicts.
- more to come.
Dear all,
i mentioned to some people a while back that I could send them detailed instructions via PM, helping them install their first custom ROM (available from our many fine cooks and chefs here: http://forum.xda-developers.com/forumdisplay.php?f=486)
Now, quite a few have been pm'ing me since, asking for help, so i thought i'd make a public post for all those who are wanting to flash their phones, but are scared or uncertain of making that first step.
SO, in as simple a way as possible, here we go:
INSTALLING HARDSPL 1.83:
(note: YOU CAN NOT INSTALL HardSPL via SD Card!!!! YOU HAVE TO USE ACTIVESYNC via USB!)
- Make sure your phone is fully charged and your data backed up!!!
- Download HardSPL 1.83 from here: http://forum.xda-developers.com/showthread.php?t=520312
- the page i linked does contain instructions, but i'll summarise:
1) connect your phone to your pc using ActiveSync (NOT the DiskDrive connection)
2) Make sure you have an active internet connection
3) run Topaz-HardSPL_V5_00R5.exe from your PC and follow the steps HardSPL prompts you with (incase your antivirus says something, trust me, there is no virus)
4) Press OK when asked to wait
5) everything will continue automatically (if an error pops up, STOP and mail me with your error)
6) you will see your phone jump to a tri coloured screen eventually. anything displayed on screen will be automated (again, any errors here...well let's hope you don't get any)
7) Your device will automatically reboot and you have HardSPL 1.83
Now, let's make sure it installed correctly!
- switch off your phone.
- hold down the Volume - button (minus/volume down) and press the power button. This will take you to the famous Bootloader mode. Here you should see the word Olinex somewhere. If you do, YAY, softreset your phone (the little red button under the battery cover)
- if NOT: send me a message
!!!IMPORTANT!!! You only have to do the HardSPL installation ONCE After completing the above, you can simply proceed with the following steps from now on.
OK! Now you have the means to install the ROM you want!
Step ZERO: - Connect your phone via activesync -> open My Computer -> double click on your diamond 2 -> You will now see two folders. One is internal memory, the other is your storage card -> right click on your storage card -> properties -> look for the words FAT 32 -> If it says that, proceed with "Choose your ROM!!!" below.
If it DOESN'T say FAT 32, then do the following:
- close that window and right click on your storage card again. Now click format (REMEMBER TO BACKUP)
- select FAT 32 as your File System (NOT NTFS) and then click format
- once that is complete, you may proceed with the next steps below.
Choose your ROM!!!! (I am a Dutty fan, so that's the first one i'm going to recommend...however, the method of flashing stays the same)
Once you have downloaded your chosen ROM, make sure you have the following files: TOPAIMG.nbh and TopazRUUWrapper.exe
there are TWO ways of flashing: (again, please make sure your phone is fully charged)
Method one:
- Copy the TOPAIMG.nbh file into the ROOT directory of your storage card (NOT onto your phone). (Root directory means as soon as you double click on the storage card, THAT place, that's the root directory...some people call it base directory)
- switch off your phone and enter bootloader mode (read how to in the HardSPL section above)
- You will now come to a white screen with blue writing.
- It should tell you that you can continue flashing by pressing the power button.
Once that is pressed, you sit back and wait till your phone is flashed!
watch this for help: http://www.youtube.com/watch?v=FbRboNeo2XE
(credit to wadialdoor)
Method 2:
ALTERNATIVE WAY OF FLASHING YOUR ROM WITH RUU.exe
- Turn off your device by using the Power Button
- Go to Boot loader mode. Push and hold Vol. Down and press the Power button.
- Connect your device to PC (with activesync, yes it works even if your phone is not "fully" on)
- Run the TopazRUUWrapper.exe and follow the screen instructions.
Whichever method you choose, once you get the message that everything was successful, open your battery cover and press the red reset button once. THEN, as soon as you have entered your pin code and your phone is on, switch it off
Now hold volume up (+) AND volume down (-) and press the power button. You are thereby doing a "Hard Reset".
Once that is done, CONGRATULATIONS! your new ROM is ready to go!!!
I hope this proves useful to some!
-Simon
Good and Clear
Thanks for including some missing points which some of our members missed/or/got questions during flshing (first flash ).
Thanks.
great job. it will be very helpful for the first time flashers
Sorry for the double post dont know what hapend!
great job. it will be very helpful for the first time flashers
Another tip fort first-time flashers:
Do not forget your silk underwear and trenchcoat!
Seriously though, this is a great simple guide for newbies like me. I'm still in the process of exploring the standard WinMo 6.5 as well as Manila, trying to decide what I want as it is and what I want differently.
Hey guys, if you are having trouble with some of the content in this guide, please check out my other "pre-guide guide" over here: http://forum.xda-developers.com/showthread.php?p=4963913#post4963913
also, if you have any questions, you can post them THERE (above link) as i would like to use that post as a Q and A place (and not my inbox )
Thanks for all the help, ive sucessfully installed my first ROM
Very helpful, The pre-guide and this.. both helped a LOT.
Thanks
One more thing, do i have to do the HardSPL 1.83 flashing part everytime i want to install a new ROM, or is that enough if its done once, and then only do the RUU.exe from the pc?
Drag-On said:
Once you have downloaded your chosen ROM, make sure you have the following files: TOPAIMG.nbh and TopazRUUWrapper.exe
there are TWO ways of flashing: (again, please make sure your phone is fully charged)
Method one:
- Copy the TOPAIMG.nbh file into the ROOT directory of your storage card (NOT onto your phone). (Root directory means as soon as you double click on the storage card, THAT place, that's the root directory...some people call it base directory)
- switch off your phone and enter bootloader mode (read how to in the HardSPL section above)
- You will now come to a white screen with blue writing.
- It should tell you that you can continue flashing by pressing the power button.
Once that is pressed, you sit back and wait till your phone is flashed!
watch this for help: http://www.youtube.com/watch?v=FbRboNeo2XE
(credit to wadialdoor)
-Simon
Click to expand...
Click to collapse
Only one thing, the SD must be formatted in FAT 32
htcdiamond8 said:
Thanks for all the help, ive sucessfully installed my first ROM
Very helpful, The pre-guide and this.. both helped a LOT.
Thanks
One more thing, do i have to do the HardSPL 1.83 flashing part everytime i want to install a new ROM, or is that enough if its done once, and then only do the RUU.exe from the pc?
Click to expand...
Click to collapse
I am very glad you managed to get it all working!
the answer to your question: NO HardSPL is done and over with, you only have to do it once. I will update this in the guide, to reflect the once off HardSPL'ing.
Also, thanks rspillo:
rspillo said:
Only one thing, the SD must be formatted in FAT 32
Click to expand...
Click to collapse
i will update this too.
Excellent guide, I wish I have seen it before flashing my first ROM, it is always comforting to have a step-by-step guide to follow even if the process is quite simple.
After some research on xda, I have followed the same steps you mention, and the ROMS are working perfectly, so I guess I have done it right....still there was some anxiousness at the end of the flash that is not mentioned in your guide: HardSPL stop telling flashing the ROM went OK, but never reboot....basically, to reboot it i am forced to use the soft reset button behind the back cover, all the hardware buttons including power button are not responsive. This is worrying for a first timer and should be mentioned somewhere (or is it just me, the normal behavior is auto-reboot?)
Other thing worth mentioning in your guide is the hard reset after a flash: you may add that it s advisable to do, and explain how to do it (power off, then power up while holding volume-up AND volume-down pressed simultaneously). This has taken me 2 customs ROM to figure out ;-)
gkai said:
Other thing worth mentioning in your guide is the hard reset after a flash: you may add that it s advisable to do, and explain how to do it (power off, then power up while holding volume-up AND volume-down pressed simultaneously). This has taken me 2 customs ROM to figure out ;-)
Click to expand...
Click to collapse
I did not know this thanks for this
not all custom ROMs require a hard reset. i've almost never had to do it.
but i digress. i will update as recommend by all
Drag-On said:
not all custom ROMs require a hard reset. i've almost never had to do it.
but i digress. i will update as recommend by all
Click to expand...
Click to collapse
Performing an immediate hard reset upon completing the initial flash is something I almost never do. However, I continue to recommend it to people who flash my ROMs since I have had it solve some issues in the past.
-Edit-
I'm gonna move this thread to ROM Development since it centers around flashing ROMs. I have "stuck" your roll-up thread leading here.
Successfully Flashed my First ROM
Drag-on.. thank you so much for ur guide that helped me out in successfully flashing Dutty holy grail R3 ROM on my HTC Touch Diamond2..
Thread Stuck.
P.S.
You requested this thread sticking also : http://forum.xda-developers.com/showthread.php?t=585457
I suggest it might be easier to add this to the first line of the first post - as a "If you are very new to this - read here" sort of thing.
Regards,
Dave
Hi all,
I will be a new htc owner next week and i'm trying to enter this htc world to be ready as soon as i get my toy (topaz)
My topaz is not blocked to any operator and my question is: Do i need to use Hard SPL 1.83 to flash for the first time considering the device is unlocked???
Thanks
PS: i'm sorry for this questions but i really didn't find any docs for beginners!!
Have a device blocked to an operator means that you only can use a SIM from that operator, it's not related with unlock to flash cooked roms, or HTC roms not provided thru Serial Number download from HTC Site
HardSPl is allways required to flash any other rom, please read the 1st posts where an explanation is stated, and as no relation at all with SIM Block
Happy flashing
Pisca said:
Have a device blocked to an operator means that you only can use a SIM from that operator, it's not related with unlock to flash cooked roms, or HTC roms not provided thru Serial Number download from HTC Site
HardSPl is allways required to flash any other rom, please read the 1st posts where an explanation is stated, and as no relation at all with SIM Block
Happy flashing
Click to expand...
Click to collapse
Thank you for your answer, i was confused with so many threads and information. It is in fact a little bit difficult to enter in a world like this. I own an Asus P750 and in related websites of Asus sometimes after a mouth no new posts if you now what i mean
So here it is the opposite, it's good but i have some years in disadvantage to update.
If i will post some stupid questions, so be it!! It's my beginning!!
Again thanks to reply.
Zimaia said:
If i will post some stupid questions, so be it!! It's my beginning!!
Click to expand...
Click to collapse
There are no stupid questions, only stupid answers, feel free and enjoy your new device
Thanks bros for your introduction on flashing a ROM (this is particularly useful for newbie like me in reducing the problem encounter~)
1 more question..i knew that hardreset will rest all the things and revert my phone like it is released from the factory, so what is the initiative to have it hardreset after i flash a new ROM? will my newly flashed ROM got "flushed" away after this hardreset?
Thanks again!!
h9922293, doing a Hard Reset will only reset the ROM you currently have installed. It doesn't (and can't) reset to your original ROM that the phone came with, because that ROM is long gone.
Think of it as switching your pc off, then turning it on again, to find all your programs and settings have gone back to original, but your modified windows xp/vista/7 is still there.
that make sense?
Hello,
this will be a pretty extensive post, but I want to give you as much info as I can so you can help me
I got a second had EU HD2 with a stock bootloader, radio, rom, ect.
Bootloader: 1.42.0000
Rom: 1.66.479.2 (76641) WWE
Radio: 2.07.51.22_2
Protocol: 15.32.50.07U
I read the forum for a couple of years now and I'm pretty familiar with all the procedures for flashing (I own a couple more htcs,
flashed in every possible way)
The problem is that the battery life is very poor: after a hard reset, so no previously installed apps, not using gps, BT, WiFi, or
anything (even phone in airplane mode), I get 6-7 hrs battery life. Even in standby the battery drains at almost the same rate.
SpoonCharge says -140ma - -150ma with no app or anything in airplane mode. I tried 2 more batteries known to go over 2 days with other
hd2s.
So, I decide the problem might be in the rom and go ahead to flash to a new one:
I chose the Artemis v.65 - http://forum.xda-developers.com/showthread.php?t=612580
I read all the instructions and all other linked to them threads. Started flashing to the stock LEO-S 3.14 with the instructions here -
http://forum.xda-developers.com/showpost.php?p=8776196&postcount=26465
Flashed to SPL 1.66.0000, as said in step 2.
Tried to enter bootloader with VolDown and PowerOn, but it just starts the OS. From inside the OS I can enter bootloader with the EndKey
from johcos but ONLY that way! I tried another bootloader, 1.66HSPL, 2.08 SPL and HSPL, 3.03 SPL - nothing - I cant enter bootloader
manually - only through the EndKey with booted OS.
SO - why the hell??
I can go into bootloader through the EndKey, but I fear flashing because if something happens and the flashing doesn't go as expected I
wont be able to enter bootloader and fix things, no matter with USB sync or SD!
At one (brave) point I tried to flash the RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship from here -
http://forum.xda-developers.com/showthread.php?t=623283 - but it got to 1% and displayed an error: "Update utility not compatible with
device" or something similar.
So, bottom line after this long read:
1. Why/How can't/can I get into bootloader manually?
2. Why at the first place the batt life is so poor with all processes around 0%?
Thank you for the time spent reading my story!
and
Thanks in advance for any help!
here's some "hepl"
1- post in the corect section. The general forum is for these questions you know. it's quite odd for someone who've read the forums for years to make such mistake.
2- Since it's a second hand device, god knows what the previous owner did to it.
3- Does the volume down hardware key work when WinMo is running?
4- Do you turn on the device while holding down the volume down key, or do you press it after it starts, or release it before it starts?
5- I'm pretty sure the artemis build you're trying to get needs SPL 3.03 which you can get here: http://forum.xda-developers.com/showpost.php?p=11499585&postcount=3
6- try your device with SD removed. And make sure you haven't installed any program that runs in the background on the SD.
that's all I can help with
I'm very sorry for the wrong section. I was late and I was frustrated with many hours of struggling with the hd2. Please someone move it where it belongs.
@Dr.Move - thanks for trying to help!
I got it from a friend of mine and can assure I has handled well and it's never been to any kind of repair. It was never even flashed.
All keys work in WinMo.
I hold the VolDown key before pressing the PowerOn key. Tried also holding both keys together, holding VolDown and reseting with the reset button. Manual hard reset with VolUp and VolDown and PowerOn also doesn't work.
Artemis does need SPL3.03, but the flashing instructions say flashing SPL 1.66.0000, than stock 3.14-S which flashes to SPL 3.03.0000 and radio 2.15 .50.14, than Artemis. But that doesn't really matter right now, as it has nothing to do with me not being able to manually enter bootloader or hard reset.
Tried with SD in and out, formatted it (not quick) - all the same.
A thing I forgot to mention. My friend said the hard buttons didn't work, before I got the device. It happened a year ago, when we had no htc service in our country (Bulgaria) and the device had to be sent abroad, so he ditched it and got a new one. He couldn't remember what was wrong with the buttons, but it surely wasn't not being able to enter bootloader, as he doesn't even know what that is.
When I power up the device all the buttons worked and still work. (He was surprised and said "Well - good for you ).
So I'm starting to think the problem might be in the VolDown button, but the PowerOn obviously works. How can it be the buttons work in the OS and not before it boots up??
Ok, update.
I know what you're going to say, I did probably the dummest thing I could. I know now...
I did task 29, wiped the NAND. VolDown + PowerOn still doesnt work.
So empty nand and cant enter bootloader.
Is there anything I can try, what can be the reason the VolDown doesn't work (the button itself DID work in WinMo).
Can something be done or i got myself a shiny black brick?
damn
Sorry for that bro, I think you should move to the general forum now and ask there.
make sure you state your problem in the title clearly, much like you did here.
I'm sorry I can't help you any further as I'm not a developer/electrician. but seems I don't need to tell you that you shouldn't have done that before making sure the buttons worked.