yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] krdu:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.

I run the following command:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices

List of devices attached

0315c2d60935c160 device

Then I run the following command:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

ADB sees the phone; Fastboot does not.

The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:

Computer

Android Device

Android Composite ADB Interface

The driver information is as follows:

Driver Provider: Google, Inc.

Driver Date: 7/9/2013

Driver Version: 8.0.0.0

Driver Signer: Google, Inc.

Driver Details:

Driver Files:

C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))

C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)

C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))

I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit

If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.

I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?

Please help I am at my wit’s end.

For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)
[Nexus 5 Q&A, Help & Troubleshooting] PremierGT:
this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/

you'll have to edit the "android_winusb.inf" with the correct hardware id.

in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.

so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.
[Nexus 5 Q&A, Help & Troubleshooting] erikivy:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
[Nexus 5 Q&A, Help & Troubleshooting] android_mp99:
Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.

Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.
[Nexus 5 Q&A, Help & Troubleshooting] krdu:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.

I then went and tried it in the bootloader, to copy listings to post, and here's what I got!

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)

List of devices attached

0315c2d60935c160 device

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices

List of devices attached

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices

0315c2d60935c160 fastboot

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock

...

OKAY [ 41.215s]

finished. total time: 41.215s

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.

Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
[Nexus 5 Q&A, Help & Troubleshooting] erikivy:
You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.

I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.
[Nexus 5 Q&A, Help & Troubleshooting] El Daddy:
ADB is used in android and the recovery.

Fastboot is used only in the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
Just bought S3 AT&T running beanstalk rom on 4.4.1

I need to go back to stock to 4.1.1 so I can unlock it (carrier)

Odin says fail.

Any advice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xSharpi:
Do you have in download mode? (Well obviously) are you also using the ride stock image for the AT&T Galaxy S3. Make sure you have all the drivers installed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
I do have it in download mode, also drivers are installed, did it few times before going from 4.1.2 to 4.1.1 with no issues, but from 4.4, it says fail.

Anyone successfully downgraded?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
From what I remember you can't downgrade if your bootloader was updated. I've found the same to be true if your baseband was updated as mine was when I flashed the Touchwiz 4.3 leaks. I haven't seen a concrete fix for this yet but I'm sure dev's are working on it.
[Nexus 5 Q&A, Help & Troubleshooting] gamekid:
Does anyone have an idea, why my 2 month old N5 only shows "Okay" for Battery Health? I also experience decreased battery life.. Maybe a warranty case? Phone is always plugged-in at night, which was never a problem on previous phones.
[T-Mobile Samsung Galaxy Note II] naruto.ninjakid:
I was wondering how would I do this. I wanted to flash JediMaster X but im rooted on 4.1.2 Jedi X. How would i go about updating to stock 4.3 without installing knox so i can get the working bootloader then update to Jedi Master X ?

I would prefer if the stock ROM was rooted already and knox removed. Anyway have any links.

Has anyone done this process ?
[T-Mobile Samsung Galaxy Note II] tinydynamite00:
Re: Upgrading to 4.3 from stock 4.1.2

Hi, even though you are on stock 4.1.2, remember: you have root privileges now. You can flash any ROM designed/built for your particular variant of the Note 2. That simply means stick with flashing ROM that match your device's model number.

Next, I flashed JediMasterX this morning. It is built from stock firmware Android 4.3 for the Note2 so you can flash this ROM, if there's a build for your variant. You don't need to flash the actual firmware to upgrade to 4.3 ROM. All builds in the forum come from source code, which means there is a base design for each kind of phone, but Android is Android and it follows certain predetermined rules.

One thing you need to do is read the OP to whichever ROM it is you are thinking about flashing. The ROM chef is going to place some very important information on the first page where they present their ROM. It is much advised that you follow those guidelines down to the letter. For instance, you want to flash JediMasterX, right? Did you know that the OP mentions that if you haven't already updated to 4.3, (BTW...there are links in the forums for each carrier to download the stock firmware and they're already root and you don't have Knox to worry about!) that you should flash a particular kernel after flashing the ROM. You'll even find a link to the stock 4.3 modem, which is necessary for providing a data connection. That is less necessary than flashing the kernel and the OP explains why.

I hope this has helped. Make sure you have your custom recovery set-up and that you already have a Nandroid backup of your root stock firmware or another ROM you have recently flashed. Always keep a backup, more than one is even better!

Happy Flashing!

