[Please help] Trouble with rooting UMX U683CL
[Please help] Trouble with rooting UMX U683CL
(19-12-2022, 08:13 AM)maxpayne(17-12-2022, 04:46 AM)somnomania If, rather than using fastboot to try and flash the patched img, I use QFIL instead, I have problems there as well. First I get FireHose Fail (system can't find specified file), and if I hit the download button again it goes for a bit and then I get Sahara Fail. I've done everything mentioned in this thread (https://www.hovatek.com/forum/thread-30141.html); there are no spaces in the names, I've tried both firehose files I have, I'm using the latest version of QFIL. I really don't understand what it means by "use QFIL tool from within QPST"; does it mean the QFIL.exe that's in the QPST folder? Or do I launch some other exe in that folder that then has the option to open QFIL? It's not very clear.
You could either download QFIL as a zip or install a software named QPST which in turn contains QFIL; the latter is the better approach.
To use QFIL, you need to have some other XML files which you don't have so a better approach might be https://www.hovatek.com/forum/thread-26213.html
Are you sure bootloader is unlocked? How did you unlock it?
(20-12-2022, 06:09 AM)somnomania I tried reflashing the stock boot.img, and now it will only boot to fastboot mode, which means I can't even flash it again because I can't get the laptop to see it so I can boot it to EDL mode.
(22-12-2022, 10:48 AM)somnomania And how do you propose I do that when all it will do is boot into fastboot mode? Device Manager is seeing it as Kedacom USB Device > Android Bootloader Interface when I plug it in, if that helps. Again, I'm fairly certain I unlocked the bootloader in all this mess, I've been trying to get this phone rooted for like two months now and it's one of the first steps in pretty much every guide I've seen. It says Device State - Unlocked in fastboot, is that the network lock or the bootloader?
So however I get it back to a place where I can flash anything, I would restore the factory firmware from the backup of my phone (yes?), and then confirm that the bootloader is unlocked? What then?
(24-12-2022, 07:44 AM)maxpayne(22-12-2022, 10:48 AM)somnomania And how do you propose I do that when all it will do is boot into fastboot mode? Device Manager is seeing it as Kedacom USB Device > Android Bootloader Interface when I plug it in, if that helps. Again, I'm fairly certain I unlocked the bootloader in all this mess, I've been trying to get this phone rooted for like two months now and it's one of the first steps in pretty much every guide I've seen. It says Device State - Unlocked in fastboot, is that the network lock or the bootloader?
So however I get it back to a place where I can flash anything, I would restore the factory firmware from the backup of my phone (yes?), and then confirm that the bootloader is unlocked? What then?
Hold down both volume buttons then run fastboot reboot in fastboot.
See if the phone enters EDL again
(29-12-2022, 11:28 PM)somnomania Correction, though it may not be seen in time due to the replies needing to be approved before showing up: restart bootloader and recovery mode do work, if I hold the power button down for like two seconds. Restart bootloader restarts the phone, which puts me back in fastboot. Recovery mode goes to the dead android with "no connection" under it, and I've tried every single button combo the internet suggests to get around that, with no luck. Button combos either restart the phone (into fastboot), or there are a couple that reboot to a white screen, which my research suggests means there are missing system files from all this mess. I would love to just hard reset the phone and start over, but I can't even do that, apparently. ADB detects the phone if I do "fastboot devices", but I've tried many commands including ones to clear partitions, and I just get "FAILED (remote: unknown command)" for every single command.
IS the bootloader unlocked, if it says Device State - Unlocked in fastboot?
fastboot -w
fastboot reboot(02-01-2023, 07:51 AM)maxpayne(29-12-2022, 11:28 PM)somnomania Correction, though it may not be seen in time due to the replies needing to be approved before showing up: restart bootloader and recovery mode do work, if I hold the power button down for like two seconds. Restart bootloader restarts the phone, which puts me back in fastboot. Recovery mode goes to the dead android with "no connection" under it, and I've tried every single button combo the internet suggests to get around that, with no luck. Button combos either restart the phone (into fastboot), or there are a couple that reboot to a white screen, which my research suggests means there are missing system files from all this mess. I would love to just hard reset the phone and start over, but I can't even do that, apparently. ADB detects the phone if I do "fastboot devices", but I've tried many commands including ones to clear partitions, and I just get "FAILED (remote: unknown command)" for every single command.
IS the bootloader unlocked, if it says Device State - Unlocked in fastboot?
Try
Code:fastboot -w fastboot reboot
(03-01-2023, 07:29 PM)somnomania
fastboot getvar all