Related
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 everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
RacerBas said:
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
Click to expand...
Click to collapse
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
bp328i said:
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
Click to expand...
Click to collapse
If I had I wouldn't be here
RacerBas said:
If I had I wouldn't be here
Click to expand...
Click to collapse
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
bp328i said:
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
Click to expand...
Click to collapse
That's what I tried but it came up with what's shown in the screenshot
RacerBas said:
That's what I tried but it came up with what's shown in the screenshot
Click to expand...
Click to collapse
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
bp328i said:
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
Click to expand...
Click to collapse
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
RacerBas said:
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
Click to expand...
Click to collapse
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
bp328i said:
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
Click to expand...
Click to collapse
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
RacerBas said:
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
Click to expand...
Click to collapse
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Good luck man, I've got to get back to work.
I know the adb push "ROM/File.zip" /sdcard works because I tested on my phone prior to posting.
One last thought is your SDK might need to be updated as well.
bp328i said:
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
Currently trying it on my laptop which has a fresh reinstall, removing the drivers completely will take too long.
Your driver saw it as a google galaxy nexus adb Interface, when I used adb devices it didn't see it.
EDIT: when I go to reboot it says that there is no os installed so yea...
Another Edit: I will try this driver when I get home and report back. OnePlus adb drivers windows
I managed to fix it using the oneplus one toolkit by manudroid
my pixel two screen died.. google backup restore joke service failed to restore sms or app setting to new phone. i need to grab that data from the old phone but cant see or use the screen, phone is not rooted and adb debugging not enabled. and i am not much more than a novice ahhhhhh!
The same happened to me. Try using vysor in pc. It shows your Mobile screen on pc. It worked for me. You dont need to install vysor n your mobile. Pc verion will auto install it on your device.
itsfaiez said:
The same happened to me. Try using vysor in pc. It shows your Mobile screen on pc. It worked for me. You dont need to install vysor n your mobile. Pc verion will auto install it on your device.
Click to expand...
Click to collapse
I tried vysor but it says ADB debugging has to be enabled
frankygoes said:
I tried vysor but it says ADB debugging has to be enabled
Click to expand...
Click to collapse
do you have recovery installed
itsfaiez said:
do you have recovery installed
Click to expand...
Click to collapse
yes. phone was rooted then got unrooted with ota upgrade to 11
frankygoes said:
yes. phone was rooted then got unrooted with ota upgrade to 11
Click to expand...
Click to collapse
is oem unlocked. if unlocked boot to download mode and install twrp for ur device boot into twrp i will givee access to your files
itsfaiez said:
is oem unlocked. if unlocked boot to download mode and install twrp for ur device boot into twrp i will givee access to your files
Click to expand...
Click to collapse
i cant see anything. so how would i boot into twrp?
or if anyone have the same model try to change the screen and use it and then return it
frankygoes said:
i cant see anything. so how would i boot into twrp?
Click to expand...
Click to collapse
shutdown device ( power + volume down).
power button + volume up WILL BOOT TO RECOVERY
did it work
you said boot to download or recovery?
frankygoes said:
you said boot to download or recovery?
Click to expand...
Click to collapse
if you have twrp intsalled boot to recovery it will give ccess to ur files
thanks for the help but im not sure if I had twrp after all . no matter what i can't get past the adb device "unauthorized" state. turns out the pixel2 is unique in not supporting usb-c to hdmi - thanks Google. i tried unified toolkit and vysor. next thing i might try is a hammer and send the pulverized phone back to Google.
frankygoes said:
thanks for the help but im not sure if I had twrp after all . no matter what i can't get past the adb device "unauthorized" state. turns out the pixel2 is unique in not supporting usb-c to hdmi - thanks Google. i tried unified toolkit and vysor. next thing i might try is a hammer and send the pulverized phone back to Google.
Click to expand...
Click to collapse
ok
I have samsung galaxy A525f and I'm trying to install TWRP on my phone. My phone currently running Android 12.
I use Odin to install TWRP
when I install TWRP V.3.5.x, It says success but nothing happens! It loads old boot.
But when I install TWRP V. 3.6.x , It says success but It crashes the phone! No OS, just blue Download page with a red notice!
I downloaded from https://dl.twrp.me/a52q/
I used the latest version of Odin and samsung drivers
Follow the installation instructions on the XDA thread: https://forum.xda-developers.com/t/...wrp-3-6-for-galaxy-a52-4g-and-a72-4g.4405751/
Simon1511 said:
Follow the installation instructions on the XDA thread: https://forum.xda-developers.com/t/...wrp-3-6-for-galaxy-a52-4g-and-a72-4g.4405751/
Click to expand...
Click to collapse
I accidentally locked the bootloader and now the long press vol + option to unlock bootloader is gone!
How can I unlock it again?
parsa_foss said:
I accidentally locked the bootloader and now the long press vol + option to unlock bootloader is gone!
How can I unlock it again?
Click to expand...
Click to collapse
You'll likely need to turn on OEM unlock in developer settings again.
Simon1511 said:
You'll likely need to turn on OEM unlock in developer settings again.
Click to expand...
Click to collapse
It's on in setting but it doesn't appear in download mode
Simon1511 said:
Follow the installation instructions on the XDA thread: https://forum.xda-developers.com/t/...wrp-3-6-for-galaxy-a52-4g-and-a72-4g.4405751/
Click to expand...
Click to collapse
I successfully installed TWRP but when I try to install LineageOS, adb won't show the device!
parsa_foss said:
I successfully installed TWRP but when I try to install LineageOS, adb won't show the device!
Click to expand...
Click to collapse
Is your phone in sideloading mode? (It should be under "Advanced" in TWRP).
Simon1511 said:
Is your phone in sideloading mode? (It should be under "Advanced" in TWRP).
Click to expand...
Click to collapse
Yes.
It doesn't show device only in sideload mode!
I tried adb push too. It says successful but when I rebbot it, it boot in TWRP again!
parsa_foss said:
Yes.
It doesn't show device only in sideload mode!
I tried adb push too. It says successful but when I rebbot it, it boot in TWRP again!
Click to expand...
Click to collapse
Did you format data before booting? If no, do that and see if that fixes your issue.
If you already formatted it flash this after flashing lineage and format data again.
Simon1511 said:
Did you format data before booting? If no, do that and see if that fixes your issue.
If you already formatted it flash this after flashing lineage and format data again.
Click to expand...
Click to collapse
I formatted data, installed lineage, installed service Disabler then formatted data again and nothing happened. It booted in TWRP again.
parsa_foss said:
I formatted data, installed lineage, installed service Disabler then formatted data again and nothing happened. It booted in TWRP again.
Click to expand...
Click to collapse
Then you did something wrong. Try to start over from the beginning.
Simon1511 said:
Then you did something wrong. Try to start over from the beginning.
Click to expand...
Click to collapse
I followed the video and it worked!
Thanks very much
Hello,
my poco x3 nfc boots in rmain menu of the recovery mode and stucks there. Reboot ends up again the recovery mode. Maybe its because I uninstalled "com.miui.guardprovider"?
How can I install it back again while in the loop?
Is it possible to access my data from there like pictures and files or even get out of this loop?
sebflex said:
Hello,
my poco x3 nfc boots in rmain menu of the recovery mode and stucks there. Reboot ends up again the recovery mode. Maybe its because I uninstalled "com.miui.guardprovider"?
How can I install it back again while in the loop?
Is it possible to access my data from there like pictures and files or even get out of this loop?
Click to expand...
Click to collapse
If the bootloader is unlocked use: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
If the bootloader is unlocked use: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
debugging is disabled somehiw and I have no option to enable it without accessing my phone.
sebflex said:
debugging is disabled somehiw and I have no option to enable it without accessing my phone.
Click to expand...
Click to collapse
Ok I understand that you can't reinstall what you deleted with ADB, but did you unlock the bootloader?
NOSS8 said:
Ok I understand that you can't reinstall what you deleted with ADB, but did you unlock the bootloader?
Click to expand...
Click to collapse
No
sebflex said:
No
Click to expand...
Click to collapse
you can try with recovery and MIassistant.
How many menu on recovery 3 or 4?