Never did anything before. Never unlocked.
Downloaded the official exe file today, update was in the middle, but the phone was freezed. I reset then stuck in bootloader.
TITA100 MFG
SPL-2.03.1000
CPLD-9
Then, I format my micro-sd to fat32, put the renamed TITAIMG.nbh to sd, use "Hold Power and Camera + Reset" to get into tricolor bootloader.
But, I can only get into bootloader tricolor screen, nothing more. Please help me, what I can do to make it load the TITAIMG.nbh? Thanks!
I tried let it at bootloader, connect it to xp, re-run the update, then the update told me not the right update for this phone. Any help?
try to get into bootloader, connect usb and see if tri color screen says USB...
then run olipro 2.40 bootloader install...unlock ur rom, then when thats done run the official rom install again, but redownload it incase u got a corrupted file
read from dcd thread
Related
Hi to all,
please help me,
When i wana install the last atom exec rom,two days ago,everythings is ok,but after hard reset,my device stayed at O2 logo and I couldn't hard reset my device and install rom too,because didn't sync with my laptop,have you any idea for this problem?
take off the battery and try again
I take off the battry many time,but this problem exist yet.
can you enter in bootloader mode (camera + reset) ?
yes,but i see a black screen that written on it:sd detected and
"starting download ...
sdDownload:couldn't find file;diskimg.nb0;.
sdDownload:couldn't find file;eboot.nb0,.
sdDownload:couldn't find file;dm.nb0,.
..."
at the end of screen:
"SD trensfer completed."
what your idea?what things i must to do?
Once entered in bootloader mode (ignore these SDCard messages), plug de USB cable and wait the device to be detected by windows
you'll be able to upgrade a new rom
i have the same problems, i upgrade the phone still stay on o2 logo
any other solution??
thanks
have you follow the upgrade procedure correctly?
just an opinion...
remove sd card...
then enter bootloader
then run upgrade DSUU.... follow on screen instruction
should be ok to upgrade your rom...
1. remove SD Card
2. remove battery
3. hold camera button and reset (stylus) button
4. replace battery while still holding the buttons
This will bring you back to bootloader mode. Just flash the above DSUU.
DUN USE MEMORY CARD TO FLASH AGAIN!!!
joncy said:
just an opinion...
remove sd card...
then enter bootloader
then run upgrade DSUU.... follow on screen instruction
should be ok to upgrade your rom...
Click to expand...
Click to collapse
There is no SD card in the phone. the upgrades is went well 100% flashed in.
But the phone still stuck on startup O2 LOgo.
any idea??
BR
mphoneclinic said:
There is no SD card in the phone. the upgrades is went well 100% flashed in.
But the phone still stuck on startup O2 LOgo.
any idea??
BR
Click to expand...
Click to collapse
what ROM version that you used?
think better for you to downgrade to ORIGINAL WM5 ROM. since ATOM EXEC used the MN2 bootloader you will not able to update you rom via bootloader mode. BUT I will share my experience on my ATOM EXEC when my device in unable to boot condition.
1. you need to downgrade your bootloader to MN1 type (ATOM Standard bootloader), copy the EBOOT.nb to your SD card
2. prees camera+reset --> you will see the bootloader found and update, and device turn off
3. TAKE OUT SD CARD !!
4. take out your battery, press CAMERA+RESET and plug in back your battery, you should come back to bootloader mode again (now you should have MN1 bootloader on your ATOM EXEC)
5. Run Xda-Atom-Exec-ENG-20060721-MOT0822.exe, the ROM will be intalled on bootloader mode BUT will be stack 6% on EXTENDED ROM
6. when 6% (progress bar not move anymore) just take out your USB cable from your ATOM --> on this stage you already upgrade ROM + bootloader(MN2) just the EXT ROM failed to update
7. turn on your device, you will able to enter to WM5 but the job not finish yet.
8. run one more time Xda-Atom-Exec-ENG-20060721-MOT0822.exe on DSUU mode, viola after completed the progress your device will be back on ORIGINAL WM5.
note: please read step by step, if you don't understand than better DON'T DO IT, send to service center will be good choice otherwise your ATOM EXEC can really become paper weight!
chartreux said:
1. you need to downgrade your bootloader to MN1 type (ATOM Standard bootloader), copy the EBOOT.nb to your SD card
2. prees camera+reset --> you will see the bootloader found and update, and device turn off
Click to expand...
Click to collapse
What can we do if the bootloader don't start ?
it is possible to modify eboot without bootloader ?
Thanks a lot.
bedav said:
What can we do if the bootloader don't start ?
it is possible to modify eboot without bootloader ?
Thanks a lot.
Click to expand...
Click to collapse
I don't think so, if your device can not be turn on via bootloader mode, then the bootloader corrupted on your device. the key is to secure the bootloader partition. without that one will be useless
I have a T-Mobile MDA Vario II and it just seems that flashing is impossible. I am pulling my hair out!
I have searched the forum and cannot see anyone else having had the same problem
I have tried to flash WM6, as provided by T-Mobile and also I have tried to flash Hard-SPL, but get the same problems with both.
First of all, if I try to flash by flashing from the PC, via ActiveSync, it all seems to be fine until it comes to that actual flashing itself. As soon as the flashing process begins, the phone goes to the bootloader and disconnects from ActiveSync, producing an error message in the program on the PC.
I have tried doing it directly on the phone, as described in post 1160 of the Hard-SPL, Or How to Not Brick Your PDA Ever Again And Fix Bad Blocks! thread, but when I reach step 7, where it should go from the tri-color screen to another screen, asking you to press the power button to start, it doesn't happen! The tri-color screen appears, followed, for less than a second, by a screen which says "Loading..." and then it just goes back to the bootloader screen, where it stays until I do a reset.
Anyone got any ideas at all?
CID Unlock the device then try to flash it, make sure battery is fully charged too. Have you tried entering bootloader manually then trying to flash the tmobile rom?
It won't even let me do that!
I have just tried to do this, using pof's free HTC Hermes SIM & CID Unlocker but even that won't work.
Pof's zip file contains 3 methods of doing this. I'll list all 3, with a description of where it goes wrong each time. Perhaps that will make the problem clearer
Easy auto-install Instructions:
-------------------------------
1. Unzip unlocker and run AUTO_Unlock_v3a.bat
2. Follow directions on screen
The .bat file starts a program on the PC. It goes OK, until it sends the phone to the boot loader screen. ActiveSync immediately disconnects and an error message comes up on the PC...
ERROR [260]: CONNECTION
The Update Utility cannot connect to your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA Phone
Check the following:
1. The PDA Phone is connected to the USB cradle/cable
The USB cradle/cable is connected to the PC
Click 'Exit' to quit
manual instructions:
---------------------------------------------------------------------
1. Transfer SSPL/SSPL-HERM.exe to your phone and run it
2. Tri color screen will appear
3. Disable activesync (file -> connection settings -> uncheck "allow USB connections")
4. Connect your phone to your computer using the USB lead.
As long as the Tri-color screen is showing, the PC does not recognise the PDA Phone as being connected, even if the USB is connected
5. run RUU/RUU_HERM_Unlock_v3a.exe
6. follow the flashing process (Check the "I understand..." and "I completed..." boxes and update!)
Rather unsurprisingly, the same error as above appears
7. Allow your phone to reboot.
8. Transfer HERM_Unlock_v3.exe program to your phone and run it
9. Click the Unlock Button, select unlock option. Select if you want SIM/CID unlock.
10. Click "Unlock!" and wait until process finishes.
11. When done, turn off your phone for 10 seconds and reboot after that.
I actually still went through steps 7 to 11 and it all seemed to work, but although it said the PDA Phone was now SuperCID, it wasn't
update using the SD-Card Method:
-------------------------------------------------------------------------------------
1. Unrar RUU_HERM_Unlock_v3a.exe
2. Unrar RUU_Inside.exe This file doesn't exist in the zip file
3. Empty (erase the contents) of your microSD card from the Windows Mobile file explorer
or format it from your computer using a card reader (in some cases format doesn't work).
4. Rename HermesUnlocker_v3a.nbh to HERMIMG.nbh and copy it to the FAT32 formatted microSD card.
5. Insert microSD card on your phone
6. Transfer SSPL/SSPL-HERM.exe to your phone and run it
7. Confirm flashing on screen by pressing the power button. Nothing to confirm. The phone simply goes straight to the Tri-color screen and stays there until you do a soft reset
Again, I don't know how much help it is, but if I go to the boot loader screen, via the power, OK and soft resent buttons, I see the following information...
HERM300
IPL-1.01
HERM300
SPL-1.04
If I run the SSPL-HERM program on the phone, it takes me to the boot loader screen, but with the following info...
HERM300
HERM-SSPL by des
HERM300
SPL-1.09.ds
Any ideas?
Go to bootloader and tell us what your SPL is... If its 2.10 olipro then you have Hard SPL installed. This process is VERY quick so it may have worked and you just didn't notice the change.
As for using the PC & Activesync, if you have Hard SPl, use the sd card method to load new OS's onto your Phone instead as its safer and easier (same as how you loaded Hard SPL except you don't need to run the SSPL program from your device, just put file on card, rename and reset to bootloader.
Cheers...
That info is in the prevoius post. Before you worry that you are going mad, I edited the message to add that info, so I guess you probably asked, before that info was there
anyone help out a newbie?
thanks.
-Ernest.
Put it in sync before you boot it
DhaMajoR said:
Put it in sync before you boot it
Click to expand...
Click to collapse
that does not work.
Im sorta new too... whats bootloadeR? thanks
Bootloader is the Tri color screen. Wait, let me refer and tell you how to enter bootloader in Hermes.
Regards,
Carty..
Carty said:
Bootloader is the Tri color screen. Wait, let me refer and tell you how to enter bootloader in Hermes.
Regards,
Carty..
Click to expand...
Click to collapse
Yes, I am in that screen.
red, green, blue.
The white section says USB.
Ok, you can access the Bootloader by pressing both the Power button and the Side Ok button together and while you have it pressed, make a soft-reset by inserting your stylus into that hole.
Regards,
Carty..
Exactly, from that screen, connect to Desktop PC and execute the ROM Update Utility to begin flashing of the ROM.
Regards,
Carty..
i'm trying to flash a ROM via ActiveSync, and my Phone won't sync with my computer when I am in BootLoader mode.
You can actually flash without entering Bootloader! Have you tried that?
Remember, when you're in Bootloader screen, the phone will not sync with ActiveSync but can still be flashed if the RUU is executed. Did you try?
Regards,
Carty..
i will try that.
will get back to you...
One more thing, you can exit Bootloader only by flashing a ROM I guess or through a hard-reset too. If you couldn't flash from your PC, try flashing from SD Card.
Regards,
Carty..
m00b3rt said:
i'm trying to flash a ROM via ActiveSync, and my Phone won't sync with my computer when I am in BootLoader mode.
Click to expand...
Click to collapse
You actually dont need to have it synchronized. Just connect, hear that found new hardware sound, directly execute the rom update utility and it will begin flashing.
so, for the HardSPL.
i just run the RUUwraper file, and it'll work out fine?
Yup! Try it out!
But I guess hard SPL requires you to be in normal mode rather than bootloader! If you want to execute bootloader, try flashing the rom that you are about to use after hard spl and that should probably stop in the middle saying Invalid ID or something and your phone may return to normal mode. Then flash hard spl.
Thanks for telling me what bootloader is, I went through that screen but i wasnt sure what it was. Thanks
Once in bootloader mode, you can't connect with activesync...
to get connected with activesync the phone must be in normal mode.
Ok, i have gotten the ActiveSync working.
But now, my new rom, the GOLDENGLOBE by Tai,
I am stuck on the Splash Screen.
(which is the first screen that comes up, in default power on)
help.
Thanks.
Hello.
I tried to update with the ROM from SD card, but it failed.
My phone doesn't boot after that - it hangs up showing just splashscreen and some info -
ONBL 1.07.0000
SPL 1.10.0lip
GSM 02.71.90
OS 1.8.0.0
Hard reset didn't help.
I tried to flash ROM through RUU (device still goes into bootloader by pressing camera+reset/power), but it said
ERROR [200]: Invlid Update Utility
Please get newer Update Utility
Is there any way to flash my device? =\
btw, sorry for my english, i know that it's quite bad )
You need to first patch your HSPL and then flash a custom ROM.kindly read the ROM Upgrading Guide properly in the GENE forum.you can also find the link in my signature.
karan999 said:
You need to first patch your HSPL and then flash a custom ROM.kindly read the ROM Upgrading Guide properly in the GENE forum.you can also find the link in my signature.
Click to expand...
Click to collapse
If you are talking about that method -
Step 5: Use the Orefkov Unlocker
------------------------------------
1. Remove the battery, SIM card and SD Card of your phone and press the Power key for 20 seconds to draw out any residual power from the phone.
2. Replace the battery but not the SIM and SD card, and don't start the phone yet. Press and hold the Camera button and then press the Power button or Soft Reset button. Phone will come to boot loader mode (tricolor screen) and SPL 1.10.Olip will be displayed.
3. Connect the USB cable. The text USB will appear on the bottom of the screen.
4. On PC, go to the folder Orefkov in the folder extracted in step 1 and run the Mtty1_42.exe. Press the button "USB" in the window that opened.
5. In the window that opened, type the following command (don't use copy paste please) and press enter:
Code:
set 32 1
You'll see a response from phone.
6. Type the following command BUT DON'T PRESS ENTER YET:
Code:
ls boot.bin
Note : that is small L and small s in that command, dont mistake it with I.
Now, hold down the Camera button on phone, and press the enter key on computer. After a while, the screen will become White. Continue pressing the Camera button for 10 more seconds.
7. Now release the camera button, close the MTTY program and run ROMUpdateUtility.exe in the same folder, not the one outside it. That one is for RAM flashing that we will use later. Check the boxes in each step and click Next Next and then at last Update. Let it finish the process. Your phone will restart.
8. Now on the splash screen you'll see the info with updated SPL version. The version of SPL will be 1.07.Oref.
Congrats! you have successfully patched your SPL.
Click to expand...
Click to collapse
then it didn't work.
Mtty connects to the phone, it even says that bootlader patched, enters the "White screen" but RUU that is situated in the "Orefkov" folder says still the same: ERROR [200]: Invalid Update Tool
And btw, Orefkov method is for new gene only, am i right?
And I have an old one. And it's already have 1.10.0lip SPL, that allows custom ROM flashing.
LordOfFrost said:
And btw, Orefkov method is for new gene only, am i right?
And I have an old one. And it's already have 1.10.0lip SPL, that allows custom ROM flashing.
Click to expand...
Click to collapse
ya..Your SPL is patched and u have old gene
Now u can Flash Any custom rom from here(just No stock roms)
Problem was solved by deliting Active Sync, cleaning registry with CCcleaner and installing Active Sync after that...
I think that there was some driver problem or smthng >_<
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app