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?
Related
HELP PLEASE
I tried to do DCD's upgrade method to get me GPS and what not, and I got stuck at #3
1. Copy down your infromation from PST (more below)
2. Update your Hard-SPL to 2.40-olipro
3. Flash new ROM
4. Flash new Radio
5. Reprogram PST settings from earlier if necessary.
Click to expand...
Click to collapse
THEN when it was restarting it froze at the sprint splash. so i reset, and still it froze. I tried doing a hard reset and I tried the power+camera+reset combo with the stylus in
ahhhhh! please please any help is appreciated
TIA
Power+Camera then SoftReset, Just press the reset button while the power and camera are both pressed down and let them go and then the boot loader should show up
ahghhh! okay i did that and got the lovely bootloader
i hate to be retarded sounding but what next?
THANKS for your help its greatly appreciated!
OKay i tried to continue but now it says NO RADIO under the sprint logo! ahh its getting worse?
edit: of course now i can still get into the bootloader though, so what to dooo
if its of any help the bootloader says:
TITA100 MFG
SPL-2.40 Olipro
CPLD 9
u said u loaded the radio in there right, well if so go head and load the dcd rom in there now, if u dont have either go do the radio, then it will restart then freezes again if that happens do the power, camera and reset button thing and load the dcd rom then after that it will load fine
No radio means no radio. Install the full blown 3.16 to get it all, then install DCD's rom if you want.
heres a small idea. it might just work.
READ
this question has been asked a million times. geez people. if you are not willing to read and do general troubleshooting wtf are you flashing roms for?!
cluttering forums..
for the record. i want world peace as much as the next guy, but not as much as i would like to have a forum community of people who read and thought for themselves. unfortunately...much like the real world..you can idiot proof a forum
Load the image on a Fat 32 sd card, name TITAIMG and soft reset to BL, It works every time.
watson540 said:
heres a small idea. it might just work.
READ
this question has been asked a million times. geez people. if you are not willing to read and do general troubleshooting wtf are you flashing roms for?!
cluttering forums..
for the record. i want world peace as much as the next guy, but not as much as i would like to have a forum community of people who read and thought for themselves. unfortunately...much like the real world..you can idiot proof a forum
Click to expand...
Click to collapse
Don't be an effing jerk... Posts like are a waste of space* and should be considered "clutter"
At any rate... I myself had this same issue so I just tell you what I did. As you have already done, when it freezes on the splash screen, enter the bootloader. I had an issue where my pc didnt recognize my device anymore, but I was able to find an app (here on xda) that stopped Activesync. Once I did that I was able to flash a diffrent rom and start over (I used dcd's 1.6.10 Sprint)
When starting over go very slow making sure not to overlook any step. Start with http://forum.ppcgeeks.com/showthread.php?t=16806 flash it
Then flash dcd's 2.0 beta.
I'm going to be honest, between being stuck in bootloader, frozen splash screen, reading an ungodly amount of useless posts* and listening to my girlfriend tell me to "Marry the effin phone" the whole thing took me about 10 hours. So if this helps great, let me know
Load radio and os rom from micro sd!
Ok, for all sprint users that are stuck because you loaded a cooked rom without loading the correct radio first. Or you have some how overwritten the radio rom, dont ask me how I did it but i did.
Here it the fix!
I was running the 2.40 Olipro boot loader when I preformed these steps. I do not know if they will work with other boot loaders.
download the Official 3.25 rom from HTC. ftp://Mogulrom:[email protected]_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship.exe
Use winrar to unpackages it.
Format a microsd card as FAT32.
Copy Special_4350.nbh, and RUU_signed.nbh from the unpackaged 3.25 rom to the freshly FAT32 formated microsd. Rename "Special_4350.nbh" to "TITA100.nhb. Rename "RUU_signed.nbh" to "TITAIMG.nbh". Inset the microsd. Put device in bootloader mode, press and hold both power, and camera then softreset while holding the buttons. Follow on screen instruction from boot loader mode.
Hope this helps...
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
I've been searching on how to completely restore my (T-Mobile) HD2 on this forum for a while and haven't came to it, so sorry if I'm repeating any threads.
Basically I'm fairly novice in flashing and things in that nature. I've been flashing updating Energy ROMs on my HD2 for about six months since I got the phone. Which was fairly simple to do. Since WP7 ROMs, I've switched over to flashing those. The problem is that 99%, it'll flash fine, then won't get past the boot screen. And on the rare occasion it does get past it, I can't turn it off, or else I'll have to trying getting past the screen 1000 more times to be successful. I think I have all the requirements to run WP7, but not exactly sure.
So I would like to know what to download and flash/ install for it to be as if I bought this from T-Mobile today.
Thanks!
I need help with this too..I craked my screen and am going to send it to t-Mobile so they can send me a new one, but I want to put it to factory reset. Ive looked all over cant find them...the post a couple up...links are dead
you do realize that if you cracked your screen your warranty is already void. it doesn't matter what software you are running at this point.
diazjohn said:
you do realize that if you cracked your screen your warranty is already void. it doesn't matter what software you are running at this point.
Click to expand...
Click to collapse
Maybe they have the insurance feature?
Late answer, but go herehttp://www.t-mobile.com/wmupgrade/ to get stock ROM.
follow steps here http://forum.xda-developers.com/showthread.php?t=623402
your done.
how_weird said:
Late answer, but go herehttp://www.t-mobile.com/wmupgrade/ to get stock ROM.
follow steps here http://forum.xda-developers.com/showthread.php?t=623402
your done.
Click to expand...
Click to collapse
Sorry for MY late reply, but I put this phone away for a while and now my dad wants to use it. I've gone though the steps, but I can't get past "6. Hold the volume down key and power on your phone. As soon as the coloured screen changes to grey, RELEASE volume down." It never turns grey. I'm one step from taking this phone and throwing it out my window to see it shatter.
art0605 said:
I've been searching on how to completely restore my (T-Mobile) HD2 on this forum for a while and haven't came to it, so sorry if I'm repeating any threads.
Basically I'm fairly novice in flashing and things in that nature. I've been flashing updating Energy ROMs on my HD2 for about six months since I got the phone. Which was fairly simple to do. Since WP7 ROMs, I've switched over to flashing those. The problem is that 99%, it'll flash fine, then won't get past the boot screen. And on the rare occasion it does get past it, I can't turn it off, or else I'll have to trying getting past the screen 1000 more times to be successful. I think I have all the requirements to run WP7, but not exactly sure.
So I would like to know what to download and flash/ install for it to be as if I bought this from T-Mobile today.
Thanks!
Click to expand...
Click to collapse
I have done a dozen of flashings on my Tmobile HD2 and works fine so far. Thanks to XDA forum all the tools I need are available right here on XDA !!! You just to search them out yourself (sorry I don't have the links ....... ).
I suppose you know how to flash your phone so I will not explain details how to do it.
In brief, to install WP7 this is what I suggest you should do -
1. Update flash radio to the latest available update from Tmobile US website, regardless of what ROM you have at present (version 2.15.50.14 is the latest, I think).
2. Flash HSPL 2.08 to your phone to maximize 576 RAM usage, if you have it (do not use SPL 2.08.000 as this will recognize only 448 RAM size).
2. Use Task29 to clean out the existing the existing ROM on your phone (this will erase your OS and you will only be booting on the white HTC logo screen). This will clear out those ROM leftovers on your phone.
3. Flash magdlr 1.12 or 1.13 on your phone (press power button on boot to show magdlr menu).
4. On magdlr menu scroll down to no.5 USB flasher, connect your phone to pc and run dwi.exe on your WP7 installer and wait till installation has completed.
I have done these procedures a dozen times already I have not encountered problems so far. I have been flashing and flashing to choose the best ROM (WP7 or WM6.5.x) I want. On personal note, I think I would settle for WM6.5.x cooked ROMs because of usability and handiness (I find WP7 too complicated to deal in terms of tweaks and handling of personal videos/photos file security).
Some notes:
a. You need to flash radio and HSPL only once.
b. Use Task29 every time you need to install a new ROM (your choice, but recommended).
c. After Task29 you can start out clean and flash to stock ROM or any other rom you choose.
d. There are dozens of videos on YouTube to help you flash but I have not seen one using Task29 to start the process of flashing.
This works for me, hope it does to you as well. Good luck !!!
My viewpad 7 is boot-looping, it is restarting before reaching the launcher screen, and also stuck while booting into cw recovery mode. I changed font files of the root before this happened. Any way to restore it's rom without using cw recovery mode? Is it possible to boot from sd card?
Can you boot your VPAD7 into CW Recovery Mode ? (Hold down Vol. UP and Vol. Down buttons and press Power at the same time to get into recovery mode)
Anyway, you most likely need to flash a stock ROM first using the SUTL3_v1.7.9 utility available from Viewsonic and then one of the FM6*.nb0 files - it might not recognize or "see" the device, keep trying & reset/reboot and use that small "reset" button on the bottom if necessary.
Check your FTM (Factory Test Mode) for your Hardware & Software build info - and try to match the closest *.nb0 file for flashing. Hold down Vol. Down while pressing Power to start & run FTM, use tiny pin hole to press & reset device/exit this mode.
I haven't done this in a while, but it will most likely change the device back to unrooted, stock form. And, you will lose all your custom app settings - but it should come to life after a successful flash, restart & give it 5 to 10 minutes to complete initial install & setup - and, you should see your original screen again.
Then, follow steps to get it rooted again, do a NAND backup & set it aside for safe keeping, then reflash your choice of custom Rom, etc. Detailed directions are here on XDA - good luck & let us know if we can be of further help ....
I was making the root to my viewpad 7, and during the process, I took out the cable by accident. And now it's impossible for me that the process finish, it always stuck. Some ideas, please?
luisete123 said:
making root .... and during the process .... took out the cable .... And now it's stuck. Some ideas, please?
Click to expand...
Click to collapse
OMG, okay - relax & take a deep breath ....
It should be recoverable, I think - you will just need to flash the "proper" factory stock ROM first, get it working again & then repeat the rooting process.
First, check your hardware/software version in the FTM mode (it's for diagnostic, flash & download to ROM, etc. ....) & safe to do - hold down the left Volume Down key on top while pressing the Power button with the device off. If necessary, get someone to reset the device (use the smallest pin hole on the bottom of the device.) A pin works best but small paper clip will do.
In a few moment, it will show "Enter FTM Mode" and then display the VPAD7's info -
SWVer=3.410 or whatever is on yours
Model: FM6-0001 or whatever yours say
HWVer: 107 (106, 103 or whatever)
What to do with this info - it will help you select the correct or closest factory ROM to flash & restore your Vpad7 to stock condition, unrooted.
You will need one of the SULT3 or for oldest ROM, maybe SULT2 is better - download & save to PC, unzip the SULT* - and follow onscreen prompt & instructions to select your *.nb0 file.
Another suggestions, since you cannot get into Recovery Mode to wipe dalvik, cache & full system/data first, it might help to flash the *.nb0 file twice - it will take a bit of time, maybe 10 minutes or so and a few more minutes to do its initial boot-up configuration. Be patient - and write down any error messages, etc. if you run into problem.
It's best to take out any SIM card and even mSD card from your device, not required but recommended. When you can boot up again & get pass the Android activation wizard/screen, you can power down - put the mSD card back in and reboot again.
http://vsg.viewsonic.com/ViewPad7/
Good luck - there's a wealth of helpful info posted here, please set aside & take time to read it first & refer to those notes. Good Luck & Cheers - let us know if you succeed ....
A thousand of thanks Letitride!!
Before continue making mistakes, I want to ask if there is any problem to use SULT3 (because I read u posted it before) instead of SULT2, because yesterday, before post my question, I already installed SULT3_v1.7.9...
When I enter FTM Mode, the display shows:
SWVer=3.16R
Model: FM6-0001
HWVer: 106
So now I dont understand. I am a little bit lost, but I think I must to download something else from the viewsonic web that u posted (I can't repeat the link because I am new), isn't it?
Thanks again for your help. I know there are lots of help already posted, but about my problem I didnt find anything, that's why I asked. Thanks!!
Ok, I will explain what I tried, and the next error:
As I said, I already installed SUTL3_v1.7.9, so I used it. I downlodes for the viewsonic web that you posted FM6-316Q-0-1008-A01.nb0, and this is the error that the program said me:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
Maybe I need to uninstall SUTL3_v1.7.9 and try with SUTL2.1_v1.8.4? During the process I don't need to select nothing in the ViewPad screen, do I?
Thanks again!
EDIT:
I installed the SUTL2.1_v1.8.4 (without unistall the SUTL3_v1.7.9, and there is the next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
luisete123 said:
Ok, I will explain what I tried, and the next error:
I installed SUTL3_v1.7.9, FM6-316Q-0-1008-A01.nb0, the error:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
EDIT:I installed SUTL2.1_v1.8.4 (without SUTL3_v1.7.9, and next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
Click to expand...
Click to collapse
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Letitride said:
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Click to expand...
Click to collapse
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I think it was a problem while I was downloading yesterday, because I don't know why, the speed was very very low. Otherwise I can't understand, because in this other laptop that I tried, the Windows is not original, and in mine it is...
So now, as I understand, I can root it without any problems, can't I? I will wait untill tomorrow, because I am on hurry now, and I dont wan't to do any more mistake
I am really greatful Letitride, thanks again!
luisete123 said:
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I can root it without any problems, can't I?
Click to expand...
Click to collapse
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Letitride said:
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Click to expand...
Click to collapse
I am again really thank you! But, I still have the same problem... I am trying to use SuperOneClick v1.7 program, and again get stuck...
I will try with GingerBreak, but I was reading here another post about this program and I will need to read it again, in order not to make another stupid mistake!!
Cheers anyways!!
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.