i installed lsexposed magisk module which sent fine but then i installed Xposed-Disable-FLAG_SECURE_2.0.0.apk that caused the bootloop
i tried getting my phone into lineage safe mode (holding down volume button) i dont know if this is hte correct way to achieve it but i didnt get into a safe mode
and for some reason on 2 laptops i've tried (lenovo t480 ubuntu 22.04.2 and Lenovo t14 gen 1 ubuntu 23.04) i couldnt connect to adb when i enabled adb in lineage recovery
anyone have any suggestions? im pretty desperate because i really dont want to reinstall
latumus said:
i installed lsexposed magisk module which sent fine but then i installed Xposed-Disable-FLAG_SECURE_2.0.0.apk that caused the bootloop
i tried getting my phone into lineage safe mode (holding down volume button) i dont know if this is hte correct way to achieve it but i didnt get into a safe mode
and for some reason on 2 laptops i've tried (lenovo t480 ubuntu 22.04.2 and Lenovo t14 gen 1 ubuntu 23.04) i couldnt connect to adb when i enabled adb in lineage recovery
anyone have any suggestions? im pretty desperate because i really dont want to reinstall
Click to expand...
Click to collapse
Hello and good afternoon, @latumus Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to General Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
sorry for posting in wrong forum.
tried adb on windows 11 and macos now too no response on any (2 different cables)
2 broken usb cables what are the odds everything sorted now
Related
I unfortunately somehow managed to corrupt the android o/s on my acer liquid e.i try to boot into recovery mode and nothing shows up.there is no more screen with white type,my computer cannot find device,it shows up as unknown USB device ,it will install Adb test drivers,then it won't install anything else.is there any referrences I can draw knowledge from to try and recover,restore,or re-install android os. So my phones not useless anymore? Please anyone with any useable knowledge please post links etc.so I can fix this VERY annoying problem I have created myself.
You might try posting this in your device's forum's Q&A instead of general Android Q&A.
Eric_Eric_Eric said:
You might try posting this in your device's forum's Q&A instead of general Android Q&A.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1706918
Hi Guys,
i have been trying to unlock bootloader on my Doogee S55 phone, i have some experience with rooting phones.
But this thing.... i downloaded all the drivers for that phone all around the internet,,
when its normaly turned on, ADB command line recognise it, but when i boot to Fastboot using command (or manualy with power+voldown buttons, doesnt matter) it shows in device manager as unknown device, and when i input command to unlock bootloader it show just waiting for device, and when i input command to show connected devices nothing shows up (in fastboot, when booted normaly the device shows up fine)
my only possible explanation is that i dont have a right driver for ADB and this phone to communicate. but in instaled a tryed so many of them for span of several hours and days
i have instale minimal ADB and Fastboot, i have google drivers that comes with it and bunch of drivers for this phone nothing work
BigKjju said:
Hi Guys,
i have been trying to unlock bootloader on my Doogee S55 phone, i have some experience with rooting phones.
But this thing.... i downloaded all the drivers for that phone all around the internet,,
when its normaly turned on, ADB command line recognise it, but when i boot to Fastboot using command (or manualy with power+voldown buttons, doesnt matter) it shows in device manager as unknown device, and when i input command to unlock bootloader it show just waiting for device, and when i input command to show connected devices nothing shows up (in fastboot, when booted normaly the device shows up fine)
my only possible explanation is that i dont have a right driver for ADB and this phone to communicate. but in instaled a tryed so many of them for span of several hours and days
i have instale minimal ADB and Fastboot, i have google drivers that comes with it and bunch of drivers for this phone nothing work
Click to expand...
Click to collapse
@BigKjju
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Oswald Boelcke said:
@BigKjju
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Click to expand...
Click to collapse
thank you very much, this forum helped me many times over the years, this is the first time iam posting, and i am really angry at that phone please accept my apology and i promise i will do better next time
Hey colleagues,
I've a hardware device (no phone) that includes some kind of a MediaTek tablet with a MT8167 and Android 8.1 installed on it.
Currently I try to enable ADB in order to intercept some network traffic flows with custom apps I'd like to install.
Unfortunately the device is running a System.User App with no chance to escape.
I was able to dump the entire memory including all partitions. Then I tried to change the default props (adb enable, etc...) in the img and did a re-flash. The device boots into safe mode - but is stuck there.
I've seen that dm-verity is enabled / Android Verified 1.0 (not 2.0). So I tried to magisk on another arm Device and updated the boot.img. Unfortunately that lead to an ininite boot loop.
Do you guys have any other ideas?
I've physical access to the device and I am able to flash images back to the device.
Any help would be appreciated.
Osral
Osral said:
Hey colleagues,
I've a hardware device (no phone) that includes some kind of a MediaTek tablet with a MT8167 and Android 8.1 installed on it.
Currently I try to enable ADB in order to intercept some network traffic flows with custom apps I'd like to install.
Unfortunately the device is running a System.User App with no chance to escape.
I was able to dump the entire memory including all partitions. Then I tried to change the default props (adb enable, etc...) in the img and did a re-flash. The device boots into safe mode - but is stuck there.
I've seen that dm-verity is enabled / Android Verified 1.0 (not 2.0). So I tried to magisk on another arm Device and updated the boot.img. Unfortunately that lead to an ininite boot loop.
Do you guys have any other ideas?
I've physical access to the device and I am able to flash images back to the device.
Any help would be appreciated.
Osral
Click to expand...
Click to collapse
@Osral
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
So my company sent me a VR headset for development. I tried to update it, but upon doing so, it produced an error and bricked the VR headset. The customer support isn't helping at all, so I'm thinking of just flashing it myself (I'm new to this,).
I tried doing a factory reset, but it only showed me "No command" and reboots again. It has no SD card, and ADB can't recognize the device. The bootloader says it's locked, so I'm pretty sure it's almost impossible for me to crack it. The OS is available on the website, but again, it's almost impossible for me to replace the OS without the SD card and having it recognized by ADB.
If it's not possible to flash it, is there anything interesting I could do with it?
aoaofox said:
So my company sent me a VR headset for development. I tried to update it, but upon doing so, it produced an error and bricked the VR headset. The customer support isn't helping at all, so I'm thinking of just flashing it myself (I'm new to this,).
I tried doing a factory reset, but it only showed me "No command" and reboots again. It has no SD card, and ADB can't recognize the device. The bootloader says it's locked, so I'm pretty sure it's almost impossible for me to crack it. The OS is available on the website, but again, it's almost impossible for me to replace the OS without the SD card and having it recognized by ADB.
If it's not possible to flash it, is there anything interesting I could do with it?
Click to expand...
Click to collapse
Hello and good afternoon, @aoaofox
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
aoaofox said:
So my company sent me a VR headset for development. I tried to update it, but upon doing so, it produced an error and bricked the VR headset. The customer support isn't helping at all, so I'm thinking of just flashing it myself (I'm new to this,).
I tried doing a factory reset, but it only showed me "No command" and reboots again. It has no SD card, and ADB can't recognize the device. The bootloader says it's locked, so I'm pretty sure it's almost impossible for me to crack it. The OS is available on the website, but again, it's almost impossible for me to replace the OS without the SD card and having it recognized by ADB.
If it's not possible to flash it, is there anything interesting I could do with it?
Click to expand...
Click to collapse
when it boots up click power and vol up on the no command screen. then factory data reset and see if it will work . if not. let me know drivers dont exist for this headset for adb sideload updating so ya.
try using a usb c to usb c adaptor try putting the zip on the root of the sd or usb drive if not try making a file and call it dload.
owomushi said:
when it boots up click power and vol up on the no command screen. then factory data reset and see if it will work . if not. let me know drivers dont exist for this headset for adb sideload updating so ya.
Click to expand...
Click to collapse
where i can find adb drivers for Pico Vr neo 3?
leo6990 said:
where i can find adb drivers for Pico Vr neo 3?
Click to expand...
Click to collapse
they really dont exist because of what pico is using they are using old nexus 5 drivers for the pico recovery. and that is terrible. the best thing to do is download and install ubuntu on a spare pc. once its on the spare pc you will need to setup adb there. ince you have adb there you can run the normal adb sideload in recovery.
fyi you have 2 different kinds of headsets this is why it may or maynot fail at recovery.
pico has oem and non oem firmware and lucky we have access to this on the pico 3 website where the downloads are. the pico 3 pro on there is non oem firmware and the pico 3 link is oem firmware.
the best thing to do after this or if you need more help find my you tu be channel and contact me there i hardly check xda
recently my moto 5g stylus (xt2131-1) got stuck on something like a boot loop, it would start up and freeze on the needlessly animated moto logo. i exhausted the recovery options and was forced to factory reset to un-brick it loosing (possibly up to 100>/ 250gb) data. hoping that like a micro sd card there might still be 'ghost copies' of the data i plugged it into laptop and tried laptop recovery softwares (tried w/ wo usb debugging on), which failed to discover anything. then at the risk of corrupting the 'ghost data' reluctantly installed and ran android recovery apps which only detected new files intentionally-deleted to test their capabilities. im unaware of any other options other than to root my phone in an attempt to have it recognized by my laptop as another external hard drive to scan for 'ghost files'...aside from the handfull of recovery apps no new data was written over the (original data). ANYONE KNOWLEGEABLE IN ROOTING AND RECOVERY ANY HEADS UP OF WHETHER OR NOT THAT'LL WORK WILL BE GREATLY APPRECIATED
SINCERELY_FKD said:
recently my moto 5g stylus (xt2131-1) got stuck on something like a boot loop, it would start up and freeze on the needlessly animated moto logo. i exhausted the recovery options and was forced to factory reset to un-brick it loosing (possibly up to 100>/ 250gb) data. hoping that like a micro sd card there might still be 'ghost copies' of the data i plugged it into laptop and tried laptop recovery softwares (tried w/ wo usb debugging on), which failed to discover anything. then at the risk of corrupting the 'ghost data' reluctantly installed and ran android recovery apps which only detected new files intentionally-deleted to test their capabilities. im unaware of any other options other than to root my phone in an attempt to have it recognized by my laptop as another external hard drive to scan for 'ghost files'...aside from the handfull of recovery apps no new data was written over the (original data). ANYONE KNOWLEGEABLE IN ROOTING AND RECOVERY ANY HEADS UP OF WHETHER OR NOT THAT'LL WORK WILL BE GREATLY APPRECIATED
Click to expand...
Click to collapse
Hello and good afternoon, @SINCERELY_FKD
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator