Hey all,
So I was on Philz recovery (Kangabean Rom) I decided I wanted to go back to normal CWM touch. Flashed what I thought was the right zip and boom..no recovery + yellow triangle.
Turns out I flashed the normal i9505 version
To make a long story short I can't get ANY recovery back despite my efforts. Tried via goo manager to install TWRP real fast, didnt work. Tried via odin but couldn't get odin to see my phone in download mode.
Any help would be greatly appreciated.
What state is your phone on. It gets into download mode? Will it boot? Odin is your option right now. Keep trying, use original usb cable, use the usb ports in the back of your computer, try a different computer.
jd1639 said:
What state is your phone on. It gets into download mode? Will it boot? Odin is your option right now. Keep trying, use original usb cable, use the usb ports in the back of your computer, try a different computer.
Click to expand...
Click to collapse
I'm able to boot into download which enables me to boot into the OS as well. I'm going to keep giving it a go on the Odin side, im also downloading the stock firmware as well in case i need to go that drastic.
Update: Was able to install some strange version of CWM through terminal emulator on the phone using some files I found. I tried to flash philz again...wiped it out and got a yellow triangle again..
Think stock firmware flash is the best way to go?
viperguy212 said:
Update: Was able to install some strange version of CWM through terminal emulator on the phone using some files I found. I tried to flash philz again...wiped it out and got a yellow triangle again..
Think stock firmware flash is the best way to go?
Click to expand...
Click to collapse
Yes
1. Download this recovery IMG.
https://db.tt/Yp1NzlqZ
2. Move the file "recovery.img" from "sdcard/download/" to root of your internal sdcard.
3. Open terminal emulator and enter the following command lines:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
4. Recovery should have flashed! Enjoy and remember to move the file recovery to the root of your internal sdcard or else the command prompt line won't work.
"All men are created equal, some work harder in pre-season."
- Emitt Smith
THANK YOU
I did this and it got a working recovery back on my phone. I think I preferred TWRP to clockwork at this point, but honestly either one does the same thing, and I am able to make a backup of my phone which was what I wanted. Also a phone with no recovery just screams a disaster waiting to happen for me. I ended up losing recovery after running triangle away, has anyone else had this happen?
Febby said:
1. Download this recovery IMG.
https://db.tt/Yp1NzlqZ
2. Move the file "recovery.img" from "sdcard/download/" to root of your internal sdcard.
3. Open terminal emulator and enter the following command lines:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I had a similar issue, I ran triangle away to get rid of the custom icon, and after that I had no recovery, your command got Clockwork back on my phone, I admit I am more used to TWRP at this point, but any port in a storm! Greatly appreciated! I can actually back up a WORKING version of my rom with the apps I want installed on it, you are a lifesaver!
4. Recovery should have flashed! Enjoy and remember to move the file recovery to the root of your internal sdcard or else the command prompt line won't work.
"All men are created equal, some work harder in pre-season."
- Emitt Smith
Click to expand...
Click to collapse
Related
hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery
Hey everyone. Hoping to get a little help on my nexus 4. Right now I'm trying to get root access again (which I lost) and also install a recovery (im guessing that I currently have no recovery installed right now). At the moment, when I go into recovery I get a "no command" error with a red triangle. Since then I've used NRT to try to flash stock recovery. Everything seems to be going along and then my phone just goes into a blank screen and NRT says its lost connection with device. Did this trying to install TWRP as well.
Something went haywire while i was trying to unroot to get 4.3. Currently running 4.3 without root access.
Any ideas? Thanks in advance.
You could try installing GooManager from the Play Store, from which you can download and install TWRP.
bushaman said:
Hey everyone. Hoping to get a little help on my nexus 4. Right now I'm trying to get root access again (which I lost) and also install a recovery (im guessing that I currently have no recovery installed right now). At the moment, when I go into recovery I get a "no command" error with a red triangle. Since then I've used NRT to try to flash stock recovery. Everything seems to be going along and then my phone just goes into a blank screen and NRT says its lost connection with device. Did this trying to install TWRP as well.
Something went haywire while i was trying to unroot to get 4.3. Currently running 4.3 without root access.
Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Yes, you have the stock recovery installed (that Android laying on its back with a red triangle is the stock recovery).
Download SuperSU (this is what gets you root) from http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip?retrieve_file=1 and copy it to your device
You need a custom recovery like TWRP to get root (because it's a zip file you need to flash though it).
Download the Android ADT Bundle from http://dl.google.com/android/adt/adt-bundle-windows-x86-20130717.zip
Extract the file and copy the "platform-tools" folder to C:\Android (create this folder if it doesn't exist). The final path should be C:\Android\platform-tools
Download TWRP (recovery) from http://techerrata.com/browse/twrp2/mako (latest version is 2.6.0.0).
Move this file to your "platform-tools" folder
Open a command Window in your platform-tools folder by holding SHIFT and right-clicking on it
Type:
Adb devices
And make sure it says "device" after some numbers.
Now type:
Adb reboot-bootloader
Wait for the device to reboot to bootloader.
Now type:
Fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img
Using your volume buttons move to "Recovery Mode" and then press the power button. At this point you'll be taken to the recovery you just flashed. Now, once you're in, press "Install" and look for the SuperSU file you downloaded. Select it, move the slider to the right and then reboot.
That's it.
mlj11 said:
You could try installing GooManager from the Play Store, from which you can download and install TWRP.
Click to expand...
Click to collapse
Thank you so much. This worked perfectly! One last quick question, can i do the same thing on my N10? or are any of the files specific to the N4?
Thanks again.
You can do the same on your N10. The GooManager app will download the correct file for you, but just double-check the name of the file it selects to be safe.
Hit thanks if I helped
First, let me tell you how i got here. I rooted MK2, installed safestrap and downloaded the galaxy note 3 launcher. Im on AT&T. I downloaded the app and tried to install it reguarly. It said problem parsing package. Then, i went to safestrap recovery and thought i could install it there. HUGE MISTAKE. It said it installed and everything, but when i rebooted, phone was tremendously slow and kept getting the "System UI has stopped responding" message or something like that. I patiently waited trying to work my way into the sytem/app folder to delete the app there to try my luck. That didnt work, it said permission denied or something along those lines. I just want to know excatly how i can get it back into working order. It comes on and everything. I have no status bar and that notification pops up about every five seconds. Any help would be much appreciated. Please. Thank you.
tmac42 said:
First, let me tell you how i got here. I rooted MK2, installed safestrap and downloaded the galaxy note 3 launcher. Im on AT&T. I downloaded the app and tried to install it reguarly. It said problem parsing package. Then, i went to safestrap recovery and thought i could install it there. HUGE MISTAKE. It said it installed and everything, but when i rebooted, phone was tremendously slow and kept getting the "System UI has stopped responding" message or something like that. I patiently waited trying to work my way into the sytem/app folder to delete the app there to try my luck. That didnt work, it said permission denied or something along those lines. I just want to know excatly how i can get it back into working order. It comes on and everything. I have no status bar and that notification pops up about every five seconds. Any help would be much appreciated. Please. Thank you.
Click to expand...
Click to collapse
You can either try installing another launcher like nova, apex etc. Or you can follow this guide written and files provided by gtj0 to get back to stock mk2. http://forum.xda-developers.com/showthread.php?t=2526964
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
[email protected] said:
You can either try installing another launcher like nova, apex etc. Or you can follow this guide written and files provided by gtj0 to get back to stock mk2. http://forum.xda-developers.com/showthread.php?t=2526964
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
I tried that and couldnt figure out how to glash the OTA file via odin. I changed the neame and everything and odin couldnt find it
tmac42 said:
I tried that and couldnt figure out how to glash the OTA file via odin. I changed the neame and everything and odin couldnt find it
Click to expand...
Click to collapse
You can't flash the ota files via Odin.
You need to download ADB
I USE ADB FASTBOOT
GOOGLE ADB XDA AND YOU'LL FIND THE FILE.
AFTER YOU GET ADB
MAKE SURE YOU TEST IT OUT!
MAKE SURE YOU KNOW WHERE YOU HAVE THE ADB FILE IN YOUR LAPTOP OR PC
OPEN THE FOLDER THEN HOLD SHIFT + RIGHT CLICK BUTTON AND CLICK ON “OPEN COMMAND WINDOW HERE."
IT WILL PULL UP MS-DOS
TO TEST IT OUT YOU WILL HAVE TO HAVE RECOVERY ON YOUR PHONE. IF YOU DONT HAVE RECOVERY YOU NEED TO DOWNLOAD AND FLASH THE RECOVERY MJ6 FILE PROVIDED IN THE LINK I POSTED BY GTJ0.
FLASH RECOVERY IN PIT VIA ODIN. NOW YOU WILL HAVE RECOVERY
GO INTO RECOVERY WHICH IS “HOME BUTTON+VOLUME UP BUTTON" AFTER YOU RESTART YOUR DEVICE.
GO INTO OPTION ADB SIDELOAD
HOOK PHONE TO LAPTOP/PC
WITH ADB ON PC MS-DOS TYPE IN “ADB DEVICES" AND IT SHOULD RECOGNIZE YOUR PHONE IT WILL DISPLAY SOME LETTERS AND NUMBERS.
NOW THAT YOU MADE SURE THAT ADB RECOGNIZES YOUR DEVICE TIME TO ODIN
YOU NEED TO FLASH MF3 EMERGENCY FILE 1 VIA PDA
AFTER YOU FLASH AND IT FAILS
YOU NEED TO FLASH MF3 EMERGENCY FILE 2 VIA PDA TILL FAIL
RESTART YOUR PHONE
HOLD
SIDE BUTTON+HOME BUTTON+VOLUME UP
GO TO YOUR PHONES RECOVERY AS SOON AS THE PHONE RESTARTS HOLD
VOLUME UP + HOME BUTTON
YOU WILL GET TO YOUR STOCK RECOVERY IF YOU DON'T HAVE IT JUST FLASH THE RECOVERY MJ6 IN PDA VIA ODIN AND THEN IT WILL LOAD AN UPDATE JUST WAIT FOR IT.
NOW GO INTO ADB SIDELOAD OPTION IN YOUR RECOVERY.
NOW YOU WILL HAVE TO SIDELOAD THE ZIP FILES.
DO NOT UNZIP THEM LEAVE THEM AS IS AND DONT LOOK INSIDE THE ZIP
FIRST YOU WANT IN MS-DOS COMMAMD IS TO LOAD THE FIRST ZIP WHICH IS MF3-MJ9.ZIP
IN MS-DOS INPUT COMMAND WITHOUT QUOTATION “ADB SIDELOAD MF3-MJ9.ZIP"
YOU WILL SEE IT LOADING ON YOUR PC FIRST AFTER IT REACHES 100% ON PC THEN IT'LL APPLY UPDATE ON YOUR PHONE.
NOW WAIT IT TAKES LIKE 15-20 MINS SOMETIMES LONGER.
NOW YOU'LL BE ON MJ9. FROM HERE YOU CAN STAY ON MJ9 OR UPDATE VIA SETTINGS ON YOUR PHONE OR DOWNLOAD THE SMALL ZIP FILE
MJ9-MK2.ZIP
SAME THING GOES FOR THIS ZIP IN MS-DOS “ADB SIDELOAD MJ9-MK2.ZIP"
NOW YOU'LL BE ON MK2....
.......
AND PLEASE DO SOME READING BEFORE MESSING WITH YOUR PHONE..
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
[email protected] said:
You can't flash the ota files via Odin.
You need to download ADB
I USE ADB FASTBOOT
GOOGLE ADB XDA AND YOU'LL FIND THE FILE.
AFTER YOU GET ADB
MAKE SURE YOU TEST IT OUT!
MAKE SURE YOU KNOW WHERE YOU HAVE THE ADB FILE IN YOUR LAPTOP OR PC
OPEN THE FOLDER THEN HOLD SHIFT + RIGHT CLICK BUTTON AND CLICK ON “OPEN COMMAND WINDOW HERE."
IT WILL PULL UP MS-DOS
TO TEST IT OUT YOU WILL HAVE TO HAVE RECOVERY ON YOUR PHONE. IF YOU DONT HAVE RECOVERY YOU NEED TO DOWNLOAD AND FLASH THE RECOVERY MJ6 FILE PROVIDED IN THE LINK I POSTED BY GTJ0.
FLASH RECOVERY IN PIT VIA ODIN. NOW YOU WILL HAVE RECOVERY
GO INTO RECOVERY WHICH IS “HOME BUTTON+VOLUME UP BUTTON" AFTER YOU RESTART YOUR DEVICE.
GO INTO OPTION ADB SIDELOAD
HOOK PHONE TO LAPTOP/PC
WITH ADB ON PC MS-DOS TYPE IN “ADB DEVICES" AND IT SHOULD RECOGNIZE YOUR PHONE IT WILL DISPLAY SOME LETTERS AND NUMBERS.
NOW THAT YOU MADE SURE THAT ADB RECOGNIZES YOUR DEVICE TIME TO ODIN
YOU NEED TO FLASH MF3 EMERGENCY FILE 1 VIA PDA
AFTER YOU FLASH AND IT FAILS
YOU NEED TO FLASH MF3 EMERGENCY FILE 2 VIA PDA TILL FAIL
RESTART YOUR PHONE
HOLD
SIDE BUTTON+HOME BUTTON+VOLUME UP
GO TO YOUR PHONES RECOVERY AS SOON AS THE PHONE RESTARTS HOLD
VOLUME UP + HOME BUTTON
YOU WILL GET TO YOUR STOCK RECOVERY IF YOU DON'T HAVE IT JUST FLASH THE RECOVERY MJ6 IN PDA VIA ODIN AND THEN IT WILL LOAD AN UPDATE JUST WAIT FOR IT.
NOW GO INTO ADB SIDELOAD OPTION IN YOUR RECOVERY.
NOW YOU WILL HAVE TO SIDELOAD THE ZIP FILES.
DO NOT UNZIP THEM LEAVE THEM AS IS AND DONT LOOK INSIDE THE ZIP
FIRST YOU WANT IN MS-DOS COMMAMD IS TO LOAD THE FIRST ZIP WHICH IS MF3-MJ9.ZIP
IN MS-DOS INPUT COMMAND WITHOUT QUOTATION “ADB SIDELOAD MF3-MJ9.ZIP"
YOU WILL SEE IT LOADING ON YOUR PC FIRST AFTER IT REACHES 100% ON PC THEN IT'LL APPLY UPDATE ON YOUR PHONE.
NOW WAIT IT TAKES LIKE 15-20 MINS SOMETIMES LONGER.
NOW YOU'LL BE ON MJ9. FROM HERE YOU CAN STAY ON MJ9 OR UPDATE VIA SETTINGS ON YOUR PHONE OR DOWNLOAD THE SMALL ZIP FILE
MJ9-MK2.ZIP
SAME THING GOES FOR THIS ZIP IN MS-DOS “ADB SIDELOAD MJ9-MK2.ZIP"
NOW YOU'LL BE ON MK2....
.......
AND PLEASE DO SOME READING BEFORE MESSING WITH YOUR PHONE..
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
i cant flash the recovery in pit. I can do it in PDA then it only gets to the android with a spinny thing in its belly. Then it restarts after that. And, i cant get my phone to appear on adb devices in MS-DOS. Do i have to enable th eoption in the recovery first?
tmac42 said:
i cant flash the recovery in pit. I can do it in PDA then it only gets to the android with a spinny thing in its belly. Then it restarts after that. And, i cant get my phone to appear on adb devices in MS-DOS. Do i have to enable th eoption in the recovery first?
Click to expand...
Click to collapse
Do you have USB debugging checked on your phone in developer options? You have to have it on adb sideload for it to recognize the device
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
I cant thank you enough. Im donw with this stuff. Time to sell it and get a N5. Thanks alot. I dont know how it worked, but it did. Thanks
tmac42 said:
I cant thank you enough. Im donw with this stuff. Time to sell it and get a N5. Thanks alot. I dont know how it worked, but it did. Thanks
Click to expand...
Click to collapse
So you got your phone up and running?
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Yes I did. Thank you kind sir.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696
First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!
Hi guys.
I did something really stupid with my brand new lg g2. Wanted a custom rom, so flashed twrp recovery.
Then i wanted to flash the downloaded custom rom, but i somehow deleted everything on the phone.
Then i connected my device to the pc, and tried to sideload the rom. That didn't go well, so now i can't enter recovery or anything.
The phone only shows the LG logo or bootlooping.
Is there any hope?
(I tried to send in my phone during warranty, but they said i needed a new mainboard - which is very costly)
You don't sideload a ROM, you instead push it to internal storage via ADB so it can be installed via recovery (TWRP, PhilZ CWM, etc.). So this would be the command from a command prompt, run from the AndroidSDK\Tools directory or from the directory containing the ADB executable...
adb push ROM.zip /sdcard/ROM.zip
... replacing ROM with the EXACT name of the ROM file. If besides not being able to access recovery using this method...
alone-together said:
Hold the power button until the phone turns completely off, then turn on the phone while holding the power and volume down buttons. When the LG logo pops up, let go and re-press those buttons. When prompted for a factory reset, press the power button
Click to expand...
Click to collapse
... you can't access download mode to restore using either the *.tot or *.kdz method, then this may be your only alternative:
http://forum.xda-developers.com/showthread.php?t=2582142
redduc900 said:
You don't sideload a ROM, you instead push it to internal storage via ADB so it can be installed via recovery (TWRP, PhilZ CWM, etc.). So this would be the command from a command prompt, run from the AndroidSDK\Tools directory or from the directory containing the ADB executable...
adb push ROM.zip /sdcard/ROM.zip
... replacing ROM with the EXACT name of the ROM file. If besides not being able to access recovery using this method...
... you can't access download mode to restore using either the *.tot or *.kdz method, then this may be your only alternative:
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thank you very much. I was able to reach twrp again, pretty easy. I pushed a custom rom to my device, but even though the rom is installed OK, i wasn't supposed to make my device boot into the rom. The device only boots to twrp. I Installed several roms to see, if this was because of a bad flash, but that wasnt the answer. I wiped everything, and reached the aroma installer for cloudyfas rom. Installed without problems, but when rebooting, it still only boots up TWRP. Can't do anything to reach the rom (s). Any suggestions?
You may need to flash the KitKat baseband. The link is in the OP of the CloudyG3 thread.
redduc900 said:
You may need to flash the KitKat baseband. The link is in the OP of the CloudyG3 thread.
Click to expand...
Click to collapse
Thanks for answer. I did flash the baseband first.
And Tried several roms. Now Im back to stock and Wonder If i really should try again. On my first lgg2, screen Damage appeared When i was flashing a custom rom. I just don't understand Why i Couldnt load the rom after i flashed in twrp.