GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Infinity-Box


Reply
 
LinkBack Thread Tools Display Modes
Old 08-30-2017, 11:03   #151 (permalink)
Freak Poster
 
Join Date: Jul 2015
Location: douala cameroun
Posts: 113
Member: 2425737
Status: Offline
Thanks Meter: 7

my InfinityBox_install_CM2QLM_v1.15.7 don't open but InfinityBox_install_CM2mtk work perfectly please help to fix
this is my fault file

https://drive.google.com/file/d/0B2x...ew?usp=sharing
  Reply With Quote
Old 08-30-2017, 17:14   #152 (permalink)
Freak Poster
 
Angelo Cruz's Avatar
 
Join Date: Dec 2001
Location: InnovateK
Posts: 409
Member: 8012
Status: Offline
Thanks Meter: 124
-> MICloud Services remove enabled -> not working


Tried in several different Xiaomi devices (Kenzo, Land, etc..) and after phone in bootloop.
  Reply With Quote
Old 08-30-2017, 18:14   #153 (permalink)
No Life Poster
 
JayDi's Avatar
 
Join Date: Mar 2007
Location: Where you live
Posts: 18,542
Member: 462970
Status: Offline
Thanks Meter: 20,352
Quote:
Originally Posted by Angelo Cruz View Post
-> MICloud Services remove enabled -> not working


Tried in several different Xiaomi devices (Kenzo, Land, etc..) and after phone in bootloop.
For latest sw versions that not work according users test. We made another way. In next update.
  Reply With Quote
The Following 8 Users Say Thank You to JayDi For This Useful Post:
Show/Hide list of the thanked
Old 09-02-2017, 08:25   #154 (permalink)
Freak Poster
 
Join Date: Dec 2005
Age: 47
Posts: 240
Member: 205157
Status: Offline
Sonork: 100.1574537
Thanks Meter: 82
RedmiNote4 Always Shows Low Space Solved By Infy

RedmiNote4 Always Shows Low Space Solved By Infy
Flashed Many Times With Different Versions, HardReset,Format Nothing Changed

BY REPAIR DATA/MSC/CACHE SOLVED THE PROBLE
1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 400 [MSM8x26/28]
ID_BLOCK_S : 09D40D2D
ID_BLOCK_I : 009180E1
ID_BLOCK_L : BA4A20DE79E5121DCABF51BE79C05078
ID_BLOCK_L : 8FC648E3D47FEF64995439F6FC332D2E
Use CM2 Internal Loader
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8x26 , FLASH : eMMC , mVER : 1
ExtInfo : 0x0000C000/0000C000/00001000/00001000/00000000
Boot Ok!

MSC format Ok!
USERDATA format Ok!
CACHE format Ok!

Done!
Elapsed: 00:00:38

Reconnect Power/Cable!
  Reply With Quote
The Following 2 Users Say Thank You to cellncare For This Useful Post:
Old 09-04-2017, 12:45   #155 (permalink)
Freak Poster
 
Bimal Shah's Avatar
 
Join Date: Jun 2009
Location: Nepal
Posts: 489
Member: 1050365
Status: Offline
Thanks Meter: 207
Vivo Y55L Flashing successfully

Operation : Flash [ v1.15 ]
ForceFlashing : Disabled

Verify FW package ...
Verification passed!

1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 430 [MSM8937]
ID_BLOCK_S : 014D4167
ID_BLOCK_I : 0004F0E1
ID_BLOCK_L : D00F34CF5ADD1230CC2C4CAE4A71C59E
ID_BLOCK_L : 064BC134CC363D860F58B8C966AE83D9
Pickup loader from firmware package
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8937 , FLASH : eMMC , mVER : 1
MemInfo : 0x0003 / 0x0200 / 0x00000003A3E00000 [ eMMC 16 GiB ]
ExtInfo : 0x0001C000/00100000/00001000/00001000/00000200
Storage : MFR : 0x15 , VENDOR : SAMSUNG , NAME : QE13MB
Boot Ok!

Flash Chain : 133
Flashing now