tinydynamite00
[T-Mobile Samsung Galaxy Note II] naruto.ninjakid:
Yes I want to flash JediMaster X but I heard that if i don't have the stock bootloader WiFi will be dropping in and out. Support for devil kernel in V2 is being dropped or something (so i wanted a solution in which i don't have to flash devil kernel) so I need to have the stock bootloader to have stable connection. Yeah I was just looking for the simplest process to get everything working on JediMasterX 4.3
[T-Mobile Samsung Galaxy Note II] tinydynamite00:
I totally understand you. And that's where that kernel I mentioned comes in. It's called the dual-boot or Devil's kernel by [MENTION=3279686]DerTeufel[/MENTION] You need to either flash that kernel after flashing the ROM via the Aroma installer. Reboot back into recovery and flash the kernel OR flash the bootloader patch provided by another senior contributor in the forum. That link is somewhere in the OP and you have this option. Download and flash the stock root 4.3 firmware -- it already is Knox free -- for your device. Then flash your downloaded JediMasterX ROM and you won't need to worry about flashing the kernel.
[T-Mobile Samsung Galaxy Note II] naruto.ninjakid:
Ok thanks I will go the stock method way. After flashing stock do i ed to wipe data and cache ? Also is the best way to flash stock to use PC odin or mobile odin ?
[T-Mobile Samsung Galaxy Note II] tinydynamite00:
I forgot to mention one other thing. I know that JediMasterX was shared with us earlier in December. One thing of interest, and this is solely for your information...don't go trying it until you're more comfortable with flashing and more importantly recovery! The N7105 is compatible with the T889 and that allows us to flash ROM built for our respective variants. The Devil's kernel was built for the N7105 originally. And I just downloaded a pretty updated -- as of this month -- version of the kernel yesterday. I did read in [MENTION=3279686]DerTeufel[/MENTION]'s OP for the Devil's kernel that he wouldn't be supporting any requests for changes to the kernel. But the kernel is solid. Has been for quite some time!

Sorry it's taken me long to reply. Wouldn't you know my phones are both drained and I hadn't turned on my computer yet. Anyway, important thing is to read, read, read. I know you might get bored clicking through pages, but it's really cool when you find updates to certain ROM you like buried in those pages instead of posted on the main page. Or you find tips to a having a better experience on the ROM you happen to be on by using a mod listed in a forum. And you can learn a whole lot from everyone in these forums, but reading through the forums will teach you things about root, what you can and cannot do, that no single person can.

Hope this helped! Have fun flashing!

tinydynamite00

---------- Post added at 12:14 PM ---------- Previous post was at 12:02 PM ----------

Yea, you're going to download and flash through desktop Odin the stock root 4.3 firmware. You download the zip, unzip and place the .md5 file in PDA of Odin. You'll then need to flash a recovery image through Odin as well so your recovery partition will be ready to flash into recovery and then backup the stock root firmware. Keep it in case you want to go back. And always do a complete wipe in recovery for a clean install of any ROM you flash.

Computer is super slow today. ARgH! lol

tinydynamite00
[T-Mobile Samsung Galaxy Note II] ikyorince:
Here you go

I know what you mean and I'm using the official ROM now without Knox

Step 1: Root your phone

Step 2: Install Titanium Backup pro (u can download the APK from apkmania or any other site)

Step 3: Find the apps in the screenshot from Chrome to Mobile life

Step 4: back up each one of them (in case if u need Knox later)

Step 5: uninstall

Step 6: have fun, your phone is Knox free

Hit the thanks button if my post helped you please.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Chinfuk:
Hi, I've read posts about rooting without tripping knox but im worries about the kingo method because of malware concerns. I would like to use root de la vega but it doesn't seem to support my firmware n9005xxudmj7 and the thread is closed now. Has anyone managed to root this version without tripping knox. I can provide more details if needed
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Wont work

Sorry for you

Merry christmas

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] Chinfuk:
hi, thanks so much for the reply,

hope you had a good christmas and new year.

please tel me you forgot to put a 'yet' on the end of wont work ;)

Has anyone with this phone achieved root without tripping knox (or should I just not even worry about it)

may i ask what you recommend I do, shall i just wait and keep checking here for a solution.

thanks again for your reply

Kindest Regards,
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
It doesnt work (yet) and its very unlikely that it will ever work.

Noone has every done 0x0root on mj7, im camping this forum all day ;)

Happy new year

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Don't think it will be achieved... is anyone even working on it? - I don't think so tbh - if you can live without warranty take the plunge and trip that bad boy. If not, then you'll have to make do with your note the way Sammy wanted it to be.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Chinfuk:
Dam, thats really annoying.

