This is a bit of a longer story, but i'll try to make it brief.
I have a samsung galaxy note 3 (SM-N9005).
A few days ago, when I was deleting system bloatware and I must have also deleted some important parts of the system.
My homescreen stopped working and i couldn't see my phone when i connected it to my pc which is running win-10 (more on that later).
Unfortunately i didn't keep any backups, yes I was reckless.
Factory resetting with my default recovery mode didn't help at all.
After some time i managed to install twrp (team win project recovery) and flashed ressurection remix 5.8.5 (unofficial version from Lord_Eko) along with Magisk and the correct Gapps.
Everything is working fine except that I cant see my sim card (thus i can't call or text anyone) and I still can't see my phone when connecting it to my pc.
I wanted to try installing some firmware for my sim card or try flashing stock firmware before my custom rom but I can't, since I have to use bootloader/download mode for that.
I tried using Odin (v3.13 and v3.09) while in download mode, but it can't see my phone. Neither can Android debug bridge when using command "adb device" or "fastboot devices" (it just says list of attached devices and nothing).
Connecting my phone normally doesn't work either. My phone isnt even listed in device manager as an unknown device.
I even tried installing samsung usb drivers, but to no avail. My phone only gets charged from my pc.
I tried all sorts of things i don't even remember now, but none of them helped.
I read something about an IMEI being deleted and when i checked my IMEI through an app it was blank, so it seems to have been deleted.
My battery also keeps draining quite a lot, but that's probably because of how old it is.
I don't know anymore info i can give, so please, how do I get my simcard to work?
Thanks for any help and sorry if I posted this in the wrong section. <3
Related
So i have a Samsung Galaxy S running Cyanogenmod Nighly 61. Since there was a new version of MIUI, I downloaded it and I flashed it using Clockworkmod. I didn't go back to the Froyo bootloaders like I usually do when I switch between MIUI and Cyanogenmod, cause I didn't want to restore all my apps and i said that if it does get messed up I could still use odin. So When Miui finished flashing I rebooted the phone but everything forced closed and nothing would work at all. So I put my phone into download mode and I opened Odin, only it didn't show the 'added' message like it usually does. So then I flashed the cyanogenmod nightly again and everything worked again, but now my computer doesn't recognise my phone anymore and neither does Odin. I've tried to install the SGS drivers that I found on my forum, but still it doesn't work at all.
Is there any way I can fix this? Thanks in advance
Please anyone?
sandeshnl said:
So i have a Samsung Galaxy S running Cyanogenmod Nighly 61. Since there was a new version of MIUI, I downloaded it and I flashed it using Clockworkmod. I didn't go back to the Froyo bootloaders like I usually do when I switch between MIUI and Cyanogenmod, cause I didn't want to restore all my apps and i said that if it does get messed up I could still use odin. So When Miui finished flashing I rebooted the phone but everything forced closed and nothing would work at all. So I put my phone into download mode and I opened Odin, only it didn't show the 'added' message like it usually does. So then I flashed the cyanogenmod nightly again and everything worked again, but now my computer doesn't recognise my phone anymore and neither does Odin. I've tried to install the SGS drivers that I found on my forum, but still it doesn't work at all.
Is there any way I can fix this? Thanks in advance
Click to expand...
Click to collapse
Think I had this problem awhile ago. but can't remember what I did.
you could try some how get them drivers. If you download them off the web or install kies and flash back to stock. but should be somewhere in the forum about this. good luck!
cyanogenmod not recognize usb
so from what i see is that you said that when you connect the phone to you're pc , you can not access the phone or the phone is not recognize in my computer. CONNECT phone to PC after pull down the notification bar from phone and tap on the tab DEBBUGIN USB and choose action portal and tools or whatever.Also go in MEMORY and see if SDCard is mounted.
I had rooted my s3 and put a custom rom on so that i could use it on tmobile. im back on verizon and i took it to get setup and now i have data and no working call or mms. Ive even reflashed different roms and still it doesnt work. I cant return it to factory because odin will not pick my phone up no mater what port or cable i use. So the guides to reset using odin are useless to me now. I have newest samsung usb drivers installed and ive already tried installing keis which also wont register the phone in download mode. What could be causing this problem with data working but no call or text ability.
another not to ad is that with every rom i have installed windows 8.1 says the usb device malfunctioned everytime i plug it in with 6 different cables that work with other phones. I checked and my imei is not bared so that is not the reason like it has been for others.
Solved,
if your story sounds similar to mine(Go to TL;DR) Refer to post 4
ok, where to begin
my N5 was A-OK just 3 days ago running the Dev Preview of Lollipop. by A-OK i mean that it worked but with a few
bugs
(its the dev preview i know, its got bugs) like when i stayed on an app, e.g spotify, and exited to the home screen it
would take like 15 sec for all the apps on the home screen (like 6) to appear. There is not where the problem lies.
Again 3 days ago. i poked around both ROM sections to find a Lollipop based on that was to my liking, found one and
directly downloaded it to my phone (in hindsite it would of been better to do it on my comp) and being no stranger
to flashing ROMs i went on auto-pilot adn begun the wiping of cache and factory resetting, setting up for the move to
more stable ROM. When it was time to flash the ROM I completely downloaded was no where to be found, a bit
panicked i went to a backup i had on the device, it did its thing and i booted it up but it went back to Clockworkmod
recovery screen That's problem No. 1 . I rebooted it still the same thing. Scouring through
the web for help on setting ADB to sideload the ROM. The thing is that when i hooked up my phone to my desktop
it didn't recognize the device, The correct drivers are installed but it doesn't recognize the device its labeled as
unknown USB device. That's problem No. 2
*update i plugged in my N5 and the comp read it as a N5 but when i selected the option to sideload it it doesn't
recognize it anymore
and problem No. 3 is USB debugging might be turned off
TL;DR? 1. Boots into Clockworkmod
2. my computers don't recognize the device
3. USB debugging might be off
-Q: Can USB Debugging be enabled some other way.
Any help is appreciated
why is it double spaced? i find it a bit eye-straining reading that much all bunched together
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Lokke9191 said:
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Click to expand...
Click to collapse
ok, used a different cable and it now recognizes it.
tried fastboot devices and nothing
tried ADB devices and numbers appeared and what state the device is in, recovery.
thank you thank you thank you sooo much
all is good
My Nexus 5 is alive,
i tried to upgrade to 5.0 directly and kept getting errors e.g archive does not have boot.sig/ system.sig. That lead me to look up Boot.sig/System.sig, that lead me to a blog saying i could fix the problem if i added something to the directory, forgot how to get to environmental variables, i went and watched the vid that helped my set up adb/sdk and thats when it clicked..
What if i tried flash-all with KitKat and voila it started running the process of flashing. Since it was basically a new phone unrooted and everything it had the system update to lollipop.
I have a rooted S7 with TWRP recovery on it and i recently deleted my OS by accident as i was just trying to reset my phone to factory settings. Now the only thing i can do is boot into recovery mode and download mode, or i can just get stuck at a boot loop.
I have googled and googled and seen so many ways to try and fix this issue but nothing has worked for me. Heres a list of the issues i have and what i've tried so far. [Using Windows 10]
Installing Odin (3.12.3) and stock Samsung firmware from here.
Installing the necessary USB drivers from here.
My PC wont recognize my samsung device in either modes (recovery/download) and Odin wont recognize my phone either, as well as i cant find anything under "Device Manager".
Tried using ADB to transfer files to my S7 but when i activate ADB in recovery mode it just loads for a couple of seconds until it displays an error with no explanation.
I even tried downloading ADB drivers and necessary tools i got from this guide.
I also tried wiping Dalvik cache and cache.
I have tried three different USB cables on all available USB slots on my desktop PC and the one USB slot in my Surface and nothing works.
I have tried rooting previous phones but I'm still new to this rooting thing and there's a lot i don*t understand. Perhaps i downloaded the wrong USB drivers, or maybe I'm just unlucky. I just really need some help to understand how to fix this. If it can't be fixed is it possible to remove all traces of rooting on my phone?
The phone needs to be in Download Mode to use ODIN
The only sign it is connected is a COM port lit up at the top of the ODIN window
Add the .MD5 ROM to AP and hit start
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.