Hi All!
Before crash my Orbit(UK) has:
IPL: 1.25.0001
SPL: 1.25.0000
GSM: 02.67.90
OS: 1.25.00
In About was: OS 5.1.342 (Build 15096.3.0.0)
I have try to flash this ROM:
PDAVIET from PhamQuang
http://www.pdaviet.net/showpost.php?p=124633&postcount=313
(pass PDAVIET)
and made an mistake: I dont flash Artemis Update SPL (USPL) v.01 ( http://forum.xda-developers.com/showthread.php?t=311403 ) before PDAVIET from PhamQuang
Now my Orbit is freese after start on bootscreen.
But I CAN ENTER to Bootloader.
Help me to ident official ROM (and give link to file, please) or say what can I do in this situation.
I've try this ROM's:
O2 XDA Orbit 3.4.207 GER - say: FEHLER [244] : UNGULTIGE MODELL ID
T-mobile UK 1.13.110 - say: ERROR [294] : INVALID VENDER ID
English Dopod 1.25.707 - say: ERROR [244] : INVALID MODEL ID
ART_HTCFRA_11240601_026790_FRA_SHIP.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11140501_024990_WWE_Test_R.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11240501_026790_WWE_Test.exe -say: ERROR [244] : INVALID MODEL ID
DVG said:
Hi All!
Before crash my Orbit(UK) has:
IPL: 1.25.0001
SPL: 1.25.0000
GSM: 02.67.90
OS: 1.25.00
In About was: OS 5.1.342 (Build 15096.3.0.0)
I have try to flash this ROM:
PDAVIET from PhamQuang
http://www.pdaviet.net/showpost.php?p=124633&postcount=313
(pass PDAVIET)
and made an mistake: I dont flash Artemis Update SPL (USPL) v.01 ( http://forum.xda-developers.com/showthread.php?t=311403 ) before PDAVIET from PhamQuang
Now my Orbit is freese after start on bootscreen.
But I CAN ENTER to Bootloader.
Help me to ident official ROM (and give link to file, please) or say what can I do in this situation.
I've try this ROM's:
O2 XDA Orbit 3.4.207 GER - say: FEHLER [244] : UNGULTIGE MODELL ID
T-mobile UK 1.13.110 - say: ERROR [294] : INVALID VENDER ID
English Dopod 1.25.707 - say: ERROR [244] : INVALID MODEL ID
ART_HTCFRA_11240601_026790_FRA_SHIP.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11140501_024990_WWE_Test_R.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11240501_026790_WWE_Test.exe -say: ERROR [244] : INVALID MODEL ID
Click to expand...
Click to collapse
Try this with the file:
Attempt - start the device in mode bootloader. Disconnect AS and start mtty. Choose USB.
Take on one commands ( not copy/paste).
set 32
password BsaD5SeoA
ruurun 0
ResetDevice
An other thing you can try is this provided by stewd:
WARNING THIS WORKED FOR ME THERE IS NO GUARANTEE IT WILL WORK FOR YOU BUT I DON'T SEE WHY NOT TO BE HONEST (SORRY FOR THE CAPS)
Having succesfully bricked my orbit like several others, I spent the morning scratching my head....
I think it was caused by rebooting after running USPL, and then runnig the ROM upgrade....anyway........
My Orbit was stuck on the initial boot O2 screen with red writing on it
IPL 1.25.0001
SPL 1.25.0000
GSM 02.67.90
OS 3.4.0.0
Oh bollocks says I.....
What I did
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
But basically.........
Wieter = next
Abbrechen = Cancel
aktualisieren = update
The update completes succesfully and you have WM6 and an unbricked Orbit......
WOOHOO !
pvdhelm said:
Try this with the file:
Attempt - start the device in mode bootloader. Disconnect AS and start mtty. Choose USB.
Take on one commands ( not copy/paste).
set 32
password BsaD5SeoA
ruurun 0
ResetDevice
Click to expand...
Click to collapse
After that, Orbit is restart..
...and freeze on bootscreen.
On screen is only HTC wallpaper and this text:
IPL: 1.12.0001
SPL: 1.12.0000
GSM: 02.67.90
OS: 3.4.0.0
Click to expand...
Click to collapse
pvdhelm said:
What I did
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
Click to expand...
Click to collapse
In this case:
My Orbit is start's upgrade, but in 3% - reboot and:
On screen is only HTC wallpaper and this text:
IPL: 1.12.0001
SPL: 1.12.0000
GSM: 02.67.90
OS: 3.4.0.0
Click to expand...
Click to collapse
In this time on PC - FEHLER [270]: UPDATE-FEHLER
Any other ideas?
imei-check
you will have to send it to a repair center..i had the same issue
you can also send it to the guys at imei-check.co.uk but they accept only EU shipments..the repair will cost you 40£ + 7£
zipper9 said:
you will have to send it to a repair center..i had the same issue
you can also send it to the guys at imei-check.co.uk but they accept only EU shipments..the repair will cost you 40£ + 7£
Click to expand...
Click to collapse
Only this way?
I'm not from UK.
Anybody else?
Still actually.
The fourth day without phone.
pvdhelm
You see that give ????
Your file SPL from Hermes !!!
If you load this on artemis -brick!
My "getdevinfo" is:
41 52 54 45 32 30 30 30 30 00 00 00 00 00 00 00 ARTE20000.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
4F 32 5F 5F 5F 30 30 31 00 00 00 00 00 00 00 00 O2___001........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
Click to expand...
Click to collapse
DVG said:
My "getdevinfo" is:
Click to expand...
Click to collapse
Your Orbit is actually from O2 UK (CID: O2___001). You have to find a ROM for O2 Orbit UK then. Unfortunately, no one has it at the moment, and O2 UK does not seem to release the update soon. You have to wait then, I guess!
One thing I wonder: This code was returned by "getdevinfo" command from within mtty or from nbh file that you tried to flash? Usually "getdevinfo" in mtty returns only ARTE10000, ARTE20000 or ARTE30000
Use USB sniffer and see command getdevinfo
my device ARTE10000 and CID 11111111 (SuperCID )
Code:
Cmd>
67 g
67 g
65 e
65 e
74 t
74 t
64 d
64 d
65 e
65 e
76 v
76 v
69 i
69 i
6e n
6e n
66 f
66 f
6f o
6f o
0d .
0d 0a ..
48 54 43 53 HTCS
41 52 54 45 31 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ARTE10000.......
31 31 31 31 31 31 31 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11111111........
00 00 ..
e3 a4 ef 19 ....
48 54 43 45 HTCE
0d 0a ..
43 6d 64 3e Cmd>
YEAH!!! I've succesfully unbrik my Artemis!!! I'm too happy!!!
fabbio87 said:
YEAH!!! I've succesfully unbrik my Artemis!!! I'm too happy!!!
Click to expand...
Click to collapse
By what method?
Whit this method (posteb by PVDHELM)
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
But basically.........
Wieter = next
Abbrechen = Cancel
aktualisieren = update
For me this method work! I've an Italian No Brand Artemis (HTC P3300) with CID Lock and without Sim Lock.
fabbio87 said:
Whit this method (posteb by PVDHELM)
Click to expand...
Click to collapse
It means that you have a German Artemis device, but my Orbit - had UK firmware basically. And now I can't find it.
No, my phone is Italian, not german!
fabbio87 said:
No, my phone is Italian, not german!
Click to expand...
Click to collapse
You are lucky! I am sure your device is CID UNLOCKED (may be you did not know) so you could flash Black and Blue ROM. This ROM was made by HTC ROM tool and signed with SuperCID. Congratulations! You can now flash any ROM you build by HTCRT.
I don't know if my HTC is CID unlock, how can i do to know if it is? I've never try to unlock it, i only flash the USPL...
fabbio87 said:
how can i do to know if it is?
Click to expand...
Click to collapse
Turn off USB connection in ActiveSync.
Take mtty and any USB sniffer.
In mtty chose USB connection.
And then TYPE:
set 32
password BsaD5SeoA
getdevinfo
ruurun 0
ResetDevice
After getdevinfo command see what in USB sniffer. If there CID 11111111 - you are lucky - it Super CID - your device is CID Unlocked.
My problem is still actually.
i try change rom by worng file now stock in boot loader
ATHE100
IPL-V2.02
ATHE100
SPL-V3.05.0000
flash again with official rom for HTC Athena >> http://shipped-roms.com/index.php?category=windows%20mobile&model=Athena
try many official rom but error invalid vender id and model id
pls how i know my device CID
MA7MOD_GSM said:
try many official rom but error invalid vender id and model id
pls how i know my device CID
Click to expand...
Click to collapse
doing set 32 command in mtty console !
in response you will see g_cKeyCardSecurityLevel = 00 or
g_cKeyCardSecurityLevel = FF
00 - is unlocked
FF - locked
in response you will see g_cKeyCardSecurityLevel = 00 or
g_cKeyCardSecurityLevel = FF
i know cid locked but i need to know what orignal rom for my device
there any method to know CID MODEL FOR ATHENA
thanks
MA7MOD_GSM said:
in response you will see g_cKeyCardSecurityLevel = 00 or
g_cKeyCardSecurityLevel = FF
i know cid locked but i need to know what orignal rom for my device
there any method to know CID MODEL FOR ATHENA
thanks
Click to expand...
Click to collapse
Operating System that is embedded from the manufacturer are WM 5.0
i don't know what to do
in step 13
when i press 's' i got error messege in red
error:
update device fa9e0019 - adfd74d6 - ea5e52ec - 3b39c693 complete with error code: 80188222, error message: Phone Update Agent Error: The preinstallation update package <or sperpackage> isn't valid
i carfully do step by step ... what i should do?
After install cm-10.1-20130709-NIGHTLY_v2 ,i try to install stock rom and get this error.
09/21/13 10:59:08 ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7 - on device ID 0.
09/21/13 10:59:08 ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 - on device ID 0.
09/21/13 10:59:08 [Device ID: 0] Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7
any sugestion ?
SystEM4sk said:
After install cm-10.1-20130709-NIGHTLY_v2 ,i try to install stock rom and get this error.
09/21/13 10:59:08 ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7 - on device ID 0.
09/21/13 10:59:08 ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 - on device ID 0.
09/21/13 10:59:08 [Device ID: 0] Phone[0000]: Error verifying Code Group 31 checksums. File: 0x93C5, Phone: 0xAAF7
any sugestion ?
Click to expand...
Click to collapse
Redownload stock sbf.
hotdog125 said:
Redownload stock sbf.
Click to expand...
Click to collapse
i have tested dont work
Checksum errors are quite bad, indicative of some degree of eMMC failure. Try flashing dfp231 sbf or a more recent version since it seems to fix errors in some cases
Sent from my MB526 using Tapatalk 2
thekguy said:
Checksum errors are quite bad, indicative of some degree of eMMC failure. Try flashing dfp231 sbf or a more recent version since it seems to fix errors in some cases
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
dont work ç_ç
SystEM4sk said:
dont work ç_ç
Click to expand...
Click to collapse
Hardware failure then unfortunately
Sent from my MB526 using Tapatalk 2
thekguy said:
Hardware failure then unfortunately
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for helping me anyway. :laugh:
motorola defy rip.