Wait so... the initial release worked on which Operating system?An AIO ToolKit is about to be released for this device, I wrote it to handle everything from fresh untouched device to fixing a soft-bricked device. The initial release will be removed shortly and this new ToolKit is for Linux...
It is linux only because it uses a specific flashing tool optimized for linux. make a LiveUSB or somethinWait so... the initial release worked on which Operating system?
I am on Windows... I don't have Linux :/
Thanks for all your hard work though: I have one of these dumb phones.. always installs TopicNews as a System file and cant disable or remove.
install and boot linux, follow instructions in readme to install toolkit, use toolkit to do whatever you want to doCan anyone please help me understand this process? I'd greatly appreciate it
I figured it out already but thank you!install and boot linux, follow instructions in readme to install toolkit, use toolkit to do whatever you want to do
sudo apt purge ModemManager
sudo apt purge modemmanager
?Have you tried installing the custom rom zip file through the recovery that PizzaG inlcuded? I have had no problems with that (except setting up a lockout pin where it says pin not accepted even though it was correct).Hey guys, after using the ToolKit to install OrangeFox recovery, root, and the custom Assurance Wireless rom my phone won't boot.
Recovery works fine, but when the phone tries to boot, it shows the start-up animation (spinning balls animation) for about a minute before the screen goes black. (black but not off) Then nothing. I gave it a good 10 minutes.
I tried using the toolkit again, and tried the UnBrick option with the same results.
Can you help me?
I figured it out. It was happening because I forgot to wipe the data partition.Have you tried installing the custom rom zip file through the recovery that PizzaG inlcuded? I have had no problems with that (except setting up a lockout pin where it says pin not accepted even though it was correct).
That will do it. I tried a couple GSI roms. I think you have to unzip them and install the .img files. I only really got one I tried working and had to switch because I got a TMobile error saying this phone is not compatible with the network.I figured it out. It was happening because I forgot to wipe the data partition.
On another note, have you guys found any other custom roms? I've tried a couple of the GSI roms that PizzaG linked in the description post. (arm64, A/B roms) but OrangeFox recovery keeps telling me "Invalid zip file format."
Easiest way to fix is to use Linux to flash Unbrick FilesHi everyone! I was wondering if I could get some help from someone...anyone lol. Anyone with some tech expertise on this specific device would be a GODSEND. I'm pretty new here but even though it seems like a cool place to askfor help I'm going to go ahead and warn ya, this issue is complicated (at least to me). So I'm trying to figure out the easiest or any possble way to restore the UMX I have back to it's backup or factory status. Here's the deal: (I apologize for the length, I tried slimming up my message a bit)
So I was able to root my UMX U693CL following this guide but OOPS, I unplugged the device before QFIL was done sending it's REBOOT command and it just BRICKED IT....hard. I can still read from the device, and though no screen comes on I can still pull fastboot getvar all (yup, it shows as a fastboot device when the screen actually comes on but it sticks at that first screen and not a single intent-based fastboot command is recognized. So I can't flash/boot/etc. I did do a FULL backup before doing this tutorial so I literally have like 13GB of partitions, I renamed them all by appending the partition name at the start of the filename. My question is, how do I recover or begin to recover this device? Should I attempt making a loader on the sdcard?...I am just guessing but it seems that isn't the answer. I did re-establish the phone in device manager as the Qualcomm HS-USB QBLoader 9008 *proper* driver, but this is my experience...
I launch QFIL. It has found a port but I must select it. Then I select FLAT BUILD. Then I drop the programmer mbn in the correct spot and immediately go up to the top, selecting the second tab I think (I'm picturing it in my head so I'm sorry for the confusion) and then the next from the last option, Partition Manager, but eventually get timed out with an error along the lines of could not load Sahara XML...etc etc. (I will give a clear error message as soon as it turns on; its been sitting in my drawer for months so it's dead dead.) It appears as though when I tried restoring it the intial time, right after bricking it, I somehow managed to duplicate partitions maybe...have a look for yourself (if anyone's still reading this haha) Any advice would be greatly appreciated. I removed the serial number from the getprop.
Also, I use Windows 7 mostly but have Ubuntu/Linux on my laptop. I find working, especially with QPST and stuff, is so much easier on good ol' Windows 7 than any newer version, personally.
*Edit, I attached the QFIL working log*
the PIN issue is due to disabled force encryption. If you NEED the ability to lock the screen,i have a debloated vendor of my own that has forceencrypt enabled if youd like itHave you tried installing the custom rom zip file through the recovery that PizzaG inlcuded? I have had no problems with that (except setting up a lockout pin where it says pin not accepted even though it was correct).
JuSt A FrIeNdLy- shut up senior citizen,messageboards are the past. Instant messaging is the future. Just now noticed this high and mighty comment,and woooow. Im siding with Pizza,get telegram or get left out. Might see if releases can be explciity telegram too,just to spite yall. Ill ask him later.....Just a friendly reminder. Questions asked on XDA, should be answered on XDA. Not everybody uses or needs TG. After all, XDA is why we're all here in the first place.
-Regards: Badger50
There are a couple of things that need to be addressed here...JuSt A FrIeNdLy- shut up senior citizen,messageboards are the past. Instant messaging is the future. Just now noticed this high and mighty comment,and woooow. Im siding with Pizza,get telegram or get left out. Might see if releases can be explciity telegram too,just to spite yall. Ill ask him later.....
hi, i had a similar issue, good thing u made a backup. this is how i "fixed it". to unbrick: i held down power button and volume up and down , it vibrates 1 time the phones off, vibrates second time phone back on and a second later it turns off again let go, but its not really off, its in edl mode in case you cant get it in edl via toolkit or via adb and then i flashed stock recovery and got it to boot into recovery and factory data reset, booted into edl again and i could flash all the different recoveries and the custom rom without getting bricked again. my biggest mistake was not making a backup and i realized that my imei, baseband and the assurance wireless network had dissapeared, now i figured out how to fix it but i need the stock rom to do so, since you did make a backup you think you can help me out by uploading your stock rom please?Hi everyone! I was wondering if I could get some help from someone...anyone lol. Anyone with some tech expertise on this specific device would be a GODSEND. I'm pretty new here but even though it seems like a cool place to askfor help I'm going to go ahead and warn ya, this issue is complicated (at least to me). So I'm trying to figure out the easiest or any possble way to restore the UMX I have back to it's backup or factory status. Here's the deal: (I apologize for the length, I tried slimming up my message a bit)
So I was able to root my UMX U693CL following this guide but OOPS, I unplugged the device before QFIL was done sending it's REBOOT command and it just BRICKED IT....hard. I can still read from the device, and though no screen comes on I can still pull fastboot getvar all (yup, it shows as a fastboot device when the screen actually comes on but it sticks at that first screen and not a single intent-based fastboot command is recognized. So I can't flash/boot/etc. I did do a FULL backup before doing this tutorial so I literally have like 13GB of partitions, I renamed them all by appending the partition name at the start of the filename. My question is, how do I recover or begin to recover this device? Should I attempt making a loader on the sdcard?...I am just guessing but it seems that isn't the answer. I did re-establish the phone in device manager as the Qualcomm HS-USB QBLoader 9008 *proper* driver, but this is my experience...
I launch QFIL. It has found a port but I must select it. Then I select FLAT BUILD. Then I drop the programmer mbn in the correct spot and immediately go up to the top, selecting the second tab I think (I'm picturing it in my head so I'm sorry for the confusion) and then the next from the last option, Partition Manager, but eventually get timed out with an error along the lines of could not load Sahara XML...etc etc. (I will give a clear error message as soon as it turns on; its been sitting in my drawer for months so it's dead dead.) It appears as though when I tried restoring it the intial time, right after bricking it, I somehow managed to duplicate partitions maybe...have a look for yourself (if anyone's still reading this haha) Any advice would be greatly appreciated. I removed the serial number from the getprop.
Also, I use Windows 7 mostly but have Ubuntu/Linux on my laptop. I find working, especially with QPST and stuff, is so much easier on good ol' Windows 7 than any newer version, personally.
*Edit, I attached the QFIL working log*
Thank you, that worked.the PIN issue is due to disabled force encryption. If you NEED the ability to lock the screen,i have a debloated vendor of my own that has forceencrypt enabled if youd like it
Uploadgram >vendor-U693CL-hoshimmon.img
dl.uploadgram.me
There are a couple of things that need to be addressed here...JuSt A FrIeNdLy- shut up senior citizen,messageboards are the past. Instant messaging is the future. Just now noticed this high and mighty comment,and woooow. Im siding with Pizza,get telegram or get left out. Might see if releases can be explciity telegram too,just to spite yall. Ill ask him later.....
the PIN issue is due to disabled force encryption. If you NEED the ability to lock the screen,i have a debloated vendor of my own that has forceencrypt enabled if youd like itHave you tried installing the custom rom zip file through the recovery that PizzaG inlcuded? I have had no problems with that (except setting up a lockout pin where it says pin not accepted even though it was correct).