DB2020 customisation via DCU-60 ate LOGS for NOTHING! Yesterday I flashed K800 and W850 via dcu-60. Finally flashing speed was acceptable. After flashing Raw FS I made customisation (via DCU-60 ofcourse). Program done some operations took log for customisation and what?!? Configuration Error!! Same thing for 2 phones! For tests I made 2nd customisation but via UC-10 cable. Took another log ofcourse but this time no configuration error... 1st: For cruiser team, why do you give NON TESTED and NON FULLY WORKING FEATURE especially if it's connected with logs based server feature which costs extra money(what if it was my 2 last logs)!?! 2nd: What about lost logs, probably you have log register with phones models and imeis done via server? 3rd: Deactivate customisation feature until I will be fully tested and don't eat logs (in DCU-60 usb cable mode) 4th: Maybe some other users has similar problem like mine? Post it please if any. BR |
@MODS I too hve faced the same problem and i hve created a thread earlier in this forum, i had faced problem with both dcu-60 cables & fighter 4in1 cable as well! still watiing for the lost logs! about 12! so mods please look into this & refund our logs ASAP! and wht about unlocking DB2020 phones?as SEtool is doing it already? WBR ReyTech. |
yes, i too have this problem with K790 and K800. 4 credit`s will.... |
Quote:
Working super with dcu-60 cable done a few k800 and w850 so must be problem with ur cable or computer. |
yes, i have problem with K610 2 credit. |
follow the right process provided in the cruiser logs site that how to flash these phones & u never loose any of your logs. 100% sure about that. |
Quote:
2nd thing to aseemvizag: bla bla bla, process was shown to be successful but it wasn't so don't treat me like I was fool who don't understand english and don't read before doing anything. 3rd thing: I really don't care about those 2 logs but you understand my dissapointment that cruiser which was reliable tool makes those unfunny jokes because somebody doesn't give a **** to test new features well. Ofcourse it's still in beta stage but why the customers have to pay extra for tests - especially that what I see I'm not alone with the same problem. I was smart to customise phone again with old method via uc-10 and lost only 1 log extra per phone, but this is only my case - what with others!?!. 4th and finish: I'm still waiting for cruiser team answer about this case. I see no interest there. It looks like ignoration - fine. Maybe other users think twice before buying another logs for cruiser. Other users please post your problems with cruiserlog service via DCU-60. Post phone model and custiomisation you've chosen while customising. BR |
hi I have same problem with 5 phones and 7-8 credits ,,,finaly repair it with other tool.. best regards GSMsolution |
my ***! it's seem the cruiser is not well for it's new children! erverybody must be carefull via DC-60 |
ya.. i lost around 16 log yesterday.. dcu-60 really waste lots of log .. |
hm, will test it later.....never problems with box untill now...don`t test ist with dcu60 . but i`m sure if there are any problemes you wil get back your logs....Cruiser team is a very fair team.... |
Quote:
BR |
to ceedee: use ver. 10.30, and with cruiser cable make it ok. 10.33 have many bugs britva |
Quote:
|
problem is FOUND problem is that users don't follow Cruiser Logs Guide located here www.cruiserlogs.net/guide what is the problem: users use "Detach phone" and this is wrong! You must use "Power off phone" or "Shutdown FS" function detach phone just terminate connection, power off phone flush buffer and then terminate connection regards |
All times are GMT +1. The time now is 10:12. |
vBulletin Optimisation provided by
vB Optimise (Pro) -
vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -