[A51X/A70X aka Picasso 2][RECOVERY] TWRP 3.1.1-0

Search This thread

Kaban4ik86

Member
Feb 12, 2017
35
17
A700. ua_picasso2-6.0.1-20170327
I tried to change the file system on f2fs… No results
I saved last logs from recovery… But I forgot to do "adb logcat". If you need, I'll try to make them later.
 

Attachments

  • dmesg.log
    47.5 KB · Views: 20
  • recovery.log
    15.2 KB · Views: 15
Last edited:

Elibl

Senior Member
Dec 20, 2011
686
448
A700. ua_picasso2-6.0.1-20170327
I tried to change the file system on f2fs… No results
I saved last logs from recovery… But I forgot to do "adb logcat". If you need, I'll try to make them later.

this is a recovery dmesg i'd need a system dmesg. But i assume it's a sepolicy conflict from common hardware/nvidia/tegra3. You would need a build before March 23 ziyan is on it...

You've got a 3G version/a701. Are you willing to test for us as soon as we get to the point to implement 3G?

a full dmesg from initial boot would be nice though ;)
 
Last edited:

Kaban4ik86

Member
Feb 12, 2017
35
17
this is a recovery dmesg i'd need a system dmesg. But i assume it's a sepolicy conflict from common hardware/nvidia/tegra3. You would need a build before March 23 ziyan is on it...

You've got a 3G version/a701. Are you willing to test for us as soon as we get to the point to implement 3G?

a full dmesg from initial boot would be nice though ;)

Build from 20 Mar works.


I will try what I can. :)
How to make a full dmesg from initial boot?
 

Sterist

Senior Member
Sep 30, 2011
644
123
Galaxy S, quadrant 2
@Elibl you linked the a510 2.7 recovery as the new 3.1 in OP

I did notice before flashing it but assumed it was just a naming mixup on the file and not links, and the result is a bricked tab except for fastboot

you might want to fix that quickly ;)
 
  • Like
Reactions: Elibl

schuckid

New member
Apr 29, 2019
1
0
Just tried to update my A510 to CM12.1. Actually, OS is still original 4.1.2. First step was to get root access with Kingo Root, done. Then tried to install TWRP via Flashify - Flashify says successfully. Then try to reboot into recovery: Failed - "...not verified". What could be wrong? Which TWRP version I have to use? Any help is welcome, thanks.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15

    Hi here i bring to you TWRP Touch Recovery.

    everything is working

    only compatible with roms based on unlegacy-android device tree
    that means most probably all builds after 20170226

    since twrp 3.1.0-0 all variants (A510/A511/A700/A701)
    are unified from kernel and rom side and supported by one image file


    Installation:

    flash it with flashify from play store or via fastboot using following command:

    Code:
    fastboot flash recovery twrp-3.1.1-0-picasso2.img

    if you're updating from an lvm recovery (bigsystem) you need to format data and system and reboot recovery afterwards


    Download:

    twrp-3.1.1-0-picasso2.img


    Additional info:

    official site including changelog

    device tree
    kernel
    manifest


    Device specific:

    look at the device tree it's up to date

    Code:
    20170530:
    - update to twrp-3.1.1-0
    
    20170405:
    -unify a51x and a70x to picasso2
    -switch to kernel 3.4
    -leave lvm and just exchange cache and system partitions
     [B][COLOR="Red"]credits to ziyan for this genious idea[/COLOR][/B]
    
      [B][COLOR="Red"]Important:[/COLOR][INDENT]it will only be compatible with roms based on unlegacy-android device tree
    that means most probably all builds after 20170226[/INDENT][/B]
    
    20140623:
    - lvm implementation to resize system with flex partition
    
      [B][COLOR="Red"]Important:[/COLOR][INDENT]it's only compatible with bigsystem roms at the moment
    only ParanoidAndroid 4.4 from now on and cm11 in the near future[/INDENT][/B]



    credits to pawitp and TWRP Team

    and huge thanks to ziyan for bringing up 3.4 kernel

    just press thanks



    XDA:DevDB Information
    TWRP, Tool/Utility for the Acer Iconia A700 and A510

    Contributors
    Elibl, ziyan, pawitp, shreps

    Version Information
    Status: Stable

    Created 2014-07-16
    Last Updated 2017-05-30
    2
    That's true! :p
    It's running well but I'm waiting for an update of my ROM so, than will see how it works ;)

    Sent from my Nexus 4
    2
    @Elibl
    That's not a problem if you don't have the time. I found a workaround to get my tab back recovered without starting from scratch. That means, without wipe all partitions.

    At the moment TWRP is working fine. But two times (cannot say which circumstances are necessary) it's loosing the system partition information. Messages like "no OS installed" or "no SU found" were shown.
    Reflash the ROM fix the problem.
    If that happen again, I will capture the recovery log for you.
    Yeah shouldn't be a big deal at all as in most cases you go to recovery to flash a rom...

    don't know when I'll find the time may won't be soon but I know now the issue ;)
    2
    That will be great, if you can do so. (sry. German's English)

    here you go (not tested)

    please report back
    2
    Thank you

    ---------- Post added at 12:46 AM ---------- Previous post was at 12:07 AM ----------



    TWRP is now installed. Thanks you you help.
    How do i boot in the TWRP when the tablet is off?
    I tried Volume up + power button that didnt work.
    press volume down (2 dot) + power
    first vibrate release power
    second vibrate release volume down (2 dot) + press volume up (1 dot)