Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs
Related
First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Sent from my Nexus 7 using xda app-developers app
If your ROM is rooted, you can flash the recovery partition from a root shell using the "dd" command.
That is, from a terminal emulator:
$ su
# cd /sdcard
# dd bs=4096 if=name-of-recovery-image-file.img of=/dev/block/mmcblk0p1
good luck. I didn't understand everything you said in your post, but I got the part about the dog
buckwheat_shawt said:
First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Click to expand...
Click to collapse
Are you still unlocked and rooted after the update to 4.2.2 ?
If not you must unlock and root your N7 again, but be careful, All root tools doesn't work for 4.2.2. and are not updated for 4.2.2
I unlocked my N7 normally, but I used CF auto-root (update) and now I'm unlocked and rooted with DirtyBox rom.
Thanks a lot. This will be my first time using the terminal emulator, should be a good learning experience
Sent from my Nexus 7 using xda app-developers app
I'm still unlocked and rooted. I just can't access my recovery after the update. This happened once with CWM on my GNex but I still had the oem usb so I just flashed it again with my computer. I don't have an oem usb for my N7. Btw, I was using twrp on the N7.
Sent from my Nexus 7 using xda app-developers app
buckwheat_shawt said:
I just can't access my recovery after the update.
Click to expand...
Click to collapse
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.
buckwheat_shawt said:
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.
Click to expand...
Click to collapse
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.
bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
bftb0 said:
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.
Click to expand...
Click to collapse
You're right I wasn't. I just found out and I've rooted and installed my recovery. Thanks alot though, probably wouldn't have figured it out without you all. First time having to make a post to solve an issue. Thanks again! :victory:
I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?
I had a similar issue a couple days ago, problem I think was due to TWRP not having "RT -RM" (? - sorry I'm not looking at the exact text right now or have it memorized) option checked in Settings in TWRP, or possibly due to issue of older TWRP version, .2 and the newer .3 works better. My System directory was unmounted and couldn't come back, stuck in boot-loop until I followed the revert-to-stock directions. I had to download the 2 gig file, taking about 2 hours, and it contained readme.txt w/ instructions and all files needed to revert, but it was very tricky. A .DLL must be overwritten in Windows to get the LG firmware flashing software to work right, and you need the .TOT file. It will work if you are diligent, so don't give up hope. I thought my bada$$ new phone was bricked but finally got it to flash back to stock using that method, possibly similar to the quote in this thread, http://forum.xda-developers.com/showpost.php?p=48434571&postcount=1150, using Verizon instructions / sprint files. You can get it back. Mod will probably lock this thread as it is not development so follow that post I just linked, along with the OP. I am in Windows 8.1 x64 so I think it can work on any version of Windows.
Oh and this thread should probably get locked as it shouldn't go in dev section, mod will probably move or lock it. Hope you figured it out.
Sent from my LG-LS980 using Tapatalk
Thread Moved as it does not belong in the Development Section.
What I did ti fix diwnload mode
I took the rom I last flashed. Opened it. went to the system folder and extracted the build.prop (opened it with notepad). Press the find button in one of the drop down menus and find the model number your g2 thinks it is and change it to what it actually is.( in my cause mines had a d801 rom so it thought was one instead of an ls980) I changed mine from d801 to ls980. Saved it (make sure its saved as build.prop). Now go into the rom you originally got the build.prop from and replace it with the new one adb push the rom to the phone in twrp then flash it. Then boot into download mode and flash away
viper42391 said:
I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?
Click to expand...
Click to collapse
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
NBreunig3 said:
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much! Work great!
I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?
Mortred said:
I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?
Click to expand...
Click to collapse
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.
vPro97 said:
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.
Click to expand...
Click to collapse
Yeah that is exactly what i did (used ioroot25, and the autorec app is amazing!!), but since i didnt have anything installed on my pc i had to download everything from scratch
and a simple 20 min process became a multiple hours one (trying to avoid that in the future).
anyway i've got the cloudy ROM now and it seems that it is already unlocked so i got that going for me which is nice .
Hi,
I have an LG G2 D802 and already installed TWRP 2.6.3.4 for installing zip-files. But now there is an update (only browser, but 4.4 shouldn't be that far away), but without stock recovery it's impossible to install it I know the way how to get back to stock completely, but I don't want to go back to stock every time there is an update, installing all of them and then reinstall TWRP. I think on CWM the problem is the same, but i don't want to miss the camera tweak and splitwindow, so I need an custom recovery for the zip-files:crying: Is there any way to get the stock recovery back without installing complete stock or at least a possibility, to only "boot" the custom recovery when I'm back on stock, like on Nexus devices, and only use it for the flashing and then lose it on the next reboot?
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
simon_lefisch said:
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
most likely, but cannot confirm it, you ooen a stock kdz, and try flashing the kernel .img thats inside, I am not sure
anyone confirm it works that way
Sent from my LG-D802 using xda app-developers app
for all I know, the kernel doesn't contain any recovery... but I will test it tomorrow, when I downloaded the kdz if you could say me how to open a kdz-file.
Artim_96 said:
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
Click to expand...
Click to collapse
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
simon_lefisch said:
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
Click to expand...
Click to collapse
If it's not working, I have a backup of the current. but I will test it tomorrow, then I have more time. But thanks for the quick answers.
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Artim_96 said:
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Click to expand...
Click to collapse
I've had similar problem, i think I just installed the KDZ file trough the way they showing: http://forum.xda-developers.com/showthread.php?t=2432476
It just erased the rooy and TWRP, and all of the apps and settings did not change, its like a repach.
at least it should be. but I can't take the last step. "By turning off, Holding down power and Vol Down until it comes up on the screen." doesn't works, there only starts the normal software, and that's the old one. And unpacking the kdz file with 7zip or Peazip also don't work. Peazip can do ist, but I have to find out how to let it extract it. After installing it, there is another file with the same name, but it's an .cab file with password. If I boot over widgetsoid into recovery (I think this is what the manual means) there is only a little droid with a read sign. How to get further?
EDIT: found out how to come into that menu. It wants to make a hard reset so I make an backup first.
Finally I was able to install the complete new software version (D80210e-EUR-XX) over the LG PC Suite. The file downloaded from the manual seemed to be corrupted or so as it only caused an unpacking error in the programm.
Does anybody knows a way how to flash a zip without a custom rom? Flash Gordon seems to not work.
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
shaggy9585 said:
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
Click to expand...
Click to collapse
we need a story, for starters what did you do/happened before you got into fastboot?
XxZombiePikachu said:
we need a story, for starters what did you do/happened before you got into fastboot?
Click to expand...
Click to collapse
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
shaggy9585 said:
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
Click to expand...
Click to collapse
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
XxZombiePikachu said:
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
Click to expand...
Click to collapse
is there a way to flash a rom using adb while in twrp or fastboot?
shaggy9585 said:
is there a way to flash a rom using adb while in twrp or fastboot?
Click to expand...
Click to collapse
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
XxZombiePikachu said:
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
Click to expand...
Click to collapse
now i just need to figure out whats going on with the touch sensor. idk if its the phone or just twrp
I posted this in the original DEV discussion and I also posted it as a reply to some people with the question. I'm only making this thread to save people from searching through hundreds and hundreds of posts. As you may know there is no kdz or tot for the v410 gpad. Without any clue as to why I woke up and my v410 was in twrp, tried a restore, a wipe, installing custom roms, each time it would say it was successful yet each time it would just boot right back into TWRP. Then i stumbled across a thread made by "Thecubed" in 2013 that had nothing to do with this device, it was a thread about being stuck in TWRP after OTA, so I thought id give it a shot and it worked like a charm 8) here are my instructions
1. if you dont have adb setup adb you can get a minimal adb here
https://www.androidfilehost.com/?fid=385035244224386526
install it, navigate to program files (Or if your on a 64bit system program files(x86)
Right click and click "Open command window here"
2. plug in your device if it isnt already pluged in, and type the following commands pressing ENTER after each line
DO NOT COPY PASTE THE WHOLE THING EACH LINE MUST BE PRESSED ENTERED separately
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
exit
adb reboot
Your phone should boot into your rom now
You can hit thanks for my effort of days of searching and you can also thank the dev of the thread that I got these instructions from "thecubed" here at this link http://forum.xda-developers.com/show....php?t=2451696 Hope this helps someone
Saved my ass tonight! Thanks bud!!
I'm stuck in your boat as well, only booting to twrp. The google docs link dead... but I was able to find the minimal adb. I haven't been able to get a working v410 driver though. Any ideas? I'm on Win10, so perhaps that's my problem.
Edit: I tried another v410 and my pc recognized it, so it's something to do with this tab being stuck in twrp and not getting recognized. if that helps.
I'm in the same boat, nothing I have tried, including the steps listed here seems to work.
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
mikiemc73 said:
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
Click to expand...
Click to collapse
Both links are broken, which is a special feat given the post is only 4 months old and edited on 8/26. Anyway the link you mentioned is correctly posted here: http://forum.xda-developers.com/showthread.php?t=2451696
However, if like me, your device cannot be recognized in Windows, and you're stuck in TWRP, you should run try and run the following command while in TWRP by clicking "Advance" then "Terminal Command" and "Select"
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
The command should run, then tap the return button until you're back to the main screen. Reboot without installing SuperSU.
I have 6 v410 devices with nearly exact same setups. I say nearly, because there must be something different that I'm not aware of. 4 out of 6 updated fine, 2 were bricked. 1 had to be sent to LG for warranty replacement. Go figure.
"I have 6 v410 devices with nearly exact same setups."
Good day, Sir! I have v410 and accidentally bricked it when I tried to change something in build.prop. I have no recovery installed. Nothing at all. The only change I did is the root and I cannot flash it due to some errors. A friend of mine told me I should find back up of other good v410 (.tot file if I'm not mistaken) and it could be applied to my bricked v410. Will it work? What method should be used for the .tot file? Are there anyway I could unbrick it without returning it to service centre? I have no warranty since I bought it abroad. I'm looking forward for your answers. Thank you!
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
If you flash the stock recovery here using flashify,: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0, you will be able to install the ATTT updates without softbricking into twrp.
ChristopherXDA said:
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
Click to expand...
Click to collapse
Good!
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
The Krugz said:
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
Click to expand...
Click to collapse
Here is the v410 stock recovery: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Thank you, kind sir! I'll inform you if it does worked. :good:
Unfortunately, it didn't work. Perhaps you have v410 stock rom I can flash using lg flash tool?
V410 KDZ or stock recovery request.
ChristopherXDA said:
Here is the v410 stock recovery: //drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
triathleteninja said:
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
Click to expand...
Click to collapse
That file is just the recovery partition, not a whole system image.
To the best of my knowledge there has been no kdz released for the V410. Thank your carrier for that, because LG provides it for the V400.
please help my when i command adb shell have error device not found i have Qualcomm HS-USB QDLoader 9008 mode on lg gpad v410 ((
Alright this post is almost a year old...But i still went back and updated the Minimul ADB link, the second link on my post is simply a thanks to the original person, yes it was deleted theres nothing I can do but you guys do not need it it was only there for you guys to say thanks to him. This thread is only the solution to being stuck in TWRP, some people here asked me for the stock rom,At the time i wrote this thread no one had a kdz for the v410 however now there in fact is one, its android 4.4.2 http://www.mediafire.com/file/2433xqabj1k8b8d/V41007h_0.kdz and I found it here https://forum.xda-developers.com/g-pad-10/general/unbrick-v410-t3105091. Probably easier then my thread to simply flash this with the flash tools but If you decide to follow my old outdated method, and follow the steps %100 it should theoretly get you out of the TWRP bootloop, it worked for me and I was simply sharing, However if it doest work for you dont bite my head off, there are many reasons why you might be in a boot-loop and many factors that come into play so My solution might not be the best for you. Anyway I dont know why I'm reviving an almost year old thread but I just never read the responses as I havent been on XDA for a while and figured I would post in case anyone still wanted it. Again there is a much easier way now because there is a KDZ so this is outdated.