Flashing : NON-HLOS.bin
Flashing : sbl1.mbn
Flashing : sbl1.mbn
Flashing : rpm.mbn
Flashing : rpm.mbn
Flashing : tz.mbn
Flashing : tz.mbn
Flashing : devcfg.mbn
Flashing : devcfg.mbn
Flashing : adspso.bin
Flashing : sec.dat
Flashing : emmc_appsboot.mbn
Flashing : emmc_appsboot.mbn
Flashing : boot.img
Flashing : recovery.img
Flashing : system_1.img
Flashing : system_2.img
Flashing : system_3.img
Flashing : system_4.img
Flashing : system_5.img
Flashing : system_6.img
Flashing : system_7.img
Flashing : system_8.img
Flashing : system_9.img
Flashing : system_10.img
Flashing : system_11.img
Flashing : system_12.img
Flashing : system_13.img
Flashing : system_14.img
Flashing : system_15.img
Flashing : system_16.img
Flashing : system_17.img
Flashing : system_18.img
Flashing : system_19.img
Flashing : system_20.img
Flashing : system_21.img
Flashing : system_22.img
Flashing : system_23.img
Flashing : system_24.img
Flashing : system_25.img
Flashing : system_26.img
Flashing : system_27.img
Flashing : system_28.img
Flashing : system_29.img
Flashing : system_30.img
Flashing : system_31.img
Flashing : cache_1.img
Flashing : cache_2.img
Flashing : cache_3.img
Flashing : persist_1.img
Flashing : oem_1.img
Flashing : oem_2.img
Flashing : mdtp.img
Flashing : cmnlib.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib64.mbn
Flashing : cmnlib64.mbn
Flashing : keymaster.mbn
Flashing : keymaster.mbn
Flashing : survival.img
Flashing : dp_AP_signed.mbn
Flashing : dp_MSA_signed.mbn
Flashing : apps_1.img
Flashing : apps_2.img
Flashing : apps_3.img
Flashing : apps_4.img
Flashing : apps_5.img
Flashing : userdata_1.img
Flashing : userdata_2.img
Flashing : userdata_3.img
Flashing : userdata_4.img
Flashing : userdata_5.img
Flashing : userdata_6.img
Flashing : userdata_7.img
Flashing : userdata_8.img
Flashing : userdata_9.img
Flashing : userdata_10.img
Flashing : userdata_11.img
Flashing : userdata_12.img
Flashing : userdata_13.img
Flashing : userdata_14.img
Flashing : userdata_15.img
Flashing : userdata_16.img
Flashing : userdata_17.img
Flashing : userdata_18.img
Flashing : userdata_19.img
Flashing : userdata_20.img
Flashing : userdata_21.img
Flashing : userdata_22.img
Flashing : userdata_23.img
Flashing : userdata_24.img
Flashing : userdata_25.img
Flashing : userdata_26.img
Flashing : userdata_27.img
Flashing : userdata_28.img
Flashing : userdata_29.img
Flashing : userdata_30.img
Flashing : userdata_31.img
Flashing : userdata_32.img
Flashing : userdata_33.img
Flashing : userdata_34.img
Flashing : userdata_35.img
Flashing : userdata_36.img
Flashing : userdata_37.img
Flashing : userdata_38.img
Flashing : userdata_39.img
Flashing : userdata_40.img
Flashing : userdata_41.img
Flashing : userdata_42.img
Flashing : userdata_43.img
Flashing : gpt_main0.bin
Flashing : gpt_backup0.bin

Flash sequence completed!

Applying patches for storage # 0
Records : 26
Patch sequence completed!

BootConfig set to 0x00

Flashing done!

Done!
Elapsed: 00:03:30

Reconnect Power/Cable!

But Read Error

Operation : Read Flash [ v1.15 ]

1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 430 [MSM8937]
ID_BLOCK_S : 014D4167
ID_BLOCK_I : 0004F0E1
ID_BLOCK_L : D00F34CF5ADD1230CC2C4CAE4A71C59E
ID_BLOCK_L : 064BC134CC363D860F58B8C966AE83D9
Use CM2 Internal Loader
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8937 , FLASH : eMMC , mVER : 1
MemInfo : 0x0003 / 0x0200 / 0x00000003A3E00000 [ eMMC 16 GiB ]
ExtInfo : 0x0001C000/00100000/00001000/00001000/00000200
Storage : MFR : 0x15 , VENDOR : SAMSUNG , NAME : QE13MB
Boot Ok!


Brand : vivo
ProdName : PD1613F_EX
ProdModel : vivo 1603
Device : msm8937_32
AndroidVer: 6.0.1
Manufact. : vivo
QLMxCPU : MSM8937

DevInfo : MSM8937__vivo__vivo__ANDR_v6.0.1__vivo_1603__msm89 37_32__PD1613F_EX

ReportFile : C:\InfinityBox\CM2QLM\QLM_5report.log
Send report to mail : [email protected] with title "QFW" !

Info : Device is not supported yet!
Send log and report.log to support! Include device info also!

Reconnect Power/Cable!
  Reply With Quote
Old 09-09-2017, 10:28   #156 (permalink)
Junior Member
 
Join Date: Jul 2017
Posts: 2
Member: 2740055
Status: Offline
Sonork: k
Thanks Meter: 0
how

how to connect nokia 6 to be seen in cm2qlm
  Reply With Quote
