Related
having trouble with ADB
i sold my nexus one, so my computer is setup for ADB devices but for some reason it doesn't find the vibrant...also tried to root using method in android developement and it didn't work
any ideas?
Going to assume that your phone is rooted. Go into settings -> applications -> development and make sure that USB debugging is enabled as well as Allow mock locations
then try it in ADB and it should detect your Vibrant.. make sure that drivers for the phone are also installed
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
fordstang99 said:
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=728929 Those drivers.
And uhm.. I don't know if it needs root to use ADB but it would make sense to be rooted so you can have ADB without any restrictions.
Was USB debugging enabled?
ok well i put the update.zip file on the root of the internal memory and hold down the volume up and down and it just boots normally
ok adb is working....i didn't see those drivers thanks
now just the update.zip, cant seem to get into recovery, i geta Downloading....Do not turn off target !!!
ok got everything working
thanks
Same Problem USB DEBUGGING
I just want to be able to use the USB Debugging feature. Is this something that is unly available with root? If so then I have no problem, if now I am not able to have the pc detect my Vibrant when in USB Debugging mode. It will connect without it so I'm curious as to my first question. I am not rooted, but plan to soon.
Thanks for any help
CRX
[EDIT]: Phone rooted and still have same problem!!!
Any help would be appreciated!!
Crx
bump for assistance
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
crxforya said:
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
lqaddict said:
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
Click to expand...
Click to collapse
I dont know what ur talking about. Nobody on this thread said anything about winblues???
ISprayCandy said:
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Click to expand...
Click to collapse
Thank you for this info, ill give it a shot
crxforya said:
I dont know what ur talking about. Nobody on this thread said anything about winblues???
Click to expand...
Click to collapse
crxforya said:
I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
you need winblues drivers for sammy, search for samsung kei software
The updating of my SDK made the difference. I was able to install the correct driver and now ADB is working smoothly again. Thanks for all your help.
Crx
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.
x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.
USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.
Mind telling me what you did, im stuck in the same situation
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26
Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server
EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?
It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!
jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.
Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?
myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers
I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.
how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.
Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:
leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.
did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:
Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.
Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
nm8 said:
Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
Click to expand...
Click to collapse
Did you tried flash stock+Unroot (Device is on/Normal ) mode ?
KrilanPL said:
Did you tried flash stock+Unroot (Device is on/Normal ) mode ?
Click to expand...
Click to collapse
yes, but it does not work because the software says it needs USB debugging enabled... but I can't boot to android
Hi try this i watched in you tube. Mine was stuck in bootlop after ota to 4.4. I hope this will help you and sorry if i am wrong about it. http://m.youtube.com/results?q=return to stock nexus 7&sm=3
Sent from my MB855 using xda premium
deny_kei said:
Hi try this i watched in you tube. Mine was stuck in bootlop after ota to 4.4. I hope this will help you and sorry if i am wrong about it. http://m.youtube.com/results?q=return to stock nexus 7&sm=3
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Hi
thanks for the link, good informations there, but I already solved the problem by using MSKIP's software.
Thanks for helping though...
nm8 said:
Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
Click to expand...
Click to collapse
Hi I recently bricked my nexus 7 too and unbricked it myself. there aren't a lot of people willing to help here as I know, and I know I can help you. First thing first, there is noway you can brick your nexus 7, no matter what you have done, so just clam down.
to unbrick your nexus 7, there is what I suggest you to try>
1, download fastboot, adb. make sure they are the newest version.
2, download recovery-clockwork-touch-6.0.4.3-grouper. this is a recovery img that you install into your nexus 7
3, get Google android USB driver!! uninstall every before you install this!!
4, put your neuxs 7 into boot loader mode by holding about 3 buttons.
5, connect your nexus 7 to your PC
6, If you are a windows using, using command prompt "fastboot.exe devices"
7, something should come up. then you are in the right track.
8, type fastboot.exe flash recovery recovery-clockwork-touch-6.0.4.3-grouper
9, you should get a message saying everything is install correctly.
10, using vol down to go the recovery mode on your device. The CWM should be installed!!!
11, Download any android ROM for nexus 7, and simply install it using CWM!!
12, Adb doesn't work on me because I can't get into USB debug mode. You have to use an OTG USB cable. Copy the ROM to an USB driver and connect that USB to your nexus using this OTG USB cable.
13, install!!! done!!!
nm8 said:
Hi
thanks for the link, good informations there, but I already solved the problem by using MSKIP's software.
Thanks for helping though...
Click to expand...
Click to collapse
Could you elaborate a little more on what step you picked from the main menu of that software? I'm not having any luck getting my Nexus fixed.
Posted my thread for help here http://forum.xda-developers.com/showthread.php?t=2560975
Guess I will try megapig's suggestions next. I've tried so many procedures and none of them are working.
EntityPacket said:
Could you elaborate a little more on what step you picked from the main menu of that software? I'm not having any luck getting my Nexus fixed.
Posted my thread for help here http://forum.xda-developers.com/showthread.php?t=2560975
Guess I will try megapig's suggestions next. I've tried so many procedures and none of them are working.
Click to expand...
Click to collapse
I just uninstalled all the crap that the other software installed, then on MSKIP's software, I chose no. 1, then after that, I installed stock, can't remember the number but it is there...
Thanks, I did manage to get it fixed last night. Posted update in my thread.
Whew
Hey guys,
I have some troubles getting update for my G9006v. Until couple months ago I thought it is G900F but as soon as I decided to flash my phone I realized it is a G9006V and somehow merged with 2 frame-ware. The actual question is, could I use any other Rom like Cyanogen 14.1 and in case it was buggy could I downgrade to my original Rom?
Thank you
birdenemedir said:
Hey guys,
I have some troubles getting update for my G9006v. Until couple months ago I thought it is G900F but as soon as I decided to flash my phone I realized it is a G9006V and somehow merged with 2 frame-ware. The actual question is, could I use any other Rom like Cyanogen 14.1 and in case it was buggy could I downgrade to my original Rom?
Thank you
Click to expand...
Click to collapse
Yeah, you can try. Always have a backup!
Cyclic01 said:
Yeah, you can try. Always have a backup!
Click to expand...
Click to collapse
Thank you Cyclic01. As I know there is no way to root my device, considering that, which program do you recommend for reliable backup of my stock Rom?
birdenemedir said:
Thank you Cyclic01. As I know there is no way to root my device, considering that, which program do you recommend for reliable backup of my stock Rom?
Click to expand...
Click to collapse
You can use titanium backup or nandroid. I just used the backup option in TWRP, worked fine for me when I needed to go back to my stock ROM . Take a look at this too
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
Cyclic01 said:
You can use titanium backup or nandroid. I just used the backup option in TWRP, worked fine for me when I needed to go back to my stock ROM . Take a look at this too
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
Click to expand...
Click to collapse
Thanks. I'm trying to install TWRP, but don't know why it remains stuck and says "waiting for device". I checked with "ADB device" commend as it shows my device ID but in download mod when I try to flash img, it gives me waiting message. Is it unlock related issue or what?
birdenemedir said:
Thanks. I'm trying to install TWRP, but don't know why it remains stuck and says "waiting for device". I checked with "ADB device" commend as it shows my device ID but in download mod when I try to flash img, it gives me waiting message. Is it unlock related issue or what?
Click to expand...
Click to collapse
I'm not sure..... have you tried reinstalling the ADB drivers?
Cyclic01 said:
You can use titanium backup or nandroid. I just used the backup option in TWRP, worked fine for me when I needed to go back to my stock ROM . Take a look at this too
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
Click to expand...
Click to collapse
Cyclic01 said:
I'm not sure..... have you tried reinstalling the ADB drivers?
Click to expand...
Click to collapse
I did. I've tried everything even PDAnet. by the way, I'm on windows 10. with "ADB device" commend it confirms my device but in download mod with "fastboot device" commend it shows waiting for device. I don't really konw it's a driver issue or bootloader issue ( I don't have any OEm option in developer options)
birdenemedir said:
I did. I've tried everything even PDAnet. by the way, I'm on windows 10. with "ADB device" commend it confirms my device but in download mod with "fastboot device" commend it shows waiting for device. I don't really konw it's a driver issue or bootloader issue ( I don't have any OEm option in developer options)
Click to expand...
Click to collapse
Don't stress about the OEM option, search around the forums or the web mate. I don't know much ):