Welcome, visitor! [ Register | Login ] 

Post ROM
3575
  • Title: Lenovo A820
  • Listed: January, 2014
  • Last modified: 04/15/2014 10:27 pm
  • Version: ROM Android 4.1.2

    • You must be logged for ROM download.


Overall Rating : ★★★★★ 668


634159 total views, 11 today

523 Total favorites

  

CUSTOM
Lenovo A820
Lenovo A820 - Image 1Lenovo A820 - Image 2Lenovo A820 - Image 3Lenovo A820 - Image 4Lenovo A820 - Image 5

Author adMember Info

  • Listed by: infrared
  • Member Since: 04/06/2013

DESCRIPTION


Report bugs here: https://docs.google.com/spreadsheet/ccc?key=0AifNThxT1gbTdDRldHl6ZVJLR2lPOXBlRTBXNXFEWEE&usp=sharing#gid=0

Extra Ported Apps – CM File Manager, LenovoCalculator, new LenovoPower

http://d-h.st/users/I.nfraR.ed/?fld_id=33861#files

 

ROM Phone Lenovo A820
ROM Android 4.1.2
Based on Lenovo Version : A820_S150

Features ROM:

Lambda v2.4.1 Update from v2.4 (CWM/TWRP/OTA)

Changelog SelectShow

 

Lambda v2.4RC1 / v2.4 (CWM/TWRP)

Hidden-text SelectShow

 

 

Lambda v2.3.5/2.3.5a (CWM/TWRP)

Hidden-text SelectShow

 

Update Lambda v2.3.3 to v2.3.4 (CWM/TWRP/OTA)

Hidden-text SelectShow

 

Update Lambda v2.3.2 to v2.3.3 (CWM/TWRP/OTA)

Hidden-text SelectShow

 

Update Lambda v2.3.1 to v2.3.2 (CWM/TWRP)

Hidden-text SelectShow

 

Update Lambda v2.2.1 to v2.3.1 (CWM/TWRP)

Hidden-text SelectShow

 

Update Lambda v2.3 to v2.3.1 (CWM/TWRP)

Hidden-text SelectShow

 

Lambda v2.3 (CWM/TWRP)

Hidden-text SelectShow

 

V1 – removed from download section, not needed anymore
All changes in this version are included in newer ones.

Hidden-text SelectShow


V2.1 (CWM/TWRP)

Hidden-text SelectShow


V2.2 (CWM/TWRP)

Hidden-text SelectShow


Install ROM:
 V2 and up

Download desired zip and copy on sdcard.

You need a modified recovery to install the firmware and updates. If you have it already, proceed to step 3. If you don't have, follow these steps:

1. Download Lenovo drivers, unzip the archive. Turn off the phone and remove battery. Open device manager and connect the phone to PC. Watch for new devices. It will be displayed as МТ65хх Preloader. You need to be quick, because it will dissapear in some second. Click on it with the right button and select update driver. Point the wizard to the driver folder, it will install the correct driver automatically.
If it doesn't work with removed battery you can try to power on the phone and turn on developer options in settings or enter meta mode – hold Volume Down and Power buttons. Then connect the phone to PC again.
2. Download and extract Recovery zip and Flash tools. Run Flash Tools, click on DL DA All With Check Sum, load the scatter file located in Recovery folder, uncheck Preloader and hit Download (F6). Remove battery from phone and connect it to PC. When done, a green circle will appear.
3. Enter recovery mode – hold Volume Up, Volume Down and Power buttons until you see the logo. Make a backup of your current system first. Install new zip.

 



※Please make a backup of your device before installing or updating ROM

