System 1.8/ Iphone App 2.9C / EFI App 2.9C

[HDB]

Friday, 28 July 2017, we made an update to our operating system on HDBOX and updated it to version 1.8. Update was aimed at SD-Card operation and Sound Pack operation.

More details can be found at:
SYSTEM 1.8 Released ? Sound Packs | HDB Team
iPhone APP 2.9C ? Sound Pack and UX tweaks | HDB Team
Apple EFI 2.9C ? Sound Pack, UX & Functionality Tweaks | HDB Team

And the respective sound packs can be downloaded from:
Support | HDB Team

Android App is still on the 'operating table' as we are using the improved stability of access to the SDCard from System 1.8 to implement next feature to the android app: standalone password brute forcing for our android tool.

Best regards,
HDBOX support team.

[qual_service]

good day ,
i had tested the samsung s8 , with pattern lock, that after each wrong try , will have 2 min waiting time.
i had tried 8 times worng pattern, after each 2 minutes..and the timer is not increasing.
so the waiting time is remaining 2 minutes everytime.
can help us providing with pattern find algorythm for 2 min delay pattern finder.
thx in advance for your attention!

[HDB]

Hello,

I contacted dev team, and they will look into implementing this new setting in the our next planned release of the android app ( Should be V1.5 ). We already implemented for the V1.5 release the possibility of loading pin/passwords from a txt file located on the HDBox SD Card at the location [HDBOX SCard Letter:]\HDBox\Android.app\codes.txt, and the possibility to select a text file from multiple txt files present at that location is planed for V1.6 but for now it is fixed set to this specific file.

p.s. The fun part about Android APP is the size of app that is growing and growing, already using 4 storage slots, so we had to some house keeping in HDBOX to make room for it, and this is one reason why V1.5 was not released last friday.

Best regards,
HDBOX Support team.

[HDB]

And a quick preview of Android V1.5 Setup process... we might tweak it before release:

[qual_service]

hi..just coming back with updates on that s8..
i keep tring and tring diferent models patterns..and after more and more tries..i think after 8-10 tries...it modified timer to 4 minutes....after 10-12 tries more..now up to 8 minutes..
so..i think that if timer is increasing...i think will be low chance for remove pattern? or..could be that after many many tries..to ask for any code?
or time will increas until....infinite?

[qual_service]

also..solution should work on xperia phones? but the same condition for timer to be stable, if not icnreasing..should work ?

[HDB]

Hello,

The only issue when unlocking via Brute-force is that you have to have that timer stable. Otherwise it will be not practical, as the unlocking time will be longer and longer.



For example on a 4 digit standard android the math is simple:

1. 4 digit pin will have 10.000 max possible codes,
2. entering code takes about in 0.5seconds, testing 1 second, and having 30 seconds delay between each 5 codes batch :
   1s + ( 0.5s + 1s ) x 5 + 30 s = 38.5seconds for 5 codes = about 7.7sec/code,
3. 10.000 * 7.7 = 77.000 Seconds = 1296minutes = About 22 hours

So this is why we said to test all 4 digit codes will take about 1 day, but if instead you got 2 minutes between codes the estimated max time will be (0.5s + 120s) * 10.000 = 1.205.000 seconds = about 14 days.

p.s. Usually for pattern locks, after around 10 or 20 wrong patterns they phone will display an option to use the backup pin to unlock it ( "Forgot Pattern?" or "Backup Pin" labels are used most common and are displayed next to the emergency button). And with Android Brands and models, depends on model/brand/ android version if that backup got no delay between codes, this is why our setup process for Android phones is having more steps than Iphone or EFI setup process.

Best regards,
HDBOX Support team.

[qual_service]

in some cases...customers are willing to wait 1-2-3 weeks..just to have solution.
we wait new updates from you, and thank you for support!

[HDB]

Hello,

Android was on hold for last two weeks while we worked to implement IOS10.3.2 , IOS10.3.3 and IOS 11 Unlock for iPhone 7. We finished the private testing for the iPhone 7 unlocking and today we will make the official announcement for it.

We choosed to remain silent and not inform people in advance about the iPhone 7, to avoid the thing with mac connectors. For the mac connectors while even the first one worked, now we are on 3rd re-version of them, and now they are even more small and compact than ever and now they will fit in all computers with no problems. We had issues with diferent macs where the adaptor will simply not fit because of the nearby components.

Thank you for your understanding,
HDB-Team support team.

[qual_service]

Originally Posted by HDB

Hello,

Android was on hold for last two weeks while we worked to implement IOS10.3.2 , IOS10.3.3 and IOS 11 Unlock for iPhone 7. We finished the private testing for the iPhone 7 unlocking and today we will make the official announcement for it.

We choosed to remain silent and not inform people in advance about the iPhone 7, to avoid the thing with mac connectors. For the mac connectors while even the first one worked, now we are on 3rd re-version of them, and now they are even more small and compact than ever and now they will fit in all computers with no problems. We had issues with diferent macs where the adaptor will simply not fit because of the nearby components.

Thank you for your understanding,
HDB-Team support team.

what do you mean by iphone 7 unlocking?i suppose it is user lock related

[HDB]

Originally Posted by qual_service

what do you mean by iphone 7 unlocking?i suppose it is user lock related

Yes,you are obsolutely right!