UMX U683CL root?

Search This thread

bigsteve62275

Member
Aug 8, 2019
16
2
52
Topeka
hey guys, when it comes to all of this i would say i am beyond a newb. so if i violate any protocol i plead ignorance and hope that you will bear with me. i have my disable sister who lives with me and i am responsible for who has had a government phone for years. just recently the powers that be in our great government who are in charge of how our tax dollars are spent somehow decided that one government phone was not enough for her.
to make a long story short she received a second phone out of nowhere that i now have the opportunity to play with.
it is a UMX U683CL and i can find nothing on the web to help me gain root. so i pose to you good people to share whatever links, knowledge and wisdom you can to teach me to pull the stock rom so that a possible custom recovery can be developed and then achieve root.
once again if i have violated any protocol i apologize, please correct me. and thank you in advance for any help>



bigsteve62275
 
Last edited:

Str8Budheavy

New member
Aug 6, 2019
1
0
I with you....

If anyone could help us root this phone that would be amazing! i ended up with three of these things lol
 

baileychic8

New member
Oct 1, 2019
2
0
Umx u683cl

If it helps you might search for ANS UL40 root info.....when I check my IMEI online it comes back to the ANS model.....and once it came back as
Brand:Teleepoch LTD Model:Lifesaver I thought that was odd. Nothing is available for the UMX that I've found. From what I was told by Assurance wireless they aren't able to unlock them either. None of the pay to unlock online companies can do it. These are really decent phones I suspect it's the service that makes them unusable.
 

bigsteve62275

Member
Aug 8, 2019
16
2
52
Topeka
ok what the heck is this (see attached) this is what i get when i run getvar all

Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4229940
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xfa00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x313c79a00
(bootloader) partition-type:carrier:
(bootloader) partition-size:carrier: 0x3200000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0xfa00000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x80000
(bootloader) partition-type:eek:em:
(bootloader) partition-size:eek:em: 0x800000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xa00000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:pad:
(bootloader) partition-size:pad: 0x100000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6e00000
(bootloader) partition-type:persist:
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x5dc00000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:DDR:
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x4200000
(bootloader) serialno:990b2328
(bootloader) kernel:lk
(bootloader) product:MSM8909
all:
finished. total time: 0.204s

C:\WINDOWS\system32>
 
  • Like
Reactions: BadRx

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
I believe this device ships with an unlocked bootloader. Would be easy to root, methinks. Standard custom recovery flash and SuperSU or Magisk flashable ZIP should land the plane. TWRP builds are way more prevalent than before. Shouldn't be hard to port from the U673C if they have the same CPU.

---------- Post added at 06:09 AM ---------- Previous post was at 05:41 AM ----------

If it helps you might search for ANS UL40 root info.....when I check my IMEI online it comes back to the ANS model.....and once it came back as
Brand:Teleepoch LTD Model:Lifesaver I thought that was odd. Nothing is available for the UMX that I've found. From what I was told by Assurance wireless they aren't able to unlock them either. None of the pay to unlock online companies can do it. These are really decent phones I suspect it's the service that makes them unusable.

The UL40 is not the same phone. They may have a similar processor, but they aren't nearly the same.
 
  • Like
Reactions: X--Force

X--Force

New member
Oct 23, 2019
4
0
I believe this device ships with an unlocked bootloader. Would be easy to root, methinks. Standard custom recovery flash and SuperSU or Magisk flashable ZIP should land the plane. TWRP builds are way more prevalent than before. Shouldn't be hard to port from the U673C if they have the same CPU.

The UL40 is not the same phone. They may have a similar processor, but they aren't nearly the same.

---------------------------------------

Hi Figlet! Could you give a newbie a little more info on the "Standard custom recovery" .. what and how should I do this for the Unimax U683CL? Thank you very much!
 

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
Basically, you just have to find a port of twrp or cwm recovery for this device and flash SuperSU or Magisk. You'll probably have to find someone willing to port the recovery image because I haven't seen any ports in my search, but I believe there are similar devices and twrp builder makes it pretty easy to make a recovery for any device. I'm not going to post a tutorial because there's plenty of information how to flash a custom recovery on any device.

Good luck!
 
  • Like
Reactions: X--Force

X--Force

New member
Oct 23, 2019
4
0
Basically, you just have to find a port of twrp or cwm recovery for this device and flash SuperSU or Magisk. You'll probably have to find someone willing to port the recovery image because I haven't seen any ports in my search, but I believe there are similar devices and twrp builder makes it pretty easy to make a recovery for any device. I'm not going to post a tutorial because there's plenty of information how to flash a custom recovery on any device.

Good luck!

