Related
I just installed RomManager because I wanted to make a backup of my current ROM before trying to play around.
After installing it, I clicked the button to make a backup, and it told me I needed to install ClockworkMod, and I clicked Okay. So it downloaded that mod, rebooted, and now my phone is practically dead.
I mean, it works as a phone and all, but here's the problem:
WLAN stopped working
adb shell does not work
making a local session in ConnectBot doesn't work
doing *anything* in RomManager just does *nothing*
I can still use it as a "phone" to write messages and call people. But I can't do anything else now.
So I tried a factory reset.
This only made things worse.
I now cannot use the market to install apps - it just won't connect, and time out.
Internet works however.
I cannot open a shell in adb shell.
I have no idea what's going on. It feels however like rommanager removed the execution rights of all my files in the filesystem - it would at least explain why I cannot run a shell...
I need help please!!! :'(
Edit:
I just hope that when the official froyo update FINALLY comes, it fixes the problem :/
Edit2:
Okay, after using the factory reset from the settings menu instead of recovery boot mode, I can log into the market again...
WLAN still doesn't work though... so I'm back to where I was before the first factory reset.
Not that I know a lot about this, but if you can still get to download mode, I'm sure you could probably flash the phone.
Follow these instructions h**p://forum.xda-developers.com/showthread.php?t=790686 (replace the ** with tt)
Good luck.
What if I'd like to keep the branded version?
Mainly to make sure I can upgrade to the "correct" branded froyo later using Kies :/
Or do you think the registry hack would work for that?
Edit:
i think I can live without wlan for a few days...
Either there is an update available then, officially, or I'll go to the next Drei shop and ask if they can give me the firmware files :S
or flash it for me...
Otherwise I'll have to take the risk of flashing the JPM...
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
My Evo gave me grief for a solid hour when I first got it. Followed the walkthrough here and one of the contingency plans worked like a charm.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Thanks, but it is not a driver problem as the drivers are installed correctly and ADB can see the phone connected.
I tried on 3 different PC's, replaced US cables. everything failed.
I think something is up with my unit which will be going back tomorrow.
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
So it worked fine before you rooted it?
Yes, SuperOneClick is using ADB to push the root files, so i assume ADB worked then.
I am also getting constant device reboots (random) so i think there is a hardware problem. i'll take it back tomorrow.
I had drivers installed, but the set of drivers PDAnet ended up installing for me fixed the issue. Till I get my paycheck, I won't be able to play with it
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
I am now on my 4th phone - so will be waiting for things to simmer down before I go back to modding again, but the other 3 have all had the same issue after using the superoneclick to root.
Once root is done all ADB access goes away. Something is amiss.
edit: More specifically my 4th atrix.
airbillion said:
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
Click to expand...
Click to collapse
I ended replacing the phone as I had other problems with it. Now a adb works fine even after root.
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
SNadler said:
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
Click to expand...
Click to collapse
It does not solve the problem.
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
airbillion said:
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
Click to expand...
Click to collapse
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
clubtech said:
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
Click to expand...
Click to collapse
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
airbillion said:
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
Click to expand...
Click to collapse
I tried restoring my device to factory default several times. It did not solve the ADB problem and not my random reboot problem (even with zero 3rd party apps installed).
I tried installing ADBWireless from the market - no go.
I googled and found a command to run via local terminal to force ADB to stay up - no go.
I finally came to a conclusion that a) I have bad hardware because my device was rebooting b) i can't fix the ADB problem without a full SBF file which we don't have.
Went to at&t, got it replaced. no more reboots. rooted with superoneclick and did not do the sideload fix from that app.
Then i manually edited the settings.db file to allow sideloading and been running fine ever since.
Clubtech,
Thanks for the file! It works for me!
Here is a post on the fix: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1
Can anyone explain this for a noob? i just want aRoot to work and the HDMI cable thing to work... the oneclickroot worked but nothing else will and i think it is because ADB is not recognized...
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
see post 4
see post 4
see post 4
d802 int
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
kye1987 said:
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
Click to expand...
Click to collapse
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
XxZombiePikachu said:
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
Click to expand...
Click to collapse
Cheers I'll see if the supermarket has them at a half reasonable price, otherwise ebay has them for £1 delivered and I'll have to wait. Thanks for the reply and confirmation that would work though.