yashsingh1/xdaforums huggingface dataset:
[Android General] andreidi:
That is not a custom ROM. It's a custom kernel only. This is the only single way to have KK back without touch bug. If you don't want this option, then flash S124 Lollipop or upgrade existing S030 KK via settings.
[Android General] ahmedmoselhi:
has anyone tried this rom https://vk.com/lenovo_a5000pda?w=wall-111995812_4303%2Fall they said it has front purple camera fixed!
[Android General] 7awliet:
Anton runs the A5000 VK.com group, they take things without permission. Spoken about this in the last 10 pages.

Two versions of kernel 3.10.103: darklord4822's which has front purple camera bug and Luck@S' which doesn't have front purple camera bug. I don't know much about either kernel nor have I tried them but Luck@S' kernel was disseminated (shared) without permission and we won't be spreading that kernel publicly in this thread. Thanks.
[Android General] ahmedmoselhi:
sorry for my misunderstanding to this and i know it's not good to share someone's else work without his permission
[Android General] andreidi:
I couldn't find anything at all regarding the volume boost fix: nothing in the ROM, nothing in the kernel. All 3.10.103 ROMs so far are based on the same pattern, so the volume boost is everywhere for now. Let's hope someone will release a ROM with normal, unmodified volume.
[Android General] 7awliet:
CM 14.1

Can't believe I'm gonna suggest trying it but *sigh* look in this thread's first post, CM 14.1 (darklord4822 kernel), which I think was taken from VK group which in turn I think was taken from 4PDA... Maybe even try a 3.4.67 kernel with this... or..... another kernel...
[Android General] romario_ne:
VK Group asked darklord4822to make a "new Kernel for CM14.1". Well he did it! For 6$ :D only.

So as you can see it`is buggy. As his first kernel it has pink frontal camera, hasn`t video recording sometimes mic trouble and NO 3G support.

So you get what you paid for.
[Android General] northwindtrades:
Did we get a s125 update recently?

I'm not sure if we got one , but if we did then don't jump in and install it,wait for a review or something,this is lenovo were talking about here
[Android General] mikeleo:
depanare lenovo a5000

andreidi, ajuta-ma te rog intr-o problema. Am un Lenovo a5000 si ieri am incercat sa descarc o alta versiune firmware decat cea care era instalata, am folosit smart phone flash tool si pe la jumatatea procesului de instalare a firmware-ului am apasat din greseala pe butonul stop si nu se mai aprinde telefonul. Culmea, cand il conectez la pc, acesta il recunoaste dar telefonul tot nu raspunde la comenzi. As vrea sa il desfac dar are baterie nedetasabila. Am fost la doctor GSM dar ma costa vreo 60 lei reparatia. Ce sa fac? Mersi.
[Android General] northwindtrades:
Leave the phone alone for sometime and then flash official firmware using sp flash tool.
[Android General] Enty1927:
Hey OP, your Lenovo A5000 custom ROM site is rubbish. Every effing click is an advert. I'm sure its not that expensive to run a simple site that keeps most of its files in Google Drive anyway. If its only the main page, that's fine, but this is every bloody page.

And what's with the purple front camera thing?? Nearly every custom rom seems to have it.
[Android General] northwindtrades:
Get ROMs from this thread then, there's a link that bundles most ROMs in my signature,most ROMs are 3.4.67 kernel version that must be flashed over KitKat or the like.purple camera is associated with kernel 3.10.103 darklord version.

But a bit of manners wouldn't hurt
[Android General] Eazart:
I wasn't asking for a Custom Rom either but the custom Kernel Fix... Well
[Android General] 7awliet:
S125

Saw the 4PDA posts on that too. People saying it's a 11MB/12MB update from S124 to S125 but I dunno how real it is. Many are saying it bricks their device. Unless it's a MM 6.0.1 or a NG 7.1.x update, I don't wanna know. Perhaps it's just a security or battery fix for LP.
[Android General] andreidi:
Cum zicea northwindtrades, lasa-l linistit o perioada (cateva zile), se va descarca bateria si se va opri ceea ce i-ai dat de facut. Ulterior, pune-l la incarcat si ia-o de la capat cu flash-uirea. Nu te panica, acest telefon nu moare foarte usor. Pentru mai multe informatii, intra aici: https://forum.softpedia.com/topic/1013464-lenovo-a5000/page__st__3672