Thanks very much for the reply and the info!! I'm off to hunt for a tutorial now lol. And "someone willing to port the recovery image..." which I have no idea what is. But, I will find out! Twrp builder, here I come. Thank you again!

Edit.. Oh, and I wanted to confirm something you said earlier. It does ship with an unlocked bootloader. Also, if it helps anyone, the "Secure Boot" setting is "Disabled", the bootloader version is blank, the "Variant" is "QRD eMMC", and the "Product Name" is "MSM8909".
 
Last edited:

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
Any news on this yet
I'd assume a good few months might take place before we hear anything on this device. If anyone needs cloud compute resources to compile code for this, id be glad to build a temporary VM with whatever specs necessary, depending on compute time & bandwidth required.

I'd also be glad to host any files until an official thread or GitHub is created
 
Last edited:
  • Like
Reactions: X--Force
Jun 11, 2011
32
1
Grandville
I at least need the recovery for this this phone don't have one so I can't flash magisk zip without a recovery its Android 8.1 the bootloader is already unlocked but no twrp and when i google search a bunch of clickbait sites come up for twrp.apk i do adb reboot recovery the phone restarts with the android guy saying no command
 
Last edited:

MrInsidious

New member
Feb 15, 2017
2
0
i have root on the phone!!!! You'll need to Reboot into EDL more and flash a custom boot img. im making a tutorial right now and will have everything up later this afternoon! Custom recovery will be on its way as well

Any updates on this? It's definitely been longer than that afternoon lol I'm anxiously awaiting a method to achieve root on this phone.
 

bigsteve62275

Member
Aug 8, 2019
16
2
52
Topeka
guess i am way too stupid to pull this off. cant get anything to work at all. keep getting sahara fail and cant figure out how to flash .img at all
 
Feb 9, 2020
1
0
I learned not to call Assurance with an issue with the UMC U683CL. The support team had me call from another phone asked for the info and they took the phone I used to call and flipped the sim codes on both phones, cell numbers etc, now neither function. So, if there's a will there is a way. It's an Android which is great but the menus and apps just aren't all that great. The issue is, once you unlock, remove Google their just aren't any decent apps to install. Damn Google. Makes the man want to hurl.
 

BadRx

Member
Dec 15, 2014
42
6
46
Azusa, CA
Google Pixel 3a XL
Moto G 5G
ok what the heck is this (see attached) this is what i get when i run getvar all

Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4229940
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xfa00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x313c79a00
(bootloader) partition-type:carrier:
(bootloader) partition-size:carrier: 0x3200000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0xfa00000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x80000
(bootloader) partition-type:eek:em:
(bootloader) partition-size:eek:em: 0x800000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xa00000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:pad:
(bootloader) partition-size:pad: 0x100000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6e00000
(bootloader) partition-type:persist:
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x5dc00000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:DDR:
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x4200000
(bootloader) serialno:990b2328
(bootloader) kernel:lk
(bootloader) product:MSM8909
all:
finished. total time: 0.204s

