Related
Hello everyone. I just wanted to install SDSL3 for my Swift. I get into fastboot flashed MBN file for 170mb system partition and when i was flashing system i get "TOO MANY LINKS" error.
After that i was trying to do that again but fastboot said <WAITING FOR DEVICE>.
Now I'm trying to flash my Swift with KDZ (English Version)
All the time i get this:
Code:
[R&D Test Tools Log File]
19:35:58 : Launching SW update
19:35:58 : Unpacking KDZ
19:36:03 : KDZ file extraced
19:36:04 : Files were extracted.
19:36:04 : LGMobileDL Load.
19:36:04 : Port = -1
19:36:04 : Connecting to phone
19:36:19 : Check Phone mode = 1
19:36:37 : Phone type check.......
19:37:00 : _DetachDLL Call
19:37:00 : _DetachDLL Call End
19:37:00 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\poland.dz
19:37:00 : Param : moduleDir =
19:37:00 : Param : waitTime = 0
19:37:00 : Param : UsbHighSpeed = 1
19:37:00 : Param : PhoneMode = 1
19:37:00 : Param : BinVersion = openpl (1)
19:37:00 : Param : AuthMark = 0
19:37:00 : Call fn_StartUpgrade
19:37:08 : CDMA: wParam = 3, lParam = 0
19:37:08 : Step : C Drive Erase
19:37:53 : CDMA: wParam = 205, lParam = 0
19:37:53 : Model Dll Msg Not Found(205, 0)
Please HELP ME! :C
I suppose it is drivers problem. Reinstall and try again
Sent from my GT540 using Tapatalk
It doesn't help
Hows behave your phone, are you able to get into recovery or fastboot, or it normally starts
Sent from my GT540 using Tapatalk
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Help anyone?
Sent from my GT-P3100 using XDA Premium HD app
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Aditya16 said:
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
have you tried "Triangule Away" ?
you can installed it from google play
but you need to root your device first
sapiterbang said:
have you tried "Triangle Away" ?
you can installed it from google play
but you need to root your device first
Click to expand...
Click to collapse
I resetted it with that only. Is it some bug in jb?
Sent from my GT-P3100 using XDA Premium HD app
Alvin Lai said:
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Will try that.
Sent from my GT-P3100 using XDA Premium HD app
May be try installing supersu ( not superuser) from google play and give permissions to triangle away
Install latest version 1.95 of triangle away
Sent from Galaxy S2 or Galaxy Tab2
I confirm Triangle Away and SuperSU combination still work in JB.
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone can help you...
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone could help you
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
ketut.kumajaya said:
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
Click to expand...
Click to collapse
How will i get this sbl.bin file from?
Aditya16 said:
How will i get this sbl.bin file from?
Click to expand...
Click to collapse
From /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3. Be careful, this is a critical part of boot process.
I really do not not know how to do it advice please?
Sent from my GT-P3100 using XDA Premium HD app
News update guy's. Chainfire pm'ed me saying that he will look into the matter. Now all we can do is cross our finger and wait.
Oh and also this download mode does not show +1 when I replaced CWM with stock recovery. I wonder why?
Sent from my GT-P3100 using XDA Premium HD app
UPDATE:
No warning when boot to stock JB XXCLI5 recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x135b4d bytes)
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
More investigation needed, when boot to unofficial recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x39a7b0 bytes)
Ramdisk @ 82800000 (0x1e4fc6 bytes)
[WARNING] Current kernel is NOT official binary!!!
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
Normal boot to stock JB XXCLI5 kernel:
Code:
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Parsed above value from /proc/last_kmsg. From last_kmsg value (second boot loader message?), I can confirm my boot logo hack is safe. Sbl successfuly mount param.lfs:
Code:
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
Hello, i failed to flash v10k_00, rooted, unlocked bootloader and CWM ror throght KDZ.
It shows:
18:46:47 : Launching SW update
18:46:47 : Unpacking KDZ
18:48:34 : KDZ file extraced
18:49:57 : Files were extracted.
18:49:57 : LGMobileDL Load.
18:49:57 : Port = -1
18:49:57 : Connecting to phone
18:50:06 : Check Phone mode = 2
18:50:23 : Phone type check.......
18:50:29 : _DetachDLL Call
18:50:29 : _DetachDLL Call End
18:50:29 : Param : Path = C:\Documents and Settings\All Users\Application Data\LGMOBILEAX\Phone\LGP700AT-ROOT-CWM-NewBoot-00-V10k-EUR-XX-FEB-22-2013+0.dz
18:50:29 : Param : moduleDir =
18:50:29 : Param : waitTime = 0
18:50:29 : Param : UsbHighSpeed = 1
18:50:29 : Param : PhoneMode = 2
18:50:29 : Param : BinVersion = V10K_00
18:50:29 : Param : AuthMark = 0
18:50:29 : Call fn_StartUpgrade
18:50:30 : CDMA: wParam = 206, lParam = 0
18:50:30 : Model Dll Msg Not Found(206, 0)
What should i do to flash this success ?
Sorry for bad english.
faters said:
18:50:30 : Model Dll Msg Not Found(206, 0)
Click to expand...
Click to collapse
Those errors are normal, let it finish, it will reboot the phone automatically.
Ok, ill try one more time
same problem and i wait about 10-15min and nothing happen with my phone
UNOSlv said:
same problem and i wait about 10-15min and nothing happen with my phone
Click to expand...
Click to collapse
What phone do you have? I have a L3.Did you try flashing without the battery in your phone. Also what mode are you using diag or emergency
FlowUK said:
What phone do you have? I have a L3.Did you try flashing without the battery in your phone. Also what mode are you using diag or emergency
Click to expand...
Click to collapse
I have L7 , i am using emergency mode and i try one time flash without battery
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
i need a cat /proc/iomem
I don't know what you meant by logcat, but I presume this is what you want.
Code:
athene:/ # cat /proc/iomem
0005c000-0005cfff : tsens_eeprom_physical
000601d0-000611cf : vmpm
0006c000-0006c1ff : phy_csr
0006c000-0006c1ff : phy_csr
0006c000-0006c1ff : phy_csr
004a8000-004a9fff : tsens_physical
004ab000-004ab003 : pshold-base
01871000-01871003 : restart_reg
01b00020-01b0002f : csi_clk_mux
01b00030-01b00033 : csiphy_clk_mux
01b00038-01b0003b : csiphy_clk_mux
01b04000-01b040ff : 1b04000.qcom,cpp
01b08000-01b080ff : 1b08000.qcom,csid
01b08400-01b084ff : 1b08400.qcom,csid
01b08800-01b088ff : 1b08800.qcom,csid
01b0a000-01b0a4ff : 1b0a000.qcom,ispif
01b0ac00-01b0adff : 1b0ac00.qcom,csiphy
01b0b000-01b0b1ff : 1b0b000.qcom,csiphy
01b0c000-01b0cfff : 1b0c000.qcom,cci
01c00000-01c0ffff : kgsl-3d0
01c20000-01c2ffff : kgsl-3d0
04020000-0402003f : rmb_base
04080000-040800ff : qdsp6_base
07803000-0780afff : /soc/[email protected]
07824900-07824dff : mmc0
07864900-07864a1b : mmc1
07884000-078a2fff : /soc/qcom,[email protected]
078b0000-078b01ff : msm_serial_hsl
078b6000-078b6fff : 78b6000.i2c
078b7000-078b75ff : 78b7000.i2c
078b8000-078b85ff : 78b8000.i2c
078db000-078db3ff : core
078db000-078db3ff : core
07af5000-07af55ff : spi_qsd
07af8000-07af85ff : spi_qsd
0a0120a8-0a0120af : alarms_txctl
0a012448-0a01244f : alarms_tactl
0a08040c-0a080413 : wlan_tx_status
0a080488-0a08048f : wlan_tx_phy_aborts
0a080c00-0a080c00 : pronto_mcu_base
0a080fb0-0a080fb7 : wlan_brdg_err_source
0a100400-0a1005ff : pronto_a2xb_base
0a205050-0a20524f : pronto_ccpu_base
0a219000-0a21901f : pronto_saw2_base
0a21b000-0a21dfff : pronto_phy_base
0b017000-0b017fff : msm-watchdog
20000000-84efffff : System RAM
20008000-213c663f : Kernel code
21514000-21916ff7 : Kernel data
86800000-86bfffff : System RAM
8d900000-dfffffff : System RAM
Silesh.Nair said:
I don't know what you meant by logcat, but I presume this is what you want.
Code:
athene:/ # cat /proc/iomem
0005c000-0005cfff : tsens_eeprom_physical
000601d0-000611cf : vmpm
0006c000-0006c1ff : phy_csr
0006c000-0006c1ff : phy_csr
0006c000-0006c1ff : phy_csr
004a8000-004a9fff : tsens_physical
004ab000-004ab003 : pshold-base
01871000-01871003 : restart_reg
01b00020-01b0002f : csi_clk_mux
01b00030-01b00033 : csiphy_clk_mux
01b00038-01b0003b : csiphy_clk_mux
01b04000-01b040ff : 1b04000.qcom,cpp
01b08000-01b080ff : 1b08000.qcom,csid
01b08400-01b084ff : 1b08400.qcom,csid
01b08800-01b088ff : 1b08800.qcom,csid
01b0a000-01b0a4ff : 1b0a000.qcom,ispif
01b0ac00-01b0adff : 1b0ac00.qcom,csiphy
01b0b000-01b0b1ff : 1b0b000.qcom,csiphy
01b0c000-01b0cfff : 1b0c000.qcom,cci
01c00000-01c0ffff : kgsl-3d0
01c20000-01c2ffff : kgsl-3d0
04020000-0402003f : rmb_base
04080000-040800ff : qdsp6_base
07803000-0780afff : /soc/[email protected]
07824900-07824dff : mmc0
07864900-07864a1b : mmc1
07884000-078a2fff : /soc/qcom,[email protected]
078b0000-078b01ff : msm_serial_hsl
078b6000-078b6fff : 78b6000.i2c
078b7000-078b75ff : 78b7000.i2c
078b8000-078b85ff : 78b8000.i2c
078db000-078db3ff : core
078db000-078db3ff : core
07af5000-07af55ff : spi_qsd
07af8000-07af85ff : spi_qsd
0a0120a8-0a0120af : alarms_txctl
0a012448-0a01244f : alarms_tactl
0a08040c-0a080413 : wlan_tx_status
0a080488-0a08048f : wlan_tx_phy_aborts
0a080c00-0a080c00 : pronto_mcu_base
0a080fb0-0a080fb7 : wlan_brdg_err_source
0a100400-0a1005ff : pronto_a2xb_base
0a205050-0a20524f : pronto_ccpu_base
0a219000-0a21901f : pronto_saw2_base
0a21b000-0a21dfff : pronto_phy_base
0b017000-0b017fff : msm-watchdog
20000000-84efffff : System RAM
20008000-213c663f : Kernel code
21514000-21916ff7 : Kernel data
86800000-86bfffff : System RAM
8d900000-dfffffff : System RAM
Click to expand...
Click to collapse
oops sorry thanks Machu i typed it in half sleep