Old 09-09-2017, 12:06   #157 (permalink)
No Life Poster
 
princesaddam's Avatar
 
Join Date: Apr 2009
Location: Inside Infinity
Posts: 1,688
Member: 1010626
Status: Offline
Sonork: using fb
Thanks Meter: 735
Quote:
Originally Posted by davibby View Post
how to connect nokia 6 to be seen in cm2qlm
Hello,
If u have EDL Cable then connect it,, if not then see this theard http://forum.gsmhosting.com/vbb/f296...-2246357/,,and also dont forget to install emergency drivers
  Reply With Quote
The Following User Says Thank You to princesaddam For This Useful Post:
Old 09-09-2017, 15:27   #158 (permalink)
Junior Member
 
Join Date: Nov 2008
Posts: 33
Member: 891676
Status: Offline
Thanks Meter: 3
Dear sir my CM 2 Dongle is not working How to repair it please reply thank you sir
  Reply With Quote
Old 09-09-2017, 16:32   #159 (permalink)
No Life Poster
 
nahidroman's Avatar
 
Join Date: Aug 2015
Location: Bangladesh
Age: 30
Posts: 600
Member: 2443283
Status: Offline
Thanks Meter: 518
Donate money to this user
MR JayDI what happened Huwei Y530-U00 Flashing Poblem


Quote:
Operation : Identify [ v1.15 ]

1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!

Error : Device stuck in S-EDL!
S-EDL : Reset power. Use BootJIG ( probably it is time to seek TP )

Reconnect Power/Cable!

Operation : Flash [ v1.15 ]
ForceFlashing : Enabled

Verify FW package ...
Verification passed!

1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!

Error : Device stuck in S-EDL!
S-EDL : Reset power. Use BootJIG ( probably it is time to seek TP )

Reconnect Power/Cable!


Quote:
Operation : Flash [ v1.15 ]
ForceFlashing : Enabled

Verify FW package ...
Verification passed!

1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!

Wait for phone...
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 2x/4x|00 [MSM8x10]
ID_BLOCK_S : 00B731BB
ID_BLOCK_I : 008110E1
ID_BLOCK_L : C83852AC0B979C8F782D2728F7B2C20A
ID_BLOCK_L : 92E1AFFEF362CC597CBB1CD5DFD6C00B
Pickup loader from firmware package
Loader Sent! Initializing ...

Error : FH Configuration failed!
Remove battery, cable. Check cable and connection. Repeat operation!

Reconnect Power/Cable!
  Reply With Quote
Old 09-10-2017, 10:48   #160 (permalink)
Product Supporter
 
Join Date: May 2005
Location: uae
Posts: 29,245
Member: 148515
Status: Offline
Thanks Meter: 19,534
Quote:
Originally Posted by Imran Sharief View Post
Dear sir my CM 2 Dongle is not working How to repair it please reply thank you sir
Hello,
What is th problem with your dongle ?
  Reply With Quote
Old 09-11-2017, 04:41   #161 (permalink)
Junior Member
 
Join Date: Jun 2017
Posts: 15
Member: 2723847
Status: Offline
Thanks Meter: 1
Infinity Chinese Miracle-2 QLM
Does this dongle support remote sharing?
  Reply With Quote
Old 09-11-2017, 14:24   #162 (permalink)
Product Supporter
 
Join Date: May 2005
Location: uae
Posts: 29,245
Member: 148515
Status: Offline
Thanks Meter: 19,534
Quote:
Originally Posted by cfl804 View Post
Infinity Chinese Miracle-2 QLM
Does this dongle support remote sharing?
Please do not use sharing tools to avoid software conflicts.
  Reply With Quote
Old 09-12-2017, 20:06   #163 (permalink)
Junior Member
 
Join Date: Sep 2017
Posts: 1
Member: 2757088
Status: Offline
Thanks Meter: 0
OnePlus 3T Memory Tool

I'm trying to recover data from OnePlus 3T/ qlm msm8996.
Is it possible to dump the whole storage (UFS) with CM2 memory tool?
  Reply With Quote
Old 09-13-2017, 05:37   #164 (permalink)
No Life Poster
 
Join Date: Jul 2011
Posts: 529
Member: 1613469
Status: Offline
Thanks Meter: 192
Quote:
Originally Posted by YellowBoss View Post
Infinity Chinese Miracle-2 QLM v1.15 - Nokia5, Nokia6, Nokia6CN, new features