C:\WINDOWS\system32>
May I ask how you actually got to fastboot on the phone? It seems to be stuck on the UMX logo on most other folks.
 

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
I just got one of these, I'll try and find the source and maybe build a rom or something. The charger port is loose so I'll be a while before I can do anything substantial.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    ok what the heck is this (see attached) this is what i get when i run getvar all

    Microsoft Windows [Version 10.0.18362.418]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>fastboot getvar all
    (bootloader) version:0.5
    (bootloader) battery-soc-ok:yes
    (bootloader) battery-voltage:4229940
    (bootloader) variant:QRD eMMC
    (bootloader) unlocked:yes
    (bootloader) secure:no
    (bootloader) version-baseband:
    (bootloader) version-bootloader:
    (bootloader) display-panel:
    (bootloader) off-mode-charge:0
    (bootloader) charger-screen-enabled:0
    (bootloader) max-download-size: 0xfa00000
    (bootloader) partition-type:userdata:ext4
    (bootloader) partition-size:userdata: 0x313c79a00
    (bootloader) partition-type:carrier:
    (bootloader) partition-size:carrier: 0x3200000
    (bootloader) partition-type:vendor:
    (bootloader) partition-size:vendor: 0xfa00000
    (bootloader) partition-type:config:
    (bootloader) partition-size:config: 0x80000
    (bootloader) partition-type:eek:em:
    (bootloader) partition-size:eek:em: 0x800000
    (bootloader) partition-type:keystore:
    (bootloader) partition-size:keystore: 0x80000
    (bootloader) partition-type:splash:
    (bootloader) partition-size:splash: 0xa00000
    (bootloader) partition-type:ssd:
    (bootloader) partition-size:ssd: 0x2000
    (bootloader) partition-type:fsc:
    (bootloader) partition-size:fsc: 0x400
    (bootloader) partition-type:misc:
    (bootloader) partition-size:misc: 0x800000
    (bootloader) partition-type:modemst2:
    (bootloader) partition-size:modemst2: 0x180000
    (bootloader) partition-type:modemst1:
    (bootloader) partition-size:modemst1: 0x180000
    (bootloader) partition-type:pad:
    (bootloader) partition-size:pad: 0x100000
    (bootloader) partition-type:apdp:
    (bootloader) partition-size:apdp: 0x40000
    (bootloader) partition-type:devcfg:
    (bootloader) partition-size:devcfg: 0x40000
    (bootloader) partition-type:tzbak:
    (bootloader) partition-size:tzbak: 0x200000
    (bootloader) partition-type:tz:
    (bootloader) partition-size:tz: 0x200000
    (bootloader) partition-type:rpmbak:
    (bootloader) partition-size:rpmbak: 0x80000
    (bootloader) partition-type:rpm:
    (bootloader) partition-size:rpm: 0x80000
    (bootloader) partition-type:abootbak:
    (bootloader) partition-size:abootbak: 0x100000
    (bootloader) partition-type:aboot:
    (bootloader) partition-size:aboot: 0x100000
    (bootloader) partition-type:sbl1bak:
    (bootloader) partition-size:sbl1bak: 0x80000
    (bootloader) partition-type:sbl1:
    (bootloader) partition-size:sbl1: 0x80000
    (bootloader) partition-type:keymasterbak:
    (bootloader) partition-size:keymasterbak: 0x80000
    (bootloader) partition-type:keymaster:
    (bootloader) partition-size:keymaster: 0x80000
    (bootloader) partition-type:cmnlibbak:
    (bootloader) partition-size:cmnlibbak: 0x40000
    (bootloader) partition-type:cmnlib:
    (bootloader) partition-size:cmnlib: 0x40000
    (bootloader) partition-type:devinfo:
    (bootloader) partition-size:devinfo: 0x100000
    (bootloader) partition-type:recovery:
    (bootloader) partition-size:recovery: 0x2000000
    (bootloader) partition-type:cache:ext4
    (bootloader) partition-size:cache: 0x6e00000
    (bootloader) partition-type:persist:
    (bootloader) partition-size:persist: 0x2000000
    (bootloader) partition-type:system:ext4
    (bootloader) partition-size:system: 0x5dc00000
    (bootloader) partition-type:boot:
    (bootloader) partition-size:boot: 0x2000000
    (bootloader) partition-type:sec:
    (bootloader) partition-size:sec: 0x4000
    (bootloader) partition-type:fsg:
    (bootloader) partition-size:fsg: 0x180000
    (bootloader) partition-type:DDR:
    (bootloader) partition-size:DDR: 0x8000
    (bootloader) partition-type:modem:
    (bootloader) partition-size:modem: 0x4200000
    (bootloader) serialno:990b2328
    (bootloader) kernel:lk
    (bootloader) product:MSM8909
    all:
    finished. total time: 0.204s

    C:\WINDOWS\system32>
    1
    I believe this device ships with an unlocked bootloader. Would be easy to root, methinks. Standard custom recovery flash and SuperSU or Magisk flashable ZIP should land the plane. TWRP builds are way more prevalent than before. Shouldn't be hard to port from the U673C if they have the same CPU.

    ---------- Post added at 06:09 AM ---------- Previous post was at 05:41 AM ----------

    If it helps you might search for ANS UL40 root info.....when I check my IMEI online it comes back to the ANS model.....and once it came back as
    Brand:Teleepoch LTD Model:Lifesaver I thought that was odd. Nothing is available for the UMX that I've found. From what I was told by Assurance wireless they aren't able to unlock them either. None of the pay to unlock online companies can do it. These are really decent phones I suspect it's the service that makes them unusable.

    The UL40 is not the same phone. They may have a similar processor, but they aren't nearly the same.
    1
    Basically, you just have to find a port of twrp or cwm recovery for this device and flash SuperSU or Magisk. You'll probably have to find someone willing to port the recovery image because I haven't seen any ports in my search, but I believe there are similar devices and twrp builder makes it pretty easy to make a recovery for any device. I'm not going to post a tutorial because there's plenty of information how to flash a custom recovery on any device.

    Good luck!
    1
    Any news on this yet
    I'd assume a good few months might take place before we hear anything on this device. If anyone needs cloud compute resources to compile code for this, id be glad to build a temporary VM with whatever specs necessary, depending on compute time & bandwidth required.

    I'd also be glad to host any files until an official thread or GitHub is created