Responses to “Lenovo A820”

  3. 1
  4. 2
  5. 3
  6. 4
  8. 185
  9. 186
  10. 187
  11. 188
  12. 189
  13. 190
  14. 191
  15. 192
  16. 193
  17. 194
  18. 195
  19. 196

  1. 10/17/2013
    Ukraine

     

    alexuresp on 12/25/2014 @ 11:12 pm

    Hi, is any one have issue with ideafrient+lenovo launcher ? I cant see notification count of missed cals\sms on icons.

    I try to update ideafriend, change launcher for  Launcher2.apk but  nothing helps.

    Have any one such problem, how to fix it ?

  2. 11/25/2013
    Unknown

     

    staleta on 12/28/2014 @ 5:17 pm

    Can i add, remove or change icons in quick bar,or rearrange them horizontally i don't know what is the name i think is quick bar,
    on internet everybody calls is different…

  3. 03/05/2014
    Peru

     

    PerZhI on 12/29/2014 @ 11:59 pm

    the lower buttons do not respond (HOME button and the others). sometimes work, but generally unresponsive, help me!

    i installed the room v.2.4.1        HEEEELP! 

  4. 05/14/2013
    Taiwan, Province of China

     

    jwchen119 on 12/31/2014 @ 5:33 am

    Hi, infrared.

    I found one of the reason why my "boot.img" won't boot. Maybe I sould add the MediaTek header to both of the zImage and ramdisk by "mkimage"

    but when I run the script: 

    mkimage zImage KERNEL > zImage_with_header

    It shows that I use it by the wrong command.

    Tried everything I can but with no luck. :(

     

     

     

  5. 04/06/2013
    Italy

     

    infrared on 01/01/2015 @ 11:28 am Author ad

    The problem is you don't have ramdisk in your boot.img

    I've repacked it and it boots fine: https://drive.google.com/open?.....#038;authuser=0

  6. 04/06/2013
    Italy

     

    infrared on 01/01/2015 @ 3:19 pm Author ad

    Take the repacked kernel from my drive, extract the repacked boot.img and place it in the folder with scripts.

    You need to unpack it, but for Windows and the given scripts from the git repo you need bash for Windows. You can try this one, because it should be simple, but I haven't tried it myself: http://win-bash.sourceforge.ne.....t/ . I use cygwin. You also need perl, I use Strawberry Perl for Windows. Or maybe it would be easier to install the Android Kitchen (there should be tuts on the net), then add the mtk plugins for the kitchen and use that to repack/unpack boot images and sign the installation zip aftwerwards.

    If the unpack is successful, you need to have ramdisk folder.

    • 04/06/2013
      Italy

       

      infrared on 01/01/2015 @ 3:49 pm Author ad

      Here's how a correctly unpacked boot.img looks like on Windows.


      Here's the help for repack script

      $ ./repack-MTK.pl
      MTK-Tools by Bruno Martins
      MTK repack script (last update: 30-12-2014)

      Usage: repack-MTK.pl <COMMAND …> <outfile>

      COMMANDs are:

        -boot <kernel> <ramdisk-directory>
          Repacks boot image

        -recovery <kernel> <ramdisk-directory>
          Repacks recovery image

        -logo [--no_compression] <logo-directory>
          Repacks logo image

       

      What you need to do is repack boot image with your zImage. You can also rename it to boot.img-kernel.img and replace the unpacked one with yours. Then use

      ./repack-MTK.pl -boot boot.img-kernel.img boot.img-ramdisk.img boot.img

       

    • 04/06/2013
      Italy

       

      infrared on 01/01/2015 @ 3:51 pm Author ad

      ./repack-MTK.pl -boot boot.img-kernel.img boot.img-ramdisk boot.img

      is the correct one ofc, ramdisk is a directory, not an img file, but you get the idea :)

  7. 05/14/2013
    Taiwan, Province of China

     

    jwchen119 on 01/01/2015 @ 4:16 pm

    I'm using the VM to run the ubuntu to unpack/repack the boot.img, there's no problem to build the environment or run the script.

    The point is , when I run the scripts: 

    ./unpack-MTK.pl boot.img

    the "ramdisk" means the folder that unpacked by the scripts named "boot.img-ramdisk"?

    After I got the folder. I run the next script: 

    ./repack-MTK.pl -boot zImage boot.img-ramdisk new-boot.img

    Then renamed "new-boot.img" into "boot.img" and put it in the flashable zip.

    There's the log 

    —————————————————————————————-

    MTK-Tools by Bruno Martins

    MTK unpack script (last update: 17-10-2014)

     

    Valid Android signature found…

     

    Input file information:

     

    Kernel size: 2965528 bytes / load address: 0×10008000
     
    Ramdisk size: 640309 bytes / load address: 0×11000000
     
    Second stage size: 0 bytes / load address: 0x10f00000
     
    Page size: 2048 bytes
     
    ASCIIZ product name: ''
     
    Command line: (none)

     

    Kernel written to 'boot.img-kernel.img'

    Ramdisk size: 2246 blocks

    Extracted ramdisk contents to directory 'boot.img-ramdisk'


    Successfully unpacked kernel and ramdisk.

    marmalade@marmalade-virtual-machine:~/下載/mtk-tools-master$ ./repack-MTK.pl -boot zImage boot.img-ramdisk new-boot.img

    MTK-Tools by Bruno Martins

    MTK repack script (last update: 16-10-2014)

     

    Repacking boot image…

    Ramdisk size: 2246 blocks

     

    Successfully repacked boot image into 'new-boot.img'.

    —————————————————————————————-

    Even worse, I unpacked the boot.img from the zip uploaded from you then repack it again.

    Again, fail to boot…:(

  8. 04/06/2013
    Italy

     

    infrared on 01/01/2015 @ 5:14 pm Author ad

    I have the same output from the script and it works for me.

    If you delete unpacked files and then unpack the new boot.img, do you get ramdisk folder again?

    Because when I unpacked your boot.img the script said there's no ramdisk.

    Could it be that your username is in Chinese? I don't expect to have such a problem on Linux, but who knows.

  9. 05/14/2013
    Taiwan, Province of China

     

    jwchen119 on 01/01/2015 @ 5:36 pm

    I still get the ramdisk when I unpack the new boot.img.

    Here's the new one

    https://drive.google.com/file/.....iew?usp=sharing

  10. 04/06/2013
    Italy

     

    infrared on 01/01/2015 @ 7:54 pm Author ad

    Btw, you can also try the "KK" kernel, the initial merge with Dr.Shadow's repo: https://github.com/infraredbg/.....ernel_proton_kk

    I've built it with 4.8 toolchain and repacked with the mtk tools from the repo I gave you before. It boots fine.

    Don't mind it shows 3.4.5 at the moment. It is hardcoded, but will change it when I have the chance. Maybe I will work on that one for a while.

  3. 1
  4. 2
  5. 3
  6. 4
  8. 185
  9. 186
  10. 187
  11. 188
  12. 189
  13. 190
  14. 191
  15. 192
  16. 193
  17. 194
  18. 195
  19. 196

Leave a Reply
▲

You must be logged in to post a comment.


Terms&Conditions  -  Privacy&Cookie © 2012 - 2026 Needrom.com