[MENTION=7523876]7awliet[/MENTION]: Yeah, I agree, 11MB cannot be 6.0 or 7.0 update. Strange thing it bricks the phone, I'm never going back to stock.
[Android General] sanctumware:
Yes. There's an update of s125 rolled out just recently. Mostly got a boot loop unless wipe and clear cache after receiving it. Might be due to a vulnerability patch that's being rolled out with other devices as well. Not sure about it though but Android released a vulnerability patch bulletin. Let me get back to you in a while. Have to look for that link and I'm currently on mobile.
[Android General] andreidi:
I tried that too, but the differences were insignificant. The main differences are in the kernel binary file. This is why I could easily swap the zimage of the darklord kernel with luckas' one and obtain a fully working bootimg. I also tried the kernel included in Anton's VK latest and single ROM based on luckas' kernel, I had to modify some information regarding the rom name to make it to work with RR, but I couldn't see any differences at all from the standalone kernel.

I was hoping to find a way to tune volume boost and earpiece volume, but I couldn't find anything like that in the kernel bootimg. I really think the CM13 on which all 3.10.103 ROMs are based (RR, bliss etc.) has been released with another method of adjusting the volume, different from the CM13/RR with 3.4.67. And it's really driving me crazy since the earpiece volume is lower than stock and the speaker volume is so boosted that I have to reduce the volume at 75% to avoid distorsions when ringing or listening to music.

Also, I found another nasty bug in RR/CM13 3.10.103: FM RADIO IS MONO, never STEREO, no matter how much signal you have. I've been even next to the antenna of a local station and still couldn't get any STEREO. Can anybody confirm this? I'm gonna try to swap the FMRadio app from the 3.4.67 version to see if it works properly.

Last, but not the least, I still experience the proximity sensor bug during longer calls: the screen gets off, but when I take the phone away from my ear, the screen never comes back on by itself, I have to press the power button to end the call. This was also happening in RR 5.7.4 with 3.4.67 kernel and it's pissing me off...
[Android General] ahmedmoselhi:
can you please upload the lucas kernel you modified to work for RR 5.7.4 As it has front purple cam fixed unlike the darklord's one???

PS: I tried the memory fix you posted for RR 5.7.4 on VK"s Dirtyunicorn but it doesn't work
[Android General] andreidi:
I'm afraid I cannot do that, because of the terms written in previous pages. What can I do is guide you how to obtain it yourself, using free stuff available online, which are not forbidden to use:

1) Download Android Kitchen for Windows: https://xdaforums.com/attachment.php?attachmentid=4018225&d=1485461046 and extract the contents to a folder.

2) Download this ROM: https://vk.com/lenovo_a5000?w=wall-111995812_4303/all and extract boot.img to the same folder you extracted Android Kitchen.

3) Drag and drop "boot.img" to "unpackimg.bat", let it finish, go to "split_img" folder and copy "boot.img-zImage" from there to any other location.

4) Execute "cleanup.bat" and delete existing "boot.img" from Android Kitchen folder.

5) Extract "boot.img" (with the bug) from your current RR 5.7.4 zip file, into the Android Kitchen folder.

6) Drag and drop "boot.img" to "unpackimg.bat", let it finish, go to "split_img" folder and copy the previously copied "boot.img-zImage" from where you saved it to the "split_img" folder, overwriting the existing one.

7) Execute "repackimg.bat" and your compiled boot image will be there named "image-new.img".

8) All you have to do is flash this new image using SP Flash Tool and scatter txt from other bootimg flashable kernels, or you could alteratively create a TWRP flashable zip with the boot.img using online guides, such as this: http://www.guidingtech.com/49814/create-flashable-zips-custom-recovery/
[Android General] ahmedmoselhi:
I got this error: could not load kernel zImage 'split_img/boot.img-zImage' when compiling the new boot img
[Android General] andreidi:
It's working, pay more attention to every step, just make sure you put the zimage file from the VK link bootimg version into the extracted bootimg from your RR 5.7.4.
[Android General] ahmedmoselhi:
I figured out a mistake and it works like a charm :laugh: but i noticed two things at luckas kernel different from darklord kernel:

1- luckas kernel drains battery faster than darklord's one :rolleyes:

2- luckas kernel has front camera fixed but still volume boost problem not solved as in darklord's kernel
[Android General] andreidi:
1. I never noticed, plus I'm using WiFi now almost 24/7 and a lot of talking and skype-ing, so this means more activity than in the past and I really can't tell.

