What is this "calypso a318uu"

Search This thread

dorkxperience

New member
Dec 7, 2021
4
0
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
 

Giancarlol

New member
Jul 29, 2022
1
0
guys i'm a noob and i lost my phone the other day and this a318uu was a gift i live in bolivia and this thing doesnt work its gsm locked if i follow the instructions in the guide will it unlock the phone to use with any carrier?
 

Kaynejulian

Member
Feb 26, 2020
14
0
Hopefully someone see this. This is actually my first project on phones but I know my way around android somewhat. Thanks to mrmazak I was able to get the calypso-super img although I didnt realize you don't have to extract the img and push to do individual partitions. Its just flash super.
Phone has no partitions though.
Tried create logical super 24000
Failed command
Fastboot getvar all shows no slot a slot b...no slots of any kind. Sure the phone let's me fastboot but not sure its fastboot
User return is no.
Was able to install the twrp mrmezak wrote so obviously it does push the img. Now I also have a DM verity corruption.
In any way other than fastboot the phone just bootloop and restart right back into bootloop. Max is 10-15 seconds. Fastboot will say on indefinitely though.
Two part question
How do I repair partions?
How do I remove DM verity corruption?

All I have access to is Windows 10. A lot of possible help full programs are Linux based which I dont have
 

Kaynejulian

Member
Feb 26, 2020
14
0
Microsoft Windows [Version 10.0.18362.30]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot devices'
fastboot: usage: unknown command devices'

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot devices
Y5XOAQZ5F6D6GUCQ fastboot

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x80000
(bootloader) hw-revision: cb00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4156mV
(bootloader) partition-size:sgpt: 4200
(bootloader) partition-type:sgpt: raw data
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 2ee5fbe00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:carrier: 800000
(bootloader) partition-type:carrier: ext4
(bootloader) partition-size:cache: 7000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:super: 92800000
(bootloader) partition-type:super: raw data
(bootloader) partition-size:tee2: ce0000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:dtbo: 800000
(bootloader) partition-type:dtbo: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 1800000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:loader_ext2: 10000
(bootloader) partition-type:loader_ext2: raw data
(bootloader) partition-size:loader_ext1: 10000
(bootloader) partition-type:loader_ext1: raw data
(bootloader) partition-size:lk2: 100000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:gz2: 1000000
(bootloader) partition-type:gz2: raw data
(bootloader) partition-size:gz1: 1000000
(bootloader) partition-type:gz1: raw data
(bootloader) partition-size:mcupmfw: 100000
(bootloader) partition-type:mcupmfw: raw data
(bootloader) partition-size:spmfw: 100000
(bootloader) partition-type:spmfw: raw data
(bootloader) partition-size:md1dsp: 1000000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 4000000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: ade000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: 800000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:md_udc: 169a000
(bootloader) partition-type:md_udc: ext4
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:vbmeta_vendor: 800000
(bootloader) partition-type:vbmeta_vendor: raw data
(bootloader) partition-size:vbmeta_system: 800000
(bootloader) partition-type:vbmeta_system: raw data
(bootloader) partition-size:vbmeta: 800000
(bootloader) partition-type:vbmeta: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 1800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:pgpt: 8000
(bootloader) partition-type:pgpt: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: Y5XOAQZ5F6D6GUCQ
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: u318
(bootloader) is-userspace: no
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR12A.R3.MP.V107.4.P20
(bootloader) version-bootloader: u318-36902ef--20210721124416
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.078s

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>
 

Kaynejulian

Member
Feb 26, 2020
14
0
The history may help someone help me as well.
So this phone bootloped when the owner tried to adapt a battery he had laying around directly via jumper wires. From an external tablet battery to the prongs of the phones battery. After that... Bootloop at start
 

mrmazak

Senior Member
Jun 16, 2013
3,255
1,341
Blu Vivo XL
BLU R1 HD
The history may help someone help me as well.
So this phone bootloped when the owner tried to adapt a battery he had laying around directly via jumper wires. From an external tablet battery to the prongs of the phones battery. After that... Bootloop at start
well that right there says hardware issue then.

first off there seems to be no reason to have done a battery jump start if there was not issues before hand,

then, also the contents of the flash memory (android system files) shouldn't have been effected by doing that so flashing doesn't seem likely to fix it.
 

mrmazak

Senior Member
Jun 16, 2013
3,255
1,341
Blu Vivo XL
BLU R1 HD
Microsoft Windows [Version 10.0.18362.30]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot devices'
fastboot: usage: unknown command devices'

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot devices
Y5XOAQZ5F6D6GUCQ fastboot

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>fastboot getvar all
......
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: u318
(bootloader) is-userspace: no
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR12A.R3.MP.V107.4.P20
(bootloader) version-bootloader: u318-36902ef--20210721124416
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.078s

