So I installed TWRP on a new rooted G2 and now I'm stuck in TWRP with no ROM to flash. I can't boot into Bootloader mode- selecting that options just boots me back into TWRP.
I tried ADB Sideload from the advanced menu but that doesn't work either.
Is my only option to get some kind of external usb storage with a ROM on it and try to install from there?
I also tried holding Vol up and Down and plugging in USB cable from the powered off state and all it did was take me into TWRP again.
Not sure if this helps, but I made an error screwing around with build.prop and ended up in a bootloop. Was able to boot into recovery (cwm and not twrp) And And sideload wasn't working either for some reason. I did manage to adb push Clean Rom and install from zip, which saved me... so maybe adb push is worth a shot if sideload isn't working
Sent from my VS980 4G using Tapatalk
No backup to restore? You may have to get an external connection/sd with a ROM already loaded on it.
Related
I recently just picked up a nexus 4 and i'm trying to get a custom ROM on it. I updated it to 4.3 and that was fine. Went to install custom recovery and every since it will not boot! I've reverted to factory 4.3 using fastboot, and relocked it and locked it but still will not boot. It gets stuck at the X logo. Left it for an hour and won't get past it. If i install a custom recovery, it'll boot into the custom recovery no problem, but won't install root as it can't mount the SD card. I can get to fastboot mode no problem and flash stuff in fastboot but will never boot up. I'm puzzled as to what to do. I'm going to try 4.2.2 factory image here shortly and see if i can get it to take. I forgot to enable USB debugging so i think thats why i can't get custom recoveries to work. I tried pushing a ROM using ADB push but it wouldn't get there. Maybe it did as it said it did on the computer but the recovery won't read the memory. Any ideas as to what to do
UPDATE: Ok after flashing stock 4.2.2 from fastboot it boots.
UPDATE: turns out just having USB debugging was the culprit of everything. So make sure USB debugging is enabled before starting the whole process!
Hey All,
So here is what happened. I had the Maluidus ROM installed and wanted to try the KK zip that cloudyfa made. I flashed it, and it went well. However when I booted I could only get to the verizon screen. I can boot my phone but into PHILZ recovery I can not access download mode. When I try to use adb to sideload a rom I type adb devices, and my device is not listed. The drivers are installed as I used IO root to to root it. Anything I can do in recovery to add a zip to the internal sd card? any help?
****Edit**** When in recovery the device is not recognized and the drivers can not be installed.
I installed the 3.0 update and it never removed TWRP, however TWRP is not working. If I flash the zip file for 3.0 it reboots the system in the middle of installing. I tried flashing the cm12 and cm13 zip files and they say they flashed successful but nothing appears to have installed, and I currently have no rom or firmware installed and can't seem to boot to fastboot. Any ideas?
Here is what happens when i flash the 3.0 zip file. https://youtu.be/-ZVnaNdn6-M
I seen the same logo don't know what to do as well. My parent click update while i was away from home when i got back it just the logo with nvidia.
Restore using the recovery images here for your device https://developer.nvidia.com/gameworksdownload using fastboot not twrp.
The way I get to bootloader is pull the power cable, plug back in and hold power immediately until the menu appears YOU MUST HAVE micro usb connected to a pc while doing this.
I'll give it a try. Thank you for the reply
Try this:
http://forum.xda-developers.com/shield-tv/general/guide-how-to-flash-recovery-image-t3321404
I flashed to cm13 nightly 20160302 and my phone boots to cm with no problem but now I am unable to boot into recovery through any method with twrp 3.0.0.4 or any twrp version I tried inside of twrp manager or flashify, I am put into fastboot mode when trying to enter recovery with 3.0.0.4 and a few other I tried while other versions give me unsecured boot message. When trying to go into download mode I get the first download mode screen and then the screen goes blank and brings up 15 system partitions on my pc with only one partition containing a folder called image with a bunch of files. The phone is detectable through adb and as a storage device on my pc while booted into cm and while in fastboot mode the phone shows up as marshal london device- marshal london bootloader interface in device manager with no storage.
I planned on going to cloudyg2 but now I'm thinking about just going back to stock, would I be able to use the lg flash tool to get back to stock? Or possibly use adb recover to stock or use adb sideload to flash the default lg rom?
hevydevy said:
I flashed to cm13 nightly 20160302 and my phone boots to cm with no problem but now I am unable to boot into recovery through any method with twrp 3.0.0.4 or any twrp version I tried inside of twrp manager or flashify, I am put into fastboot mode when trying to enter recovery with 3.0.0.4 and a few other I tried while other versions give me unsecured boot message. When trying to go into download mode I get the first download mode screen and then the screen goes blank and brings up 15 system partitions on my pc with only one partition containing a folder called image with a bunch of files. The phone is detectable through adb and as a storage device on my pc while booted into cm and while in fastboot mode the phone shows up as marshal london device- marshal london bootloader interface in device manager with no storage.
I planned on going to cloudyg2 but now I'm thinking about just going back to stock, would I be able to use the lg flash tool to get back to stock? Or possibly use adb recover to stock or use adb sideload to flash the default lg rom?
Click to expand...
Click to collapse
I have the same problem. Any solution found?
stormrider2230 said:
I have the same problem. Any solution found?
Click to expand...
Click to collapse
if you can enter download mode. press vol up and connect usb.. then just go back to stock.. or see if srk tools would help..
Hi,
I was flashing twrp with flashify when I just rebooted in recovery and since that moment my phone is stuch on an infinite bootloop showing me the:
"Recovery booting (recovery is not seandroid enforcing...)"
I'm plugging off the battery for some hours, but when plugged in nothing changed.
My phone has the usb port broken, so I can use it only to charge the battery, but no pc will recognize it.
Since the fact that I can't access download mode, or recovery mode to restore a nandroid backup, It's insane to buy a usb port to change it on the phone and try to link to a pc?
I mean, is there a way to access download mode?
Does JIG usb work in this situation of hard brick?
Any advice?
Thanks for answering.
whychange said:
Hi,
I was flashing twrp with flashify when I just rebooted in recovery and since that moment my phone is stuch on an infinite bootloop showing me the:
"Recovery booting (recovery is not seandroid enforcing...)"
I'm plugging off the battery for some hours, but when plugged in nothing changed.
My phone has the usb port broken, so I can use it only to charge the battery, but no pc will recognize it.
Since the fact that I can't access download mode, or recovery mode to restore a nandroid backup, It's insane to buy a usb port to change it on the phone and try to link to a pc?
I mean, is there a way to access download mode?
Does JIG usb work in this situation of hard brick?
Any advice?
Thanks for answering.
Click to expand...
Click to collapse
You need a working usb to flash a custom recovery or an offical fw. I thought flashify needs root access to work?. Or if you already have root, you could adb to flash twrp but it's too late now.
Try getting into download mode. When it asks to proceed or cancel, choose cancel. Some people are lucky that the phone boot into system again but they need to fix the broken recovery later.
Sent from my SM-G925F
Rosli59564 said:
You need a working usb to flash a custom recovery or an offical fw. I thought flashify needs root access to work?. Or if you already have root, you could adb to flash twrp but it's too late now.
Try getting into download mode. When it asks to proceed or cancel, choose cancel. Some people are lucky that the phone boot into system again but they need to fix the broken recovery later.
Sent from my SM-G925F
Click to expand...
Click to collapse
After 2 months of battery out, finally I got download mode to work, and pressing cancel my phone started.
Thanks.
But now it seems that there is no custom recovery installed, so when i go in custom recovery, the loop starts again.
How may I install again a custom recovery, knowing that:
1) I can't connect to pc, cm 12.1 has a bug, no pc recognizes my phone;
2) rom manager doesn't install any custom recovery on my phone;
3) flashify made my phone in boot loop, and I can't understand what I was wrong 2 months ago.
Thank you, man.
See your other post man .
Flash the tar version of TWRP using Odin. If there is no tar version, you can use Cygwin to convert an img file to a tar file.