2. Is volume boost problem really a kernel issue? Or is it more like a ROM issue? I am thinking it might be a ROM issue because all ROMS (including RR) are based on the same CM13 3.10.103 version, as most of the files in system are the same for all. You indirectly gave me an idea: to try and unpack the zimage itself and compare with 3.4.67, maybe there's still a chance to fix it, so you might be right about it.

LE: I think you are right: the volume issue IS LIKELY to be a kernel issue. I just found this for Nexus (just for comparison): "Until Google provides an official solution, for a fixed boot image please refer to: https://github.com/eugenesan/android_kernel_lge_hammerhead/releases/tag/6.0.1-MOB30P-Audio-Fix", which says "This a fixed version of an 6.0.1 2016-July-05 (MOB30P) with a fixed audio. Only kernel image was modified, the initrd is untouched." So I guess it's time to unpack the kernel itself and check with older GOOD kernels.
[Android General] Tuna-kun:
I'm using an unofficial cm13 nightly but it doesn't have FM radio. I can't find a working FM radio in the internet.

Can anyone please give me a flashable FM radio for my la5k? Thanks.
[Android General] 7awliet:
Warning About Upgrading To S125

WARNING RE: UPGRADING TO S125

If you are on stock firmware and want to upgrade to S125 then it is required to FIRST wipe Cache, Dalvik Cache, and most likely Data (so backup!) too. If you do not do this first and upgrade to S125 then you can expect a bricked phone (see my signature how to fix).

You have been warned.​
[Android General] mido800:
guys a little question

what is some symlink failed and how to fix it

it happens everytime i try to install any rom with new kernel other than lineage
[Android General] 7awliet:
Use searchbox

Are you getting Error 7? If so just search 'symlink' in the search box on the right:

Error 7, failed symlink, and other problems whilst flashing in TWRP - they're all related.

You either wiped System partition, are running TWRP 2.7.8.0 instead of 3.0.0.0, or your updater-script in the ROM is not correctly set for A5000.

Post #719, #720, #722, #883-#888, #1136, #1140-#1147, #1603-#1610

2nd question, line 5 of FAQs in post #1580
[Android General] Eazart:
Please am sorry to batch in another topic please any body know or have MIUI V8 or any better Custom Rom for HTC DESIRE 626G MT6592? I dnt like CM/RR always exclamation mark on network which force me to buy data before use internet and some minor issues... Am sorry once Again.
[Android General] northwindtrades:
What we have here is miui v8 for Lenovo a5000 mt6582.

You should be asking this in a mt6592 thread instead.the best you could with this thread is cross port the MIUI 8 provided here to your mt6592 device.
[Android General] Eazart:
Cross port? Sound interesting am sorry how can that be done? Should i PM you? Am sorry Everyone if am disturbing anybody please
[Android General] 7awliet:
It's ok, you're asking about porting from MT6582 to MT6592, which is relevant because the reverse porting (MT6592 to MT6582) could be useful to someone here. As northwindtrades said though, it's best to ask in a MT6592 thread, which there are plenty. Use the search box at the top for MT6592.

There are tutorial threads on xda, on many blogs, and many other websites:

https://www.google.com/search?q=port+mt6582+to+mt6592

https://www.youtube.com/results?search_query=port+mt6582+to+mt6592
[Android General] mido800:
i just installed a dirty unicorn rom first it was giving me some symlink failed but now it's installed just right and installed nano open gapps after that

wiped cache a dalvik the rebooted gave me lenovo powered by android screen then rebooted again to recovery and it does this every time

what did i do wrong

---------- Post added at 06:50 AM ---------- Previous post was at 06:42 AM ----------

im using twrp 3.0 by jemini im sure i got the name wrong but im using 3.0

and when i flash a rom i roll back to kitkat and do a factory reset but this dirty unicorn wont install and gives me symlink failed

so i restored my lollipop and made a factory reset it installed correctly but wont boot always reboot to recovery
[Android General] mido800:
http://i.imgur.com/Q4CLLBq.png

why is that

every rom with new kernel gives me this
[Android General] KnightElf009:
what is the latest stable rom and recovery ? thanksss
[Android General] 7awliet:
Where did you get the Dirty Unicorns ROM from?

Dunno why, I don't have much info on your ROM nor your setup. I've heard of Chamelephon used to fix IMEI but for now you can use another method. About as simple Chamelephon: post #1000

ROM: Any KitKat, any Lollipop. Marshmallow? They're stable but depending on the ROM you will need to flash a patch or two to fix the camera and GPS