C:\Program Files (x86)\Common Files\Adobe\Acrobat\New\platform-tools>
the line there "is-userspace:no" tells this ids he bootloader fastboot mode.

fastbootd mode will have a Yes entry. and that is where you need to flash super.img/ but from your history on the phone, im not sure it will help.\\
 

Kaynejulian

Member
Feb 26, 2020
14
0
well that right there says hardware issue then.

first off there seems to be no reason to have done a battery jump start if there was not issues before hand,

then, also the contents of the flash memory (android system files) shouldn't have been effected by doing that so flashing doesn't seem likely to fix it.
Ah. I agree. What he did was illogical. But now I know. This project is toast. Thanks for you time man. Truly appreciated
 

Asadullah

Senior Member
Aug 24, 2010
1,032
351
casselberry
Greetings fellas. Wanted to say thanks to mrmazak. Go recovery working pretty good I'm using this phone as a daily so can't test Android 12 yet. Is there a super user binary you would recommend?
 

Asadullah

Senior Member
Aug 24, 2010
1,032
351
casselberry
Greetings fellas. Wanted to say thanks to mrmazak. Go recovery working pretty good I'm using this phone as a daily so can't test Android 12 yet. Is there a super user binary you would recommend?
Hey so I messed up big time. Does anyone have the original at&t files for this phone? Mine is stuck in boot loop cuz I was too dumb to backup. The files mrmazak posted won't restore mine.

EDIT:
Alright so I was able to get the files from another calypso. I'll upload them soon as I can I don't get WiFi much and actually did this process from Ubuntu installed on a tablet. But every thing is working now.
 
Last edited:

mrmazak

Senior Member
Jun 16, 2013
3,255
1,341
Blu Vivo XL
BLU R1 HD
Hey so I messed up big time. Does anyone have the original at&t files for this phone? Mine is stuck in boot loop cuz I was too dumb to backup. The files mrmazak posted won't restore mine.

EDIT:
Alright so I was able to get the files from another calypso. I'll upload them soon as I can I don't get WiFi much and actually did this process from Ubuntu installed on a tablet. But every thing is working now.
great..

pls, just for reference i suppose. What process did yo uuse to restore your phone?
fastboot flash?
twrp?
that MTK tool (i cant remember th name right now)?
 

Asadullah

Senior Member
Aug 24, 2010
1,032
351
casselberry
great..

pls, just for reference i suppose. What process did yo uuse to restore your phone?
fastboot flash?
twrp?
that MTK tool (i cant remember th name right now)?
I used terminal version of the mtk client you linked. Just drop super.bin and vbmeta.bin in same directory as mtk binary.
use these commands:
python3 mtk w super super.bin
python3 mtk w vbmeta vbmeta.bin
Then reboot into fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.bin


as a side note I edited the lk.bin to remove the orange state using a hex editor and I haven't had any issues yet.
 
  • Like
Reactions: mrmazak

das280zx

Member
Jan 18, 2012
7
0
A friend gave me this phone so I thought I would play around with it a bit. Thanks to those who came up with the process. I was successfull in getting the aosp rom on there. Is there a way to make the camera work? Also, I'd really like to get the thing carrier unlocked. Any idea on how to do that without AT&T's help? Thanks a bunch!
 

Kaynejulian

Member
Feb 26, 2020
14
0
I used terminal version of the mtk client you linked. Just drop super.bin and vbmeta.bin in same directory as mtk binary.
use these commands:
python3 mtk w super super.bin
python3 mtk w vbmeta vbmeta.bin
Then reboot into fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.bin


as a side note I edited the lk.bin to remove the orange state using a hex editor and I haven't had any issues yet.
Anyway I can get you to send me a link of a clean super.img and lk files?
 

das280zx

