Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
whynottry said:
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
Click to expand...
Click to collapse
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Crap I forgot to mention I can't go into download mode. Sorry about that..
atmxpert said:
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Click to expand...
Click to collapse
Related
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?
So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)
Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
U are in edl mode u need to search for blank flash it should get u back up and running
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
Did you get it running
I got a few Problems, at first i tried to unlock the bootloader, after a while i got that, bootloader unlocked.
Then i tried to root my Moto G7 Power, with bad results... Tried to install TWRP with the fastboot commands etc. I got into TWRP but couldnt install it permanent, tried it in different ways but nothing worked. After hours of testing my phone decided to stop working and it bricked.
I can get into fastboot mode, but every time ill try to start it the screen with "Your device has been unlocked and can`t be trusted." shows up, then it goes off and the same screen comes back again, tried to get ride of that but with no results.... Can anybody help me with that?
Second thing: How the hell did i install TWRP permanent on my phone??
I had to do the Thing with the img again and again to get in, tried to push the zip to my internal storage and install it from there, the red warning "Failed to mount system root" showed up...
Its my first phone im trying to root since years, and my knowledge and english is pretty bad^^
Thanks for your answers
Gousch said:
I got a few Problems, at first i tried to unlock the bootloader, after a while i got that, bootloader unlocked.
Then i tried to root my Moto G7 Power, with bad results... Tried to install TWRP with the fastboot commands etc. I got into TWRP but couldnt install it permanent, tried it in different ways but nothing worked. After hours of testing my phone decided to stop working and it bricked.
I can get into fastboot mode, but every time ill try to start it the screen with "Your device has been unlocked and can`t be trusted." shows up, then it goes off and the same screen comes back again, tried to get ride of that but with no results.... Can anybody help me with that?
Second thing: How the hell did i install TWRP permanent on my phone??
I had to do the Thing with the img again and again to get in, tried to push the zip to my internal storage and install it from there, the red warning "Failed to mount system root" showed up...
Its my first phone im trying to root since years, and my knowledge and english is pretty bad^^
Thanks for your answers
Click to expand...
Click to collapse
Go to the Moto g7 power suport group in tellagram there is some people that can help
So this was what happen, i have been trying to format my phone this day to put a rom and i had an issue (that which never happend to me) my phone was always getting an error either on Parse, or Vendor check, i kinda decided to install TWRP on bootloader as i thought i could go around, but figure out i had to download the files, since i didnt want to lose time what i actually did, was flashing the phone again to see if the phone could go further.. but the phone didnt want to pass to that phase.. i was getting impatient.. i disconnected the cable or "how we can say i closed the program multiple time betwen a flash.
I was on 1909. My bootloader was detected everything was detected the phone everything, but since i thought that windows 10 version 1909 might had something with it, i thought "well why not download a recent version" take in mind i have no option, i have no recovery, i tried already to acess it by pressing and hold POWER UP, it returns right away to fastboot, my phone name isnt detected under device manager, nor when i do adb devices, fastboot devices detects it, and i tried already some commands like passing the TWRP to it, but it doesnt overwrite anything, sometimes i get the error"No devices or emulators found" .
Im lost i think i lost my phone, im desperate
Any expert here that can help me with this?
Im gonna try to go back to an early windows 1809, which i used to format this phone a lot to other rom
Meanwhile i need some help on this