Database Info

[Q] Nexus 5 stuck on boot, and wont go into recovery help?

Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.

GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.

GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.

jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>

But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens

When in the twrp I can't get fastboot to recognize it as a device, or adb either

2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.

jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash

GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?

2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp

jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5

[SOLVED] Stuck in bootloop even after flashing back to stock

Hey everyone,
I've been tearing out my hair for the past 34 hours (with the exception of sleeping). I restarted my phone yesterday and it got stuck in the boot animation, for hours.
I have never unlocked my bootloader, or flashed any custom rom on this phone, so I was really shocked when this happened. So I took to these forums, because lurking here usually solves all my issues (thanks awesome people), and flashed the stock image as recommended-> bootloop -> factory reset in recovery mode -> bootloop-> repeated this all night and today with multiple flashing methods (fastboot using flash-all and flashing individually, no dice.
I was wondering if I was out of luck, seeing as though my phone just randomly did this to itself, without prior tampering, or if there was something I could try doing. I haven't tried any custom recoveries as I don't really know how that would help me if I am willing to flash back to stock and lose all my data.
I am able to boot into fastboot mode and go to recovery mode, so this indicates to me that my hardware is fine, unless I am wrong
Thanks, I would appreciate all the help I can get

Was fast boot one of those multiple flashing methods?

theesotericone said:
Was fast boot one of those multiple flashing methods?
Click to expand...
Click to collapse
Yeah, both using Flash-all and flashing each individual, Ill update post

ChunksOfLemon said:
Yeah, both using Flash-all and flashing each individual, Ill update post
Click to expand...
Click to collapse
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.

theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
I'll try this now and let you know

theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
Yeah, no luck there either
I guess I'll call LG in the morning

ChunksOfLemon said:
Yeah, no luck there either
I guess I'll call LG in the morning
Click to expand...
Click to collapse
First reboot to recovery and wipe cache.

theesotericone said:
First reboot to recovery and wipe cache.
Click to expand...
Click to collapse
Nothing is working, I'll check to see how much it'll be to repair

ChunksOfLemon said:
Nothing is working, I'll check to see how much it'll be to repair
Click to expand...
Click to collapse
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?

beekay201 said:
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
Click to expand...
Click to collapse
OMG YES THIS WORKS! Thank you, I read that thread in my initial search, but it didn't seem to apply. But I just tried it and my device booted in like five minutes.
Thanks for helping me guys, don't need to buy another phone

Weird problem after reflashing Nexus 5

Hello. I'm facing a very weird problem with my Nexus 5. I have been using a custom ROM (Dirty Unicorns) and everything was fine, until I saw that there was a 7.1 ROM for the Nexus. I decided to give it a try. I've played around with it for a couple of minutes and decided that it's not so stable, so I flashed stock image with the Nexus Root Toolkit. Everything went fine, the phone booted to OS, but when I try to watch a YouTube video for example the screen goes black and I cannot do anything. Phone's hardware buttons are working, but the touch isn't. Hard reset fixes the problem, but its back again under a medium or heavy usage. I thought that the factory img that I flashed via the Nexus Root Toolkit is corrupted somehow, so I downloaded an earlier version and flashed it via old fashion way via adb. Unfortunately the problem still persists, even appearing more frequently now. From time to time it starts and stays on boot screen, stays for a while and again goes black. I have tried also to downgrade from Marshmallow to Kitkat, unfortunately problem is still there.
Any ideas what could have gone wrong?
Thanks in advance!

It may be hardware problem. Check it out at some harware or phone store

How did you flash with adb? I would try wiping a few times and seeing if that helps.

Try reflashing all partitions, including the userdata.img file and perform a factory wipe before booting the rom for the first time.

wangdaning said:
How did you flash with adb? I would try wiping a few times and seeing if that helps.
Click to expand...
Click to collapse
I meant fastboot, not adb.
1st. I have tried to flash the Stock ROM via cmd by executing the flash-all.bat file, everything flashed correctly, no errors shown, but again black screen. I then executed thoose commands for manually flashing:
Code:
fastboot flash radio
fastboot reboot-bootloader
fastboot erase system
fastboot flash system
fastboot erase userdata
fastboot flash userdata
fastboot erase boot
fastboot flash boot
fastboot erase recovery
fastboot flash recovery
fastboot erase cache
fastboot flash cache
No luck again.
audit13 said:
Try reflashing all partitions, including the userdata.img file and perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
Done this a million times. I guess it is a hardware problem. So I'll be taking it to the hardware store in a few days.
Thank you all for your replies.

In my opinion it has been damaged display connector on the motherboard. I had the same problem, but for me I did not have to do anything to become a black screen and does not respond to anything

bykumza said:
In my opinion it has been damaged display connector on the motherboard. I had the same problem, but for me I did not have to do anything to become a black screen and does not respond to anything
Click to expand...
Click to collapse
Could be the case, but why the display is working only in Bootloader and sometimes lights up in Recovery? It can stay all day in bootloader, but when I try to boot to OS or go to Recovery it goes black. If its a display connector problem, shouldn't it be black always, no matter that I'm in Bootloader, OS, etc.?
Sent from my SM-G920F using Tapatalk

How to Unbrick LG V20

UPDATE 11/30/20: I AM STILL PROVIDING FAST 1 ON 1 SUPPORT VIA DISCORD https://discord.gg/RNJXXPp
READ WHOLE THING!
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: http://www.mediafire.com/file/pcuslla00j22zqw/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Now put it back in
THIS IS VERY IMPORTANT:
http://www.hardreset.info/devices/lg/lg-v20/
FOLLOW METHOD 1 AND DO IT TWICE! TWICE I SAID!
It won't give you a success message so after you do this pull the battery out and put it back in
hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode.
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
UPDATE: If you are stuck in TWRP after the OTA follow the these steps:
1. Wipe everything in twrp. (internal storage, data, cache, davilk etc.)
2. Flash a custom rom from xda. (I used Overdirve. No promises if it works on anything else: https://forum.xda-developers.com/v20/development/rom-maximum-ovrdrive-lg-v20-v2-0-t3518475
3. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Now put it back in
THIS IS VERY IMPORTANT:
http://www.hardreset.info/devices/lg/lg-v20/
FOLLOW METHOD 1 AND DO IT TWICE! TWICE I SAID!
It won't give you a success message so after you do this pull the battery out and put it back in
hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode.
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you are still having issues, join this discord I made and leave a message. I will response faster there: https://discord.gg/RNJXXPp
If I helped, please feel free to donate paypal.me/ScottM911

ScottFlysPlanes said:
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: https://build.nethunter.com/misc/h918/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Put the battery back in, and hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode. Type
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
If I helped, please feel free to donate http://bit.ly/2gilo51
Click to expand...
Click to collapse
How did you get the system.img onto your device to flash? I keep getting a file size limit error whenever i try to copy it over...

Murphy71984 said:
How did you get the system.img onto your device to flash? I keep getting a file size limit error whenever i try to copy it over...
Click to expand...
Click to collapse
Use a flash drive and get a USB to USB c adapter. I had one from my note 7. You can also use adb push

ScottFlysPlanes said:
Use a flash drive and get a USB to USB c adapter. I had one from my note 7. You can also use adb push
Click to expand...
Click to collapse
I'm still getting a bootloop to the Recovery....ugh I just don't get it. I followed everything to a T.....I thought that as long as I could get to TWRP I could flash the Stock Odex/DeOdex zip found in another thread and everything would be fine...when it gets to the LG screen it sorta does an 'old TV flash' and goes into recovery...what am I missing?

Murphy71984 said:
I'm still getting a bootloop to the Recovery....ugh I just don't get it. I followed everything to a T.....I thought that as long as I could get to TWRP I could flash the Stock Odex/DeOdex zip found in another thread and everything would be fine...when it gets to the LG screen it sorta does an 'old TV flash' and goes into recovery...what am I missing?
Click to expand...
Click to collapse
Try wiping everything including /system. Also make sure after you flashed the images, see if there are files in /system using the twrp file manager.

ScottFlysPlanes said:
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: https://build.nethunter.com/misc/h918/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Put the battery back in, and hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode. Type
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
If I helped, please feel free to donate http://bit.ly/2gilo51
Click to expand...
Click to collapse
@ScottFlysPlanes
Hi, I did the same thing you mentioned with yours and accidentally deleted /system. I felt a little relieved when I saw your post. But unfortunately your method is not working for me. I tried every step as per your directions. My phone boots back into TWRP (after doing 'fastboot oem unlock") and I checked /system folder which has alot of files in it... I have a question, during the initial steps, after flashing boot.img and then system.img and before rebooting, TWRP say "No OS available"! ....Your steps did not mention this. Is it supposed to say that?
I would really appreciate your help. I am freaking out here.
Thanks!!!

bighit101 said:
@ScottFlysPlanes
Hi, I did the same thing you mentioned with yours and accidentally deleted /system. I felt a little relieved when I saw your post. But unfortunately your method is not working for me. I tried every step as per your directions. My phone boots back into TWRP (after doing 'fastboot oem unlock") and I checked /system folder which has alot of files in it... I have a question, during the initial steps, after flashing boot.img and then system.img and before rebooting, TWRP say "No OS available"! ....Your steps did not mention this. Is it supposed to say that?
I would really appreciate your help. I am freaking out here.
Thanks!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20

Murphy71984 said:
Try this: http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
@Murphy71984
Thanks for the reply. Unfortunately the same thing happens, it just boots back into TWRP ... What am I doing wrong? I couldnt have messed up that bad by deleting /system...or did I???? I see other people having success with the method you linked me to, but not me.
Any other tips that might work?
Thanks once again!

bighit101 said:
@Murphy71984
Thanks for the reply. Unfortunately the same thing happens, it just boots back into TWRP ... What am I doing wrong? I couldnt have messed up that bad by deleting /system...or did I???? I see other people having success with the method you linked me to, but not me.
Any other tips that might work?
Thanks once again!
Click to expand...
Click to collapse
When you go into /system the first time when it should be clear... are you seeing a lost&found folder? That needs to be deleted.
Sent by using the battery of my LG V20

Murphy71984 said:
When you go into /system the first time when it should be clear... are you seeing a lost&found folder? That needs to be deleted.
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
I tried to delete it, but it says Done and right after in red it says "rm -r f "/system" process ended with ERROR: 1"
???

@bighit101
Are you mounting /system beforehand?
Sent by using the battery of my LG V20

Murphy71984 said:
@bighit101
Are you mounting /system beforehand?
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
Yes The system, cache and dalvik have check marks on them....

bighit101 said:
Yes The system, cache and dalvik have check marks on them....
Click to expand...
Click to collapse
Hmmm.... I don't know then! That process helped me. Just double check you are doing everything correctly and in order especially....Wipe > Format Data (type 'yes')....the Fix Contents bit...etc.... Just go through step by step.
Sent by using the battery of my LG V20

Ok, when you wipe /system and everything. Reboot. Then flash, boot.img, THEN. System.img. After that reboot, it should still take you into twrp. Wipe cache dalvik. Then reboot. Then from twrp reboot to fastboot mode and lock the bootloader. Reboot again. If you see the red triangle, and it should keep looping. Then pull out the battery and put it back in to completely turn it off. Now follow this guide http://www.hardreset.info/devices/lg/lg-v20/ for hard reset. It should just reboot after you press the reset and boot into the red triangle. Now boot back into fastboot, (hold down volume and plug in cable) and type fastboot oem unlock. Now reboot. Tell me if that works for you?

Help!!! I'm stuck on TWRP. tried different roms and no luck. I'm unable to move the system.img to the SD or phone storage. I don't have a flash drive and ADB push is failing

well i been having the boot problem as you go now but now i went from orange triangle to red. I think i have a brick for sure now if anybody knows a fix please let me know.

jrdejavux said:
well i been having the boot problem as you go now but now i went from orange triangle to red. I think i have a brick for sure now if anybody knows a fix please let me know.
Click to expand...
Click to collapse
You need to re-unlock your bootloader. Sounds like you relocked it.
Sent by using the battery of my LG V20

Murphy71984 said:
You need to re-unlock your bootloader. Sounds like you relocked it.
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
i tried but it wont go into fastboot

lourock21 said:
Help!!! I'm stuck on TWRP. tried different roms and no luck. I'm unable to move the system.img to the SD or phone storage. I don't have a flash drive and ADB push is failing
Click to expand...
Click to collapse
When doing adb push did you make sure you press "Open command window here?" In the folder of where the file you are trying to push is located.

Yeah, it starts to push then fails at around 30%

Boot loop to recovery

Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.

Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk

This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more

Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk

OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?

hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0

No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.

So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?

Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck

Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?

Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417

Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.

For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....