Recovery: TWRP v3
[Android General] Eazart:
I can Download Ur MIUI V8? And do the cross porting? Or I should go find the MT6592?
[Android General] 7awliet:
You can do both. I recommend getting a MiUI ROM built for MT6592 because it is much easier: https://www.google.com/search?q=miui+8+mt6592
[Android General] mido800:
i got it from vk but i removed it wasn't working i now have a rr from 4bda with darklord's pink front can kernel

any fix for that yet since i have no money to support any kernel developers and we can't get luckas working kernel
[Android General] 7awliet:
I'm sorry, no fix for pink front camera yet.
[Android General] mido800:
ok what about internal + sd card fix without the darklord kernel integrated in it
[Android General] andreidi:
Internal + sd card fix cannot be done without also editing the bootimg itself: https://xdaforums.com/showpost.php?p=70762868&postcount=1777

Also, maybe you are interested in fixing capacitive buttons not vibrating and restoring stock headset buttons keymap: https://xdaforums.com/showpost.php?p=70771939&postcount=1786
[Android General] andreidi:
[MENTION=7523876]7awliet[/MENTION], [MENTION=7387201]northwindtrades[/MENTION]: I've found some good information about possible sound fix. You can test it on your own: plug some headset/headphones in the jack socket and go to Sound in Settings and choose any ringtone to play it and it will play on the phone's speaker too. Raise the volume to max: there is no distortion on phone speaker. While ringtone continuously plays, remove the headset/headphones from the jack: this will make the ringtone distort again, to stop it from doing that you have to lower the volume by 2 steps. Now it's obviously somewhere there is a different value only for the speaker and it's normal when having headphones plugged. You can also hear the lock/unlock sound in the headphones: it's not that boosted such as when using the internal speaker. The main question is now: should this be kernel related OR ROM related? If we could just find out where these values are stored, we could easily copy-paste those values from headset mode (which doesn't distort) to speaker mode (which distorts). And maybe we could also find values for earpiece volume during calls.
[Android General] 7awliet:
...which boot.img are you packing there?

You're on the right track. It's kernel related from what I gathered. Someone some pages back said they have darklord's kernel 3.10.103 running either MM 6.0.1 or NG 7.1.1 (can't remember) and it has no sound issues. So it has to be kernel. Where in the kernel? I'd say the main kernek itself (zImage) rather than ramdisk. Either way, it'd take some decompiling to get into them.

As a side note, I read in a post that it's a severe breach of GPL v2 open-source license to modify and share something without providing the source code for it (where you got it), on top of that doing it for money? yikes. So I dunno how much standing the kernel devs have any more. https://www.kernel.org/doc/pending/gplv2-howto.html
[Android General] andreidi:
Those are the fixes we figured out last month for the darklord's 3.10.103. Nothing else.

The issue is there on 3.10.103 darklord release. This is the problem: it has been there from the beggining of 3.10.103 roms for our phone. Maybe those who say there are no sound issues don't mind the distortion of the ringtones and lock/unlock screen on internal speaker. The only RR/CM13 roms with no sound issue are the 3.4.67 ones, BUT with data/nvram sound fixes. I also believe those ROMs already have earpiece volume fix applied, because it is higher than others. The other main problem is that 3.10.103 roms do not react when applying vol_fix or spiker_fix, they don't even react if you delete the data/nvram/apcfg/aprdcl folder and all it's contents. Nothing changes. So I guess the kernel (zImage) has some overriden variable which tells to ignore any settings from APRDCL files.

Of course, compared to 3.4.67 roms without fixes, sound is way better in 3.10.103, because there is no volume level variations, as the boost is not raised high above, which made quieter parts of music sound equal to louder parts. The only issue left in 3.10.103 is that the volume itself of the internal speaker seems raised by 2-3 volume steps than it should be at it's max and that the earpiece is as quieter as stock roms and spiker_fix doesn't change anything. I remember how the calling the other person's BEEEEEEP distorted in the earpiece, but I didn't mind that at all because the overall in-call volume was higher and I could hear the speaker a lot better. Also, I wouldn't mind headphone's voluem raised by some more level steps. It would be so nice if we could configure all these by our likings.

Do you have any knowledge in unpacking zImage's content under Windows?
[Android General] 7awliet:
Kernel Source Code

I don't think you can decompile a kernel (other than at boot.img level of course) but the best you can do is make look at it through something like IDA Pro.

The way darklord and luckas edited the kernel is from the source. Then they built/compiled it.

