yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] terranaut:
tx for this toolbox coming out!

i got this phone via assurance, and indeed, it not only installs many apps/websites with zero user control, but also apps with all chinese characters, and that was right out of the box. a month later i called assurance to stop my service with them, though i've kept this phone. they asked why i was stopping their service, and i just told her it was enough that i had daily apps/games/sites installed without my permission or control, but that some of them were in a chinese character set; this from a phone given to u.s. citizens applying for federal help during covid.

i now use safelink instead, which just gave me a sim for my pixel 3a, much simpler/safer than assurance.
[Miscellaneous Android Development] clintongsan:
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.

I followed the guide step by step but as I have attempted other root options in the past, I think it caused my phone to soft-brick due to those past attempts that I tried with only my own limited knowledge.

So this is my personal experience, only posting for others in the event that someone else has a similar or identical issue. The issue(s) I had were almost certainly not at the fault of the person who wrote this guide, just FYI. For many, their process has proved successful first-try, as you'll see within the comments.

Again, MY experience:

FIrstly, I had to do things differently. So I DID NOT flash anything to the boot partition. I SKIPPED THAT STEP. (Of course this is after my first try when I followed the post's instructions. After my first attempt I found myself in a soft-brick situation. Luckily, I have two of these devices so I was able to rescue the device using the working device's firmware and I only flashed recovery to begin with, and then booted into TWRP, pushed Magisk and installed it...error. Sideloaded Magisk, SUCCESS!

(Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've got you some Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. PitchBlack wouldn't show my files AT ALL so options were very limited with that recovery.

And other than that, this guide is awesome! I'm now rooted, and I've got LSposed and even changed my font with a magisk module, as well as the boot up screen haha.

Thank you so much to @PizzaG , for not only putting this together but for taking the time to share and help others.

(TAKEN FROM ORIGINAL POST-UNCHANGED): We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
[Miscellaneous Android Development] Deleted member 11575455:
you are false in giving people that "advice" if you were in the test Telegram group for this device, you would surely know that 3+ people have been testing the ToolKit without issue. I post the Telegram link for a reason. So if people have an issue with something, instead of badmouthing an option or feature, you come get live help to fix the real issue at hand, which is not flashing the boot image.
[Miscellaneous Android Development] tuffasagong:
So I pushed root for this device and installed a batick recovery and bootloops, trying the unbrick restore.
[Miscellaneous Android Development] :
come to the Telegram group please. Did you format data in recovery? Did you wipe encryption ?
[Miscellaneous Android Development] Badger50:
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
[Miscellaneous Android Development] :
then expect long delays in responses as I'm on Telegram 24/7 as apposed to logging on to a forum, which I only do a couple times a week. TG is for support use it or don't. I suppose I should just stop sharing since I can't get proper testers or feedback anyways
[Miscellaneous Android Development] imevil2011:
this works used readme in the file did as it said works root and twrp
[Miscellaneous Android Development] :
That's Fantastic, I appreciate the feedback and happy it worked out for you. More Recoveries and tweaks are still on the way, enjoy
[Miscellaneous Android Development] imevil2011:
Looking forward keep up awesome work
[Miscellaneous Android Development] tuffasagong:
I used 0.6 there was no twrp image even though it said there was an option. It says u693cl on the screen. I don't know what the flip is going on. I have been rooting phones since the of droid and never had issues like this. I have not been able to boot into recovery at all and now it just boots the UMX screen and goes into error state. I did the whole soft unbrick option and remove device encryption although it doesn't have a custom_vendor.img just like 0.6 didn't have a twrp, am I downloading something wrong??? Guess I will just throw it out the window.. glad it worked for others.
[Miscellaneous Android Development] :
Download version 0.08 and run the unbrick option, then when booting again run custom stock and a recovery. The 0.06, only recovery was Batik and all options were flashing that
[Miscellaneous Android Development] tuffasagong:
Thanks man, I will try it. So I actually got batik recovery to boot, I couldn't get into any of the recoveries at all so there is some progress.

Edit: Everything works! Thank you for your help and your awesome program. Love the custom stock rom (boot screen kicks a$$).
[Miscellaneous Android Development] clintongsan:
You're a little bit of an angry man, aren't ya? First off, I began the entire post by giving great credit to the person/people who developed this guide. Is it my fault that the magisk patched boot img bricked the device? No...that's not my fault dude. I followed YOUR instructions. Is it my fault that maybe you overlooked a detail in your guide? NO, I have no ownership over the guide YOU posted. Is it apparent that I was thankful for the guide and only providing information in hopes that IF anyone else experienced the same problem, they'd know someone else who likely found a resolution and prove to be a help to them? Yeah...so what the hell is your problem? Do you think you're entitled to speak to people however you want because you figured out how to use a busted, old, bug-filled software tool to root a meaningless, very low-spec device? Do you do everything perfect the first time and NEVER, EVER make mistakes? I would hate to be your boss at a job. Simply because I do not enjoy firing people but if you worked for me I can already observe you are the type of person who thinks he is all-knowing and therefore DOES NOT take criticism well and tends to do things his own way regardless of what he's told by others, EVEN when it doesn't work. So I'd probably have to have many meetings with you before ultimately I do the one thing that is never enjoyable, fire your butt for not following the rules/breaking rules. I'll go ahead and make my own post on this subject, WHERE PEOPLE CAN GIVE BACK EXAMPLES OF THEIR EXPERIENCE WITHOUT WORRYING THAT SOME JERK IS GOING TO BE CONDESCENDING TO THEM. Get yourself some manners, man. This is a community, not "PIZZAG'S FORUM". ...rude.
[Miscellaneous Android Development] clintongsan:
Sounds like you had a similar problem...was it just a matter of waiting for QFIL to clear programming/reboot EDL? I tried taking this guide a step further by doing a factory reset, unrooted, with TWRP, and saving partitions to create a similar-to-stock firmware file. Unfortunately, I unplugged during the last step where QFIL reboots the phone out of EDL when you close the partitions information box and it was ummm...well, no bueno...lol. Now I have to learn QPST/QFIL even further because I finally have the device booting (black screen, straight to EDL or download mode) and there is corruption on the phone's file system/memory so I worked for a couple hours on it yesterday and I'm about to start back at it today. That's why I'm asking...I came back here to see if anyone had any advice. Unfortunately, the creator of the post is not very friendly, to say the least, so I'm likely going to have to figure this out on my own. I followed the guide step-by-step and ran into a small problem, a soft-brick, if you will, that was EASILY resolved by just re-flashing the boot.bin I had extracted as a backup prior to doing this and then flashing Magisk from within TWRP after that....booted right up. Now this could've and most likely, now that I've been deemed "false" for posting my experience, it's only fair to say this could've and seems to be an isolated issue with just my device. Some people only hear praise but the minute someone has a problem they prove to be....*clears throat* difficult, when working with others lol. Back to the playground!
[Miscellaneous Android Development] clintongsan:
I haven't found any ROMs, did you happen to find one?
[Miscellaneous Android Development] clintongsan:
hahahaha, sounds like you caused multiple issues man. But at least you're being helpful to some people. I've edited my post in hopes that it complies with your sensitivities.
[Miscellaneous Android Development] clintongsan:
Does anyone have the stock firmware/or knows which order I should flash the stock partition backups I saved in QFIL? It worked once but I'm doing something wrong. I don't know enough about Android development to understand how the file system comes together during flash/first-boot. For example, the older device, U683CL, has a forum page where someone provided the stock april firmware, which only consisted of four files; boot, system, recovery and vendor, I think. There are, however, on the U693CL modem, over a dozen partitions that come up in QFIL's Partition menu. So would it be safe to assume that flashing just boot, system, recovery and vendor will rewrite the device's filesystem...at least, in theory? Because I backed up every single partition, including the 9+GB userdata partition, just in case. Any help would be appreciated. Thanks to all those providing help/support and advice!
[Miscellaneous Android Development] clintongsan:
You're going to get told off by the post creator for badmouthing...(P.S. ANY bad experience is a form of bad mouthing apparently). If you're still having issues I'll help you out. My telegram handle is @clintonsonn
[Miscellaneous Android Development] tuffasagong:
@clintongsan

So to get it running into recovery I basically had to install the recovery, the magisk bootimage, the unbrick files, the custom stock rom and the recovery again and it finally booted into the recovery. Don't know why or how but that is how. Now with the flashable zip (it works great I tried it) I would just flash that through orange or dark recovery than trying to flash the custom stock rom through the tool cause that was a bit time consuming and a bit of a process as well (had to use some dd commands in recovery cause was just booting into recovery).

PizzaG has been very kind to me and I appreciate his tool and all the recoveries and custom stock. I have a Blu G9 pro as my main phone and only use this for wifi tethering. It runs very well on the custom stock rom, like 5x better.
[Miscellaneous Android Development] guero.lurias:
does anyone have the stock firmware backed up that they can share with me please?
[Miscellaneous Android Development] guero.lurias:
the phone doesnt recognize the sim card anymore since i flashed it, does any one know a fix for that please? and thank you for all the cool recoveries and rom
[Miscellaneous Android Development] guero.lurias:
Hello anybody out there?
[Miscellaneous Android Development] Lulz§wag:
Well.. it seems as though this venture is going to be more interesting than I thought. I'm determined to root this damn phone but the adventure seems to be an arduous one. I just wanted to thank the OP and content provided to possibly make this happen as I've been searching EVERYWHERE and someone on Reddit finally sent me here.
[Miscellaneous Android Development] earickb:
Can anyone please help me understand this process? I'd greatly appreciate it
[Miscellaneous Android Development] Brickstin:
Wait 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.
[Miscellaneous Android Development] transgirlphoebe:
It is linux only because it uses a specific flashing tool optimized for linux. make a LiveUSB or somethin
[Miscellaneous Android Development] Pokemoncrusher1:
install and boot linux, follow instructions in readme to install toolkit, use toolkit to do whatever you want to do
[Miscellaneous Android Development] earickb:
I figured it out already but thank you!
[Miscellaneous Android Development] SlickStretch:
I think I found a typo in one of your scripts.

In 'Run_Setup.sh' line 5 reads

sudo apt purge ModemManager

I am getting an error that says "ModemManager not found."

Shouldn't it be

sudo apt purge modemmanager?

Now it works fine.
[Miscellaneous Android Development] SlickStretch:
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?
[Miscellaneous Android Development] tuffasagong:
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).
[Miscellaneous Android Development] SlickStretch:
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."
[Miscellaneous Android Development] tuffasagong:
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.
[Miscellaneous Android Development] cuzimthatnerd86:
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*
[Miscellaneous Android Development] earickb:
Easiest way to fix is to use Linux to flash Unbrick Files
[Miscellaneous Android Development] transgirlphoebe:
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
[Miscellaneous Android Development] transgirlphoebe:
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.....
[Miscellaneous Android Development] Didgeridoohan:
There are a couple of things that need to be addressed here...

First of all, that is not the way we expect users to address other members. Rudeness, flaming, etc is not tolerated on XDA. Treat other members with respect (no matter their age, young or old) and courtesy. This is quite clear in the forum rules, under "Member conduct", so if you're not familiar with said rules I suggest you read through them carefully:

https://xdaforums.com/t/xda-developers-forum-rules.4200559/

Secondly, Telegram. Chat apps can be quite useful, especially when there's need for direct and quick communication. But, if someone wants their work available here on XDA there needs to be support for it here as well. We're not simply a gateway to other forums or platforms... We generally allow development projects to have a Telegram support link, but if the thread is used solely to drive traffic away from XDA it will be closed.

XDA is about sharing, and you don't even have to be a member of the forum to be able to benefit from everything that's available here. We want to keep it that way, but if all support and development can be found under Telegram links it won't be so readily available.

TL;DR: Tone down the attitude and while Telegram links are allowed support and development need to be available on XDA if a thread is to stay open.

If anyone has anything to add on this, or have any questions my inbox is always open. Let's not keep posting about this here since we want to keep the thread on topic.

Cheers

Didgeridoohan

Senior Moderator/Developer Committee/Developer Relations
[Miscellaneous Android Development] guero.lurias:
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?
[Miscellaneous Android Development] tuffasagong:
Thank you, that worked.
[Miscellaneous Android Development] transgirlphoebe:
Glad i could help! and to Moderator/Dev Relations,your rules are behind the times,this account is older than half the members here darn near,im aware of the rules,but penalizing someone for not installing your half baked pile of garbage app is absurd at best insulting at worst.

@Didgeridoohan if you expect people to be here,then make a app worth using,like the old app was,it was nice. Could autodetect your device and point you to your forums easily,so dont come at me,for addressing flaws with most forum sites. Until the,telegram supremacy,and i still hope @PizzaG has the sense to switch away from XDA,and take his projects with it. Androidfurms/telegram supremacy. I have half a mind to kill the link for the vendor image just to be petty​
[Miscellaneous Android Development] imevil2011:
I don't get the hate here but just a fyi the readme in the file is self explained 2 3 4 then as you desire I've bricked my device 3 times with full support and recovery from this tool kudos 🍕 love this keep em coming bro muck love from ky ps my personal number call I'll help
[Miscellaneous Android Development] cannotkeepup:
Can someone take pitty on the stupid in the room???

I have read and read this web page and most of what I read is like some kind of alian to me.

I am hoping someone can in very child like terms set me straight.

I have a UMX u693cl.

I liked the phone because it is light in weight and small enough to fit in my wallet. Thanks to a friend all the extra stuff was removed making it so even the dumb like me could use it.

I could make a call, get a call, look at email, google direction or a phone number. That is all I need.

My service was with Assurance Wireless. Not a great company but I could call AAA if I needed to.

Well as I am sure you know TMoble bought out Sprint and in turn Assurance Wireless..

I got a letter saying I had to upgrade my phone to the new Tmoblie system. I called and asked what I needed to do and was tod I had to get a new phone. Something I cannot do right now so I figured I would wait. Then I get an email telling me all I needed to do was call and get a new SIM card. So I did.

About 4 days later new SIM card in hand I called them and ask now what. They tell me how to open back and install. Then tell me they had to restore something on there end and it would take an hour.

Two hours later my phone went from a 4g to a 3g and will not work at all. If is now a paper weight.

Call again told they sent the wrong SIM card.

A few days later I still have a paper weight.

So I put the old sim card back and it is working again but still on the sprint system.

So I called Safelink to see if I could just switch to them and bring my phone with me. They tell me yes but I have to have Assurance unlock it.

Called Assurance and they tell me they do not have to and will not to bad. I know this is against the law but what am I going to do about it.

So can any one tell me is there a way I can unllock it so I can use it on Safelink and how?

Again thank you for reading this and I am sorry it is so long.
[Miscellaneous Android Development] ways2:
Thanks for everything! this is a nifty little tool I really like it.

Only problem I've really had so far was being locked out after setting a lock screen password.

If I set up a password I won't be able to unlock when inputting the correct password. I tried searching for that .db file in file manager to delete but couldn't find it. Had to reformat and just use my phone without a lock screen password for now.