kelvin 2 Posted December 10, 2023 Share Posted December 10, 2023 My phone was flashed with Ubuntu Touch and then I tried to flash it back to the Android system, but my computer crashed during the process. Now, I have used the 9008 method to flash the official package back to the original system, but I panicked when I saw that the available space was only 8GB, so I flashed it again. This time, I selected some options on QFIL that I shouldn't have, including the option to clear all partitions. During the process, the computer froze, and after I forcefully shut it down, it turned into its current state. Now, the situation is that it boots to the Android logo screen, then the screen goes black and a red indicator light stays on. Is there still a chance to save it? 1 Quote Link to post Share on other sites
EskeRahn 5,421 Posted December 10, 2023 Share Posted December 10, 2023 I'm no expert in this, but the persist partition contains important information like imei, and I do not think we as users can recreate it. In principle you could clone the partition from another phone, but as they would share imei they could not co-exists on the net as active phone, so it would require some tool that can recreate the parts that are different between phones. So I will suggest you to contact [email protected] and hear what they will suggest. I fear that you would need to return the phone, for fxtec to do whatever 'magic' needed. 1 2 Quote Link to post Share on other sites
kelvin 2 Posted December 23, 2023 Author Share Posted December 23, 2023 I contacted [email protected] and their response was I came here for help and I'm really speechless, what product is this selling? Now my phone has been flashed with the official firmware using 9008, and after turning on the phone, the screen will go black and enter 900E mode after waiting for 10 seconds. I have re-flashed the phone dozens of times, and the situation is the same. It is the same whether it is firmware with or without GMS. 2 Quote Link to post Share on other sites
trahe 5 Posted August 28 Share Posted August 28 (edited) I had the same issues, and did do all the steps as explained in:https://drive.google.com/drive/folders/1h0NqcNvkcX0nV5V3VVie4-smEm5ijW36 mentioned here. The result is still the same bricked phone, even so the QFIL process went flawlessly, but the reboot still leads to the bricked phone, this time not even having the recovery partition. (the Lineage and UBTouch recovery worked fine before) Fairly to say this is the worst experience i had got with any kind of hardware i purchased. Still have some old Motorola Atrix, for which i stil can use TWRP and flash it successfully with different ROMs on the SDCard.P.S. Also important: as i reeived the phone it worked, i tried to flash UBTouch, which bricked it. I really got tired and kept it on my shelf for about 4 weeks (fully charged!) As i fetched it later and tried to turn it on, it seems the battery was drained below it should be So finally i needed to do the Rubber Band trick over night to get it trying to power on again. So this explains even more the worst experience with this piece of shit hardware, which is on top completely outdated, which i would not even mind, if i would be able to use UBtouch and ssh, which was my intention anyhow Edited August 28 by trahe Quote Link to post Share on other sites
brunoais 333 Posted August 29 Share Posted August 29 21 hours ago, trahe said: P.S. Also important: as i reeived the phone it worked, i tried to flash UBTouch, which bricked it. Just to double-check: Is secure boot confirmed turned off? Quote Link to post Share on other sites
trahe 5 Posted August 29 Share Posted August 29 7 hours ago, brunoais said: Just to double-check: Is secure boot confirmed turned off? It is: I can boot into the ub recovery Quote Link to post Share on other sites
brunoais 333 Posted August 30 Share Posted August 30 20 hours ago, trahe said: It is: I can boot into the ub recovery If you can login to recovery, then the phone is not bricked. You can still do things with it. Did you backup the partitions? 2 Quote Link to post Share on other sites
trahe 5 Posted August 30 Share Posted August 30 (edited) 2 hours ago, brunoais said: If you can login to recovery, then the phone is not bricked. You can still do things with it. Did you backup the partitions? Thanks for your reply. Yes that is for sure i good sign. Anyhow whatever and however i flash onto it, the result is still a not usable device. I did not backup the original phone, as i did not intend to use anything but UBTouch. When booting into UBTOuch, it shows the Android logo, and once i was able, totelnet 192.168.2.15 dmesg: ... [ 4.648619] initrd: Halium rootfs is /dev/mapper/system_a [ 4.649234] initrd: mounting system rootfs at /halium-system [ 4.653391] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 4.655506] initrd: WARNING: Android system image not found. [ 4.655650] initrd: mounting /dev/mapper/system_a (user mode) ... Edited August 30 by trahe Quote Link to post Share on other sites
brunoais 333 Posted August 30 Share Posted August 30 Did you delete all partitions that came with the phone? The persistent partition is one of the most important ones to keep a copy of. 1 Quote Link to post Share on other sites
trahe 5 Posted August 31 Share Posted August 31 Well i did not do any backup, but started the UB Installer, so it seems i lost this partition 2 Quote Link to post Share on other sites
brunoais 333 Posted September 1 Share Posted September 1 I don't know if UBInstaller deletes the persistent partition. Look at this guide: Try to do a backup of the partitions and let us know the outcome of it. If you are willing to, show us the full output from the tools used to backup. 2 Quote Link to post Share on other sites
trahe 5 Posted Monday at 08:22 AM Share Posted Monday at 08:22 AM (edited) OK sure, and thanks for helping the edl backup procedure i logged, and for further information i as well included the output of fastboot getvar all the product is *bengal* the last flash attempt has had been UBTouch i can as well have Pro1x or QX1050, depending on which ROM to flash (stock rom / Lineage21 i tried to no bootable avail) As a sidenote, i as well tried to do the : Pro1-X: Flash Stock Firmware in fastbootd Mode from the "official" Gdocs, and as well installed the newest platform-tools, but fastboot create-logical-partition checkparti_a 1024 Creating 'checkparti_a' FAILED (remote: 'unknown command') So i tried as well the QFIL on Windows method (btw:what a hassle to get the driver running) to me it seems there is no error there, but again, it does not boot. After the QFIL process, the device is in edl memory dump mode: edl /Users/htr/Documents/develeop/edl/edlvenv/bin/edl:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html __import__('pkg_resources').run_script('edlclient==3.62', 'edl') Capstone library is missing (optional). Keystone library is missing (optional). Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) sahara - Protocol version: 2, Version supported: 1 main - Mode detected: sahara Device is in memory dump mode, dumping memory Reading 64-Bit partition from 0x45ef20c0 with length of 0x780 OCIMEM.BIN(OCIMEM): Offset 0xc100000, Length 0x2a000, SavePref 0x1 CODERAM.BIN(RPM Code RAM region): Offset 0x4600000, Length 0x28000, SavePref 0x1 DATARAM.BIN(RPM Data RAM region): Offset 0x4690000, Length 0x14000, SavePref 0x1 MSGRAM.BIN(RPM MSG RAM region): Offset 0x45f0000, Length 0x7000, SavePref 0x1 DCC_SRAM.BIN(DCC SRAM region): Offset 0x1bed000, Length 0x3000, SavePref 0x1 DCC_CFG.BIN(DCC CFG region): Offset 0x1be2000, Length 0x1000, SavePref 0x1 CD_STRCT.BIN(CD STRCT region): Offset 0x40000000, Length 0x1f0, SavePref 0x1 CD_BTDDR.BIN(CD BTDDR region): Offset 0x400001f0, Length 0x100000, SavePref 0x1 CD_BTIMM.BIN(CD BTIMM region): Offset 0x401001f0, Length 0x180000, SavePref 0x1 CD_SHIMM.BIN(CD SHIMM region): Offset 0x402501f0, Length 0x1000, SavePref 0x1 DTDDR0_0.BIN(DDR0 DTTS0 region): Offset 0x44b9000, Length 0x0, SavePref 0x1 DTDDR0_1.BIN(DDR0 DTTS1 region): Offset 0x44b7000, Length 0x0, SavePref 0x1 IPA_IU.BIN(IPA IRAM region): Offset 0x5860000, Length 0x1f00, SavePref 0x1 IPA_SRAM.BIN(IPA SRAM region): Offset 0x5847000, Length 0x3000, SavePref 0x1 IPA_HRAM.BIN(IPA HRAM region): Offset 0x584a000, Length 0x1c54, SavePref 0x1 IPA_MBOX.BIN(IPA MBOX region): Offset 0x5872000, Length 0x100, SavePref 0x1 IPA_GSI.BIN(IPA GSI region): Offset 0x5806000, Length 0x1000, SavePref 0x1 IPA_SEQ.BIN(IPA SEQ region): Offset 0x585e000, Length 0x1fc, SavePref 0x1 PMIC_PON.BIN(Pmic PON stat): Offset 0x45e97000, Length 0x8, SavePref 0x1 PMON_HIS.BIN(PM PON HIST ): Offset 0x45e97008, Length 0xcc, SavePref 0x1 RST_STAT.BIN(Reset Status Region): Offset 0x45e970d4, Length 0x4, SavePref 0x1 DDR_DATA.BIN(DDR Training Data): Offset 0x45eb0964, Length 0x3000, SavePref 0x1 PIMEM.BIN(PIMEM region): Offset 0x10000000, Length 0x900000, SavePref 0x1 FSM_STS.BIN(Rst fsm stat): Offset 0x45e970d8, Length 0x4, SavePref 0x1 FSM_CTRL.BIN(Rst fsm ctrl): Offset 0x45e970dc, Length 0x4, SavePref 0x1 DDRCS0_0.BIN( DDR CS0 part0 Memo): Offset 0x40000000, Length 0x80000000, SavePref 0x1 DDRCS0_1.BIN( DDR CS0 part1 Memo): Offset 0xc0000000, Length 0x80000000, SavePref 0x1 DDRCS1_0.BIN( DDR CS1 part0 Memo): Offset 0x140000000, Length 0x80000000, SavePref 0x1 DDRCS1_1.BIN( DDR CS1 part1 Memo): Offset 0x1c0000000, Length 0x80000000, SavePref 0x1 load.cmm(CMM Script): Offset 0x45ebb084, Length 0x8cc, SavePref 0x2 Dumping OCIMEM.BIN(OCIMEM) at 0xc100000, length 0x2a000 getvar_all.log edl_backup.log QFIL_windows.log ubports.log Edited Monday at 10:39 AM by trahe provide more information 1 Quote Link to post Share on other sites
brunoais 333 Posted Monday at 11:00 AM Share Posted Monday at 11:00 AM (edited) I agree. There's no noticeable errors or warnings in the logs. @trahe I found this almost by chance: Does it help you? It shows that restoring some of the partitions worked to unbrick his phone. Edited Monday at 11:01 AM by brunoais 2 Quote Link to post Share on other sites
trahe 5 Posted Monday at 06:49 PM Share Posted Monday at 06:49 PM 7 hours ago, brunoais said: I agree. There's no noticeable errors or warnings in the logs. @trahe I found this almost by chance: Does it help you? It shows that restoring some of the partitions worked to unbrick his phone. No unfortunately it did not help. The backups i have are doubtful i guess... But there is one noticeable difference after running the UBports installer: the recovery starts with: Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perofrma a factory data reset and erase all user data stored on this device. Try again Factory data reset So if i choose Factory data reset i get --Wiping data... Formatting /data E:format_volume: fs_type "auto" unsupported Data wipe failed 1 Quote Link to post Share on other sites
brunoais 333 Posted Monday at 06:52 PM Share Posted Monday at 06:52 PM Looks like something really screwed up your partitions... This is now beyond what I can think at the moment. I'm currently out of ideas. 1 2 Quote Link to post Share on other sites
trahe 5 Posted Monday at 07:03 PM Share Posted Monday at 07:03 PM 11 minutes ago, brunoais said: Looks like something really screwed up your partitions... This is now beyond what I can think at the moment. I'm currently out of ideas. right something about the partitioning is my guess as well 1 Quote Link to post Share on other sites
trahe 5 Posted Thursday at 09:36 PM Share Posted Thursday at 09:36 PM so with a lot of help and custom made images from TheKit, now i got it running. Basically the persist of mine was corrupt. Some other device persist.img flashed and it worked! 2 Quote Link to post Share on other sites
phukfxtec 20 Posted yesterday at 12:13 AM Share Posted yesterday at 12:13 AM glad you were able to recover your device. On 9/2/2024 at 6:49 PM, trahe said: running the UBports installer do you select manual? ubports says "QX1050 is not recognized" for me Quote Link to post Share on other sites
EskeRahn 5,421 Posted yesterday at 04:55 AM Share Posted yesterday at 04:55 AM I wa under the impression that the persist partiton contained unique information so copying it would sort of making the two devices clones. Interesting if that is NOT the case as we could thus have one available somewhere. 2 Quote Link to post Share on other sites
trahe 5 Posted yesterday at 06:10 AM Share Posted yesterday at 06:10 AM (edited) 1 hour ago, EskeRahn said: I wa under the impression that the persist partiton contained unique information so copying it would sort of making the two devices clones. Interesting if that is NOT the case as we could thus have one available somewhere. i still did not figure out, so i am not sure if the e.g. phone works. (e.g. IMEI is not shown) So know we know, that the root of my problems was regarding to the corrupted persist but wifi and bluetooth works just fine... So the the keypoints for the fix: having some ~working~ persist i needed to the patched boot.img, which stops early and runs the telnet server, so i was able to format userdata into ext4 Edited yesterday at 06:14 AM by trahe 1 Quote Link to post Share on other sites
trahe 5 Posted yesterday at 06:12 AM Share Posted yesterday at 06:12 AM 5 hours ago, phukfxtec said: glad you were able to recover your device. do you select manual? ubports says "QX1050 is not recognized" for me As i installed UBTouch the first time, i think Pro1x was recognized. After some messup i needed to manual select, indeed: (QX 1050/Bengal i had shown mostly) Quote Link to post Share on other sites
Cizzlemob 0 Posted 20 hours ago Share Posted 20 hours ago Not sure if this is the place but I screwed up. I was trying to go from Lineage to stock Android and misunderstood the instructions. I thought that it said that you simply have to lock the boot loader by running fastboot flashing lock. However after running this the phone will only boot into into bootloader or lineage recovery it will not boot into an operating system. If you try to run fasboot flashing unlock is says command failed unauthorized or something along those lines. Is there a way to unlock without being able to enable developer options and usb debugging? 1 Quote Link to post Share on other sites
EskeRahn 5,421 Posted 17 hours ago Share Posted 17 hours ago 23 hours ago, trahe said: (e.g. IMEI is not shown) I think that is a crucial thing, that we as users can not easily set/change. IF it was easy to change it would make it too easy for thieves to give a phone a new identity. Quote Link to post Share on other sites
brunoais 333 Posted 15 hours ago Share Posted 15 hours ago 4 hours ago, Cizzlemob said: If you try to run fasboot flashing unlock is says command failed unauthorized or something along those lines. Is there a way to unlock without being able to enable developer options and usb debugging? Start with a backup of whatever you have now (in EDL mode, if needed). Try booting your phone into EDL mode then search these forums for more information. I don't know what works and what doesn't. If you can't solve it, make a new topic with your problem and what you tried. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.