Database Users

Need Help. Rooted but used Flashify for TWRP as Boot Image

So I rooted my new LG G2 correctly but had some things to do and my brother had experience with phones so I let him do the TWRP install. He used flashify and flashed it as a Boot image instead of recovery. Now when I boot my phone I can only boot to TWRP. Can someone help walk me through fixing my phone?
Your help is extremely appreciated.
Thanks again.

Youre basically going to have to restore to stock with the LG tool and start fresh. I believe there is a thread in the general forum with instructions.
Been there, done that. It sucks. You live and learn.
edit: here ya go http://forum.xda-developers.com/showthread.php?t=2432476

[Q] Recovery boot error

I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?

I think I have the same problem. Could u solve the problem?

N12X93R said:
I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?
Click to expand...
Click to collapse
no you can't get recovery on kk because they patched our recovery/loki exploit on kk bootloader

not able to boot in recovery on Lg g2 802.. with stock 4.4. 2
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.

Purav786 said:
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.
Click to expand...
Click to collapse
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok

Drachenminister said:
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok
Click to expand...
Click to collapse
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?

Purav786 said:
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?
Click to expand...
Click to collapse
There is a sticky thread in the general section of the forum

Drachenminister said:
There is a sticky thread in the general section of the forum
Click to expand...
Click to collapse
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?

Purav786 said:
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?
Click to expand...
Click to collapse
No, no easy one, and some might even say none at all, but you can read the rooting thread where they discuss recovery as well http://forum.xda-developers.com/showthread.php?t=2448887

[Q] Unable to flash TWRP

I was able to root fine with the ioroot, but now I'm following this guide http://forum.xda-developers.com/showthread.php?t=2449670&highlight=loki+tool and when I get to the point to flash the recovery with loki_tool I just get this screen.
I'm on a Verizon G2 (VS980) and still on 4.2.2.
Using the 2.6.6.3 TWRP img.
Any ideas?

bretto13 said:
I was able to root fine with the ioroot, but now I'm following this guide http://forum.xda-developers.com/showthread.php?t=2449670&highlight=loki+tool and when I get to the point to flash the recovery with loki_tool I just get this screen.
I'm on a Verizon G2 (VS980) and still on 4.2.2.
Using the 2.6.6.3 TWRP img.
Any ideas?
Click to expand...
Click to collapse
Have you tryed FreeGee from Playstore?
Read in the same thread you show that someone got recovery with that apk.
Just download TWRP 2.7.0.0 and you should be ok.
Nevertheless, read the last pages of the thread you mencioned and you will find a solution.
EDIT: Think I got my recovery using this method:
http://forum.xda-developers.com/showthread.php?t=2633941
Give it a try.

Magic2010 said:
Have you tryed FreeGee from Playstore?
Read in the same thread you show that someone got recovery with that apk.
Just download TWRP 2.7.0.0 and you should be ok.
Nevertheless, read the last pages of the thread you mencioned and you will find a solution.
EDIT: Think I got my recovery using this method:
http://forum.xda-developers.com/showthread.php?t=2633941
Give it a try.
Click to expand...
Click to collapse
I tried the tool that you linked and it seemed to work. I'm just always nervous about not knowing what is actually running with some of those. Thanks though.

[How to] Unbrick v410

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.

Replace Kingo Superuser with SuperSU.

EDIT: First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
I'm sorry if this is the wrong section but, I couldn't find a section for the M919V. So I recently rooted my Galaxy S4 SGH-M919V running lollipop 5.0.1 using the PC version of Kingoroot. I've been looking for a way to replace Kingo Superuser with SuperSu. I can only seem to find anything about replacing Kinguser/Kingroot (not Kingo Superuser). I would keep Kingo Superuser but, after a reboot it doesn't allow any apps to use root access even though it says it is. I have to keep uninstalling and reinstalling Kingo Superuser and waiting then it finally fixes by it's self (currently it's broken) . SuperSu-Me says I don't have Kingroot (once again, not Kingoroot). I've also tried a script but, once again, it didn't work. I know next to nothing about the inner workings of android phones so please keep any answers simple please.

Flash custom recovery.
Flash SuperSU.
Can't get any simpler.

The sgh-m919v is basically the same phone as the T-mobile S4. The sgh-m919v was issued by Canadian varriers that run an AWS network: https://www.sammobile.com/firmwares/database/SGH-M919V/
The t-mobile s4 forum is here: http://forum.xda-developers.com/galaxy-s4-tmobile
Here's what I would do: flash a stock ROM via Odin to bring the phone back to a stock state and then root using cfautoroot if you want stock recovery or flash TWRP and flash supersu from TWRP.

First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.

Flash the stock ROM.

Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Could you link me to a good tutorial to do this?

Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Hey man, I got the flash to work. Thank you so much!

ben3759 said:
Hey man, I got the flash to work. Thank you so much!
Click to expand...
Click to collapse
Now, if you still want SuperSU, flash CF-Auto-Root.