Lenovo A5000 KitKat & Lollipop source code: http://lenovomobilesupport.lenovo.com/gb/en/products/Phones/A-Series/A5000/downloads

Learning to compile source code teaches you a lot, if you're interested in compiling the latest ROMs (Nougat 7.1.1: LineageOS 14.1, RR 5.8.0, etc.) yourself.

Couldn't find the exact repos they used but:

LuckAs:

https://github.com/luckasfb?tab=repositories

https://github.com/luckasfb/MT6592-KK-KERNEL/

darklord4822 (including 3.10.103 for CM 13):

https://github.com/darklord4822?tab=repositories

https://github.com/darklord4822/cyanogenmod_kernel_lenovo_a5000

Fix the error, compile it, boom. On Windows? Ehh can be done but you may wanna definitely go the Linux path. Starting pointers? Learn what GitHub is and how to use it.
[Android General] andreidi:
I'll have a look with IDA, I don't expect much.

Thanks for all the info, but I'm a complete noob in Linux, not to mention compiling and stuff. It would take me months or years to learn that and I don't have that much spare time. If I can't find anything useful with IDA and can't find any way to easily decompile zimage, I guess I'll have to leave the fix to be figured out by more experienced persons. My only hope is to be able to spot the difference comparing 3.4.67 zimage with 3.10.103 zimage and to "copy-paste" the code from 3.4.67 to 3.10.103. But I really don't think that can be that easy.
[Android General] romario_ne:
Hi! I`m not sure...

What if this will be useful for you:

https://xdaforums.com/showpost.php?p=64322609&postcount=195

http://processors.wiki.ti.com/images/1/18/Audio_Stack.jpg

maybe it`s not a kernel problem?!
[Android General] jrareola:
error executing updater binary in zip. Can someone help me

I keep getting the error executing updater binary in zip
[Android General] desertrose4aj:
Official/Stock Recovery image?

Hello dear,

As Lenovo A5000 is receiving OTA updates (11mb) "S125". It could not be updated through TWRP (or may it be only in my case).

It is requested you to kindly upload Stock Recovery image (better if you upload image with scatter file) or share any link for stock/original recovery.

Warm Regards​
[Android General] northwindtrades:
What where you trying to flash,which recovery where you on and what all did you wipe before flashing?

Theres a link in my signature which in turn links to a FAQ.

"Click to show content"

You need to flash stock firmware fully(not just stock recovery) to update succesfully.You also need to wipe data,cache and dalvik or you'll get a bricked phone

Links are provided in my signature or #1540
[Android General] Eazart:
Still can't find any MT6592 forum but I later found MIUI8 6.9.22 AND when I installed it I get system update and my phone download it with my knowledge so I check ☑ the downloaded update its V8_6.10.22 but I still need to port it to my device but still don't know how to port any porting I do I get bootloop or Black screen any help?
[Android General] andreidi:
Did anyone with CM13/RR 5.7.4 experienced the following after a longer period of phone in sleep mode?

1) WiFi connection drop: either it shows exclamation mark when unlocking, or it shows ok but there is no connection, sometimes it works after n seconds, sometimes you need to turn WiFi off then back on.

2) Skype/Whatsapp not taking any incoming calls or messages: sometimes they appear if you unlock the phone, sometimes they don't, so you need to restart the app by force-closing it. This may also require to do stuff from 1).

3) Google Play not showing pictures and not starting any download until after more than 10 seconds. This may also require to do stuff from 1).

I am using Greenify Donate with Xposed module, but I never added these apps and no system processes.

... BUT today I've found about "Battery Optimization" in System-Battery-three dots menu, from here: https://www.reddit.com/r/cyanogenmod/comments/3uh2i5/is_doze_enabled_on_cm13_because_it_doesnt_look/ --- "Battery Optimization queues wake-ups when idle so that apps wake the device less frequently and apps are asked to handle their business while the device is awake, rather than whenever they want. That's why you can exclude some apps if you want them to always wake the device whenever they want. Calls and SMS will never be affected by this, nor will notifications sent to apps using Google Cloud to Device Messaging (that's why Play Services can't be excluded)."

So now I think I got it, this must be the cause. I got angry and disabled this for all apps I have in the list (including system apps) and I'll be testing further. The thing is I don't know which app/system app is responsible for the WiFi connection, as I could only disable this battery optimization function only on apps I have trouble with (Skype, Whatsapp, Google Play etc.)

Any thoughts?