Related
I have the LG G2 D800 (AT&T), my phone is completely wiped and all I can do is get into TWRP and ADB is not recognizing my phone. Is there any other way I can push files to the sd card (it's non-removable)? I'm not sure exactly what the ADB sideloader is in TWRP or how it works but even if I try to run it, it never gets past "Starting ADB sideload feature....."
Thank you in advance for your help :fingers-crossed:
In TWRP you can go to "Mount", select "sdcard" and then Mount USB Storage.
cmg178 said:
I have the LG G2 D800 (AT&T), my phone is completely wiped and all I can do is get into TWRP and ADB is not recognizing my phone. Is there any other way I can push files to the sd card (it's non-removable)? I'm not sure exactly what the ADB sideloader is in TWRP or how it works but even if I try to run it, it never gets past "Starting ADB sideload feature....."
Thank you in advance for your help :fingers-crossed:
Click to expand...
Click to collapse
When I try to mount USB OTG, error message unable to mount '/usb-otg'
And when you are in TWRP you can't access the device via ADB right? So my only suggestion is to put your phone into fastboot.
To do that go into TWRP->Restart->Bootloader. In your computer check the device with "fastboot devices".
I'm not very familiar with fastboot, so you need to search a little for this. Good luck
I'm running v2.6.3.2 and the only options are to boot into recovery or system, system just stays on the LG logo though. I was hoping there would be a way to use the ADB sideload feature in TWRP or use the terminal commands
Ok I was able to use this terminal command to restore the stock ROM
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
and everything is working, never again will I underestimate the importance of backups!!
cmg178 said:
Ok I was able to use this terminal command to restore the stock ROM
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
and everything is working, never again will I underestimate the importance of backups!!
Click to expand...
Click to collapse
yes thats work fine thaks
Tried the terminal command since I havea similar problem. It seems it extracted some files but i still cannot load the stock rom. Are there any steps I am missing?
I have the same phone and the latest version of TWRP installed. ADB is commencing but not starting.
mtayabkk said:
yes thats work fine thaks
Click to expand...
Click to collapse
Have you installed adb driver... i ever have problem same like u and my friends recommand to install universal adb driver to use adb command... thats working perfectly in my devices... good luck
Sent from my PICOpadGCE
No rom install lg g2 ls980
fresti said:
Have you installed adb driver... i ever have problem same like u and my friends recommand to install universal adb driver to use adb command... thats working perfectly in my devices... good luck
Sent from my PICOpadGCE
Click to expand...
Click to collapse
Hi Guys!
I forget to make backup and now there is no ROM install in my LG G2 LS980. I am currently using TWRP 2.7.0 recovery. The problem is USB-OTG not mounting and i think because of this issue i also can't able to install ADB Drivers as in PC device manager there is no drivers showing their even i tried Universal ADB drivers. Can anybody help me how to install ROM in my G.2 The ROM which was installed in my phone was Cloudy G3. I tried almost every trick and procedure but failed to recover my ROM.
Kindly help me in this matter. Thanks in advance
Regards
Bilgramiz
I am working on a CM11S port and need to be able to pull a logcat since it loads the boot animation but won't load any further as of now. Any advice would be great.
TekGadgt said:
I am working on a CM11S port and need to be able to pull a logcat since it loads the boot animation but won't load any further as of now. Any advice would be great.
Click to expand...
Click to collapse
You can launch your adb logcat from the (custom) recovery then reboot normally.
Primokorn said:
You can launch your adb logcat from the (custom) recovery then reboot normally.
Click to expand...
Click to collapse
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
TekGadgt said:
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
Click to expand...
Click to collapse
'adb devices' command doesn't recognize your phone? Are you sure that your ADB setup is correct?
BTW we need a custom recovery to use adb commands.
Primokorn said:
'adb devices' command doesn't recognize your phone? Are you sure that your ADB setup is correct?
BTW we need a custom recovery to use adb commands.
Click to expand...
Click to collapse
No it doesn't. I have read about the issue but haven't found a real fix. And I know I need a custom recovery, I mentioned that I had tried CWM, TWRP, and Philz Touch.
TekGadgt said:
No it doesn't. I have read about the issue but haven't found a real fix. And I know I need a custom recovery, I mentioned that I had tried CWM, TWRP, and Philz Touch.
Click to expand...
Click to collapse
So fix your adb setup. The only tool that allows a logcat from boot is adb AFAIK so there's no other choice.
Primokorn said:
So fix your adb setup. The only tool that allows a logcat from boot is adb AFAIK so there's no other choice.
Click to expand...
Click to collapse
I fixed my adb setup but still can't seem to get a logcat starting in recovery
TekGadgt said:
I fixed my adb setup but still can't seem to get a logcat starting in recovery
Click to expand...
Click to collapse
adb devices is working?
You can also use DDMS: http://developer.android.com/tools/debugging/ddms.html#logcat
Primokorn said:
adb devices is working?
You can also use DDMS: http://developer.android.com/tools/debugging/ddms.html#logcat
Click to expand...
Click to collapse
Yes adb devices is working. And I might look more into DDMS.
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?
lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!
lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?
berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Wow what a difference DATA2SD and ROM2SD make!
lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW
lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?
lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...
Hi,
I try to made my own boot.img for the z3 but it's bootloop. I can't access to recovery or adb.
My boot create log on the phone but how access to read them ?
I try to flash a boot.img that work properly but i can't access to my logs. (they are delete probably)
Any idea for debugging ?
Thanks for all
Thomas
Copied from stackexchange (google is your friend):
There's a couple of ways to do this:
cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt
dmesg > /sdcard/kernel_boot_log.txt
plug in the usb cable with the smart-phone switched off. Then issue the command adb logcat from your Windows cmd or Linux terminal, it will hang waiting for the device to come on-line, now power up the smart-phone. The logcat should start scrolling off then.
Click to expand...
Click to collapse
Original thread: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Cheers.
Omario-242 said:
Copied from stackexchange (google is your friend):
Original thread: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Cheers.
Click to expand...
Click to collapse
hi, thanks for your answer. Like i told you in my previous message i can't access to adb. I'm stuck at the sony logo and there is no adb logcat at this moment.
Thomas
You still should be able to either read out dmesg or last_kmsg.
Those are kernel related logs and should help you find the cause of your bootloop.
Omario-242 said:
You still should be able to either read out dmesg or last_kmsg.
Those are kernel related logs and should help you find the cause of your bootloop.
Click to expand...
Click to collapse
ok, but how ? I only got fastboot available
You could try to boot a recovery.img using fastboot and then getting the logs, but
I seriously don't know if the logs get deleted if you boot with another recovery.
Omario-242 said:
You could try to boot a recovery.img using fastboot and then getting the logs, but
I seriously don't know if the logs get deleted if you boot with another recovery.
Click to expand...
Click to collapse
I can't access to recovery too
thelittlefireman said:
I can't access to recovery too
Click to expand...
Click to collapse
Yeah if you are in fastboot mode you can type "fastboot boot recovery.img" with "recovery.img" being a working recovery.img file in the directory/folder of your fastboot/adb command line on your PC.
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
jwoegerbauer said:
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
Click to expand...
Click to collapse
Will this work if debug mode is not enabled? And I don't know if bootloader is unlocked
ADB only works if USB debug got enabled: should be obvious.
BTW: FastBoot only works if OEM unlock got enabled.
jwoegerbauer said:
ADB only works if USB debug got enabled: should be obvious.
Click to expand...
Click to collapse
I don't know if it's enabled, as I said this isn't mine. Any way to check?
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
jwoegerbauer said:
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
Click to expand...
Click to collapse
I get this result:
List of devices attached
JAD82015000614 sideload
but if I try to use the second line of code I get:
error: closed
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
jwoegerbauer said:
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
Click to expand...
Click to collapse
it gives me back the same error when trying "adb usb"
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
It's not worth for this phone, thanks for your time, if you have other ideas let me know
TunguskaMed said:
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
Click to expand...
Click to collapse
That's how I solved the issue. I called the Wiko assistance and I asked for the stock firmware because of boot looop. They sent me an exe wich did all by itself and now the phone is fully working. That was easy after all!