I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....
Related
Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
The CD key ought to come from flash ROM, but it depends on how the recovery image works, which I don't know >.<
If you can use his recovery image to boot to command prompt, you can mount your SSD's registry hive and dump the product key data, then decode it on a Windows PC. Then after recovering with the image, even if the product key ended up copying your colleague's Surface's key, you could just go to System and click "Change product key" and type your own key. (In this situation, the desktop will likely be black, a sign that Windows was unable to activate. Changing the key to yours will fix that, of course.)
I'm not saying that this is easy or anything, but this ought to work, with my understanding of Windows NT.
Note that you don't need to bother decoding the registry data if you notice after recovering that your product ID in System is different than your colleague's, and it also says that Windows is activated. This would mean that the recovery image grabbed your CD key out of flash ROM.
EDIT: I guess what I meant to say is that when you boot to command prompt, run regedit. In regedit, go to HKEY_LOCAL_MACHINE then File/Load Hive. Find your system hive on your SSD, which may be on a different drive letter than usual, in somewhere like Z:\Windows\System32\config\SYSTEM. Give it some name like "meow". Find the subkey meow\SOFTWARE\Microsoft\Windows NT\CurrentVersion. Go to File/Export and export that to a .reg file on your USB stick. If there is an option to do so non-recursively (I forget, and I'm on my iPad), use it because that key is big. Once you've backed it up, you're safe to recover, because now you have everything needed to find out your old key if required.
If in fact you do need to use that .reg file to determine your old key, let me know so I can help you out. Some tricks will be required to proceed.
Melissa
munsterrr said:
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
Click to expand...
Click to collapse
If you recover using an 8.1 recovery image form somebody else it won't mess with the keys. Worst case is that you may have to activate and you do not have a key. If you look at this post by Osprey you will see how to get the key from a 8.0 installation. That won't help you of course unless you have access to the registry and hive as Melissa suggested.
I actually recommend you use an 8.0 image to recover your RT and then upgrade. The only thing you have to do is get the image and "burn" it to a thumb drive. There are no steps required to obtain your key. Make a bootable thumb drive with an image you can download from here and start from scratch. Your system will automatically activate going this route. I've done this several times to switch between Preview 8.1 and 8.0. Follow the instructions above from Osprey's post to obtain your key just in case you do need it sometime in the future. Then you upgrade to 8.1 (nothing necessary in terms of activating this way).
Here is a post with a link on how to recover with a USB recovery image. One important point when you put the image onto the thumb drive is that it has to be bootable. Use UltraIso or Rufus to put the image onto the thumb drive (FAT32 formatted).
munsterrr said:
Any ideas/direction/thoughts AT ALL are greatly appreciated.
Click to expand...
Click to collapse
Apparently this is a widespread problem, and one of the reasons I haven't upgraded to 8.1. Heres the solution: http://kickthatcomputer.wordpress.com/2013/10/19/windows-rt-8-1-upgrade-fails-with-boot-configuration-error/
Thanks for the replies everyone. My colleague was able to upgrade to 8.1 on his RT with no problems. We were able to copy the image(minus recovery partition) over to a thumb drive and I was able to boot from that and eventually upgrade myself.
Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!
Good morning, afternoon or evening depending on where you are reading me from. As the title says, it seems that my LG G8 Verizon has become a paperweight since it remains in a recovery loop. My LG G8 has the bootloader unlocked with Firehose and QFIL (https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/), I followed the guide (https://forum.xda-developers.com/t/...wos-12-1-for-lg-g8-alphaplus-alphalm.4354847/) months ago to install the Arrow OS rom and everything worked correctly.
Now the matter in question, days before this week most of my accounts were tried to be violated by a hacker, I don't know where I could have caught the ware but it's done already. Today after several hours in front of the laptop I moved all my accounts, changed passwords and started with one and only gmail and outlook account. To finish everything I decided to factory reset my device, everything seemed to be going well until I saw that it started in the recovery and not in the typical screen after a factory reset. I have little experience in flashing custom roms, the previous times I've flashed everything went as it should and I lived without any problem so right now I don't know what to do.
Every time I enter recovery I get a message on the bottom log saying
"E:failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
When I try to make a factory reset from the recovery it says
"Wiping data...
Formatting /data...
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/userdata
Success
Formatting /metadata
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata
Success
Data wipe failed.
E: failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
I really don't know what the problem could be, I already tried to use LGUP to try to go back to my original rom but it stops at 4% and the executable closes. Days before, I deactivated the developer options since it was a requirement of the Malwarebytes app and I know that it is partly my fault for not having activated it again. I can go into download mode by pressing volume up but to the best of my knowledge without debugging and oem unlocked I can't do much. [Edit: Reading the firehose and qfil guide hours later I discovered that the Verizon variant doesn't mention as necessary to turn the oem unlock so maybe a little hope?]
If it helps, I still have the backups of sysnand_00.bin, essential.exefs and some others I made before unlocking the bootloader with firehose and qfil, as well as a zip called "Arrow36backup1647621938922" with a .bak named "launcher_backup_main".
Right now I have no way to upload images of the recovery log that is in the advanced settings of the arrow recovery, I will try to do it later but notice that it is quite long.
I sincerely hope that someone has the slightest idea that it could be happening and I will gladly read it and appreciate your time for giving me a hand.
At the end of it all it wasn't that hard to solve my problem, it was just that I was afraid of messing it up even more.
After rereading the guides that I had followed months ago and also the various comments, I came to the conclusion that LGUP could solve it, only that I had done it wrong before. It was thanks to this thread that I was able to download a better version of the tool (https://forum.xda-developers.com/t/lgup-1-16-3-patched-found-and-works-with-lg-wing.4357211/) and after following the instructions everything was like new on my device.
If someone else is going through the same problem as me, you can write to me and I will help you with what worked for me.