After a little pain and scouring the threads in the forum I found a way to accept the OTA and then re-root.
This is not my process it is one that I have seen in pieces and after trial error and several soft bricks I have root on NC5 and am Back cruzing away.
(--Disclaimer, this is what I did to My device and How I was Able to resolve My situation. YOUR results may be different and I DO NOT assume
any responsibility for what you do with your device.
If you are not sure if you are in the same boat or you do not understand basics of rooting, flashing and using ODIN please do you research and educate yourself)
This was my situation and how I was able to get back to root.
I was on the Original Stock Rom Rooted with CF-AutoRoot... (NAE) Root NAE Life is great! :cyclops: (Find it in Original Android Dev)
I accepted the OTA via Kies and after reboot was unrooted NC5 running fine.
I tried to flash CF-Auto root several times and It always crashed and left me in a soft brick... in Odin it would get to cache and hang....
I then flashed the NB3 recovery via ODIN. (I used 3.09) (reboot, Yeah, we up again...) :good:
I re-flashed CF-Autoroot and Profit! $$$
went to playstore and installed superSU
I then re-flash TWRP 2.7.0.2 and made a back-up.
The Lesson learned here is flash the NB3 Recovery before you go Flash CF-AutoRoot.
I have attached it.
~Bizack
BIG note: Don't use a USB 3.0 port on your PC. At least for me, this was the killer for re-applying the CF Auto Root after following the above instructions. Flashing the NB3 recovery worked in Odin 3.07 and 3.09 just fine. Every time I tried to re-apply CF Auto Root, it hung on cache.img like so many others.
Like I'm supposed to do, I scoured the posts and general internet so I wouldn't ask a question that's been answered many times. What caught my eye was the repeated note to open Odin and load the file to be flashed in Download mode FIRST, then connect the USB cable. One post said to do this and wait for the Download mode drivers to load. This got me thinking that the device needed different drivers for different connection modes. If USB Debugging, MTP, PTP... were different, why wouldn't USB 2 or USB 3 also be different???? I was always in USB 3 out of habit and decided to try a USB 2 port on my PC (bingo).
1. Updated to NC5 using Kies using USB 3. Worked without issue. OTA wouldn't work b/c I was rooted already.
2. Flashed the NB3 recovery (PDA slot) as noted above in USB 3 using Odin 3.07. Worked without issue.
3. DON'T DO THIS - Flashed CF Auto Root recovery using USB 3 (PDA slot). This is where my problems started and the device was in what I think is called a soft brick.
Intermission to scour the internet and try different solutions
4. Disconnected USB cable.
5. Get into Odin 3.07, load NB3 recovery file (PDA slot)
6. Connect USB cable to USB 2.0 port (directly to mobo port, not a USB hub just in case)
7. Flash NB3 recovery. No problems
8. Disconnect USB cable from Note (still in 2.0 port on PC)
9. Reboot into Android NC5. No problems (Exchange account was gone - no big deal)
10. Connect USB cable and let the PC recognize the device. I switched between MTP and PTP to make sure both drivers were registered and it did register twice proving that these are different connection types (kind of a 'duh yeah' thing)
11. Disconnect USB cable from Note, shut down and boot into Download mode.
12. Get into Odin 3.07, load CF Auto Root recovery into PDA slot.
13. Connect USB cable to Note.
14. Start (flash). BINGO!!!!
15. Disconnect USB cable, reboot
16. Boot into Android NC5.
17. Download SuperSU and open it. Rooted again!
Are all these steps needed, maybe not. But for me, the key was to not use USB 3.0 connection on the motherboard. The cable was USB 3.
For all the times someone else posted a really thorough post that saved me time, thank you!!! This one's for all you awesome folks out there who help out.
Works perfectly
Thanks for posting this. It works perfectly:good:
James L said:
Thanks for posting this. It works perfectly:good:
Click to expand...
Click to collapse
Ditto!
Related
Hello!
I have royally F***** up my phone so if there are any geniuses out there, I will be so happy to hear your thoughts on my issue.
Here's my problem and I am open to any solution:
-My phone isn't rooted so CMW, TWRP, and any other custom recoveries are not an option.
-USB doesn't work
-Factory reset doesn't help (I've tried both ways)
-Any installs via extSD get the signature fail notification
-USB debugging is checked
-Allow apps from unknown source is checked
-App verification is unchecked
-Any kind of app that is meant to root my phone doesn't work
Thank you in advance!
Can you put it into download mode? If you can then you should be able to odin a custom recovery or odin the stock rom back to your phone and start from scratch. Have you downloaded the Samsung USB drivers? Only use the cable that came with your phone, others may not work or charge only. Also, try a different usb port.
Signature fails because you are on the stock recovery and the file you are trying to install hasn't been signed by Samsung.
cruise350 said:
Can you put it into download mode? If you can then you should be able to odin a custom recovery or odin the stock rom back to your phone and start from scratch. Have you downloaded the Samsung USB drivers? Only use the cable that came with your phone, others may not work or charge only. Also, try a different usb port.
Signature fails because you are on the stock recovery and the file you are trying to install hasn't been signed by Samsung.
Click to expand...
Click to collapse
I can put it into download mode but my phone still isn't recognized. I've tried many different cables, computers, usb ports, etc. I've downloaded the drivers from people posting them on here or on samsungs website directly but either way, i'm using windows 8 and windows 8 does it automatically. this wasn't a problem from the beginning, this just recently started happening and it has nothing to do with my computer or any computer for that matter.
Have you installed the drivers 'as administrator'?
Have you used Odin before?
How did you do what ever it is you think you did?
Have you tried Odin'ing a complete stock .tar? Here's one. Just download zip and extact the .tar.md5 file.
When you launch Odin are you right clicking and running as admin?
Did you put your phone into download mode before connecting it to a RUNNING Odin session. Meaning start Odin on PC as admin. Then put phone into download mode and then plugging it into computer.
Seems you can get into your phone right?
You may also try copying the extracted .tar to your SD card (via PC adapter or whatever) putting the SD card back in your phone and then trying to flash it via Stock Recovery.
Always nice when someone asks for help and then never reports back.
I am trying to root my Samsung Galaxy Note 3 (well actually i would like to install a new rom and recovery) , but i am running into a problem.
Odin3 (v1.85) only finds my phone when i am not in the recovery mode (or the sideload to be precise), adb on the other hand is able to to do sideload but the loaded images fail with "Wront footer" and "verification failed".
Some Data:
AP: N9005XXUENA7
CP: N9005XXUENA2
CSC: N9005DTMENA2
Model: SM-N9005
Android: 4.4.2 (Stock, no root)
USB Debugging: On
Reactivation Lock: Off
USB Driver: Kies 3 (also tried the CWM Drivers)
If you have KIES installed it doesn't play nice with Odin, remove KIES or kill all KIES processes and try again.
radicalisto said:
If you have KIES installed it doesn't play nice with Odin, remove KIES or kill all KIES processes and try again.
Click to expand...
Click to collapse
Thank you,
i removed Kies and tried again, i still don't get "ID:COM" in Odin.
Sorry I should have said, once you uninstall KIES you remove the USB drivers, you need to install them again. Again, sorry should have said
exclusive iblument
radicalisto said:
Sorry I should have said, once you uninstall KIES you remove the USB drivers, you need to install them again. Again, sorry should have said
Click to expand...
Click to collapse
No problem,
i actually installed the "SAMSUNG_USB_Driver_for_Mobile_Phones" Pack after removing Kies and doing the reboot stuff.
Still don't get the device via odin.
Maybe i will remove all the drivers and try the CWM Driver again.
Try a different USB port - Not sure why it's not showing for you
radicalisto said:
Try a different USB port - Not sure why it's not showing for you
Click to expand...
Click to collapse
I tried different Ports (USB 2 and 3), different Cables and different drivers.
Removed Kies3, tripple check that debugging is on and recovery lock is off.
Still, Odin finds the device when it is not in recovery mode (sideload),
Was another user who had the same problem had to use another PC, I'm struggling to think of what may be the cause.
I had also the sane problem. I also tried all ports on my PC but did not work. I installed KIEs on my Laptop and it worked. I could flash the CWM recovery.
KiVi-Wolf said:
I tried different Ports (USB 2 and 3), different Cables and different drivers.
Removed Kies3, tripple check that debugging is on and recovery lock is off.
Still, Odin finds the device when it is not in recovery mode (sideload),
Click to expand...
Click to collapse
Put phone in download mode then with Odin NOT running, plug USB cable to phone. Finally ran Odin ( I'm assuming you installed Samsung USB drivers ).
Sent from my SAMSUNG-SM-N900A using xda app-developers app
hey_joe said:
Put phone in download mode then with Odin NOT running, plug USB cable to phone. Finally ran Odin ( I'm assuming you installed Samsung USB drivers ).
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I did this on a new computer that never saw an Android device before.
Odin does not detect my device despite following this advice and the one before.
I installed Kies, made my device known to the Windows Device Manager, rebooted, connected device while in sideload-mode and waited until detection was finished. The next step was firing up Odin3 v1.85 and my device didn't show up, but i was able to use the adb sideload which failed with "Verification Error" when installing a new recovery or rom.
Could it be that the phone being branded by T-Mobile Germany changed the game even though the model is just plain SM-N9005 ?
Is there another option to root this device or preferably install some other rom without Odin?
Never ran into so much trouble with my Asus eeePad, the Samsung I9000 or the HTC One X.
study esjoys
Well when stupidity strikes you...
I always went into the recovery rom (Vol+ & Power & Home) instead of going with the odin mode (remove battery, power device on with Vol- & Home & Power).
Thanks everyone who tried to help me, but you were no match to my blindness ^^
Maybe this might help someone who utilizes the search function after he or she didn't read the tutorials carefull enough.
KiVi-Wolf said:
Well when stupidity strikes you...
I always went into the recovery rom (Vol+ & Power & Home) instead of going with the odin mode (remove battery, power device on with Vol- & Home & Power).
Thanks everyone who tried to help me, but you were no match to my blindness ^^
Maybe this might help someone who utilizes the search function after he or she didn't read the tutorials carefull enough.
Click to expand...
Click to collapse
It's always the simplest things
PC&Odin not able to detect phone via USB after flashing custom ROM: tried dif pc too
Hi all,
I've recently flashed this awesome ROM: [GearCM][i9500][4.4.4] Optimized CyanogenMod 11 for Samsung Galaxy S4 [20140912] in my device. ROM works great, very stable, fast performance, however since install, I am not able to detect my phone via USB. Not even ODIN sees the device connected.
Was doing my research before posting, so I will let you know what I've tried which was recommended in other posts and google:
1. Re-installed Samsung USB Drivers: No Go
2. Used different USB Cables (using stock one that came w/ phone right now): No Go
3. Tried different USB Ports: No Go
4. Tried a different PC: No Go
5. Yes, I am testing with my screen unlocked
Anything else I can try? Maybe a setting in my Phone?
Thanks!
Odin should always see your phone in download mode. No rom will change that.
If Odin doesn't detect your phone in download mode then it's either a:
- Driver problem
- Cable/port problem
- Faulty usb port
By the way, the device charges normally when connected to my computer USB.
Lennyz1988 said:
Odin should always see your phone in download mode. No rom will change that.
If Odin doesn't detect your phone in download mode then it's either a:
- Driver problem
- Cable/port problem
- Faulty usb port
Click to expand...
Click to collapse
Good call. Odin is not detecting the phone in download mode-- so I guess we can eliminate problem in the device configuration.
I'm going to try again in another PC and different cables. Maybe my Cable went bad, sucks because it's pretty new? Going to copy Odin to a pen drive so I can try in friends computer. On other PCs I only tried connecting in Windows-- no download mode & odin.
Ok, so I was able to get working back.
I enabled developer options by going in about and clicking the build 7 times. Proceeded to go to Debugging options and selected Android Debugging marked. Reinstalled Drivers again, then it showed PC connected as Media Device on notifications. I clicked there and changed to Camera PTP and then back to MTP.
Now I'm able to see the Device again!
No idea why I was not able to see it in Odin while on download mode, however, I can see it now even when not download mode.
Thread can be closed, thanks!
Hi All
I am looking for an update.zip file I can use to flash the stock 6.0.1 rom again over my existing version to fix a USB connection issue. I need a Samsung OTA update.zip which can be flashed from the stock recovery via an sd card.
This has come to light as I've recently tried to update my note 4 to nougat but came across an issue where the phone will not connect with my PC via USB. I have tried all the usual tricks on the phone (dev options, usb debugging, MTP+ADB etc) but nothing was working. In the end I have replaced the micro usb daughter board on the phone thinking there must be an issue with the data pins but the phone still refuses to connect but charges fine. Strangely the phone thinks it's connected fine but the PC says it is not getting a device descriptor response. I have checked drivers etc and also tried 3 other PCs all of which connect to my old S4 without issue. I have also tried various USB cables including a new genuine samsung one.
Due to not being able to connect to a PC in any mode (such as odin download mode or recovery) and having the stock recovery without root my only hope is that a new update.zip will sort out corruption from the last OTA update. I believe this may be the reason as I was able to connect fine until the most recent update a couple of weeks ago. I have tried using a zip from the samfirm downloader but the recovery failed immediately with 'unable to map file'
Any help you guys can give would be greatly appreciated as I really don't want to be stuck on Marshmallow now Samsung will no longer be updating the Note 4.
I have tried connecting in MTP mode, odin download and recovery mode with usb debug both on and off
Many Thanks
Luke
Have a note 4 on a custom rom- android kitkat. Was working fine, until i wiped data/cache a few times in TWRP recovery to do a clean install of the rom. Phone restarted without an OS, and then i couldn't get pass the boot logo screen. Couldn't flash any rom in recovery. So i did a restore thru TWRP from a backup. So now the phone boots, but it pc won't recognize it. Everytime i plug it, I get "One of the USB devices attached to your computer has malfunctioned, and Windows does not recognize it". Under device manager, I get "Unknown USB Device (device descriptor request failed)".
Things I have tried:
-Uninstalled usb drivers and let windows reinstall,
-at least 5 different usb cables
-at least 3 different Samsung oem usb cables
-other usb ports on the PC
-3 different pc (all with same- so im guessing its a problem with the phone)
-physically tried to push up the usb port on the phone- bad connection (someone recommended on google search)
- even when as far to reinstall windows OS
-*#0808# and set it to AP, MTP + ADB
-yes usb debugging is enabled
-download mode (odin does not see the phone, so cannot flash stock/custom rom
-diferent versions of odin
-different version of Samsung usb drivers
-have other samsung phones (note 5, and s6) and windows recognize those.
-phone does charge thru usb
need to get phone working again
-
Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.
yashthemw said:
Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.
Click to expand...
Click to collapse
You might try reading the whole post, rather than just replying.
JagDave said:
You might try reading the whole post, rather than just replying.
Click to expand...
Click to collapse
Sorry, my bad.
So, the author can try to repair partitions via twrp.
Go to wipe/advanced wipe and then select "Repair or change file system".
Select the partitions and repair them.
Reporting Via N910G.
Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents
ziggsta said:
Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents
Click to expand...
Click to collapse
i have tried. at this point i think it's hardware failure with the usb port. Stupid buying those cheap usb cables probably damaged the port because it seems to require a little more force than samsung cable. Planning ordering one and replacing. hopefully i don't do more damage. Had this phone for a long time and miss flashing roms on it.
i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.
jxlee0215 said:
i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.
Click to expand...
Click to collapse
Replace the battery