Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den
go_l_den said:
Hey guys,
I'm about ready to throw a brick through a window at Samsung's Headquarters, so I'm sure this will make an excellent first post.
Earlier today, my dad decided to update is rooted phone via a T-Mobile update sent out via the internet to the latest J16 firmware. Not surprisingly, his phone was one of many to get soft bricked. From this point I used ODIN to flash back to J15 and then used it again to upgrade to J16. Now, the phone boots normally, but it still seems to have ROM manager and other root applications on its hard drive despite the fact that ODIN should have wiped out all of the packages.
This coupled with the fact that I have failed to re-root the device and USB connectivity is awful compared to J15, I decided to try and flash back to J15 using ODIN. Only this time, when I get the device into download mode it isn't recognized properly as a USB device by my computer; therefore, ODIN won't recognize it either.
My dad is about ready to take the phone to T-Mobile in hopes of getting a new device, but before he attempts this I'm wondering if there are any solutions to my problems that A) Fix USB connectivity in download mode or B) Allow me to whipe all data and revert to J15 in some other manner.
Help would be appreciated!
Go_L_Den
Click to expand...
Click to collapse
First and foremost make sure your plugging the usb into a usb port that is connected directly to the motherboard. Should stablize the usb connection. ( I had the same issue) Second flash to JFD via odin, then you want to upgrade to J16 via the vibrant version of kies mini. OTA update is not the greatest.
The JI5/6 updates don't wipe all data and apps, as they were designed to be OTA updates and not complete new installs. Can't have people complaining that an update wiped their entire phone, right? Stock JFD is a full flash which wipes all user data.
And yes, try to have it plugged directly into the motherboard's USB ports, make sure the contacts on the microUSB aren't corroded, and try deleting the Vibrant drivers and reinstalling them.
which version of odin you using? try 1.3 if not already
Kies or ODin
Nevermind I found it here ars.samsung.com/customer/usa/jsp/faqs/faqs_view_us.jsp?SITE_ID=22&PG_ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559
All you hace to do is go to USB settings and with the OTA update for J16, there's an option to choose "Ask what to connect" either samsung kies, mass storage, etc. Happen to me, did unroot, factory reset and there you go, just need to go to that stupid settings.
Related
I have searched and tried a few things I found but with no luck. Makes me think the driver is screwed up. I have the US/Sprint tab if that makes any difference. I keep getting the Error Kies cannot connect and needs to be in PC Studio mode. Thx for any help.
make sure you havent enabled usb debugging mode and left it on
Some times restarting the tab fixes the kies connection problem.
FWIW, I wasted the better part of yesterday trying to get Kies to connect with no luck. Some of the remedies I tried were a utility to locate long file names on the Tab and installing a UK version of Kies.
I believe the general consensus is that for many of us, Kies is a POS. Since I can't get it to connect, I seem to be stymied in my attempt to regain root access until another fix comes along.
Have you used adb? Or odin? I have flashed 5 tabs and never used the kies program.
Have not tried those. Is there a link on how to use? I really want to get my Root back.
"Have you used adb? Or odin? I have flashed 5 tabs and never used the kies program."
Haven't tried adb, although I used it when I originally rooted my MotoDroid. However, I don't recall seeing anything for using it on the SGT.
I have a Sprint Tab, so I thought odin would not work on it.
Please note that the US version of the Tab are not currently supported by the full version of Kies. You can only use the mini version of Kies with the tabs to do firmware upgrades only. Also of note, I can connect and get Kies-mini to recognize my T-Mobile tab, but no firmware upgrades have been made available.
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
vivek318795 said:
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
Click to expand...
Click to collapse
I'm running into the exact same issue, did you ever find a solution?
Same issue
I have the same issue. Is there no help? Chainfire? do you have a CF-Root for SM-N900V yet?
Thanks. any help is appreciated.
my s6e+ (g928f) will not connect to my PC. I do not believe it to be a driver issue because i have tried uninstalling reinstalling etc and tried barebone drivers.
Also the other day my phone stuck at 0% and would not charge, either wired or wirelessly. After 2 days it started to charge again.....
I thought my usb port was bust but this seems like a software issue, right? I obviously cannot connect to odin because it doesn't detect my device.
Is there such a thing as flashable stock roms i can flash in CWM, instead of using odin?
Its worth mentioning i did a couple weeks ago update to MM and then downgrade back to LP so i believe my modem and bootloader were updated during the process, would they have been downgraded back to the LP versions after restoring my nandroid backup?
I know this is a tricky one but i'm in a mess, help
Hi,
I'm having some trouble restoring the official FW on my old S4. The idea was that I wanted to give it to another family member, and would prefer to give them the stock FW rather than deal with whatever potential issues a custom FW offers (don't get me wrong, custom FW tend to be awesome, but I hope you get the picture).
I downloaded the latest, official FW for this phone and proceeded to try and flash it using Odin (MD5 file specified as PDA). Alas, this got stuck on flashing BOOT. So I tried to hook up the USB cable to a different USB port (I was using a hub before) and that went through BOOT, but failed with a write error later d.wn the line. This, alas, has been my experience thus far. I've tried other Odin versions and another FW version, all failing with the write error.
I've even tried to use KIES to restore, but now KIES fails to recognize the phone at all (neither normally, nor in the recovery mode as the phone suggests, nor can I "initialize" the phone, as apparently the GT-I9505 does not support it).
I do feel not all is lost, as I can get into the download mode without issues, but I'm unsure how to proceed. Please help.
OK, I think I got it.
It turns out my USB cable was sh*t. With a new USB cable it works fine.
I have a Galaxy S8 SM-G950U on Verizon.
In March I flashed my phone with the following ROM so I could get the S9 messanger,
https://forum.xda-developers.com/galaxy-s8/development/rom-pixelish-s9-rom-custom-snapdragon-s8-t3766891
Everything worked for a few months, including system updates. But as of roughly two months ago I am unable to install any system updates, they always fail. The rest of the phone works fine, its just the updates.
I have tried to use Smart Switch to install the update through my PC, but the process would freeze after downloading the update. The same happened when I tried emergency software recovery through Smart Switch.
I also tried using Verizon's software update utility to both update and recover the phone, but the program would freeze just like Smart Switch.
I have also tried flashing both stock firmware and re-flashing the ROM to the phone with no success. I have tried flashing with the following 4 versions of Odin:
- Odin3-v3.12-PrinceComsy-
- Modded Odin v3.13.1 Raymonf
- Odin3 v3.13.1_3B_PatcheD
- Odin3_v3.12.3
No matter what version I tried, Odin would either outright fail or freeze at either "SetupConnection" or "Intializing". I tried plugging my phone into both USB 3.0 and USB 2.0 ports. I was very careful to get the correct stock firmware for my phone. I downloaded the stock firmware from both sammobile.com and samsung-firmware.org
I also tried simply restting the phone to factory setting both from inside Android and from Recovery Mode.
Does anybody have any clue what might be causing this and what I can do to fix it?
I really dont want to be stuck with a phone that can't get updates.