Related
Please note this is a rewrite and cleanup of first post. Original firstpost is in post#3.
Here I publish the ROM's I make for the MT6575 based Lenovo Dual SIM phone
The current and advised ROM is A750_ROW_S114_cybermaus_ICS_V3.1 described in post#2 below
This is the original A750 thread, but as not everyone can post in developer threads, I also have a publicly available new Q&A thread.
I advise you post your question here (if a more advanced and development specific A750 question) or in the Q&A question.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only. Please understand I do not know everything, so using the Q&A thread is better then PM'ing me, as that way maybe others know the answer too.
Also, I am moving file hosting to Dev-Host. So if you encounter a dead link to a ROM file, do look here in my Dev-Host folder.
ICS IceCream Sandwich
Starting 2012/09/12 I have a second flavor of ICS ROM for the A750
ICS V1 ~ V1.3 are based on the original Lenovo A750 ROM's Most people tried them, but went on to APKHOT because of multilang. There was a V2, but never released
ICS V3 and onward is based on the Lenovo P700 ROM, see below
ICS V1 series
It is a update.zip type update. If you already got S306, and rooted/gapps'ed it yourself, you could stick to that, this is the same, with some minor extra cleanup.
'Normal' cleanup actions:
- Prevented update from overwriting Recovery
- Added root (Chainfire) & gapps (CM9 120429) & Maps & Streetview
- Cleaned Chinese & SmsReg
- Replace talking Unicom bootup with silent butterfly
- Set to US/en & added MoreLocale2
- Added MobileUncle 2.0.9
Instructions for A750_S306_120530_cybermaus_ICS_V1:
Assuming you have the custom recovery. If not, flash the recovery from my 4-shared using the flash tool.
- Put S306 V1 zip file on SD card (do not unzip)
- Also put S306 V1.3 zip file on the SD card (do not unzip)
- Boot into Recovery
- First apply V1, then apply V1.3
- Potentially, clear userdata and cache, especially if you come from any S14x GB
- Reboot, and wait for it to complete.
BTW: It should probably be noted that while I packaged V1.2 and V1.3, it was again bgcngm who we have to thank for knowing how to solve the location problems.
If you already lost recovery due to the S306 OTA update, reinstall it using the flash method from first post.
Please always respond if you tested it, even if you did not like it.
Oh, and if you do like it, press the thanks button of course.
ICS V3 series
For a long time I guessed the P700 is similar to the A750, but why bother. Until I recently heard it has a multilingual ROW (Rest Of World 海外版) version!
So I took the leap, and transplanted the A750 kernel into the P700 ROM (needed because the screen driver is different), and installed it on my A750.
It works pretty well. I did not need to fix location services or gapps (though I did put the newest in there). Also did I not need to clean up any Chinese apps. And the Calender is Chinese free, and the Dialer free of Chinese city names. So I barely had to do anything. Also GAPPS TTS was in there, though I still cannot find the settings menu.
But alas, the only 'multilang' in the ROW was Vietnamese. I guess "Rest Of World" is pretty limited.
Also, for those of you that liked it, the Security App (Anti-Virus, and limit permissions per App, so sort of a firewall) is also missing. I may put it back in later, but I want to run vanilla for a while to test stability.
But it is still nice and clean, and all programs a month newer. And Chinese out of the browser/email-setup/calender/dialer. Oh, and for all of you that went to APKHOT because of the newer SIM taskbar icons: It also has the newer icons. For an ongoing list of findings in post #585
So for those of you that want to try: A750_ROW_S113_cybermaus_ICS_V3 based on P700_ROW_S113_120801.
Assuming you have the custom recovery. If not, flash the recovery from my 4-shared using the flash tool.
A750_ROW_S114_cybermaus_ICS_V3.1
Based on factory ROM P700_ROW_S114_120903, and located in my Dev_host. Similar to V3, but newer, and a few extra tweaks.
Summery of changes:
- Same as on V3, and additionally:
- Whatever Lenovo fixed in their S114 (there is a unconfirmed suggestion that it may be signal strength related)
- Different (better?) call-log and Caller-ID behavior, see post #3 below
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
- Kept the original S306 radio firmware (baseband). They had the same timestamp as the P700 one anyway.
Instructions:
This is a update.zip type ROM. If you are on any ICS ROM, you do not need to flash V3 first, you can directly flash V3.1"
- Put ROW_S114 zip on SD card
- Boot into recovery
- Apply zip file
- Reboot, and wait for it to complete.
- If you came from a domestic Chinese ROM, clean data for calender, notes, desktop and if possible contacts, using these utilities. Or if you do not mind, wipe all data from recovery.
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
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.
=================
Hi All
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.
Specific changes:
- 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
Instructions:
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.
IMPORTANT: 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
IMPORTANT: 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.
Download A750_S148_120428_cybermaus_V1
I will also upload the driver, flash utility and official ROM's there.
Enjoy
May 11, 2012
cybermaus
------------------------------------
Caller ID bug
Caller ID on the on the A750, on the P700 ROW, and I suspect in general on the Lenovo phones.
The lenovo 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.
EDIT: 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 for it.
Links to other A750 ROMS and other useful information:
EDIT: I have not kept this list updated. Search this thread for other ROMS, especially Smileyvvv's APKHOT seems popular
Original A750 ROMs: (S14x=GB; S30x=ICS)
A750_S148_120428 - Chinese/English - No root - No play store
A750-S305-120514 - Chinese/English - No root - No play store
A750_S306_120530 Original full S306 (no OTA, flash package)
Please note that all *official* ROMs come with password bbs.lenovomobile.com. If the password is missing, someone did something to the ROM. Also, there are 'root' images availible that only flash boot.img. These work by overwriting system.img *on every restart*. Creative, and I used it myself for a while, but currently I feel the method described below is a better method.
Other modified ROMs (GB):
S750 S143 Etotalk Multilang
A750_S148_120428_RUS by Anton_vrn V1.3 (true Russian translation!)
BM's Hebrew fixed
BaderMQ's multilang+Arabic fix
(please note none of these are really multilang, just multi-locale, which means system apps will remain English, but third party apps can be set to other languages, similar to my ROM's, I simply do not make the claim. Anton is the only one who actually translated the ROM, but to only one new language)
Other modified ROMs (ICS)
My ROM in sepo of course
lenovo750-4.0.3_Anton_vrn_v3.01(true multilang?? Hints that it contains: ar-de-es-fa-fr-in-it-nl-pt-ru-th-tr-vi-zh, but based on S305)
Etotalk S306 multilang_by_Dean : It exists, but I do not know an internet location to download it from.
How to root a ROM yourself:
- Flash the CWMR Recovery partition (the recovery only, not the root&recovery one)
- Reboot into recovery (poweroff - Press/hold Power for 2 secs, then also Up/Down)
- Apply this root update
- Use RootExplorer to remove any Vending* or Phonesky* from /system/app
- Apply the correct GB or ICS GAPPS package, from bottom page here, or its mirror here.
- If a ICS rom, even though not from me, you may still want to apply my ICS V1.3 update, especially if you have location or market compatibility issues.
Caller ID
Hy I have a Lenovo A750 and all my contacts in the address book are saved in international format ex.: +44 78......, and when somebody calls me the number that shows up on the display is 0 78....., as local format.
Unfortunately the phone doesn't recognise it as being saved in my address book and it show's me "078 .... is calling" instead of "Ben is calling".
How could I fix this?
Please help me, or at least give me directions.
Thank you
Its one of the more important (of not most important) issues, and it has focus of myself and more experienced people. It's listed above as "Caller-ID to Contact mapping should ignore IDD prefixes." But alas, afaik, at this moment, no solution exists.
Keep an eye on this thread, and/or this one. Rest assured that as soon as we know how, it will be fixed.
Edit: Caller ID bug is less prominent in ICS ROM's
And in any case, using this, you can work around it.
COOL
You have done great job man thank you. I was using etotaks v 2.0 rom but it kind of sucked so i decided to try yours and its all good. I like the net traffic, battery saving and LeSecurity and they come only with the lenovos rom. I will look foreward for future releases. Great Job.
Reagards.
RTL
Hi,
Are you planning to update your rom?
i was searching for a Lenovo A750 rom that support Arabic - Hebrw RTL.
There is a methods out there but its only for deodex Roms,and your rom odex.
anyway to convert odex to deodex?
Thanks
There is already a Arabic & Hebrew RTL version for A750 out there. Not my me, but by someone more experienced, though A750 is not his focus.
I am playing with my ROM, and while it is not on the top of my list, once I get round to updating it I was thinking of copying his RTL fix to my ROM also. In the mean time, try the other one, and tell me how it works in relation to the issues I still have on the to-do list.
Thanks
I downloaded the rom from that topic , it failed to install . it give me an error msg when i try to flash it thru CWM.
I manage to convert the lenovo A750 Roms to odex using crcstudio_1.2.0.0
now i'll try to apply the fix manually.
Well, you can always try to use the recovery I am using. It seems to work well for Bruno's ROM's.
I have never even attempted to put CWM on these Mediatek based phones. Nor have I heard of anyone else (other than you). Are you able to flash anything with it? I was assuming there was a reason people were not using CWM on Mediatek.
I advise you to put Recovery ROM from here, flash it using this method. And then use that to apply the zip based ROM's.
I am working to update my ROM with Hebrew also (actually, working on other stuff, but will try to also put that in), but be aware, it will also be a 'flash-utility' ROM.
Edit: ROM V1 is coming tomorrow, but no RTL, sorry. I was able to fix the location service and Play Store is now not blocking so many apps.
I already did try CWMR ... But when i ever try to flash BM Rom it shows an error.
And by the way .. I already used CWM to flash other roms on my A750 and its working.
so what i did:
I extract BM Rom and merge it with other chinese rom S148 and build new rom.
It works.. i can read/write Arabic . and for browser/gmail i install the Brightidea's app from the market. it fix the Arabic problem.
New V1 upload in first post.
Spanish from etotalk?
There are any possibility to get the spanish traduction from the etotalk rom?
Thank you
I'm using new ROM since last night.
I made a complete flash (userdata, sd...).
Now there are less Chinese applications, is good.
Good work, Thank you.
Quick question
Hi cybermaus
sorry for the noobie question but I didn't own a smartphone since windows mobile. I expect a A750 and it might come unrooted. Do I have to root it before installing the rom or is this done automatically in the flushing process? Thank you.
newbie_vlc said:
There are any possibility to get the spanish traduction from the etotalk rom?
Click to expand...
Click to collapse
Check if the Spanish selection is part of the 'MoreLocale2' app. If not already there, add it as a custom locale.
Edit: If you meant: can I take Etotalk ROM and transplant its Spanish into my ROM, then that is already done! Neither Etotalk nor myself actually translate anything, we both just added the free public app MoreLocale2, which has most translations in it. Using MoreLocale2, the phone becomes 'reasonably' translated, though there may remain some English parts.
cliviu said:
Hi cybermaus
sorry for the noobie question but I didn't own a smartphone since windows mobile. I expect a A750 and it might come unrooted. Do I have to root it before installing the rom or is this done automatically in the flushing process? Thank you.
Click to expand...
Click to collapse
This flash is using bootloader method, not recovery, and it will not need root. Upon flash, it will apply root automatically. Use the flash sequence as linked in the first post.
It is strange the size is only 157 mb. I will give it a try
Yes, V0 accidentally had two copies of the rom image inside the rar. It did not hurt, but it bloated the package a bit. The 157GB (164 981 710 bytes) is correct
Good to see you are paying attention though
Remove the Unicom bootup animation
I landed on this page when I was looking for help to remove the Unicom talking bootup animation/sound and remove all Chinese apps from my phone (A750) that I recently picked up.
But I have never done this and I am no developer but can you please help me with a list of procedure that I can follow to use this A750_S148_120428_cybermaus_V1?
If someone has skype or share their phone number I can call to seek help.
Email: [email protected]
Q&A for CyanogenMod 12.0 for Photon Q
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CyanogenMod 12.0 for Photon Q. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0
I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!
Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!
CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...
CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).
I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.
Download link https://download.lineageos.org/osprey
There is a need to maintain list of stuff not working in the nightlies, since some people have Osprey as their primary phone
The purpose of this post is for easy access to a list of bugs by both the developers and the end user
Feel free to add to the post
-mention the ROM version
-the bug
-and any other relevant information
List
version lineage-14.1-20170125-nightly
Bug : Cellular Data doesn't work after disconnecting from Wifi
Temporary Solution : Developer Options -> Cellular data always active
Bug : When music is played through headphones and charger is connected/disconnected sound is played via both the headphones and speakers. Also happens for Shutter Sound
Bug : Random Bluetooth Disconnections after long periods of bluetooth being connected
Solution : Disable Battery Optimization on all bluetooth related services
Bug: version: lineage-14.1-20170302 -lineage-14.1-20170309
Bug: Phone doesn't rescan new media such as Whatsapp images, downloaded images
Temporary Solution : Manually rescan media
Ideally it should be in the first post of the LOS thread in Original Android Dev. But if you manage to maintain it, it could be referenced.
Hey guys, my phone is stuck on "Checking for updates" and I am looking for a solution. If I install this rom will it fix my problem?
Is it as easy as downloading it, starting on bootloader and $ adb sideload thisthing.zip ?
All the help is highly appreciated, I am not interested in modding stuff or special apps, I just want my phone to run again. Thanks.
MOTO G3 - XT1540 2015
LostInTheDarkness said:
Hey guys, my phone is stuck on "Checking for updates" and I am looking for a solution. If I install this rom will it fix my problem?
Is it as easy as downloading it, starting on bootloader and $ adb sideload thisthing.zip ?
All the help is highly appreciated, I am not interested in modding stuff or special apps, I just want my phone to run again. Thanks.
MOTO G3 - XT1540 2015
Click to expand...
Click to collapse
Are you on stock rom? A simple reboot should fix the problem. And if you could send screenshots that would be good
M_Maha said:
Are you on stock rom? A simple reboot should fix the problem. And if you could send screenshots that would be good
Click to expand...
Click to collapse
If by stock rom you mean the original and official rom then yes. I've rebooted a thousand times now, wiped data and cache another thousand times, recovery/reset another hundred times, and got adventurous to flash a rom via adb sideload but it complained about invalid signature or something. Still stuck on "checking for updates".
The screenshot is a blue screen with a yellow progress line telling me "Checking for updates" just after the welcome and wifi verification., just like this one but with a different label "Software Update - Checking for updates": http://www.androidpolice.com/wp-con...nexus2cee_screenshot_20161020-090044_1024.png
STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.
Brilliant! Will download now and report back later. Thank you.
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??
@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.
Hi guys,
I experienced a very strange issue with whatsapp at the moment. Just bought a Galaxy S4 I9505 and put some CM11 on it. Everything is working like a charm except of whatsapp.
Here I can open the app - getting the alert that my custom rom was recognized - and then I can enter my phone number.
But whatever I'am entering - I CANNOT CLICK "NEXT" oO
I've tried resetting the DPI to default / disabling root / developer mode / cleaned cache with dalvik etc. but nothing seems to work.
Did any1 of you guys had this issue and solved it finally?
Thanks for your help!
ask a moderator to move your thread to Galaxy S4 forum, you might get answer there.
why this had been moved to "General questions" ? I've posted this in the Whatsapp section as this is a specific question about Whatsapp?
Well in fact I have changed the ROM I used and it was working - only with this CM11 version the error occurs.
I can remember I had this issue once on a Blackberry Q10 with the android app of Whatsapp - where I needed to use the magnification tool to hit the "Next" button - but it did not help on android.