Related
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
dim920 said:
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
Click to expand...
Click to collapse
Humm... that is quite a mouthful. Have you got the correct version of Radio_.nbf ? Not really sure how things work in ipaq. If you have not tried this already, please remove all the .nbf files (in a full rom upgrade package there are 3) except the radio_.nbf and execute the upgrade with the original cable while in the bootloader mode. The original cable is particularly recomended for radio roms. Out of the three .nbf files radio_.nbf takes the maximum time so be patient. Hope this works....and yes please do search an ipaq fora as you will get more specific help.
Thank you very much to try to help me !
The Beetles device work very close to yours.
Excuse me to come in this forum, but i look around the world forums,
but i think helpfull persons are on device like yours.
The Rom upgrade beetles from Hp come with Hpruu.exe and 4 files :
RadioOS.nbf
RadioFS.nbf
CEOS.nbf
Extrom.nbf
If i do only a selected upgrade as you say, i can reinstall the Os,
but never the Radio, always stuck at 1%.
(after os reinstall, gps & bluetooth ok, but gsm asset blank)
It's very similar problem to a lot of bricked Universal device who was
successfully unbricked here.
I spend a lot of time in the Bootloader,
I Know now that my CID is ok, but my Radio Os dead.
All success story i see here manually erase some adress range,
and manually rewrite the radio part.
I can do that in the bootloader with commande "erase" and "wdata".
But i don't know how in the other device you have successfully
find the good adress range to erase and rewrite.
How i can investigate this ?
I have all install of rom from Hp, unofficial, dump rom of a working device of a selected adress range who normally include the radio part, etc..
Thank you
Dim
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
I need help with reviving my bricked HTC Magician. It got bricked when I tried to update with Cotulla WWE 04 ROM. I tried to find an original HTC Magician rom and could only find MA_O2AW_11200_920_11200_Ship.exe. Well trying this too does not work as the following errors appear on the RUU log. Can someone HELP me please?
11:05:15:205 [msg] : Version : [1.5.0].
11:05:15:236 [msg] : Config Info : [776571],[1],[1],[0].
11:05:20:001 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
11:05:24:611 [msg] : Disconnect ActiveSync .... [2]
11:05:24:783 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
11:05:26:861 [err] : BL Get Device Data Error.
11:05:26:908 [msg] : IsBL. BL : [1]
11:05:26:939 [msg] : START UnInitialization !
11:05:26:970 [msg] : END UnInitialization !
Hi All,
I was updating my LG 540GT toswift droid 2.3 from 2.1.While using kdz_fw_upd.exe ,some error occured in between and the process was some what like stuck and not responding.So i exit the program,(meanwhile phone was showing downloading mode).So i unplugged the usb cable and removed the battery to restart it.But after that it is not even switching ON.i tried to go to recovery mode by pressing volume down+camera+power keys,button nothing happened.i tried home+volume up key,the same result.
i tried using Kdz_fw_upd.exe again,its showing "PHONE WAS NOT FOUND" error.I tried all the ways i could.Please help me if i can do anything with it?
Its bricked.
Sent from my GT540 using xda premium
So i cant do anything???
anoopmohamed said:
So i cant do anything???
Click to expand...
Click to collapse
if the phone doesnt turn on at all then u can't
do anything about it..
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
anoopmohamed said:
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
Click to expand...
Click to collapse
actually u do have little hope!
Follow this, this might unbrick ur phone if u
are lucky!
[HOW-TO] Repair your device if it feels like dead | When you click power button nothing happens (Note that this may or may not work)
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to boot your phone into Emergency/Download mode (VOL DOWN + POWER).
If the phone booted into Emergency/Download mode, launch KDZ Updater.
In TYPE dropdown menu, choose EMERGENCY.
Load KDZ(ROM) and flash your phone.
If the phone failed to boot into Emergency/Download mode (VOL DOWN + POWER), launch KDZ Updater.
In TYPE dropdown menu, choose CS_EMERGENCY.
Load KDZ(ROM) and flash your phone.
Thanks to fishears!
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
anoopmohamed said:
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
Click to expand...
Click to collapse
trust me i know how it feels...
the first week i got my phone i stuffed it up by trying
fastboot... then i managed to fix it myself. from then on
i stuffed my phone nearly every single time i tried something...
But i always managed to fix it!
But i guess bad luck 4 u..
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
anoopmohamed said:
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
Click to expand...
Click to collapse
yeah they can be changing the motherboard!
But i think that will cost more than the phone itself..
If u have warranty just say ur phone doesn't turn on and
they will give u a new one!
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
anoopmohamed said:
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
Click to expand...
Click to collapse
Yeah u took out the USB cable while flashing!
Sent from my GT540 using xda premium
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
anoopmohamed said:
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
Click to expand...
Click to collapse
I dont know about that ....
Sent from my GT540 using xda premium
the program showed up a windows-message that it does not work anymore ?
or was it just doing nothing ?
1st the program showed windows error(im using vista) asking the close down the program.So i closed and restarted the program and loaded the kdz file and it again started to do the work.but after few seconds it displayed some upgrade error like "WPARAM_UPGRADE_ERROR Error Code = 1002"
the log file is shown below
[00:15:21:945] : =============================================
[00:15:21:945] : Log is started on 26.11.2011, at 00:15:21:945,
executable: C:\Users\anoopmohamed\Desktop\swift droid\KDZ_FW_UPD.exe (ProcID: 0x00001120),
compile time : Sep 8 2010 17:19:53
[00:15:21:945] : Version :
[00:15:21:947] : strFilename1 = eur
[00:15:21:948] : m_DlMode = 4, m_strBinaryPath = C:\ProgramData\LGMOBILEAX\Phone\europen+fastboot.dz, m_nSelectedImages= 70787108
[00:15:46:357] : Start Web Downloading
[00:15:46:357] : Get Usb Port
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : rsi.strFriendlyName=Standard Modem over Bluetooth link #2
[00:15:46:436] : Remove Standard Modem over Bluetooth link #2
[00:15:46:436] : rsi.strFriendlyName=Nokia 6300 Bluetooth Modem
[00:15:46:436] : Remove Nokia 6300 Bluetooth Modem
[00:15:46:436] : rsi.strFriendlyName=Agere Systems HDA Modem
[00:15:46:436] : Remove Agere Systems HDA Modem
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM13)
[00:15:46:436] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[00:15:46:436] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM13
[00:15:46:436] : Port = COM13
[00:15:46:436] : Clear
[00:15:46:437] : Clear
[00:15:46:438] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:438] : Clear
[00:15:46:439] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:439] : Clear
[00:15:46:440] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:440] : >> DIAG_STATUS_F FAILED
[00:15:46:445] : >>Get Model Name [DIAG_VERNO_F]
[00:15:46:445] : Clear
[00:15:46:446] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:446] : Clear
[00:15:46:447] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:447] : Clear
[00:15:46:448] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:448] : Clear
[00:15:46:449] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:449] : Clear
[00:15:46:450] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:450] : Clear
[00:15:46:451] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:451] : FAIL (No Phone)
[00:15:46:451] : GetModelName() Operation Failed Check Diag CMD
[00:15:46:451] : EMERGENCY Booting Mode
[00:15:46:451] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[00:15:46:451] : Clear
[00:15:46:451] : Clear
[00:15:46:452] : BS/GT540/7D
[00:15:46:452] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - GT540
[00:15:46:452] : >>Get Mobile SW [DIAG_EXT_BUILD_ID_F]
[00:15:46:452] : Clear
[00:15:46:452] : Clear
[00:15:46:453] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:453] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:453] : Clear
[00:15:46:454] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:454] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:454] : Clear
[00:15:46:455] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:455] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:455] : FAIL
[00:15:46:455] : Phone_Diag_Status = FALSE
[00:15:46:455] : Clear
[00:15:46:455] : Clear
[00:15:46:456] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:456] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:456] : Clear
[00:15:46:457] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:457] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:457] : Clear
[00:15:46:458] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:458] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:458] : NV Write Fail : NV ITEM 9028(9028)
[00:15:46:558] : m_pPhoneCtrl->m_pDload->Dl_GetCommMode(&m_pPhoneCtrl->m_pDload->m_nCommMode)
[00:15:46:558] : >> GET DLOAD COMM MODE
[00:15:46:558] : Clear
[00:15:46:558] : Clear
[00:15:46:559] : [GetCommMode] Communication mode : 2
[00:15:46:559] : Pre Nand Download
[00:15:46:559] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[00:15:46:559] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[00:15:46:559] : Clear
[00:15:46:559] : Clear
[00:15:46:560] : [COM13] >>NandFlashInitWithFile(PARTITION TBL), BinType =8
[00:15:46:560] : NandFlashInitWithFile :: LG3GBinaryList[BinType].szBinaryTypeName = PARTITION TBL, BinType = 8
[00:15:46:560] : NandFlashInitWithFile ::
[00:15:46:560] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[00:15:46:560] : Clear
[00:15:46:560] : Clear
[00:15:49:672] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:49:672] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:49:672] : Clear
[00:15:52:777] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:52:777] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:52:777] : Clear
[00:15:55:880] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:55:880] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:55:880] : [COM13] FAIL
[00:15:55:880] : Clear
[00:15:55:880] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[00:15:55:880] : Close Port<<
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002
[00:15:55:904] : Log finished
So no process was showing later.I tried a couple of times,same.So i thought of doing it later.Exit the program.But the phone was still in DOWNLOAD MODE,then i pulled out the battery and the usb cable from it.
Hi guys,
Cloud_Commander is a universal gsm software.
The software was targeted towards phone technicians and users for free.
Currently development is at ver 1.7 which will be completed in 1 weeks time.
This new version includes upgrades to the user interface, lumia unbrick , huawei code calculator.
It also has an added pinouts page, pinouts editor, f2search(search engine) editor.
Most of the data is stored on my server and aws s3 bucket for easy distributing.
All bugs should be reported to [email protected]
NB: THE SOURCES OF THIS SOFTWARE IS ALSO FOR SALE INCLUDING ALL RIGHTS (OWN THIS SOFTWARE AS YOUR OWN), CONTACT ME FOR MORE DETAILS !
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY!
SCANNED WITH BIT-DEFENDER ANTI-VIRUS
DOWNLOAD_HERE VER1.2
EDIT:
Version 1.2 does not update tables since we shifted our servers to cloudflare and has some minor engine flaws thus it's obsolete.
Download the latest version to maintain commands compatibility.
DOWNLOAD_HERE VER1.6
VER 1.6 ADDED LUMIA UNBRICK
Inspired by this thread: Lumia Unbrick.
All you need are the hexfiles in their original naming e.g 00E9427DF118D9E27D098D13BECB6C6C89CE59F4.hex in the tools/mpreg folder.
And the ffu+vpl file.
The tool will do the whole procedure without the user issueing a single command.
You can also use uefi flashmode.
Just make sure you have the necessary drivers installed and don't forget to runas administrator.
CLOUD_COMMANDER VER 1.7 (PIRATES EDITION) THREAD
XDA:DevDB Information
Cloud_Commander Ver1.6 (Anathema) [BETA], Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Testing
Current Beta Version: 1.3
Beta Release Date: 2016-05-24
Created 2016-5-24
Last Updated 2016-05-24
Currently I am looking for someone to compile us a modified adb.exe with a few additional parameters specifically to allow us to port almost all existing tools to our newly founded tool.
I can't compile adb myself since the current state of my server is delicate and would result into overuse of current resources on my server.
Commonly used scripts and commands will become available soon, it's only a matter of time.
[Cloud_Commander ver1.1 updates]
Added Monkey virus remover.
Added (Password Cracking) Hash identifier.
Added (Password Cracking) John the reaper.
The rest of the algorithims should be easy give the md5 as an example.
This is proof that Cloud_Commander's capabilities endless.
(Make sure you update tables first).
Download necessary files from Google drive [ h t t p : / / a d f . l y / 1 U G w e s ]
Remove spaces above.
Extract the files to the Cloud_Commander base dir and overwrite.
We will fix this once we find sharing bandwith srry.
Features_added
FEATURES_ADDED
Remote view (WIP)
NB:ALL DEVELOPEMENT HAD BEEN PAUSED
Psn_adn tools
The setups section now works.
By the way, antivirus software may see rooting tools as a virus beware.
Hi all,
Since we moved our servers to cloudflare, one important feature of cloud_commander is not working "Update tables.
This service relies on rapidxml to download the *.xml updates.
However we are working on a solution to move over to libcurl which is faster.
To use this feature you you will have to wait for Cloud_Commander release codenamed "Bluebuilds" probly by the end of this week.
Nokia Lumia 925 RM-892
erro
Code:
Preparing ffu file.
Starting Lumia Unbrick.
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
tools\lumia\thor2.exe -mode ffureader -ffufile C:/Users/MSA/Desktop/CD-01/CD-celular/Lumia 925 fw/059V013/RM892_3051.50009.1424.0001_RETAIL_lta_brazil_910_01_441464_prd_signed.ffu -dump_gpt -filedir C:\lumia\files
Process started Tue May 24 21:55:35 2016
Logging to file C:\Users\MSA\AppData\Local\Temp\thor2_win_20160524215535_ThreadId-3584.log
Debugging enabled for ffureader
Initiating do FFUReader operations
Version of FfuReader is 2015061501
Parsing FFU... Please wait...
readFfu() Start.
readSecurityHdrAndCheckValidity() Start.
readSecurityHdrAndCheckValidity() End.
readGpt() Start.
readGpt() End.
readRkh() Start.
readRkh() End.
readRkh() Start.
.readRkh() End.
DumpGpt() Start.
DumpGpt() End.
checkDppPartition() Start.
checkDppPartition() End.
readFfu() End.
Successfully parsed FFU file. Header size: 0x000e0000, Payload size: 0x0000000062dc0000, Chunk size: 0x00020000, Header offset: 0x00000000, Payload offset: 0x00000000000e0000
HeaderStart 0x80000
GPT Header
-------------
Revision : 65536
CRC32 : 0x58e24762
FirstUsableLBA : 34
LastUsableLBA : 20971486
AlternateLBA : 20971519
MyLBA : 1
NumberOfPartitionEntries : 128
PartitionEntryLBA : 2
PartitionEntryArrayCRC32 : 0xfd6e37aa
GPT Partitions
-------------
DPP
startLBA : 0x0000000000001000
endLBA : 0x0000000000004fff
Size : 0x0000000000004000
Attributes: 0x8000000000000000
MODEM_FSG
startLBA : 0x0000000000005000
endLBA : 0x00000000000067ff
Size : 0x0000000000001800
Attributes: 0x8000000000000000
SSD
startLBA : 0x0000000000007000
endLBA : 0x000000000000701f
Size : 0x0000000000000020
Attributes: 0x8000000000000000
SBL1
startLBA : 0x0000000000008000
endLBA : 0x0000000000008bb7
Size : 0x0000000000000bb8
Attributes: 0x8000000000000000
SBL2
startLBA : 0x0000000000009000
endLBA : 0x0000000000009bb7
Size : 0x0000000000000bb8
Attributes: 0x8000000000000000
SBL3
startLBA : 0x000000000000a000
endLBA : 0x000000000000afff
Size : 0x0000000000001000
Attributes: 0x8000000000000000
UEFI
startLBA : 0x000000000000b000
endLBA : 0x000000000000c387
Size : 0x0000000000001388
Attributes: 0x8000000000000000
RPM
startLBA : 0x000000000000d000
endLBA : 0x000000000000d3e7
Size : 0x00000000000003e8
Attributes: 0x8000000000000000
TZ
startLBA : 0x000000000000e000
endLBA : 0x000000000000e3e7
Size : 0x00000000000003e8
Attributes: 0x8000000000000000
WINSECAPP
startLBA : 0x000000000000f000
endLBA : 0x000000000000f3ff
Size : 0x0000000000000400
Attributes: 0x8000000000000000
BACKUP_SBL1
startLBA : 0x0000000000010000
endLBA : 0x0000000000010bb7
Size : 0x0000000000000bb8
Attributes: 0x8000000000000000
BACKUP_SBL2
startLBA : 0x0000000000011000
endLBA : 0x0000000000011bb7
Size : 0x0000000000000bb8
Attributes: 0x8000000000000000
BACKUP_SBL3
startLBA : 0x0000000000012000
endLBA : 0x0000000000012fff
Size : 0x0000000000001000
Attributes: 0x8000000000000000
BACKUP_UEFI
startLBA : 0x0000000000013000
endLBA : 0x0000000000014387
Size : 0x0000000000001388
Attributes: 0x8000000000000000
BACKUP_RPM
startLBA : 0x0000000000015000
endLBA : 0x00000000000153e7
Size : 0x00000000000003e8
Attributes: 0x8000000000000000
BACKUP_TZ
startLBA : 0x0000000000016000
endLBA : 0x00000000000163e7
Size : 0x00000000000003e8
Attributes: 0x8000000000000000
BACKUP_WINSECAPP
startLBA : 0x0000000000017000
endLBA : 0x00000000000173ff
Size : 0x0000000000000400
Attributes: 0x8000000000000000
UEFI_BS_NV
startLBA : 0x0000000000018000
endLBA : 0x00000000000181ff
Size : 0x0000000000000200
Attributes: 0x8000000000000000
UEFI_NV
startLBA : 0x0000000000019000
endLBA : 0x00000000000191ff
Size : 0x0000000000000200
Attributes: 0x8000000000000000
PLAT
startLBA : 0x000000000001a000
endLBA : 0x000000000001dfff
Size : 0x0000000000004000
Attributes: 0x80000000
00000000
EFIESP
startLBA : 0x0000000000020000
endLBA : 0x000000000003ffff
Size : 0x0000000000020000
Attributes: 0x8000000000000000
MODEM_FS1
startLBA : 0x0000000000040000
endLBA : 0x00000000000417ff
Size : 0x0000000000001800
Attributes: 0x8000000000000000
MODEM_FS2
startLBA : 0x0000000000042000
endLBA : 0x00000000000437ff
Size : 0x0000000000001800
Attributes: 0x8000000000000000
UEFI_RT_NV
startLBA : 0x0000000000044000
endLBA : 0x00000000000441ff
Size : 0x0000000000000200
Attributes: 0x8000000000000000
UEFI_RT_NV_RPMB
startLBA : 0x0000000000045000
endLBA : 0x00000000000450ff
Size : 0x0000000000000100
Attributes: 0x8000000000000000
MMOS
startLBA : 0x0000000000046000
endLBA : 0x000000000006e67f
Size : 0x0000000000028680
Attributes: 0x8000000000000000
MainOS
startLBA : 0x0000000000070000
endLBA : 0x00000000004c8e7f
Size : 0x0000000000458e80
Attributes: 0x0000000000000000
Data
startLBA : 0x00000000004cc000
endLBA : 0x00000000013fefff
Size : 0x0000000000f33000
Attributes: 0x8000000000000000
Number of partitions found 28
RKH of SBL1: CD84376222AAF204C85119532BF34EA55C8844E4CEA35F3E508D25AA34D96637
RKH of UEFI: CD84376222AAF204C85119532BF34EA55C8844E4CEA35F3E508D25AA34D96637
Platform ID: Nokia.MSM8960.P6023
Hi. index sector 20967168
Computing integrity of FFU. Please wait...
..............................
FFU integrity OK.
Exited with success
Loading hexfiles.
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/00E9427DF118D9E27D098D13BECB6C6C89CE59F4.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/0CBD2EED6F62230571CBAB55B7DBC15F8A7DC7BB.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/106D7E7DDC685B6E693326851A5DDACB7326B029.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/25C0C84AECBD154F817825B24D4EB4BCF5E606E6.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/26323C81CFBFD503F6C530F0EA1C2E7A34039581.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/64356634FCA08BC9E0D02C14BDB230B0076D3109.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/67131691EEDD1F38568C7FFAE284FB2621680FEA.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/77081E5E2C97F9CF18CE2FA47446465D7B637964.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/7C81AABA97E4904DB782605A6C74A59480361E5A.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/87112B5F595D325FCE763FDF58E292D44B174496.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/8C042CBCE09E4064586DA2A5DFB81D3C52A3B99F.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/96704211798B2DBA62809761554D3CB57DB62FDE.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/98BECD6BD8BA16F28867306AE571DC79E50714EB.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/9DF6E11153C33AA85F7984C21EFA43AEDF9B82BE.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/A74593CEE9F88EDA6D4950CA46A3A634381F9458.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/CD84376222AAF204C85119532BF34EA55C8844E4.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/D3767535C2FBE04AA0398D933F3EA95D791098C9.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/D9370EF349090B2A08AF2EC7FBF8E4A9CD7CDA6E.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/DB73418E5840941CE7BD35949085B8F74628D511.hex
Found hexfile :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/F771E62AF89994064F77CD3BC16829503BDF9A3D.hex
HEXFILE:Using :C:/Users/MSA/Downloads/Compressed/release/tools/mpreg/CD84376222AAF204C85119532BF34EA55C8844E4.hex
Lumia Unbrick Step 2.
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
tools\lumia\thor2.exe -mode emergency -hexfile C:\lumia\files\HEX.hex -mbnfile C:\lumia\files\msimage.mbn -orig_gpt
Process started Tue May 24 21:56:14 2016
Logging to file C:\Users\MSA\AppData\Local\Temp\thor2_win_20160524215614_ThreadId-6008.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Message send failed with error code -1
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 7.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.18 exited with error code 85021 (0x14C1D)
Try running the tool as administrator.
Sent from my GT-I8260 using xda app-developers app
The device will switch mode after receiving hexfile, yours doesn‘t.
Also try a second option ‘retry‘
It uses uefi flashmode
Sent from my GT-I8260 using xda app-developers app
kenkitt said:
Try running the tool as administrator.
Sent from my GT-I8260 using xda app-developers app
Click to expand...
Click to collapse
friend run as administrator yes
my lumia 925 RM-892
the ever mistake it not only connects recognizes as QHSUSB_DLOAD
Try using windows recovery tool.
If it fails jtag.
where is the bloatware,monkey and virus removal tool?
sorry,now i find the command but plz add something for clean android system,sex pages,links,china malwaresexy hot wallpaper,hot video,love beauty,lutu,morecast,poly videos,mp3 free downloader etc etc,thanks
"The ffu file you chose may have failed to extract!, press cancel and start over". I'm getting this error, But the ffu extraction was exited with success.
Model: RM-875
LUMIA 1020
santhosh369 said:
"The ffu file you chose may have failed to extract!, press cancel and start over". I'm getting this error, But the ffu extraction was exited with success.
Model: RM-875
LUMIA 1020
Click to expand...
Click to collapse
If extraction was successfull you should find the files in C:\lumia\files
if there are no files make sure you create the directory first( C:\lumia\files).
The message appears if there is no.
GPT0.bin
if the file is found it will be renamed to:
msimage.mbn
The last file to be added after (step 2) is the hex file which is matched from the signature ofRKH of SBL1 :
HEX.hex
nykocam said:
where is the bloatware,monkey and virus removal tool?
sorry,now i find the command but plz add something for clean android system,sex pages,links,china malwaresexy hot wallpaper,hot video,love beauty,lutu,morecast,poly videos,mp3 free downloader etc etc,thanks
Click to expand...
Click to collapse
If there are new commands make sure you choose "setups from devs" in combo index 1, then install the neccessary components.
To remove monkey virus you must have a rooted device with usb debugging enabled.
Unfortunately I haven't encountered most virus, I only add those I come accross. Fortunately anyone can add commands to the tool.
TO ADD COMMANDS/SCRIPTS:
Go to menu-->dev console
After adding commands, make sure you share necessary files by adding them into the "setups from devs" section.
You can use wget so that anyone can download files.
The reason I made this tool open, is so that anyone can use it to add their own components.
Like FRP Removal tools combo 1 "Password and Cracking tools"
You can add your own virus removal scripts. But remember that , if files are needed by your command they shoud go in the setups section.
Can't open the tool (with administartor also can't)
I'm using Windows 10 Pro x64.
I can't open the tools, what missed?
T4ufik_Hidayat said:
I'm using Windows 10 Pro x64.
I can't open the tools, what missed?
Click to expand...
Click to collapse
I haven't tested it on 64bit yet, but there is nothing that would prevent it from running, make sure you run as admin, or post logs after the app crushes (If it crushes)
Cloud_commander ver (1.7 pirate edition)
CLOUD_COMMANDER VER (1.7 PIRATE EDITION)
Added adb latest adb support.
Improved layout and increased window size.
Added f2search user panel.
Added LG file download by imei and flashtool launchers.
Improved lumia unbrick tool(works in progress).
Added powerfull windows driver manager.
Fixed huawei calc layout bug.
Added advanced phone hardware pinouts for hardware help.
Added f2search username in settings(New files will be added on release).
We'll fix commands arrangement to follow order (also on release).
Watch out for new thread link