Database Info

[Q] Frozen on boot screen after 2.3.3

Hi All,
I have a Nexus S with a strange problem. It was originally stock, with no ROM mods at all, I then applied the SU patch get root happening - all worked fine for months.
I then manually applied the 2.3.3 update about 1 week ago. All working fine with no issues.
Today however, i've come to check my phone to find it 'frozen' on the boot screen.
Thinking it was just another lovely OS glitch, I battery pulled, to find it turned into an endless Nexus S boot loop. I booted into recovery, wiped the cache. Same Issue. I Booted into recover a gain, did a factory data reset. Same issue. I booted in recovery again and re-applied the 2.3.3 update which was on my memory from the previous update. Same issue.
The phone seems to either freeze during boot, or go into and endless loop.
Ideas? - The only other thing that i thought would be to do a bootloader unlock to wipe EVERYTHING... but im not sure if its worth it.

Why not? You can lock it back with fastboot oem lock command.

If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.

distortedloop said:
If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Click to expand...
Click to collapse
Sadly, it was a locked bootloader, so had no luck with that
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
distortedloop said:
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
Couldn't get in as i had no ADB access.
In any case, i did a OEM unlock, and still had similar boot issues. The OS would boot, but despite flashing a custom clockwork recovery, it wouldn't get from BootLoad thru to Recovery. It also still had random hangs on boot.
I performed a fastboot flashall and also a fastboot erase boot and recovery. Leaving the phone totally empty.
I then re-loaded a rooted 2.3.3 with latest Clockwork and all worked fine. I've also updated radio to B3 - seems to work flawlessly.
I can only think something was screwy with the boot/recovery sections - very weird but all appears to work fine now.
Many thanks for the help.

g33k84 said:
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
Couldn't get in as i had no ADB access.
Click to expand...
Click to collapse
You don't need recovery access to use adb. We might be miscommunicating, and it doesn't matter much since you've already nuked the phone, but what I was suggesting was a regular boot while trying to adb logcat the phone. I've used this technique to document the startup process in the past. Adb access loads up fairly soon in the process. If your phone wasn't even getting that far, of course it wouldn't work, but wanted to clear up what I was suggesting with that particular paragraph.

Rooted 2.20 now cant boot my phone

Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.

I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium

subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.

dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"

DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.

movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium

You won't be able to flash anything until you fixed your sdcard using the method in that link.

Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium

ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.

"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.

If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium

DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.

movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader

Thank you both will try that now.

Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am

Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.

marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.

fastboot only works in bootloader btw

Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X

Sent from my HTC One XL using Tapatalk 2

[SOLVED/THANKS GUYS] hopeless boot loop.. :(

was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck

TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me

wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.

iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?

wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM

TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.

wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind

it does, but even that didn't work..

[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

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%