Related
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hey guys, new member here but been a lurker off and on for awhile.. not sure what to do, you guys are my last hope.
I have a Samsung Galaxy Core Prime from straighttalk. Android version is 4.4.4 (I think).
Anyway, I was screwing with it trying to speed it up using a few apps I downloaded from the store, the apps let you uninstall apps that the normal manager won't let you and manage what system apps are allowed to run at startup..etc. also I was messing with applock and phone encryption.. So I'm not sure what messed things up.
Well needless to say, I shoulda been more careful, because now my phone is screwed! I can't view my home screen at all so can't call/txt and can't access my settings to try to fix the problem..
Before people tell me to reformat it, I have tried 100 times.. I press volume up + power + home to get to bootloader and tried doing a full reformat as well as wiping the cache partition... Reboot phone the setup screen comes up asking for my name/google account..etc but I can't complete it, it always crashes sayin either "hangouts has stopped working" "setup wizard stopped working" or something about a android.keyguard service.
So next I jumped on Google and read to try the Kies software but I can't for life of me get it to detect my phone.. took awhile but I think I got all the drivers installed.. kies will just say it's connecting to my device but never does. Tried kies 2 and 3 and different cords, I think it's because android isn't even truly fully installed since the setup wizard crashes.. so the MTP capability isn't even there.. under my computer I don't see my phone either like I use to, just a blank drive that has no name and can't be accessed.
So then after more reading I decided to try "ADB sideloading".. I'm a newb is to this stuff so idk if I even did it right but hooked usb up went into bootloader and reformatted/cleared cache then I went to ADB and using cmd on my pc I tried to send a zip of cyanogenmod (got it on xda, suppose to work on galaxy core prime) and it said it was successful but it doesn't do anything.. so idk if it's cuz u can't use custom roms with the stock bootloader? I read about other Rom managers but how am I suppose to install them?
if a stock firmware will work, where can I find one?
Sorry for the wall of text, I'm just stuck here and wanted to add everything I could think of that I tried already.
I dont think it's a physical hardware problem, I think i just screwed some system files up somehow which screwed up the recovery partition..
Extra note:
I am able to use the internet browser though, when the setup gets to the step to link your google, in the top right I can go to "enter browser signin" and then I can bypass the fact there's no search bar by clickin privacy policy and clicking a logo to bring me to Google's homepage.
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Mr.cryptkeeper said:
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Click to expand...
Click to collapse
Get a custom recovery (preferably twrp) and then wipe EVERYTHING in the wipe section except your sdcard and then just adb sideload cyanogenmod or any other CUSTOM rom for your phone.
You should just be able to reload the original firmware with Odin. Or Kies will probably work, but you have to use Download Mode to be able to restore it, not while it is booted into the OS.
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Mr.cryptkeeper said:
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Click to expand...
Click to collapse
Yes you have to be in recovery to actually be able to do adb sideload, try adb reboot recovery.
March 22 2019 - Solved because I'm an idiot. Story on page 2
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
What I need help with:
Adb communicating with Fastboot
How far I got:
Unlocked bootloader (unlock symbol when booting)
Installed plethora of Adb Driver's via Google, Xiaomi, Qualcomm
Used USBDeview to uninstall all drivers even from my past devices and try reinstalling just drivers involving Xiaomi, Poco ect...
What does work:
Adb commands recognized in Miui
Adb commands recognized in Miui Recovery as sideload (after selecting pc suite option)
Miui unlocking tool (was able to unlock and can still detect the device unlocked in Fastboot)
In Miui File Transfer & PTP mode
What I tried:
Different USB ports 2.0 & 3.0 directly in the back of the PC and the front hub
Different USB C cords with and without extension cord (even though that shouldn't matter)
Different drivers old and new
Powershell & CMD as administrator.
What's already been done before you suggest it:
2nd computer, different ports, satanic ritual, different cords, turning PC on and off again after driver installs.
Trying methods from First 5 results when you Google anything along the lines of "Poco f1 adb Fastboot not recongnized"
Uninstalling drivers and retrying
USB Debugging on, duh.
Oem unlock on, duh.
Basically it's this, clearly the device is being recongnized and being talked to, just able to unlock the device via Xiaomi unlock tool is proof enough of that it's detected in and out of Fastboot, but in a adb window via powershell or cmd-here, it's just not recongnized my device in Fastboot. In Miui or recovery theres no issue, they communicate fine.
Or if there's an alternative way to install TWRP that doesn't involve Fastboot I'm all ears on that.
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
I want the recovery so I have an option that isn't miui.
My phone isn't slow, but it's running more than a fair share of mi bloat.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Also can you roll back to 8.1 without twrp, root, or adb?
I tried rolling back via the update screen and selecting the package/downgrade, but Miui won't allow installing/flashing older software, which is something I tried before.
No one else has this problem?
Chocolina said:
No one else has this problem?
Click to expand...
Click to collapse
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
tnsmani said:
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
Click to expand...
Click to collapse
Don't you need TWRP to install root?
I haven't rooted 1st and then did recovery since the Nexus 5 days, every device I've had since has had root guides that wanted me to fastboot flash the recovery first and install root that way.
And i dont know if my pc is Ryzen, not a pc gamer so all I have is on board, but it is old amd machine running windows 10. I also don't have a monitor these days, I have my pc setup to accept remote desktop so I interact with it that way because it's rare I need a pc these days
All I know is adb works with miui and recovery (sideload) fine, it's fastboot giving me problems, and all the root guides require fastboot
Also same exact issue regarding my mi pad I just got too
https://forum.xda-developers.com/mi-pad-4/help/please-help-troubleshoot-xiaomi-t3910249
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Tell me more about this Linux/your method
I never used Linux, so I don't know what I'd do to get it or if I could boot it temporarily off of another form of storage or something.
Chocolina said:
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
Click to expand...
Click to collapse
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Dose the roms solve touch issue???????
MasterFURQAN said:
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Click to expand...
Click to collapse
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Chocolina said:
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Click to expand...
Click to collapse
If it's more than 5 years old, then it's not ryzen. Fyi Ryzen is the newest range of CPUs from AMD.
I went out and bought an Intel laptop and it still won't work!!
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Chocolina said:
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Click to expand...
Click to collapse
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
tnsmani said:
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
Click to expand...
Click to collapse
It was a headache because my precautions weren't working. Next time I'm just going to check if it'll take flash commands anyway before asking for help.
On the plus side, I got to learn what a laptop made by RCA is like. It's **** sure, I'd expected as much, but it was as bad, if not worse than those $99 "windows 8" tablets from 2014-2015 running those archaic Intel Z3735 Atom series processors. Stay away
TL;DR Samsung s10e, stock Android 10, soft-bricked itself during security update. Want photos. Starts reliably in Android Recovery Mode. Can't see from PC - nothing from cmd window with ADB either.
My Samsung s10e (US, Verizon) soft-bricked itself a couple days ago. I wanna grab my photos before factory reset / flashing the OS. It starts in Recovery Mode, and Samsung includes a "mount /system" option, but I haven't found a good description of what that does. Anyways, I've tried to plug it in via USB to both Win 10 and Ubuntu, but neither see the device at all (not in Device Manager as Unknown Device for instance, just nothing).
I have computer expertise, but not with Android, so I tried following some tutorials and downloaded ADB. I made sure the s10e drivers were installed on my PC as well. When I run "adb devices" the list is empty. I downloaded Google USB Driver, but it appears like I am supposed to install that on the phone, not on the PC, so that's no help right now. I came to realize that I needed the phone to have a custom recovery tool previously installed. I also came across this thread, but it's 6+ years old so I was a little wary of following the advice. What am I missing to be able to connect through ADB, is that thread still valid, is there an easier way? Is there another way to mount the device and navigate the files through my PC? If I could just magically go to C:\Android and press copy/paste, that's all I need. Any other suggestions - like a magic way to fix the initial problem without clearing my data?
Bonus Question: what does "clear my app data" do? Should I try that, or will I lose my native photos? I'm okay losing the Snapchat/Facebook ones for the sake of getting the rest. Booting in Safe Mode is currently not helping, but the debug menu suggests that may help it (doubtful) to do the clear.
Any advice would be greatly appreciated!
P.S. I did also find this thread which dampened my hopes a bit....but some of the answers seemed slightly conflicting
Edit: btw, I think I might have turned on developer options at some point, but not sure if I ever turned on USB debugging. Not sure if that matters now or not. Otherwise, the phone is completely non-custom.
Hi, I've got a 7.1 which recently became unresponsive. I think I've tried the basic stuff, but I'm out of my league with this phone.
Screen is black and I always thought it just wasn't powering up because the battery was dead but after messing around I found windows seems to be able to mount/dismount because I hear the sounds sounds and device manager shows a QUSB_BULK device and the yellow triangle! symbol. I tried looking for drivers, but thought it's PNP.
ADB devices comes back with nothing, so maybe it's a driver thing, but it was a generic PNP device before and I don't think that would have changed.
I'd really like to wipe the phone, but I've exhausted all the options I know of.
I also don't want to install any non-official firmware because there may be a chance this could get sent in if any wipe/reset attempts aren't successful.
Is there a guide I could use? I think it's a bad sign that ADB can't even locate the device.
FWIW, I likely had developer option enabled, but can't say for sure. I can't unlock the phone now because I can't see anything. I've tried a bright light to see if it's a backlight issue but couldn't make out anything.
Is there any chance a screen protector could have caused a problem? It's got one and I haven't removed in the event it can be woken up...
Thanks
I'm wondering if I've got a bad adb, I tried two other devices, one LG which is stuck in a reboot loop and a zte which boots. In all cases the adb I'm using shows no devices with a
Code:
adb devices
running on win10 with adb found in platform tools r32.0.0.
Are you sure you have ADB enabled in developer settings?
Andrive said:
Are you sure you have ADB enabled in developer settings?
Click to expand...
Click to collapse
Not 100%, but it is something I normally would do for the rare occasion where it's needed.
Are there options to reset/update if adb isn't enabled? I'm pretty sure update is no, but I'm not sure about reset.
I think I've exhausted all options to get this this back myself and will likely see what Nokia charges to bring it back...