What is this "calypso a318uu"

Search This thread

dorkxperience

New member
Dec 7, 2021
4
1
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
 
  • Like
Reactions: notreal456789

Osamaaj03

Member
Nov 13, 2020
16
2
20
damascus, syria
can anyone provide me with a stock vendor/super.img, mine seem to be corrupted and I've apparently lost my backup. I would be really thankful
if you can provide we with a full backup file it would be better since I'm not really sure that the vendor is the problem, the thing is that I used phh aosp gsi for a while but I found it laggy and now that I've wanted to go back to stock, I couldn't find the backup files so I went and downloaded the ones mrmazak uploaded and flashed them using fastboot, after that the device didn't boot and went back to fastboot, try to decompress the calypso-stock-super.img file I found out that it was corrupted (the vendor.img to be specific). I tried downloading it multiple time but no use, it seems that the original file is faulty
 
Last edited:

Osamaaj03

Member
Nov 13, 2020
16
2
20
damascus, syria
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.
Hi, I broke my phone, didn't back up and now can't for the life of me find the og firmware other than an android host page that has a corrupted super.img (which what broke the phone in the first place) so... did you upload the files? and if not do you still have the phone on you? I really need them
 

Asadullah

Senior Member
Aug 24, 2010
1,033
351
casselberry
Hi, I broke my phone, didn't back up and now can't for the life of me find the og firmware other than an android host page that has a corrupted super.img (which what broke the phone in the first place) so... did you upload the files? and if not do you still have the phone on you? I really need them
Naw sorry the tablet I had backed em up on got taken
 

Miles8732

New member
Jul 8, 2023
1
0
I have this att calypso phone. I recently lost sim card when I call att they want the pin code I reset pin code it apparently went to the text to the sim card i do not have so now I am locked out of the att customer service part. I was gonna try to get the device unlocked. I tried multiple sites to unlock but nothing yet. So my next option I was going to try to adb and unlock carrier I have never done this and the device is not rooted. Can I connect to wifi download material emulator and enter
su
setprop sys.no_carrier_warning 1

Will this unlock carrier?

Need help please.
 

Windswipe

New member
Jul 25, 2023
1
0
Hi, I broke my phone, didn't back up and now can't for the life of me find the og firmware other than an android host page that has a corrupted super.img (which what broke the phone in the first place) so... did you upload the files? and if not do you still have the phone on you? I really need them
I believe I still have the full MTK backup somewhere. Do you still need it?
 

GhostBry

New member
Jul 30, 2023
1
0
Hello everyone I recently got a AT&T calypso U318AA and was wanting to root it. I've never rooted any phone ever so I don't know much, I was searching on how to root the U318AA but was having some trouble understanding some parts of it and some of the words if anybody can help I'd appreciate it. Thanks.
 

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
    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
    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.