Supported CPU List:
Qualcomm MSM 8210 (SnapDragon 200)
Qualcomm MSM 8212 (SnapDragon 200)
Qualcomm MSM 8610 (SnapDragon 200)
Qualcomm MSM 8612 (SnapDragon 200)
Qualcomm MSM 8226 (SnapDragon 400)
Qualcomm MSM 8626 (SnapDragon 400)
do not grab it, it stays the same 8926 (SnapDragon 400)
Qualcomm MSM 8228 (SnapDragon 400)
Qualcomm MSM 8628 (SnapDragon 400)
Qualcomm MSM 8928 (SnapDragon 400)
Qualcomm APQ 8009 (SnapDragon 210)
Qualcomm MSM 8209 (SnapDragon 210)
Qualcomm MSM 8909 (SnapDragon 210)
Qualcomm MSM 8916 (SnapDragon 410)
Qualcomm MSM 8917 (SnapDragon 425)
Qualcomm MSM 8929 (SnapDragon 415)
Qualcomm MSM 8936 (SnapDragon 610)
Qualcomm MSM 8937 (SnapDragon 430)
Qualcomm MSM 8939 (SnapDragon 615)
Qualcomm MSM 8940 (SnapDragon 435)
Qualcomm MSM 8974/A/AA/AB (SnapDragon 801)
Qualcomm MSM 8952 (SnapDragon 617)
Qualcomm MSM 8953 (SnapDragon 625)
Qualcomm MSM 8956 (SnapDragon 650)
Qualcomm MSM 8976 (SnapDragon 652)
Qualcomm MSM 8976 Pro (SnapDragon 653)
Qualcomm MSM 8992 (SnapDragon 808)
Qualcomm MSM 8994 (SnapDragon 810)
Qualcomm MSM 8996 (SnapDragon 820)
Qualcomm MSM 8996 Pro (SnapDragon 821)
Qualcomm MSM 8998 (SnapDragon 835)


- Original Nokia phones line ( HMD Global ) supported - WorldFirst!
Nokia 5 ( all TA-10xx revisions )
Nokia 6 ( all TA-10xx revisions )
Nokia 6CN ( all TA-10xx revisions )

Supported operations:
Read Info ( Identify )
Format FS / Reset Settings
Reset FRP
MemoryTool
Read Firmware
Flash Firmware

Since all Nokia Devices are encrypted from factory - Reset UserLocks and Forensic useless.
Strictly recommended NOT use "Force Flashing" option with Nokia devices!
After Flashing/Reset device may stuck on boot - just use VOLup + Power Key, until device will not reboot

- Main
FH Protocol updated and revised
Core revised, no more stuck boot problems
MSM8976 Pro new revision supported

- Flasher
DefaultBoot setting removed, complete auto
SafeRegions detection improved

- More Secure and Generic types supported
MSM8909, MSM8916: Generic Secure Chinese types, Alcatel and some Oppo
MSM8976, MSM8953, MSM8956: Generic Secure Chinese types, Alcatel, Lenovo and some others
MSM8936: Cover more Cyanogen based models
MSM8976 Pro: new revisions and more models

- Service operations improved
FormatFS operations revised ( Repair and ForceFix mode )
Xiaomi account reset revised
-> Reset MI Account revised
-> MICloud Services remove enabled
Disable services must be used after complete device offline setup!

- Firmware Reader engine updated
New types supported ( brand-specific and generic types )
Files verification revised
Nokia Series support

-> Unlike other "solutions" CM2 make FIRMWARE BUT NOT A USELESS PLAIN DUMP ( i.e. cloning )
-> That means all device unique data, security etc. will remain safe after flashing!

- Other
DataDirect engine updated
Some other improvements and fixes


Download link #1 - Download link #2 - Download link #3


Upload file to Support - Download files via Torrent

Infinity-Box 12 years (2005 - 2017) updates and support as nobody else - News

Twitter - Facebook - Telegram
Qualcomm MSM 8960 Alcatel
Phone eMMC Name : SEM04G
Phone eMMC CID : 45010053454D30344728F0E3FC7CD0C6
Phone eMMC SCD : D00F00320F5903FFFFFFFDFF8A4040A6
???
  Reply With Quote
Old 09-13-2017, 06:17   #165 (permalink)
No Life Poster
 
JayDi's Avatar
 
Join Date: Mar 2007
Location: Where you live
Posts: 18,542
Member: 462970
Status: Offline
Thanks Meter: 20,352
Quote:
Originally Posted by ballisto View Post
I'm trying to recover data from OnePlus 3T/ qlm msm8996.
Is it possible to dump the whole storage (UFS) with CM2 memory tool?
Hello. Yes, you can dump it.
But, if there were enabled encryption ( it enabled from factory by default, until you not switch it off ) - then dumping wilm give you just encrypted file ( AES with some other stuff ) , sw show partition state in memory tool window - BINARY under userdata mean inlt encrypted.
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 06:47.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.29520 seconds with 9 queries

SEO by vBSEO