There must be loads of people with my phone wanting root, I'll happily donate to someone for a solution. I'm sure others would too.

Guess I should have done my homework more thoroughly before buying

Think I'll just take the plunge as radicalisto suggested

May I ask your preferred method for rooting (last question i promise ;))

Anyway thank you massively for the replies.

All the best
[Galaxy Note 3 Q&A, Help & Troubleshooting] emgluon:
Maybe when android 4.4 breaks root there maybe renewed interest on rooting without tripping knox. Or maybe there are different vulnerabilities that will allow root, as I believe 4.3 to 4.4 is a big update.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ione2380:
I for one, will wait for 4.4 before i root. For now, i'm happy with stock unroot.

Sent from Note 3 SM-N9005
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
4.4.2 was released ;) go devs go

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[8125, K-JAM, P4300, MDA Vario General] vettejock99:
Before someone jumps on me to Search - I have. I am a newbie, yes, but I have used aWizard to CID unlock my MDA Vario, flash the Qtek Test ROM, unlock the Extended ROM, and load a custom Extended.

HOWEVER, I cannot figure out how to flash an NBA file to the device. Most references refer to using aWizard, but in that app (I am using 1.3 beta 2, I think), I only see comments about nba related to swapping the Splash, and a couple of "not yet released" features.

I'l really like to load the Cingular Radio ROM, etc., but I can't without understanding how to use aWizard (or another app) to do this. Any help would be appreciated.
[8125, K-JAM, P4300, MDA Vario General] vettejock99:
Short answer - use aWizard and make sure your PATH has no spaces in it.
[AT&T Samsung Galaxy Note II] fuzio1963:
I upgraded to 4.3 stock. Then rooted, then upgraded to 4.4.2 custom.

Then decide to get back to 4.3. By a mistake i restored in ODIN to 4.1.1 (stupid me)

After restore, phone won't boot. Actually I cannot do anything......except for going into download mode, where I got "knox warranty void:1". And that is it! Nothing else can be done........i cannot even boot into recovery............

