K012 IMEI REPAIR FAIL

hell_sea

hello every one
im having problem with Android tool box of UFI
i had this problem before and i used other software(box or dongle) to repair intel IMEI but i was wondering why is it that UFI android tool wont write new imei into K012; even with other intel tablet had the similiar problem
the below is a log from K012 imei repair which will end up with nothing...\
please help

platform: clovertrail, cpu abi: x86
manufacturer: asus
hardware: redhookbay
board: clovertrail, name: WW_fonepad
brand: asus, model: K012
build id: KVT49L, version: 4.4.2 Lollipop (KVT49L.WW_fonepad-11.2.3.33-20150302 release-keys)
build date: Mon Mar 2 19:33:06 CST 2015
build description: WW_fonepad-user 4.4.2 KVT49L WW_fonepad-11.2.3.33-20150302 release-keys

soc(CPU):
memory(RAM): 1 GB
crypto state: unencrypted
boot serial no: 3261504C
isn: QTCYF6C0G44502CFE
serial no: EBOKBC166504
ifwi version: 64.25
kernel version: 3.10.20
baseband version: 1434_1.9.40.2_0924
csc version: WW_FE170CG_V11.2.3.33
ril version: Intrinsyc Rapid-RIL M6.59 for Android 4.2 (Build September 17/2013)
sim state: ABSENT
android id: 312181b98db84794
client id: android-asus
bt addr: ac:9e:17:c3:ef:d6
wifi mac: ac:9e:17:c3:ef:d7
imei[1]: 004999010640000
imei[2]: 004999010640000
sku: WW
battery id: 97:615:0-44b0-5n😛003-97:615:0
battery level: 33%
superuser: yes (3.54:kinguser_su)

Enabling AT mode... Done.
Waiting for COM to be ready... Done.
Waiting for ADB to be ready... Done.
Using Port: Intel Android Virtual Com Port (COM455)
New imei[1]: 3537700XXXXXXXX
New imei[2]: 3537700XXXXXXXX
Writing new imei...

madgoeslim

hell_sea Hello,
Before restoring imei , for intel platform, you can try do erase nvm at first via special task in fastboot mode.

Or, you can try using CSC firmware if you face failed in user mode firmware. CSC firmware available at support server.

akilbnd

i have this problem how fix it?

torpedo_seluler

Sorry for hijacking this thread.. seem there's some bug for intl repair in version 1.3.0.1156
I have tried both user firmware and csc firmware both stopped at write new imei.. like hell_sea log
platform: clovertrail, cpu abi: x86
manufacturer: asus
hardware: redhookbay
board: clovertrail, name: WW_a500cg
brand: intel, model: ASUS_T00F
build id: JSS15Q, version: 4.3 Jelly Bean (ASUS_T00F_WW_eng_20141219_4.3.2.963832 test-keys)
build description: a500cg-eng 4.3 JSS15Q WW_eng_20141219_4.3.2.963832 test-keys

soc(CPU):
memory(RAM): 1 GB
crypto state: unencrypted
boot serial no: Medfield194ADC52
serial no: 0123456789
ifwi version: 59.47
kernel version: 3.4.43-g263a2e3
baseband version: 1434_1.4.41.6_1013_F
csc version: WW_A500CG_20141219_4.3.2.963832_eng
ril version: Intrinsyc Rapid-RIL M6.55 for Android 4.2 (Build August 6/2013)
sim state: ABSENT
android id: 90a93ddba92d969d
client id: android-google
bt addr: null
wifi mac: 00:90:4c:11:22:33
imei[1]: 004999010640000
imei[2]: 004999010640000
sku: WW
battery id: 110:645:3-448a-Cg😛011-110:645:0
battery level: 93%
superuser: yes ()

Enabling AT mode... Done.
Waiting for COM to be ready... Done.
Waiting for ADB to be ready... Done.
Using Port: Intel Android Virtual Com Port (COM397)
New imei[1]: 357115061438029
New imei[2]: 357115061438037
Writing new imei... it stopped here

https://youtu.be/N40_zbWA09g

Any free tool to repair the imei ? the customer are urging me right now..

torpedo_seluler

My Problem solve.. i tryed to reset the comport to lower value..it cannot be change in device manager..
i downloaded ghost buster to clear the ghosted drivers. and reinstall new inter android driver..

platform: clovertrail, cpu abi: x86
manufacturer: asus
hardware: redhookbay
board: clovertrail, name: WW_a500cg
brand: intel, model: ASUS_T00F
build id: JSS15Q, version: 4.3 Jelly Bean (ASUS_T00F_WW_eng_20141219_4.3.2.963832 test-keys)
build description: a500cg-eng 4.3 JSS15Q WW_eng_20141219_4.3.2.963832 test-keys

Enabling AT mode... Done.
Waiting for COM to be ready... Done.
Waiting for ADB to be ready... Done.
Using Port: Intel Android Virtual Com Port (COM14)
New imei[1]: 357115061438029
New imei[2]: 357115061438037
Writing new imei... Done.
Rebooting device... Done.
Waiting for ADB to be ready... Done.
Synchronizing calibration data... Done.

madgoeslim

torpedo_seluler Hello, nice to hear you solve the problem.
We will evaluate the bug intel repairing imei for current software in next update. Thanks for the info.