Member
Jan 18, 2012
7
0
A friend gave me this phone so I thought I would play around with it a bit. Thanks to those who came up with the process. I was successfull in getting the aosp rom on there. Is there a way to make the camera work? Also, I'd really like to get the thing carrier unlocked. Any idea on how to do that without AT&T's help? Thanks a bunch!
Ok I figured out why the camera doesn't work. The phone keeps crashing any time an app tries to access media. I keep getting an error "android.process.media keeps stopping" or something like that. I pushed the opencamera app to it, which will at least start up, but cannot take a photo. It says "failed to save photo". I'm thinking it's a permissions issue or I am out of space. Will investigate further.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Phh aoap gsi a11 installs and runs good
    To clarify, let me tel you all which build version i have installed and outline the steps to get it loaded.


    THIS IS NOT INTENDED TO BE STEP BY STEP GUIDE ONLY AN OVERVIEW
    WHATEVER YOU DO ON YOUR DEVICE IS AT YOUR OWN RISK



    system-squeak-arm32_binder64-ab-vndklite-vanilla
    downloaded from :



    !. Bootloader must be unlocked.

    AT&T removed the enable OEM unlock from developer menu, but there is an excellent work around 'tool' to get around this.
    MTK CLIENT will allow you to read (pull) stock firmware off from phone, much like spflash tool does, except with this phone and many other newer phones the manufacture has enabled security and authorization files to block sp flash tool , SOOOO, tools like mtk client try to stay a step ahead.

    I only used the GUI options with the client, it was very user friendly , the tool has way more options than i needed to mess with.


    2. Before flashing gsi, make sure you have pulled firmware from phone, so you have stock super.img. If you don't you will not be able to restore device when / if you mess up the vendor partition.

    3. I disabled vbmeta verification .
    will need stock vbmeta from pulled firmware.

    boot into bootloader, (adb reboot bootloader , or reboot while holding the volume up button. You should get a boot menu)

    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

    (the last part need to point to you file location where ever it is)

    4. Now we need to move from bootloader to fastboot. fastboot reboot command didn't work for me so needed to boot recovery first, then fastboot.

    Code:
    fastboot reboot

    hold volume up button to get boot menu, select recovery
    from recovery select reboot fastboot

    in the fastbootd connection you will be able to flash gsi
    the system area is not large enough to fit gsi , so you will need to remove the /product partition.

    Code:
    fastboot delete-logical-partition product
    fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img


    once completed use the screen menu to reboot back to recovery and perform factory reset.

    With the exception of needing to use mtk client, the rest of these steps are standard android process. documented in many locations. I go to the android source first for information. \

    2
    They deleted the previous post, so I'm copy paste the steps from the blog post.

    Pre-requirements​

    Unlock phone bootloader​

    Bootloader must be unlocked to install the new firmware.

    MTK CLIENT will allow you to read stock firmware off from phone, except with this phone the manufacture has enabled security and authorization files to block sp flash tool.

    Install Python 3.9 from Microsoft Store and Git – Downloading Package and daynix/UsbDk · GitHub, then open a CMD:

    mkdir C:\test
    cd C:\test
    git clone https://github.com/bkerler/mtkclient
    cd mtkclient
    pip3 install -r requirements.txt
    Once installation in complete, start MTK Client with

    c:\Test\mtkclient
    python mtk_gui
    To activate BRUM mode for the phone and connect it to MKT Client

    • Turn off the phone if it’s on.
    • Press Volume UP + Volume DOWN and plug the USB cable.
    • Do not press power button and MKT Client will detect it.
    Backup:

    • In the Read partition tab,
    • Select all of them and Save to C:\Test\Firmware\Original
    • It will take about 40min to complete all the operation
    Unlock Bootloader

    • In Flash Tools tab,
    • Click on Unlock bootloader button
    • Debug log will show Bootloader: unlock and python windows list
    sej - HACC init
    sej - HACC run
    sej - HACC terminate
    sej - HACC init
    sej - HACC run
    sej - HACC terminate
    Progress: |██████████████████████████████████████████████████| 100.0% Write (Sector 0x1 of 0x1, ) 0.03 MB/s
    If you restart the phone, you will see a warning that bootloader is unlocked and it will ask you to factory reset the phone.

    Install the new firmware​

    You need to have Android DevelopersSDK Platform Tools | Android Developers installed to be able to flash the new firmware.

    Enable USB Debugging in the phone and connect ADB​

    • Start the phone
    • Perform a Factory Reset
    • Restart the phone and complete the initial wizard
    • Open Settings -> “About Phone” -> Tap the “Build Number” item seven times.
    • You should get a message saying you are now a developer.
    • Settings -> “System” -> “Advanced” -> “Developer Options.”
    • Open the menu and enable “USB Debugging.”
    To verify that ADB in installed correctly and is able to connect to the device:

    CD C:\Test\Tools
    adb version

    Android Debug Bridge version 1.0.41
    Version 33.0.1-8253317
    Installed as C:\Test\Tools\adb.exe

    adb devices

    List of devices attached
    AYMB5PKZCUEUUOSC device
    Boot into fastboot with the following command adb reboot bootloader
    or reboot while holding the volume up button and select fastboot.

    Install Google ADB FastBoot driver in Windows 11​

    Download Google USB Driver | Android Developers as they will be needed to connect the device via fastboot. To install the driver, we need to force the installation in Device Manager with these steps:

    • Open Device Manager
    • Right click on Other Devices \ Android device
    • Select “Update Driver” -> “Browse my computer for drivers” -> “Let me pick from the list of available driver
    • Select “Show All Devices” -> “Have Disk
    • Navigate to “C:\Test\Tools\usb_driver_r13-windows” and let Windows load the drivers
    • Select “Android Bootloader Interface” as driver name
    • Test that Fastboot tool is able to interact with the phone
    CD C:\Test\Tools
    fastboot devices

    AYMB5PKZCUEUUOSC fastboot
    Next step is to disable vbmeta verification with the following steps:

    Firmware update via Fastboot​

    • While the phone is in the FastBoot mode, type the following:
    CD C:\Test\Tools
    fastboot devices
    fastboot --disable-verity --disable-verification flash vbmeta "C:\Test\Firmware\Original\vbmeta.bin"

    target reported max download size of 134217728 bytes
    sending 'vbmeta' (8192 KB)... OKAY [ 0.204s]
    writing 'vbmeta'... OKAY [ 0.189s]
    finished. total time: 0.393s
    After vbmeta image is flashed, perform:

    • fastboot reboot fastboot to restart the phone and enter fastbootd
    • Check the phone is connecting correctly with fastboot devices
      and force the installation of Android Bootloader Interface in Device Manager if needed.
    The following step delete product partition so system partition has enough space:

    fastboot delete-logical-partition product

    Deleting 'product' OKAY [ 0.016s]
    Finished. Total time: 0.016s
    This command flash the custom rom on system partition:

    fastboot flash system "C:\Test\Firmware\system-squeak-arm32_binder64-ab-vndklite-vanilla.img"

    Invalid sparse file format at header magic
    Resizing 'system' OKAY [ 0.016s]
    Sending sparse 'system' 1/5 (255489 KB) OKAY [ 14.939s]
    Writing 'system' OKAY [ 7.651s]
    Sending sparse 'system' 2/5 (262100 KB) OKAY [ 15.141s]
    Writing 'system' OKAY [ 7.705s]
    Sending sparse 'system' 3/5 (262104 KB) OKAY [ 15.001s]
    Writing 'system' OKAY [ 7.595s]
    Sending sparse 'system' 4/5 (261825 KB) OKAY [ 14.752s]
    Writing 'system' OKAY [ 7.711s]
    Sending sparse 'system' 5/5 (183741 KB) OKAY [ 10.421s]
    Writing 'system' OKAY [ 5.832s]
    Finished. Total time: 107.885s
    Once flash of new rom is completed, you can restart the phone and it will boot using the new rom.



    Original post suggested to perform a factory reset.
    WARNING: In my case, a factory reset caused a reboot loop and was not able to

    If you want to proceed, in the menu on the screen:

    • Select “Enter recovery” and
    • Select “Wipe data/factory reset
    Screen on the phone will show

    -- Wiping data...
    Formatting /data...
    Formatting /cache...
    Formatting /metadata...
    Data wipe completed.
    If you missed the previous screen, or clicked the wrong button/option:

    • restart the phone holding Volume UP,
    • Select fastboot on the phone
    • Type fastboot reboot fastboot to reenter fastbootd screen
    • And repeat the factory reset
    Restart the phone and you are up and running.

    Restore original firmware​

    If you need to restore original rom, use MKT Client tool to write:

    • vbmeta.bin
    • super.bin
    then close the tool and restart the phone. It will be like new
    1
    Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
    I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
    The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C

    Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.

    Any help on MediaTek driver so I can finish the guide and post the link here?

    Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find :(

    Thanks a lot for your help!
    1
    After some extensive Googling, and since I doubt this falls under the "you're flashing the wrong build/version" because there's only one variant of this phone, I'd say it might be possible you're not running the right SDK platform package.

    Start Android Studio, go to Settings > Appearance & Behavior > System Settings > Android SDK and make sure you have the right platform packages installed (i.e. Android 10, API 29) and updated.
    1
    i did stop working with this phone already few months ago, but i did compile twrp , if your interested.

    its not real useful , in that the /data partition remains encrypted, so cant do backups, which is the main purpose. but ill link the github source and release in case you want to continue it. \


    device files, including TWRP :: https://androidfilehost.com/?w=files&flid=332377

    device tree :: https://github.com/mrmazakblu/twrp-device-att_u318aa