Hello. My name is Poise, and I'm a victim of EFS Corruption.
I know, laugh it up.
Anyways, you're either here because you don't know what the EFS is and you wanna know, you ruined your EFS and you're looking for redemption, or you just wanna see me ramble. Whichever the case, I figured I'd write this so nobody else has to deal with the looming fear of your 300 dollar phone with infamously-bad customer support becoming a worthless, barely functioning phone, if not a big 300 dollar brick.
Before I go on, I wanna mention that this guide applies for most if not all phones, not necessarily just the OPO. So if anyone is losing their mind over a corrupted or lost EFS partition, this should get them on the right track to at least understanding the problem.
BACKGROUND: AKA "WHAT IS THE EFS AND WHY DO I EVEN CARE"
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and (in my case) your phone will just not wanna respond and reboot quite a lot.
CHAPTER 1: AKA "THAT SOUNDS LIKE GARBAGE HOW CAN I FIX THIS"
So, like all nice and important things that we have on Android, we can back this folder up, assuming you're rooted and with a custom recovery (though quite frankly if you're not rooted/installing ROMs I have zero idea how you'd corrupt your EFS). I'd recommend doing it through a nandroid backup (TWRP usually has the option to backup EFS, if not there's an unofficial version for bacon that can), but there are other apps that do the job quite nicely. Backing up your EFS is just as essential as backing up your previous ROM; in fact, backing up your EFS is MILES MORE ESSENTIAL because you can just flash a ROM over a corrupted system to get it working. There is no "flashable EFS"; if it were that easy, it wouldn't be so sensitive, and I wouldn't be writing this guide.
CHAPTER 2: AKA "I'M SUPER CAREFUL BRO I'LL NEVER MESS UP MY EFS PARTITION, WHY BOTHER"
Do it anyways.
I installed a ROM, realized my gapps package was screwed up, restored a CM13 backup, and realized my SIM card wasn't being detected. My phone would lag like hell, and after a while it'd just crash and reboot. I had no IMEI, I had no SIM card detection. I knew exactly what it meant. It wasn't fun to restore it.
If ROM installations were perfect, we wouldn't really have to backup anything. But, sometimes a hiccup will occur, something will touch something else that it shouldn't, and chaos ensues. So, if you don't wanna take 4 hours out of your day to hope to Christ that you didn't royally ruin your phone and the restoring method worked, just back it up. It's like, 3MB and it'll save so much frustration. Honestly.
CHAPTER 3: AKA "YEAH ABOUT THAT MY EFS IS ALREADY CORRUPTED, PLS HELP"
Congrats, you did it! Don't feel too bad, it happens to the best of us. :crying:
Fixing an EFS on the Oneplus One is pretty easy, but really time consuming and riveting because it might not 100% of the time work. You'll need the following:
Some sort of ADB/fastboot program. I use Minimal ADB and Fastboot, which rarely has any problems, but you can use whatever as long as it'll talk to your device.
Your near-dead Oneplus One.
A few hours of your time.
Some sort of backup of your data, you'll be factory resetting.
OxygenOS. Preferrably, a package that can be flashed in TWRP. I won't find that for you.
An unlocked bootloader. I cannot stress how important this is. If you don't know what this is, do some research before trying to fix your ruined EFS. Again, how you'd have even ruined it with a locked bootloader is beyond me...
TWRP 2.8.6.0. Yes, it has to be this version; this is the only one that can install firmware correctly. The unofficial modified 2.8.7.0 might be able to, but I'm not about to try it.
Competence and good reading skills. Do everything exactly as I wrote it.
Some knowledge on how flashing a ROM works.
A modified persist.img file that we'll be flashing. You can find it in this thread. Download the Never Settle package and take out the persist.img file; we don't care about the rest. Whether this is mandatory or not, I don't know, but I used it and it worked fine so I'll include it. If anyone tries this without the persist file and it works, let me know. Thanks a ton to markbensze for making this, he saved my skin.
Now for how it's done:
To start, we gotta put your phone into fastboot mode. Do this by holding the power button and the up volume button as you're turning your phone on. You'll know it worked when the phone very dimly says "Fastboot Mode".
Plug your phone into your computer. Let it do any driver stuff it has to, then open your ADB/Fastboot program. Type "fastboot devices", if you see a bunch of letters/numbers with the word "fastboot" a few spaces away, you're set.
Seriously, if your bootloader isn't unlocked, you gotta do that. This will wipe EVERTHING from your phone, including any backups. I won't cover that mess, there's trillions of guides for that.
Type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
This erases a bunch of partitions that have to do with the EFS. They all regenerate themselves, but as an added precaution we're gonna flash that persist.img you got from the thread in the "what you need" list. In order to do this, enter the following command:
Code:
fastboot flash persist [location to your persist.img on your computer]
If all goes well, you'll get a handy success message and you can get out of fastboot mode by holding down the power button until it turns off.
Now, reboot to recovery; do this by holding the power button and holding the down volume button as you turn your phone on, until you see the TWRP splash screen.
How you do this next step is up to you; you can use the built-in MTP to transfer the Oxygen OS file over from your computer to your phone, or you can use ADB sideload. If you don't know how sideload works, just transfer it over.
Factory reset as you would installing a normal ROM, and flash Oxygen OS through the install menu/sideload/however you wanna. Let it fully install.
Reboot. Let it boot, pray to the EFS gods that they'll give you their blessing, and check if your SIM card gets detected.
If it did, congradulations! Your EFS is working. Now, go make a backup while you can.
Very glad that you made a guide about it. I didn't f*** up my phone though, but I truly got the importance of backing up the EFS. Also, got to know about it a bit more.
Thanks!
I have a feeling this is going to come in handy with my project OPO... good stuff man thanks
It worked. After I did this I kept getting boot Loops what was progress on this phone. I did the factory reset in recovery. Let it bootloop some more. Went back to recovery and fixed selinux permissions. Boot Loops again, went back to recovery wipe the dalvik. now it freaking works.
First off, great guide.
But after following this, despite having my IMEI shown previously, my baseband and my imei are now gone. I was told to use this guide to try and fix my data connection problems as it seemed something was wrong with my EFS partition, but it seems following this has left me worse off.
Any suggestions to what else I could do?
Is there a stock oxygen OS file kicking around somewhere? I tried searching for them, but most are modified by other people. One of them hardbricked my phone (the ported Oneplus X oxygen os), so I'd rather not further experiment with other modified ones. I used another OxygenOs file, but despite booting, it didn't fix the baseband or IMEI problem.
I tried doing this but using stock CM13.1.2 instead of OxygenOS, but it didn't fix the problem either. So any other suggestions?
Edit: Nvm, found the official from the OnePlus website, I'm an idiot, going to try doing this with Oxygen to see what happens.
FAILED (remote: Partition flashing is not allowed)
OnePlus 3t with TWRP BlueSpark 3.2.1 recovery.
I am open to flash Roms with TWRP with no problem but I am not able to flash persist.zip (TWRP version) it says it flash but folder doesn't appear and your instructions via fast boot I get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash persist c:\android\persist.zip
target reported max download size of 435159040 bytes
sending 'persist' (344 KB)...
OKAY [ 0.036s]
writing 'persist'...
FAILED (remote: Partition flashing is not allowed) <------ Problem here or or is my partition on my phone messed up?
finished. total time: 0.057s
I any suggestions for fixing my WiFi/Bluetooth problem?
Fastboot commands not working, ADB way of doing it?
PlayingPoise said:
Hello. My name is Poise, and I'm a victim of EFS Corruption.
I know, laugh it up.
Anyways, you're either here because you don't know what the EFS is and you wanna know, you ruined your EFS and you're looking for redemption, or you just wanna see me ramble. Whichever the case, I figured I'd write this so nobody else has to deal with the looming fear of your 300 dollar phone with infamously-bad customer support becoming a worthless, barely functioning phone, if not a big 300 dollar brick.
Before I go on, I wanna mention that this guide applies for most if not all phones, not necessarily just the OPO. So if anyone is losing their mind over a corrupted or lost EFS partition, this should get them on the right track to at least understanding the problem.
BACKGROUND: AKA "WHAT IS THE EFS AND WHY DO I EVEN CARE"
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and (in my case) your phone will just not wanna respond and reboot quite a lot.
CHAPTER 1: AKA "THAT SOUNDS LIKE GARBAGE HOW CAN I FIX THIS"
So, like all nice and important things that we have on Android, we can back this folder up, assuming you're rooted and with a custom recovery (though quite frankly if you're not rooted/installing ROMs I have zero idea how you'd corrupt your EFS). I'd recommend doing it through a nandroid backup (TWRP usually has the option to backup EFS, if not there's an unofficial version for bacon that can), but there are other apps that do the job quite nicely. Backing up your EFS is just as essential as backing up your previous ROM; in fact, backing up your EFS is MILES MORE ESSENTIAL because you can just flash a ROM over a corrupted system to get it working. There is no "flashable EFS"; if it were that easy, it wouldn't be so sensitive, and I wouldn't be writing this guide.
CHAPTER 2: AKA "I'M SUPER CAREFUL BRO I'LL NEVER MESS UP MY EFS PARTITION, WHY BOTHER"
Do it anyways.
I installed a ROM, realized my gapps package was screwed up, restored a CM13 backup, and realized my SIM card wasn't being detected. My phone would lag like hell, and after a while it'd just crash and reboot. I had no IMEI, I had no SIM card detection. I knew exactly what it meant. It wasn't fun to restore it.
If ROM installations were perfect, we wouldn't really have to backup anything. But, sometimes a hiccup will occur, something will touch something else that it shouldn't, and chaos ensues. So, if you don't wanna take 4 hours out of your day to hope to Christ that you didn't royally ruin your phone and the restoring method worked, just back it up. It's like, 3MB and it'll save so much frustration. Honestly.
CHAPTER 3: AKA "YEAH ABOUT THAT MY EFS IS ALREADY CORRUPTED, PLS HELP"
Congrats, you did it! Don't feel too bad, it happens to the best of us. :crying:
Fixing an EFS on the Oneplus One is pretty easy, but really time consuming and riveting because it might not 100% of the time work. You'll need the following:
Some sort of ADB/fastboot program. I use Minimal ADB and Fastboot, which rarely has any problems, but you can use whatever as long as it'll talk to your device.
Your near-dead Oneplus One.
A few hours of your time.
Some sort of backup of your data, you'll be factory resetting.
OxygenOS. Preferrably, a package that can be flashed in TWRP. I won't find that for you.
An unlocked bootloader. I cannot stress how important this is. If you don't know what this is, do some research before trying to fix your ruined EFS. Again, how you'd have even ruined it with a locked bootloader is beyond me...
TWRP 2.8.6.0. Yes, it has to be this version; this is the only one that can install firmware correctly. The unofficial modified 2.8.7.0 might be able to, but I'm not about to try it.
Competence and good reading skills. Do everything exactly as I wrote it.
Some knowledge on how flashing a ROM works.
A modified persist.img file that we'll be flashing. You can find it in this thread. Download the Never Settle package and take out the persist.img file; we don't care about the rest. Whether this is mandatory or not, I don't know, but I used it and it worked fine so I'll include it. If anyone tries this without the persist file and it works, let me know. Thanks a ton to markbensze for making this, he saved my skin.
Now for how it's done:
To start, we gotta put your phone into fastboot mode. Do this by holding the power button and the up volume button as you're turning your phone on. You'll know it worked when the phone very dimly says "Fastboot Mode".
Plug your phone into your computer. Let it do any driver stuff it has to, then open your ADB/Fastboot program. Type "fastboot devices", if you see a bunch of letters/numbers with the word "fastboot" a few spaces away, you're set.
Seriously, if your bootloader isn't unlocked, you gotta do that. This will wipe EVERTHING from your phone, including any backups. I won't cover that mess, there's trillions of guides for that.
Type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
This erases a bunch of partitions that have to do with the EFS. They all regenerate themselves, but as an added precaution we're gonna flash that persist.img you got from the thread in the "what you need" list. In order to do this, enter the following command:
Code:
fastboot flash persist [location to your persist.img on your computer]
If all goes well, you'll get a handy success message and you can get out of fastboot mode by holding down the power button until it turns off.
Now, reboot to recovery; do this by holding the power button and holding the down volume button as you turn your phone on, until you see the TWRP splash screen.
How you do this next step is up to you; you can use the built-in MTP to transfer the Oxygen OS file over from your computer to your phone, or you can use ADB sideload. If you don't know how sideload works, just transfer it over.
Factory reset as you would installing a normal ROM, and flash Oxygen OS through the install menu/sideload/however you wanna. Let it fully install.
Reboot. Let it boot, pray to the EFS gods that they'll give you their blessing, and check if your SIM card gets detected.
If it did, congradulations! Your EFS is working. Now, go make a backup while you can.
Click to expand...
Click to collapse
Is there a way to replicate your 3 fastboot commands, using ADB? My bootloader is unlocked and running the latest TWRP recovery 3.2.2
My results via fastboot
"
fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.024s
"
I have a Samsung Galaxy Note 2 phone with a broken logic board. I need to replace, but I may need to change the IMEI of the replacement board with my old phone's IMEI if I buy the replacement board from China.
Does the IMEI number pass to the other phone if I restore my Twrp backup which contains all partitions (more specifically the EFS partition), over this motherboard? Does it solve my problem.
Any chance to get an upload of the file needed??
Same EFS partition over time ? after updating Android ?
Thx a lot, this has saved me a lot of troubles ^^
Was just wondering, is the EFS partition always the same over time ? modemst1 & modemst2 files are the same for all Android/OxygenOS version ?
I've backed up mine under OxygenOS 3.2.8 and I was wondering if i could still use it to restore the EFS partition if anything goes wrong ?
PS : Sorry for my bad english, it's not my native language ^^
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
crenshaw1979 said:
Is there a way to replicate your 3 fastboot commands, using ADB? My bootloader is unlocked and running the latest TWRP recovery 3.2.2
My results via fastboot
"
fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.024s
"
Click to expand...
Click to collapse
You can find how to do it on this thread : https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
EFS / Modem backup option gone?
hey there :]
I want to backup my phone. In TWRP I had the option to backup EFS and modem partitions. I decided to upgrade TWRP, since my version (3.2.x) was older than the most recent (3.4). After flashing the .img from inside TWRP, everything function as expected... however, the option to backup EFS and Modem is gone.
I downgraded to older version of TWRP, but TWRP still does not show the option for EFS and modem backups.
recovery.log, that was created when I made the TWRP backup lists "Unable to locate '/modem_st1' partition for backup calculations."
What did I do wrong? Does bacon require some extra step to unlock EFS and modem access for TWRP?
Does this method work with lgv60 snapdragon 865 unlocked bootloader ?
Whenever I get a new device , on day number one I always backup my efs partitions.. I use termux app from my device and type:
su (push enter)
Then I type these in one by one in termux and grab the two files off my device's sdcard and upload them to a cloud and transfer them both to my PC and/or a thumb drive.
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
(push enter)
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
(enter)
If ever I lose my IMEI these can be fastboot flashed back and restored that way. This info I first came across over on Funk Wizard's XDA guide thread for OnePlus 6t. Works great. Only thing is now I'm a retired crack flasher so my days/years of installing everything available for my device are most definitely over and that's how I always lost mine back in the Nexus days... During an installation of only God knows what back then. Still much better to be safe than sorry and have an expensive paper weight for a phone if ever something does happen.
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
fronzee88 said:
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
Click to expand...
Click to collapse
In twrp go to mount and make sure system is mounted, then try rebooting
Sent from my LG-H910 using XDA Labs
cnjax said:
In twrp go to mount and make sure system is mounted, then try rebooting
Click to expand...
Click to collapse
It still boots into TWRP.
fronzee88 said:
It still boots into TWRP.
Click to expand...
Click to collapse
Did you try restoring a back up
Sent from my LG-H910 using XDA Labs
cnjax said:
Did you try restoring a back up
Click to expand...
Click to collapse
I made a backup with TWRP before attempting the original update that caused this issue, but I am doubting the integrity of that backup, because I was not able to decrypt the "data" partition before making the backup. So I backed up the data partition in the encrypted state, but I am not sure if that is restorable or not. Instead, I just tried reflashing the ROM.
When I navigated to the TWRP backups folder where the backup was supposed to have been saved, I couldn't find the (most recent) backup, so I am not sure if I can actually restore anything, should the need arise.
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Click to expand...
Click to collapse
I wasn't able to get connect with my laptop from adb (unauthorized message) but I did enter the dd command in a terminal directly in twrp itself (Advanced > Terminal). It worked!!! Thank you, thank you, thank you! Whew.
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
-- Brian
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
Good to know. Thanks!
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
I'm having trouble finding the latest official TWRP download for LG V20 T-Mobile (H918). The device isn't listed on their official site. Any suggestions on how to upgrade?
TWRP 3.2: https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
-- Brian
runningnak3d said:
if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
Click to expand...
Click to collapse
I'm not sure what you mean by "download" mode, but my other question is: Will flashing a KDZ cause me to lose all my data? If so, how can I make a backup of all my data if the "data" partition is encrypted? I can't get TWRP to decrypt it even when entering the correct PIN that I normally use to unlock my encrypted phone upon regular bootup.
Note that Titanium Backup is not an option if I'm planning to unroot my phone.
Yes, flashing a KDZ wipes your phone.
If your data partition is encrypted, the only way to backup your data is from within the OS (copy to SD card) or use LG backup.
Btw the reason you arnt able to get into recovery via the buttons is because you were doing it wrong, its not hold power and volume down, its actually hold volume down, press power until the screen turns on, then (still holding vol down) tap the power button (either once at exactly the right time, or repeatedly which works more consistantly) until a screen appears asking if you want to factory reset. saying yes (via the volume and power buttons) twice boots twrp if installed, else it boots the stock recovery and wipes the phone.
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
Click to expand...
Click to collapse
The same thing happened to me but on my V10. Would this command work on that phone?
So I screwed up. When wiping my system for lineageos, I accidentally wiped everything, including the system, internal storage, and data. I am in TWRP right now. Trying to send files over at MTP just makes the progress bar not move. I cannot move it over with my phone mounted as a usb storage device. When using adb push to send over a ROM, the command completes, but it does not appear in the sdcard folder as I specified. Adb sideload just stops at 50%, with the phone displaying step 2/2 and not continuing after that- I have the option to reboot or wipe dalvik / cache. I have no OS. I know that rebooting into TWRP again will make MTP work, however as I have no OS installed I know that I will not be able to access fastboot. Any ideas on how to get a rom onto my phone's storage?
You might need to format your internal storage as it may still be encrypted which may be why files aren't copying across. This is just a guess though. If all else fails (I have been in a similar situation before), you should be able to boot into fastboot (bootloader) mode from TWRP and flash OOS back through that. You would need to find the fastboot version of the ROM. I believe there is a thread in this forum somewhere. A last resort would be using the MSMTool to get back to stock. I've never had to do this myself though. The phone will be in a like brand new state though, so you would need to unlock the bootloader again if you are going to flash a custom ROM or do any modding after.
You can use OTG storage, encryption has no effect on it and you can flash files too. I used it to bypass the encryption issue in TWRP. If that doesn't work then post #2 is your best option. Also you can still boot in fastboot even if your ROM is broken. You can find the fastboot ROMs in the guide section.
I tried a while back to flash TWRP I believe, but ended up with this message (see pic 1) and now when I try to enter recovery I get the message in pic 2. Also, It looks I can't enter download mode.
Any help would be much appreciated, I have been trying to get this tablet back up and running for a while now!
Thanks as always for all the help!
Same here, ive been trying to fix this thing for a few years to no avail. Honestly i should just throw the thing away but im determined to fix this thing. No download mode or recovery mode. fastboot seems to be the only option here but that also seems to fail.
If we can somehow get this thing into download mode, this would probably work.
https://www.reddit.com/r/LGgpad7/comments/6f5tt1
It's very complex but it's possible, its similar method to what's in this post https://forum.xda-developers.com/t/qd-9008-fix-tested-on-lg-v410-g-pad-7-0-us-att.3269057/
Thought I think there was a original post about this method which was more detailed,
Anyways I broke bootloader partition before and I managed to fix it in similar way without access to download and fastboot like in the guide.
What I did was install the whole system (partition with GPT and install every single partition including system on the SD card) but my tablet was still not booting from SD card, I somehow managed to get it turning off the SD card with a special QD 9008 cable, I can't find one online now will update if I do, then when it turned I somehow managed to root it (but again not sure how as it requires download mode, I could've done it via kingoroot or by injecting root into the system partition manually and then flashing it onto the SD card) and when you have root you can use terminal emulator or ADB shell to flash corrupted partition on your tablet with DD command, after it should turn on though I recommend reflashing it with flashtool after