I spent most of the day installing OmniROM, I d just finished and the phone froze, so I left it a few mins to sort its self out went back to it a few mins later and its in fastboot mode and it wont boot at all, went into recovery and the whole thing appears to have wiped itself - all data, vendor, cache, firmware, persist, system, cache, internal storage and the entire OS, nothing is installed, how can a phone just wipe itself ?!
I ve tried formatting, changing to another filesystem type and I just cant get anything to mount of flash any ROMS, I m stuck, never experienced this before, can anyone help.
Has my eMMC just died ?
typos1 said:
I spent most of the day installing OmniROM, I d just finished and the phone froze, so I left it a few mins to sort its self out went back to it a few mins later and its in fastboot mode and it wont boot at all, went into recovery and the whole thing appears to have wiped itself - all data, vendor, cache, firmware, persist, system, cache, internal storage and the entire OS, nothing is installed, how can a phone just wipe itself ?!
I ve tried formatting, changing to another filesystem type and I just cant get anything to mount of flash any ROMS, I m stuck, never experienced this before, can anyone help.
Has my eMMC just died ?
Click to expand...
Click to collapse
try qfil unbrick tutorial
eperu1220 said:
try qfil unbrick tutorial
Click to expand...
Click to collapse
I have, but its failed twice . . .
typos1 said:
I have, but its failed twice . . .
Click to expand...
Click to collapse
try plugging usb wire ports behind of your computer
and Both Flashone & lemax2qfil.zip needs to be in C drive
shyvam said:
try plugging usb wire ports behind of your computer
and Both Flashone & lemax2qfil.zip needs to be in C drive
Click to expand...
Click to collapse
Thanks, but it was a laptop so only have side usb ports.
And not mine either, I use Linux.
typos1 said:
Lol, it says "in the folder where you extracted the images" so I was doing it in the folder called "image", but its gotta be run from the main "LE_X820_STABLE_23S_VR20_FINAL_20171216" folder where the shell scripts are, stupid me.
It failed, heres the output :
Code:
target reported max download size of 536870912 bytes
sending 'boot' (55304 KB)...
OKAY [ 1.553s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.640s
target reported max download size of 536870912 bytes
sending 'splash' (72240 KB)...
OKAY [ 2.022s]
writing 'splash'...
FAILED (remote: flash write failure)
finished. total time: 2.100s
target reported max download size of 536870912 bytes
sending 'recovery' (61992 KB)...
OKAY [ 1.742s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.819s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.059s
target reported max download size of 536870912 bytes
sending 'cmnlib64' (250 KB)...
OKAY [ 0.040s]
writing 'cmnlib64'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'ddr' (1024 KB)...
OKAY [ 0.060s]
writing 'ddr'...
FAILED (remote: flash write failure)
finished. total time: 0.137s
target reported max download size of 536870912 bytes
sending 'cmnlib' (196 KB)...
OKAY [ 0.040s]
writing 'cmnlib'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'hyp' (257 KB)...
OKAY [ 0.040s]
writing 'hyp'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'pmic' (41 KB)...
OKAY [ 0.040s]
writing 'pmic'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'tz' (1596 KB)...
OKAY [ 0.080s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 0.157s
target reported max download size of 536870912 bytes
sending 'aboot' (774 KB)...
OKAY [ 0.060s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 0.137s
target reported max download size of 536870912 bytes
sending 'rpm' (224 KB)...
OKAY [ 0.040s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'devcfg' (39 KB)...
OKAY [ 0.040s]
writing 'devcfg'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'xbl' (1793 KB)...
OKAY [ 0.090s]
writing 'xbl'...
FAILED (remote: flash write failure)
finished. total time: 0.167s
target reported max download size of 536870912 bytes
sending 'keymaster' (220 KB)...
OKAY [ 0.040s]
writing 'keymaster'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'cmnlib64bak' (250 KB)...
OKAY [ 0.040s]
writing 'cmnlib64bak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'cmnlibbak' (196 KB)...
OKAY [ 0.040s]
writing 'cmnlibbak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'hypbak' (257 KB)...
OKAY [ 0.040s]
writing 'hypbak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'pmicbak' (41 KB)...
OKAY [ 0.040s]
writing 'pmicbak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'tzbak' (1596 KB)...
OKAY [ 0.080s]
writing 'tzbak'...
FAILED (remote: flash write failure)
finished. total time: 0.157s
target reported max download size of 536870912 bytes
sending 'abootbak' (774 KB)...
OKAY [ 0.060s]
writing 'abootbak'...
FAILED (remote: flash write failure)
finished. total time: 0.137s
target reported max download size of 536870912 bytes
sending 'rpmbak' (224 KB)...
OKAY [ 0.040s]
writing 'rpmbak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'xblbak' (1793 KB)...
OKAY [ 0.080s]
writing 'xblbak'...
FAILED (remote: flash write failure)
finished. total time: 0.157s
target reported max download size of 536870912 bytes
sending 'keymasterbak' (220 KB)...
OKAY [ 0.040s]
writing 'keymasterbak'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
target reported max download size of 536870912 bytes
sending 'modem' (83012 KB)...
OKAY [ 2.327s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 2.400s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.480s]
writing 'dsp'...
FAILED (remote: flash write failure)
finished. total time: 0.558s
target reported max download size of 536870912 bytes
sending 'bluetooth' (396 KB)...
OKAY [ 0.050s]
writing 'bluetooth'...
FAILED (remote: flash write failure)
finished. total time: 0.127s
target reported max download size of 536870912 bytes
sending 'devinfo' (0 KB)...
OKAY [ 0.040s]
writing 'devinfo'...
FAILED (remote: flash write failure)
finished. total time: 0.117s
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-xiZAoc: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
rebooting...
Click to expand...
Click to collapse
Hmm, maybe a different QFIL might work?
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
Since fastboot and TWRP seem to have zero chances of working? QFIL is your only hope tbh
ThE_MarD said:
Hmm, maybe a different QFIL might work?
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
Since fastboot and TWRP seem to have zero chances of working? QFIL is your only hope tbh
Click to expand...
Click to collapse
TWRP is long gone.
Thats the qfil guide I was using yesterday (well its flashOne).
I ve yet to try the actual qfil programme but I ve had to give the Windoze pc back, not sure I want to try it on my old XP laptop - its so slow and has already crashed several times, dont want it doing that in the middle of flashing.
typos1 said:
TWRP is long gone.
Thats the qfil guide I was using yesterday (well its flashOne).
I ve yet to try the actual qfil programme but I ve had to give the Windoze pc back, not sure I want to try it on my old XP laptop - its so slow and has already crashed several times, dont want it doing that in the middle of flashing.
Click to expand...
Click to collapse
Oh, what about the XDA thread version? I thought that's the one you tried? If not, then I highly recommend the XDA guide one as that is exactly what I used.
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
As I mentioned before, I'd recommend building a Windows 7 or 10 live USB boot drive or something like that, as I have no idea if WINE or VMWare would like the QDLoader 9008 mode driver.
ThE_MarD said:
Oh, what about the XDA thread version? I thought that's the one you tried? If not, then I highly recommend the XDA guide one as that is exactly what I used.
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
As I mentioned before, I'd recommend building a Windows 7 or 10 live USB boot drive or something like that, as I have no idea if WINE or VMWare would like the QDLoader 9008 mode driver.
Click to expand...
Click to collapse
The xda thread version is also oneflash, so its the same as the Gizmodochina one, unless you mean the ROM and its different ?
But I m not sure the ROM makes much difference if the device always fails flashing ?
Yes, VM or USBboot Windoze is the next step I guess.
Yeah I think the QFIL zip could be different since it worked for me with the XDA thread version.
ThE_MarD said:
Yeah I think the QFIL zip could be different since it worked for me with the XDA thread version.
Click to expand...
Click to collapse
Right, at this point 3 days in I m loosing track of which ROMs and qfils I ve been using !
Actually I can get into TWRP, but its useless, basically everything is 0mb, which points to eMMC issues I guess, although where is recovery written, somewhere different ?
I do have 4 logs from Oneflash, there are some bocks and lines it failed to write, but cant see how that would mean the entire eMMC is dead.
I was running AICP Oreo before I flashed omni, so it wasnt Treblised, I flashed your pie blogs TWRP and then Linage 16 to Treblise it, I wonder if it didnt work properly and thats whats caused this, or would a Treble ROM not boot at all ? I also didnt wipe the entire device, my data was still there, wonder if that caused it also.
AICP Oreo was treblized if the build was after August 24, 2018 as that is when it happened and AICP is based on LineageOS trees with their own tweaks on top.
Afaik? OmniROM Pie is also treblized unless for some reason andr68rus reverted that stuff?
All the treblize script does is renames the unused last_parti partition to vendor and then formats that partition and uses it as the vendor partition. We don't resize any partitions and we don't mess with the partition table.
ThE_MarD said:
AICP Oreo was treblized if the build was after August 24, 2018 as that is when it happened and AICP is based on LineageOS trees with their own tweaks on top.
Afaik? OmniROM Pie is also treblized unless for some reason andr68rus reverted that stuff?
All the treblize script does is renames the unused last_parti partition to vendor and then formats that partition and uses it as the vendor partition. We don't resize any partitions and we don't mess with the partition table.
Click to expand...
Click to collapse
Yes Omni is treblised.
I didnt read anything about AICP being treblised when I flashed it, in fact I didnt even think I used a treblised TWRP - it was at least 6 months ago, but I remember deciding not to treblise it cos it was AICP that I wanted to use and there was no mention of needing to treblise in the first post of the AICP thread, I also tried a few other non treble ROMS at the time.. Anyway, not really relevant if its deffo not a cause.
Would the logs be any help ?
Treble method for LineageOS and AICP which is based on our LOS trees is automatic. ROM installer checks for vendor partition and if it is not set up then it renames and formats it. :good:
Logs might help, but yeah I'd definitely recommend using that XDA guide steps and downloads plus a live boot of Windows 7 which should work for QFIL
ThE_MarD said:
Treble method for LineageOS and AICP which is based on our LOS trees is automatic. ROM installer checks for vendor partition and if it is not set up then it renames and formats it. :good:
Logs might help, but yeah I'd definitely recommend using that XDA guide steps and downloads plus a live boot of Windows 7 which should work for QFIL
Click to expand...
Click to collapse
The xda guide says the same as the Gizmodo China guide and links to the same version of ONEfash, it was the ROM from the xda guide I was using as the one linked to in the Gizmodo China guide kept failing to download, so with the possible exception of the ROM I dont think theres any difference.
But my device is rejecting it for some reason, in TWRP I ve seen some messages about "device full" and all the partitions show as 0Mb.
I ll try the later version of ONEflash and maybe actual qfil, but I m not holding out much hope theyll make any difference.
These are the last bits of the logs where errors occur :
Code:
2019-04-22 21:48:44 QfilFlashThread >>> 21:48:32: INFO: Current working dir (cwd): C:\Users\****\AppData\Roaming\Qualcomm\QFIL\
2019-04-22 21:48:44 QfilFlashThread >>> 21:48:32: INFO: Showing network mappings to allow debugging
2019-04-22 21:48:44 QfilFlashThread >>> 21:48:33: INFO: User wants to talk to port '\\.\COM24'
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: Took 0.00000000 seconds to open port
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: If you don't want this, use --dontsorttags
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: Sending <configure>
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: TARGET SAID: 'Calling hotplug_poll_device('UFS')'
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: TARGET SAID: 'Can't get size of partition '/hdev/ufs1h0' - hotplug_dev_get_size returned -1 (not 0)'
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: TARGET SAID: 'storage_device_open() returned FALSE'
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: TARGET SAID: 'ERROR 13: Line 1142: HANDLE_CONFIGURE_FAILURE'
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2019-04-22 21:48:45 QfilFlashThread >>> 21:48:33: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> Writing log to 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> Log is 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
2019-04-22 21:48:45 QfilFlashThread >>>
2019-04-22 21:48:45 QfilFlashThread >>> Download Fail:FireHose Fail FHLoader Fail:Process fail
2019-04-22 21:48:45 QfilFlashThread >>> Finish Download
2019-04-22 21:48:45 QfilFlashThread >>> Qfil Flash finished!
2019-04-22 21:48:45 QfilFlashThread >>> check if Qfil Flash failed!
2019-04-22 21:48:45 QfilFlashThread >>> Qfil Flash failed!
Code:
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: TARGET SAID: 'Calling hotplug_poll_device('UFS')'
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: TARGET SAID: 'Can't get size of partition '/hdev/ufs1h0' - hotplug_dev_get_size returned -1 (not 0)'
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: TARGET SAID: 'storage_device_open() returned FALSE'
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: TARGET SAID: 'ERROR 13: Line 1142: HANDLE_CONFIGURE_FAILURE'
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2019-04-22 23:52:37 QfilFlashThread >>> 23:52:37: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> Writing log to 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> Log is 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
2019-04-22 23:52:37 QfilFlashThread >>>
2019-04-22 23:52:37 QfilFlashThread >>> Download Fail:FireHose Fail FHLoader Fail:Process fail
2019-04-22 23:52:37 QfilFlashThread >>> Finish Download
2019-04-22 23:52:37 QfilFlashThread >>> Qfil Flash finished!
2019-04-22 23:52:37 QfilFlashThread >>> check if Qfil Flash failed!
2019-04-22 23:52:37 QfilFlashThread >>> Qfil Flash failed!
Code:
2019-04-23 00:33:44 QfilFlashThread >>> 00:33:43: INFO: TARGET SAID: 'storage_device_open() returned FALSE'
2019-04-23 00:33:44 QfilFlashThread >>>
2019-04-23 00:33:44 QfilFlashThread >>> 00:33:43: INFO: TARGET SAID: 'ERROR 13: Line 1142: HANDLE_CONFIGURE_FAILURE'
2019-04-23 00:33:44 QfilFlashThread >>> 00:33:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
2019-04-23 00:33:44 QfilFlashThread >>> 00:33:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2019-04-23 00:33:44 QfilFlashThread >>> 00:33:43: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2019-04-23 00:33:44 QfilFlashThread >>>
2019-04-23 00:33:44 QfilFlashThread >>> Writing log to 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
2019-04-23 00:33:44 QfilFlashThread >>>
2019-04-23 00:33:44 QfilFlashThread >>>
2019-04-23 00:33:44 QfilFlashThread >>> Log is 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
2019-04-23 00:33:44 QfilFlashThread >>>
2019-04-23 00:33:44 QfilFlashThread >>> Download Fail:FireHose Fail FHLoader Fail:Process fail
2019-04-23 00:33:44 QfilFlashThread >>> Finish Download
Code:
2019-04-23 01:08:56 QfilFlashThread >>> 01:08:56: INFO: TARGET SAID: 'ERROR 13: Line 1142: HANDLE_CONFIGURE_FAILURE'
2019-04-23 01:08:56 QfilFlashThread >>> 01:08:56: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
2019-04-23 01:08:56 QfilFlashThread >>> 01:08:56: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2019-04-23 01:08:56 QfilFlashThread >>> 01:08:56: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2019-04-23 01:08:56 QfilFlashThread >>>
2019-04-23 01:08:56 QfilFlashThread >>> Writing log to 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
2019-04-23 01:08:56 QfilFlashThread >>>
2019-04-23 01:08:56 QfilFlashThread >>>
2019-04-23 01:08:56 QfilFlashThread >>> Log is 'C:\Users\****\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
2019-04-23 01:08:56 QfilFlashThread >>>
2019-04-23 01:08:56 QfilFlashThread >>> Download Fail:FireHose Fail FHLoader Fail:Process fail
2019-04-23 01:08:56 QfilFlashThread >>> Finish Download
2019-04-23 01:08:56 QfilFlashThread >>> Qfil Flash finished!
2019-04-23 01:08:56 QfilFlashThread >>> check if Qfil Flash failed!
2019-04-23 01:08:56 QfilFlashThread >>> Qfil Flash failed!
I cant attach the full logs cos they re 1mb and xda only allows text files of 512kb, I can send them if they ll help and you dont mind looking.
ThE_MarD said:
Yeah I think the QFIL zip could be different since it worked for me with the XDA thread version.
Click to expand...
Click to collapse
Just checked and the qfil and ROM from the XDA thread and the Gizmodochina threads are the same. I guess your sdcard isnt broken as mine appears to be.
@ThE_MarD, I ve sort of got somewhere, sort of :
I cant get access to a Windoze pc to try Qfil on for a few days so was just trying random things and what I found was that whilst I cant flash another recovery with fastboot, I could boot a different recovery with fastboot, so I tried several, I was already on the latest TWRP, so I tried your Pieblobs one, the previous version and the 2 included in the dev ROM you gave me but I got the same errors I ve been getting for the last 5 days, although with Couco92's there seemed slightly less errors.
I found that I could get TWRP to successfully install a zip, only his "wipeOTA" zip, but it actually managed to install something, it seemed things were looking slightly better. So I attempted to flash that dev ROM with fastboot and there were no "Failed" errors in the terminal as each image was written, I just knew it was working and sure enough at the end flashing was successful ! . . .
. . . only it wont boot, it tries, but then boots to recovery instead, formatting and wiping give similar errors as before, but its only failing to mount storage and data, instead of storage, data, system and cache as it was previously, so there seems to be some improvement.
Any suggestions ? Was gonna try flashing a ROM from recovery next.
Ok, so I flashed Linage 16, but it wont boot, it goes straight to recovery, tries to format data then reboots to recovery, tries to format data, basically a recovery formatting data loop, nothing stops it apart from going into fastboot.
Somehow manaed to get it to stop the loop and boot into recovery, tried formatting again, still unable to mount data, still recovery loops no matter what I try, manage to turn it off, left it overnight.
Tried again in the morning with all the same problems, still cant mount data, I attempt formatting data again and suddenly it works, no error message !
Rebooted recovery, rebooted into Linage 16 !
Dont know why suddenly I could format data, but now I appear to have a working phone again, thanks for all the help, really thought the phone was dead.
Right, installed Omni Weekly build and getting a similar problems - when I try and flash the Omni Weekly builds, even if I wipe data, convinced the problem is something to do with those builds, gonna try the Homemade build again, would rather have the weeklies but need a working phone.
Heyyo, oh nice! Glad you got your storage working again!
Hmm, that is super crazy odd that OmniROM gives errors like that... Does any other ROMs do that?
Related
C:\Users\pig\Downloads\Compressed\VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml>fastboot flash preinstall preinstall.img
target reported max download size of 1056964608 bytes
sending 'preinstall' (622592 KB)...
OKAY [ 29.097s]
writing 'preinstall'...
(bootloader) image bigger than partition
FAILED (remote: )
finished. total time: 29.364s
C:\Users\pig\Downloads\Compressed\VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml>
when i try flash preinstall, it is result.
anyone can help me ? i appreciate all comment !
[IOON] OPT RESET & Recovery Tool
Hi everyone,
I have created a Recovery Tool for the OPT. IOON is a OPEN SOURCE Project this mean that everyone can share ideas and develop. However if you have ideas please share.
IOON should be the (NON OFFICAL) OFFICAL Recovery Tool. It fix software bricks, wifi issues, fingerprint, imeu, simcard & bluetooth. And new features will follow.
Please note I’m a human if I do something wrong please tell me
I want that IOON should be a community Project developed for the Community by the Community
Note:
For Windows and Linux
IOON recover the partitions over fastboot
Fastboot is required !
Warning
You do this on your one risk. I’m not responsible for any damage. I’m also not responsible:
If your alarm clock is not working and you gets fired.
If you phone will get overheat
If the phone don’t turn on.
Features
1) Erase everything
2) Back to stock
2.1) Oxygen 2.1
2.2) Oxgen 3.0
3) [Auto] custom Recovery
4) Auto root
IOON erase:
Cache
Userdata & Userdata_64
System
Modem
Modemst1
Modemst2
And More
Instructions:
1) Download and install fastboot
2) Download the ZIP file
3) Extract the ZIP file
$ sudo unzip restore.zip
4) Move in the folder
$ cd restore
5) Type:
sudo chmod +x restore.sh
sudo ./restore
[now a Menu should pop up]
Select Erase
Select back to stock
Select custom recovery (please select costum recovery if something goes wrong you have access to your phone & and file storage )
Download the newest oxygen version
Reboot into recovery [Press volume button down and power button at the same time]
Connect your phone with PC
Drag and Drop the oxygen version on your phone
Go to flash
Select oxygen version and click on flash
Click on change recovery
Reboot
Done!
Solves:
Fingerprint BUG ( 50 % changes ) [If it is a software Brick]
Fix IMEU BUG
Wifi and simcard and bluetooth should now work
Fix crashes after flashing a android 6 ROM
Bugs:
Downloads
Version 1.0 Deleted
Version 1.1 :Mod Edit link removed.
Version 1.2 Uploaded soon!
Source Code
https://github.com/deltaxflux/IOON
I now my English is bad :angel:
Wrong Link....
Updated !
Or try this one http://www.mediafire.com/download/1jf67jsvlm1thr5/restore.zip
Yes it's work ! Thanks
@deltaxflux Instructions are more from linux POV.. need commands for windows..
@s_vohra I will add the Instruction soon, let me work on the windows version
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
jukyO said:
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
Click to expand...
Click to collapse
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
jukyO said:
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
Click to expand...
Click to collapse
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
deltaxflux said:
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
Click to expand...
Click to collapse
used Erase option.
recovered all partitions except EFS (modemst1, modemst2) - mmcblkop17 and mmcblk0p18.
I have backed up EFS through TWRP recovery, but it does not contain modemst1 and modemst2, but 'oem_stanvbk', which is mmcblk0p20.
Do you have an idea? Can I recreate mmcblkop17 and mmcblk0p18 again?
How does restore of EFS works?
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Link to OOS 2.2.1? Some special version or any?
Sent from my A0001 using XDA-Developers mobile app
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Did that.
Output of tool:
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
Select your option
1) Back to stock
2) Root
3) Erase all
4) Custom recovery
5) Reboot
6) Exit
#> 1
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
erasing 'modem'...
OKAY [ 0.038s]
finished. total time: 0.038s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'apdp' (256 KB)...
OKAY [ 0.039s]
writing 'apdp'...
OKAY [ 0.024s]
finished. total time: 0.063s
target reported max download size of 536870912 bytes
sending 'bluetooth' (1024 KB)...
OKAY [ 0.057s]
writing 'bluetooth'...
OKAY [ 0.031s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'boot' (21165 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.179s]
finished. total time: 0.710s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.186s]
writing 'cache'...
OKAY [ 0.072s]
finished. total time: 0.280s
target reported max download size of 536870912 bytes
sending 'config' (512 KB)...
OKAY [ 0.048s]
writing 'config'...
OKAY [ 0.026s]
finished. total time: 0.074s
target reported max download size of 536870912 bytes
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
sending 'devinfo' (1 KB)...
OKAY [ 0.040s]
writing 'devinfo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'dpo' (1 KB)...
OKAY [ 0.040s]
writing 'dpo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'driver' (32768 KB)...
OKAY [ 0.800s]
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
sending 'fsc' (1 KB)...
OKAY [ 0.040s]
writing 'fsc'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'fsg' (1536 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.034s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.027s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'keystore' (512 KB)...
OKAY [ 0.048s]
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'limits' (1 KB)...
OKAY [ 0.040s]
writing 'limits'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'LOGO' (16384 KB)...
OKAY [ 0.409s]
writing 'LOGO'...
OKAY [ 0.144s]
finished. total time: 0.553s
target reported max download size of 536870912 bytes
sending 'misc' (1024 KB)...
OKAY [ 0.057s]
writing 'misc'...
OKAY [ 0.030s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'modem' (81920 KB)...
OKAY [ 1.983s]
writing 'modem'...
OKAY [ 0.626s]
finished. total time: 2.609s
target reported max download size of 536870912 bytes
sending 'msadp' (256 KB)...
OKAY [ 0.049s]
writing 'msadp'...
OKAY [ 0.026s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'oem_dycnvbk' (10240 KB)...
OKAY [ 0.268s]
writing 'oem_dycnvbk'...
OKAY [ 0.096s]
finished. total time: 0.364s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (10240 KB)...
OKAY [ 0.269s]
writing 'oem_stanvbk'...
OKAY [ 0.098s]
finished. total time: 0.368s
target reported max download size of 536870912 bytes
sending 'param' (1024 KB)...
OKAY [ 0.057s]
writing 'param'...
OKAY [ 0.035s]
finished. total time: 0.092s
target reported max download size of 536870912 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.800s]
writing 'persist'...
OKAY [ 0.261s]
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'reserve1' (8096 KB)...
OKAY [ 0.214s]
writing 'reserve1'...
OKAY [ 0.097s]
finished. total time: 0.311s
target reported max download size of 536870912 bytes
sending 'reserve2' (16192 KB)...
OKAY [ 0.410s]
writing 'reserve2'...
OKAY [ 0.138s]
finished. total time: 0.547s
target reported max download size of 536870912 bytes
sending 'rpm' (500 KB)...
OKAY [ 0.048s]
writing 'rpm'...
OKAY [ 0.027s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.232s]
finished. total time: 0.921s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
error: cannot load 'sdi.img': No such file or directory
target reported max download size of 536870912 bytes
sending 'sec' (128 KB)...
OKAY [ 0.039s]
writing 'sec'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending 'ssd' (8 KB)...
OKAY [ 0.040s]
writing 'ssd'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.223s]
sending 'userdata' (510526 KB)...
OKAY [ 12.347s]
writing 'userdata'...
OKAY [ 3.906s]
finished. total time: 16.477s
target reported max download size of 536870912 bytes
sending 'userdata_64' (515143 KB)...
OKAY [ 12.662s]
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
So those 5 failed:
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
After reboot to recovery, under wipe-advance wipe there is:
Dalvik
System
Data
Internal Storage
Cache
If I try to mount system, cannot do it.
Internal storage shows 9 Gb.
Do you have another ideas?
Thanks!
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
omrij said:
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
Click to expand...
Click to collapse
Did that 1st. Removed tampered bit before the procedure. No go.
Still
oem_nv_backup the nv partition is invalid
is shown.
Anyone knows how to check if modemst1 modemst2 blocks/partitions are created properly?
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
LOL9988 said:
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
Click to expand...
Click to collapse
It'll wipe everything, but I wouldn't use it because some of your partitions don't need to be wiped and some of the fastboot commands in the restore.sh file are wrong and will cause issues
For example:
sudo fastboot flash userdata userdata.img will flash the 16GB version's userdata.img even if you have a 64GB version of the phone.
sudo fastboot flash userdata_64 userdata_64G.img won't work because there is no userdata_64 partition - it's called userdata on both versions.
TBH, you're better off using advanced wipe in TWRP to wipe internal storage.
Waiting for the windows version to see if this app do the miracle fixing the second IMEI number on my phone, I tried everything already. Thanks for make this app.
Sent from my unknown using Tapatalk
iam newbie and want to try this solution to repair my fingerprint how to?
BEWARE, DO NOT SELECT ERASE OR IT WILL ERASE ALL YOUR MODEMS AND WONT BE ABLE TO GET THEM BACK. MY PHONE'S IMEIs ARE BROKEN. BOTH IMEI SHOW 0 AND CANNOT CONNECT MY PHONE TO ANY CELLPHONE COMPANY
hi guys i have honor 9 in error mode, i try to flash in fastboot but i have this error: C:\Users\Smart Genius\Desktop\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (41012 KB)...
OKAY [ 0.887s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.127s
i try with hisuite but the phone is not supported.
any one can help me? thanks
i can't find any solution in the forum
After several searches on the net, unlock the bootloader and to do
the ROOT this phone Huawei y 6 2018, but now they are stranded
in the installation of the Twrp recovery.
Fastboot gives me this error:
Code:
PS D:\Cellulare\adb-and-fastboot> fastboot flash recovery twrp-3.2.1-1.img
target reported max download size of 535822336 bytes
sending 'recovery' (14638 KB)...
OKAY [ 0.453s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.469s
PS D:\Cellulare\adb-and-fastboot>
How do I solve?
same probleme
Hi,
Can someone clarify what this message means and why fastboot is failing?
Thanks
Code:
# fastboot flash aboot aboot_300032.bin
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.038s
Probably because your phone has unlocked bootloader and needs to be locked .
Instruction how to do that .
https://www.google.rs/amp/s/www.theandroidsoul.com/relock-bootloader-fastboot-android/amp/
Good luck : )
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
greerdd said:
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
Click to expand...
Click to collapse
I have the same problem. Did u solve this ?
exact same problem, is there any solution exist?