HELP, I lost my IMEI ! / Caller ID
Please note the content below was originally in post#1. I cleanup Post#1 a little, to make it clearer to new users.
My second Lenovo A750
ROM release: A750_S148_120428_cybermaus_V1
Edit: For ICS rom check the 2nd post.
Fixed toward V0
- Different GAPPS, resulting in
- More stable Play Store with less unlisted apps
- WiFi based Location services (from for example Places) working (GPS did work in V0)
- NANP (US style) numbering formating removed from phone
- Replaced Unicom talking bootup animation with silent Lenove butterfly
- Added 'new phone Setup' program
Still to improve (if you know how, on a MT6573/MT6575, let me know!)
- Caller ID lookup in Contacts should ignore IDD prefixes
- SMS app trips over hyphens and brackets in stored numbers
- Arabic/Hebrew RTL fix not applied yet.
- Remove 'new phone Setup' program again?
This is a simple and clean ROM, not too much done, essentially just the factory S148 ROM (A750_S148_120428) rooted, cleansed from Chinese and with Google Play Store and other GAPPS.
So it is mostly clean. It does not even have the Skype/YouTube/Flash apps, as I believe such apps change too often to be in the system portion. I upload the ones I got from Etowalk separately, in folder Etotalk_apk
, you can install yourself.
- Rooted the phone
- Set to boot in US-english
- Added MoreLocale for extra languages
- Removed Chinese apps, incl Chinese keyboard
- Removed SmsReg.apk
- Left Lenovo
Security (anti-malware) intact
- Added Google framework
- Added modded Play Store 3.x.16-mod from XDA
- Added MobileUncle toolbox V2.0.9
- Added CWMR Touch / 593zn.com recovery image
Most images are unmodified from stock S148, even boot.img is unmodified. Only system.img was really changed, you could flash only that.
You will also need the flash tool and USB driver. For example tool SP_Flash_tool_v3.1208.01 and driver USB_VCOM_Driver. The flashing is the
typical Mediatek MT6573/MT6575 based flashing sequence
as shown by bgcngm, the undisputed champion of Mediatek ROMS.
Which reminds me: Thanks to bgcngm for his help
, and to jazzor for his help
By default, the ROM will not overwrite USERDATA. If you want a clean slate, first extract empty.userdata.rar. Also do this if you get "weird" behaviour after flashing, like Play Store not starting, your old setting may be incompatible with the new ROM
By default, the ROM will not overwrite FAT (the internal SD card). If you like an empty internal SD card, extract empty.fat.rar before flashing.
By default, the ROM will clean out CACHE. If for some reason you feel CACHE should not be cleared, deselect the CACHE from flashing.
: If you want to play it safe, it may be wise to backup your phone's IMEI file before you flash or reset to factory defaults. See here
for help on backup or restoring IMEI
: If you are trying this ROM on another model phone, which I STRONGLY advise AGAINST, then do NOT flash the first two (preloader and dsp_bl) as you will may not be able to flash it back afterward and thus brick your phone. Someone
tried it against an ZP100 and bricked his phone.
I will also upload the driver, flash utility and official ROM's there.
May 11, 2012
Caller ID bug
Caller ID on the on the A750, on the P700 ROW, and I suspect in general on the Lenovo phones.
ROW (=Rest Of World) based ROM are much more international then the other Lenovo
ROMs. I cannot be sure about the other china brands, but Lenovo
in ROMs intended for the local China market, 'update' the phone to nicely recognise chinese cities. I am sure China locals will be pleased with this service. I do not know if/how this applies on phones which are already more international like the multilingual Zopo's and Thl's out there.
In doing so, Lenovo
seems to break the normal caller ID function. Not only do you get to see Chinese city names for non-Chinese numbers, but also in some cases it does not resolve an incoming call to your phone book. This seem to be especially true if the incoming call is in local format (no +CC) and the phone book is in international format (with +CC)
The ROW based ROMs work much
nicer. No Chinese city names for non Chinese numbers. Also, it finds correct country names. So far, I was called by unknown numbers from California, UK, London, Russia, Romania, Saudi, Yemen and Jordan, and it all correctly resolved them. For California and London even to greater detail then the country. It only shows this for unknown numbers, for known ones it shows the contact name.
Indeed Caller ID seems to work correctly for local vs international format. So if the incoming is formatted without +CC, but leading 0, and the phone book is +CC, it finds it.
And it seems to nicely format all phones according to the desired national formatting. So +1 XXX-XXX-XXXX for US, but +966 X XXX XXXX SA fixed and +966 XX XXX XXXX for SA mobile. And +31 XX XXXXXXX for NL fixed and +31 XXX XXXXXX for NL mobile.Very nice
HOWEVER: The caller-ID lookup now seems 'whitespace-sensitive'. I had a contact number stored as +966 XXX XXXXXX, and he did not find it. But when I changed it to +966 XX XXX XXXX it did find it. Similar for number that had "(XXX)" brackets in it, as was common in NL in the past.
This may or may not be a problem, because if you touch your phone book entry in the edit mode, it will automatically change +966 XXX XXXXXX to +966 XX XXX XXXX. Symilar if you sync through Google. But as I sync with outlook using Android-Sync
, many are stored like +CC (XXX) XXXXXXX
So, Caller ID is 'different'. But better? For most people probably yes. But may depend on your situation.
: I found the whitespace was actually due to me not clearing data. Everything seemed find, but the caller ID was a resulting problem. You need to clear contacts, so it reindexes the phone numbers, and then Caller ID is perfect. Even ignores () brackets. You can clear contacts many ways, but I made a patch