Related
Sorry if the post has already been mentioned in another forum before.
I have an O2 XDA Orbit and i'm looking to put Fracoons Artermis rom on it http://forum.xda-developers.com/show...o♦.
I'm pretty new to flashing phones and PDA's but i'm quite experienced with a PC so shouldnt need to much help!
I was wondering what steps I should ensure to take to make sure that I dont turn it into a brick, I could do with a complete guide! I've also been told that i'll need to run the Artermus USPL program after connecting the phone. But any help and advice would be a great help. Is there anyway to backup the phone in the state it is at present if or if it doesnt go wrong?
Thankyou for the help and sorry again i've this has already been asked by someone else! Will really appreciated it!
There is no assurance that the process will not make your device a brick. But it happens only on a rare case. Many 1000s of users have upgraded without problems however a few has got their devices a brick.
There is no point taking a backup as the new ROM will give you different files. Anyway, to make sure you don't end up with a bricked device:
-Charge your device fully
-Run USPL
-The process should complete successfully!
-Upgrade ROM.
-Never disconnect your Pocket PC or turn of your PC when the upgrade is going on.
-If your stuck anywhere, don't try to do anything stupid but come here and post.
-Your device should be fine
-Even if some devices get bricked during one of the upgrade process, there is still a high chance of bringing your device back to good working condition with the help of a Factory ROM and so don't worry and go ahead.
Regards,
Carty..
that's my biggest concern so far... my XDA II SHOULD be able to run WM5 but i'm very concerned that i could turn it into a brick... the reason for this is: the XDA is the only phone i have at the moment.
If it bricks, then i'm literally screwed... i have the HimaUpgrade File that does not need an ID, and as i'm pretty fluent with English, i see no problem in using an English ROM.
The Wiki is a good place to start... but i still don't know if i REALLY need active sync to be running or not, since i cannot understand what good that would do if the device is in Bootloader Mode anyway.
Reason for this is that sometimes i read "Active Sync should be on" and sometimes i read the complete opposite... it's freaking me out.
Device should be Synchronized always for the best choice. All un-official ROMs will require this. However, factory ROMs can be flashed directly from Bootloader mode.
That is why I said when you think you screwed the process of upgrading, mostly your device will be stuck at bootloader or you can access bootloader screen and only a factory rom can go from here.
PS: I wont guarantee if the above will be true on all conditions.
Regards,
Carty..
I flash all my ROMs in bootloader mode, including my own, so it's not restricted to the official ROMs. But you need a working ROM to get it back alive.
I'd recommend using a laptop for flashing or use a USV. If some guys cut your power your computer would crash right in the middle of the flashing process - won't happen on a laptop with a working battery.
This is what I want to know. How do I flash in bootloader mode?
okay, i did it this way: first of all you need a rom to flash your device with, but i guess that should be clear
To put your device into Bootloader Mode you have to press the On/Off Button, the Directional Pad AND the reset button (mostly at the lower left corner) simultaneously.
Release the Reset Button first after about a second, and then the other two Buttons.
Your Device should say "Serial" on its Screen... by that time you can put your Device in the Cradle or connect it via a USB Datacable to your PC.
Also: connect the Cable/Cradle directly to your PC, not to a hub as that could cause Problems during the Flashing Process.
Now you can start the Flash-Program, wait approximately 30 Minutes (if you are just flashing the ROM and nothing else) and follow the Instructions that came with your ROM WORD FOR WORD as these instructions are working for most people.
I'm not saying that flashing is without Problems though... when i flashed my XDA II with WM2005 yesterday, i was not able to send/receive Textmessages (SMS), so i had to reflash the device again with the last ROM released by O2, which sucks.
Ok my phone is DEAD! Yes I have have read alot of posts and used my mate "Google" but they are all saying or pointing to the threads saying flash with the .sdf files with RSD which I have done Infact i've tried most .sdf images. I work in ICT so I know to do research first before posting but I'm not getting anywhere. I just hope i'm being a numpty and missed something.
I have an unbranded UK one original version 2.21 and I had successfully flashed with the available roms on here and others by following the steps, but last night I flashed it with PAYS rom and it was fine but then it all went pear shaped when I tried to flash it back to the original 2.21 rom via RSD Lite but it's just a black screen and when plugged in I get a charge light. The Battery is fully charged.
I can not enter Bootloader and when I enter system recovery it does not respond when pressing the bottom right hand corner.
RSD does see the phone connected and it runs through the process of flashing it but then it goes to re-boot and nothing. RSD says it's finished, it does not go through the process of re-booting the phone.
In RSD on the phone properties this is all I get:-
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e600209036f60010000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: a9e56c008df05759e72a50cf0e4ce907eea6c0de
Please, please somebody help me!
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
chaihg said:
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Hi,
I have tried flashing the 2.51.sbf even tho it has the problems with downgrading. It does the same as the the other 5 or 6 i've tried.
Thanks for your suggestion tho.
I'm no expert, but is this where the touch all four corners going clockwise starting is upper left comes in?
Thought I read something about doing that when touching the single corner didn't work to get into recovery.
I could have misremembered (don't even know if it was in this forum), but it couldn't be that hard to try and it doesn't sound like you have much to lose.
maybe search four corners or something to figure out more.
Maybe time for factory repair
ABC_Universal said:
Maybe time for factory repair
Click to expand...
Click to collapse
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
it_ferret said:
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
Click to expand...
Click to collapse
Did you send it away?. You sounded like a bright guy we could have solved this together though . Ultimate thing you could have done was to flash one of the leaked original UK froyo sbf. If you still have not sent it then do this. BTW what is the bootloader version when you put it on vol up+ power ?
Have the same problem
The phone is briked. Only RSD is working but wathever sbf I flash, at the end i get the same black screen. I can not do anything. Please could someone help us?
If someone send their phone to service, please share the result.
The only sbf file that start the phone is
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF.sbf
but is working hard, the market is not working, everything i want to download is say that is downloading and nothing hapends.
Could someone tell me how to go back to original software?
The recovery mode is not working, when the android face is showing, i tap all corners and all display area but nothing hapend.
For recovery mode, you should click both vol up and vol down simultaneously. They changed the recovery button function with the new bootloader.
it_ferret said:
Ok my phone is DEAD! .....
Please, please somebody help me!
Click to expand...
Click to collapse
I had the same problem, but with luck i had read this thread :
http://forum.xda-developers.com/showthread.php?t=940647&highlight=market
and i succeded to restore my "brick" into one working phone.
Try it.
Many thanks to : adlx.xda
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
Umm... I just bricked mine (HK version 2.51.0) as well.
I used ClockWorkMod Recovery for Defy to install 3.4.2 131-003 Orange Deblur. When the recovery finished, I found a tiny yellow line "E: can't open /cache/recovery/command" on the bottom of screen. Not sure if it was there before the recovery. When rebooted the phone showed the M logo for a minute, turned black for a second, and showed the M back again in loop.
Then I installed RSDlite 4.8 to flash the sbf directly. RSDlite finished and showed a "Pass". The phone was turned off automatically but couldn't be turned on again. The battery was fully charged before I started the update so it's not likely the battery charge problem.
Weudel said:
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
Click to expand...
Click to collapse
I did post in the thread.
Heys guys thanks for all the comments, but last night it came alive.
I used 3 different computers and in the end the last pc I used was a WIN 7 x64 machine and it managed to complete the .sbf install which was a 34.4 version then i applied my previously nand backup to 34.4.4 US T-Mobile version which is Jboogie3 rom.
Keep up the good work guys and gals. This is an excellent community to be in.
ABC_Universal said:
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
I tried this install but that aswell failed.
Click to expand...
Click to collapse
im a newbie at this and did pays flash but had probs couldnt dial out ect ect so went to recovery but could not get bottom left hand screen work so after half day of trying i clicked both bottom -vol and top+ vol and restart button on top and it worked!!! but thought id give the rom one last go so did factory reboot flashed cash ect restarted signed into blur and now works great pleased i stuck with it...cheers pays
I accidentally got disconnected with my phone during an update...
and now the phone is stuck in the black "connect screen". I cant get out of it at all, i tried resetting the phone, reinserting the battery, reconnecting to pc, everything showed nothin.... but the black connect screen!!!!!
><
PLEASE NEED HELP ON WHAT TO DO!!!!!!
I have a HTC 7 Mozart, updated to Nodo, got stuck during the update to Mango beta2 7712
ANY INFORMATION WOULD BE APPRECIATED!!!
2 ?'s
1) Is there ROM's for your device?
2) If so, have you tried;
a) Pull your battery (USB disconnected)
b) Insert battery
c) Hold volume down & power on (Keep holding volume down till you see Tri-Color Screen)
d) Connect USB to PC
e) Flash ROM for your device
NOTE: Don't use a custom ROM, use a stock ROM. Don't think custom ROM's can get updates.
toothfish said:
I accidentally got disconnected with my phone during an update...
and now the phone is stuck in the black "connect screen". I cant get out of it at all, i tried resetting the phone, reinserting the battery, reconnecting to pc, everything showed nothin.... but the black connect screen!!!!!
><
PLEASE NEED HELP ON WHAT TO DO!!!!!!
I have a HTC 7 Mozart, updated to Nodo, got stuck during the update to Mango beta2 7712
ANY INFORMATION WOULD BE APPRECIATED!!!
Click to expand...
Click to collapse
Can you get into SPL mode? (the one with the colors)
http://t0.gstatic.com/images?q=tbn:ANd9GcTYjcZbbqtXqHN-vQnS4M1K1aFNaOKDwFudZiZnA_akRWAYRhR5
Try pressing Vol-Down+Power as the same time - it should come up immediately.
If it does (it really should), flash your stock ROM to get back to the start.
After that, i suggest using the DFT's method of upgrade - replace the SPL with HSPL (or RSPL) and flash a custom rom.
Ofir.
sorry...i made a mistake.please delete this entry.thanks
Thank you very much for the tips, I'll try it out
Sent from my 7 Mozart T8698 using XDA Windows Phone 7 App
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])
hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)
whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...
desperation bump
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time
Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?
What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x
d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?
d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button