Any help??? Or should i toss it against the wall?? :(
[AT&T Samsung Galaxy Note II] fuzio1963:
TY!! I did that already..........and STILL cannot boot into recovery AFTER this.... any idea???
[AT&T Samsung Galaxy Note II] rangercaptain:
Your profile says Verizon. This stuff is for at&t.

But you can reinstall TWRP if you can get in download mode.
[AT&T Samsung Galaxy Note II] fuzio1963:
VERIZON?? Oops!! That was years ago.....forgot to change it. Sorry.

And yes, i did install recovery via odin. But i cannot boot into recovery.....
[AT&T Samsung Galaxy Note II] rangercaptain:
Home+volume up and hold in power until you see first screen, then let go of power but contine to hold in home+volume up until you see TWRP screen.

Otherwise, use "adb reboot recovery" command.
[AT&T Samsung Galaxy Note II] fuzio1963:
Unfortunately, device list is empty.... got drivers installed.
[AT&T Samsung Galaxy Note II] rangercaptain:
Powered usb port stock cable correct pc directory?
[AT&T Samsung Galaxy Note II] fuzio1963:
Yup. :(
[AT&T Samsung Galaxy Note II] Deleted member 4330112:
Mine is doing the exact same thing. Wont show up in adb and wont boot in recovery, but can get in download, flashed twrp through odin and still cant get into recovery
[AT&T Samsung Galaxy Note II] rangercaptain:
There is some procedure that forces recovery that involves taking out the battery at a certain point during bootup, but I don't know it. Maybe start a new question thread about that?
[AT&T Samsung Galaxy Note II] Jspex:
Try flashing the 4.1.1 firmware from sammobile. it is the older of the 2 from att and it does not show a version number on the Sammobile site. Then flash root/cwm all through odin. Then do the battery pull trick to recovery. You may need the root and custom recovery to get the rest to work right.

Did you thank your Developer today?
[AT&T Samsung Galaxy Note II] fuzio1963:
Done that, NO luck. :(
[AT&T Samsung Galaxy Note II] Jspex:
When you pull the battery does it boot automatically into download mode? Or do you have to power the device up yourself?

Also have you tried to odin a root injected 4.1.1 fw yet? You may have to dig through the dev section but I know they are there.

Have you tried flashing the leak 4.3 yet? http://xdaforums.com/showthread.php?t=2496292

JSS15J.I317UCUBMJ4 (Android 4.3)

Really at this point I'm spit balling.

Did you thank your Developer today?
[AT&T Samsung Galaxy Note II] fuzio1963:
After battery pull out, I have power it back on. (power-home-vol/up - Galaxy Note II screen, and sits there. power-home-vol/down - download screen)

Tried 4.1.1 in odin, tried 4.1.2 as well, and rooted it in odin right away, all went OK, passed, but after battery pull out, still didn't go beyond Galaxy Note II screen.

Tried 4.3 in odin, but at the end, got "failed" result.

Damn.............for some reason, i know this has something to do with bootloader. I am not "android" guy, but rather PC computer freak... ;)......if i only know how to completely reformat entire storage space, and start from the scratch.....but unfortunately, this is not a hard drive.... :(
[AT&T Samsung Galaxy Note II] Jspex:
Just for me try this: flash 4.1.1 and as soon as the device reboots pull the battery. Dont let it get a chance to do anything. Then boot it into download mode and flash the chainfire superuser with Stock recovery built in. That can be found a in the stickey how to revery to stock thread in this exact forum. Then on reboot after flash pull the battery and let it sit for 5 min, no less. Then try to boot into recovery. If you can get into stock recovery there is hope.

I know you may have tried this already but please try it one last time for me. Keep in mind you should pull the phone Off the usb as soon as the odin flashs are done. Pulling the battery while it is still plugged in wont cut the power the way you need it to in order to reboot properly. Also if you have an external sd card in pull that sucker out as well. Sd cards can hang things up sometimes.

Like I said spitballing here. If all else fails maybe you can talk a dev into wrapping a rom into an odinable .tar file and try to force a rom on it.

Did you thank your Developer today?
[AT&T Samsung Galaxy Note II] fuzio1963:
Stand by..........will do this right now.
[AT&T Samsung Galaxy Note II] Jspex:
Cool, let us know if this actually worked. This seems to be a problem for 1/2 the people that try the revert to 4.1.1 method.

Did you thank your Developer today?
[AT&T Samsung Galaxy Note II] fuzio1963:
Sent you a PM.
[AT&T Samsung Galaxy Note II] Jspex:
Seems like i didnt get it and im not seeing the one I just sent you in my outbox. You can email me jspex1@gmail.com or if you irc I'm always in #jedi on coldfront.net

Did you thank your Developer today?
[AT&T Samsung Galaxy Note II] gregsarg:
After the downgrade via Odin. ..

Pull battery. .then power the phone into download mode again. .and run CF auto root. ..

The device will boot itself. ..

Use the UCAMA4 rooted rom from Mr. Robinsons thread. .for your downgrade. ..

Don't worry when the Odin flash fails on the bootloader portion. ..just unplug the phone and pull the battery for the CF step. ..

After boot and rom verification. ..power down and enter DL mode again to flash your custom recovery. ..

Note:

The bootloader doesn't play nice with the process. ..but it works. ..g
[AT&T Samsung Galaxy Note II] fuzio1963:
Nope, still nothing!! Sorry.
[Verizon Samsung Galaxy S 4] permafrost91:
On MJ7 but it keeps pestering me about the MK2 "upgrade." I've removed most of the bloatware via TB (not frozen: everything is backed-up and un-installed) so my question is whether I need to reinstall all these apps before running the "upgrade" or whether I can run the "upgrade" with my current state of affairs?

The last post I found with a similar question is from 2011:

http://xdaforums.com/showthread.php?t=1186450

Thanks!
[Verizon Samsung Galaxy S 4] ericmtnbkr:
It seems there are some people having problems and some people who do not. I was lucky and took the OTA with no problems, but I did have Survival Mode turned on in Super SU. I have never seen a list of what apps successful people have removed vs what apps unsuccessful people have removed. I've removed a few of the Verizon apps and frozen a few apps as well.

Not a great answer but it's all I got. Good luck.
[Verizon Samsung Galaxy S 4] decaturbob:
It's my understanding to take OTA...The stock needs to be pretty much stock. Mk2 not any thing big. Have you thought just freezing the programs that are giving you the notification?
[Verizon Samsung Galaxy S 4] permafrost91:
What do you mean by that? No apps have notified me of anything yet. I was just wondering how stock stock needed to be for the OTA.

As far as my progress is concerned, I have restored all my backups via Titanium Backup, even unrooted via SuperSU but the OTA still fails with error code 402. Interestingly, the bootloader still shows the "custom" logo with the unlocked lock symbol so I think it has something to do with that although at this point I'm not sure what is "custom" about my phone ...
[Verizon Samsung Galaxy S 4] Mightycaptain:
You need to flash the no wipe stock tar for mj7. There is a post in android dev for it. That will get rid of the custom screen and allow the ota to Take.