[Q] Deleted everything but TWRP in my G2 - G2 Q&A, Help & Troubleshooting

Deleted everything but TWRP in my G2. ADB Sideload doesn't start, it gets stuck in "starting ADB sideload feature..." any ideas what to do? Any help would be greatly appreciated

Jony7so said:
Deleted everything but TWRP in my G2. ADB Sideload doesn't start, it gets stuck in "starting ADB sideload feature..." any ideas what to do? Any help would be greatly appreciated
Click to expand...
Click to collapse
I had this problem and had to do a factory wipe to get ADB sideload to work so I could push a rom to TWRP
I never had anything but problems using TWRP on this device, I have no problems with CMR
Look through this thread;
http://forum.xda-developers.com/lg-g2/help/download-mode-t2818828

Thanks
Gabriel51 said:
I had this problem and had to do a factory wipe to get ADB sideload to work so I could push a rom to TWRP
I never had anything but problems using TWRP on this device, I have no problems with CMR
Look through this thread;
http://forum.xda-developers.com/lg-g2/help/download-mode-t2818828
Click to expand...
Click to collapse
Thank you I ended up flashing stock, will definitely review this if I get stuck with sideload again!

Related

Help, Lost Recovery!

I was installing a new ROM with TWRP and it got stuck. I can boot back into TWRP, but there is no recovery. I can connect to adb and it sees my device, but i can not get into adb shell to flash. what else can i do? At this point, i just need to flash with a different rom, but cant push or flash
zhzaen said:
I was installing a new ROM with TWRP and it got stuck. I can boot back into TWRP, but there is no recovery. I can connect to adb and it sees my device, but i can not get into adb shell to flash. what else can i do? At this point, i just need to flash with a different rom, but cant push or flash
Click to expand...
Click to collapse
What exactly is happening when you get back into recovery?
SamsungGalaxyStig said:
What exactly is happening when you get back into recovery?
Click to expand...
Click to collapse
I get to the twrp menu, but no recovery in folder.
zhzaen said:
I get to the twrp menu, but no recovery in folder.
Click to expand...
Click to collapse
Is it running a script or something? or just a blank screen?
SamsungGalaxyStig said:
Is it running a script or something? or just a blank screen?
Click to expand...
Click to collapse
i can access all menu features in twrp, but there is no recovery in the folder. if i reboot, it just gets stuck on the LG logo.

Sideloading - device not found

My phone is without an OS hence sideloading. ADB set up fine. Device is recognised in ADB until I sideload. Then I get error device not found when installing. I'm using the latest SDK and have tried downloading the latest LG driver but I get an error in spanish (Ithink). Am downloading driver from here http://androidxda.com/download-lg-usb-drivers
Anyone help please?
PS - I am not sure if USB debugging was enabled before the brick...
So I've moved on from that. Manually installed the android composite drivers and all ok. But NOW I have a new error which I get regardless of the Rom. "error executing updater binary in zip '/sideload/package.zip"
Looks a more advanced error to me...
Is there any serious guru that can help me as I am now stuck. Tried Android ADB interface as driver and also latest LG as driver. I get to about 65% of install then "error updating binary....". It has to be a driver issue right???
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
bender_007 said:
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
Click to expand...
Click to collapse
Thanks for responding. It's internal memory so can only sideload anyway right? How would I 'push' and what mode would TWRP need to be in?
bender_007 said:
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
Click to expand...
Click to collapse
Ok worked this out. Have not put TWRP in to sideload mode and have entered the text in CMD. The cursor just flashes and has done for about 5 minutes now...But at least it doesnt say error
So it's pushed the rom to the SD card and I still get the error updating binary when I try to install. Tried 3 different roms and all get this error. Think there's nothing left to try.
There is. What twrp are you on? And what ROM are you trying to install?
bender_007 said:
There is. What twrp are you on? And what ROM are you trying to install?
Click to expand...
Click to collapse
Hi - I actually (naughtily) opened another thread on this as the problem is not with sideloading anymore. I cannot install anything (recovery, any rom) either by sideload or push. It's like TWRP is corrupt. I'm on 2.8.6.1. Installed simple tool v3.2 as well and I cannot overwrite TWRP as I get the fail again.
Extract the recovery.omg, push it to internal. Then use dd command to flash it manually
bender_007 said:
Extract the recovery.omg, push it to internal. Then use dd command to flash it manually
Click to expand...
Click to collapse
Thanks. Beyond that now. Tried installing CWM using installer and now get secure boot error. At least I finally got rid of TWRP
jamesbond_28_007 said:
Thanks. Beyond that now. Tried installing CWM using installer and now get secure boot error. At least I finally got rid of TWRP
Click to expand...
Click to collapse
How do you get rid of twrp and install CWM instead?
I think my TWRP is corrupted too, bootlooping for 3 days now

Please help soft-bricked

Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated
Wow I expected people to jump on this one. I guess I'll just keep messing around with it
Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery
Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct
Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks

Help on recovering Zuk Z1

Hi All,
I have a Zuk Z1 and i used twrp to install lineage and there came a instance of factory reset and finally now my phone's dead with powers. Kindly help me recreate the best out of my phone
I have twrp with terminal access. Adb sideload works , installs cyanogenmod but doesnt boot. Just keeps booting to twrp.
When connected the device has "adb unauthorized".Even after trying all kinds of adb and fastboot install. Official lenovo usb drivers and also from xda's posts.
Now only option for me is to push the cyanogenmod os to sdcard and use terminal from twrp to make things right.
Can anyone kindly help me with this.
Thanks and Regards,
napdrag0n
Which (version)twrp you were useing.
nishu2878 said:
Which (version)twrp you were useing.
Click to expand...
Click to collapse
its TWRP 3.0.2-0
napdrag0n said:
its TWRP 3.0.2-0
Click to expand...
Click to collapse
Firstly if you boot into twrp than flash recovery twrp 2.8.7.0 ham and reboot into recovery.
I also face this problem. when i did reset, phone goes in twrp but the reset command didn't work then i manually factory reset and reboot but its reboot into twrp not system.
Sorry for bad English brother but this will going to solve your problem.

[OP5, encrypted] Open Beta 3 broke my display!

Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.

Categories

Resources