I was messing around trying to root my phone. Now its stuck in the ODIN mode. Which is the necessary ODIN and stock firmware to flash it? Do all I need to do is load into ODIN using volume down home and power. And in ODIN, click AP and choose the tar file, and then start? Can someone link me the proper ODIN and AP file please? My phone is a brick. Im a retard noob. : ( lol. Im trying though. Any help is appreciated.
It says "An error has occured while updating the device software. Use the emergency recovery function in the Smart Switch PC software.
Using Samsung Switch
All hope is not lost. You may have done what I just did and tried to flash a root exploit inappropriate to you phone's firmware version. At this time, the latest factory firmware that you can revert to is rev02 (files with the string "G935TUVU4BQB1" in their name). If you're on the latest T-Mobile update, the you've got factory rev03 firmware, for which no online release is available. Basically, T-Mo users can't restore if we try to root and screw up. But don't panic yet. Hopefully you have a computer to install Samsung Switch on.
1) Download and install Switch, and start it up with your phone unplugged. When it shows the animation of connecting your phone, do so. It probably will list it as an unrecognised device, ignore that.
2)Next to the minimise button in the upper right, select "more", then "Emergency software recovery and initialization". Go to the second tab in the window that pops up, labeled "Device initialization". If you've got the T-Mobile version of the S7 Edge, your model number is SM-G935T (which I'm assuming since we're in the T-Mo subforum). If it rejects the model number, ensure that your internet connection is working; I experienced network issues at the same time and drove myself nuts for a few minutes.
3) It then asks for your device serial number. If you know that, great. Otherwise, unplug your device. Perform a safe reboot by holding Home+Volume Up+Power, and release when a blue screen comes up informing you that loading custom OSes is dangerous. At this point, push the Home key (which the phone should say leads to barcode). The barcode screen will have your serial number on it, write it down. Safe boot the phone again (Home+Volume Up+Power), but this time press Volume Up to get back to download mode. Go back to Switch, which reset itself when you power-cycled the device, go back to that "more" menu, to the second tab. Input your model again, followed by the serial you just wrote down.
4) At this point, Switch should start downloading a pretty big file. If it's anything like the size of the other factory firmwares I tried downloading (the rev02 ones that won't work, with the G935TUVU4BQB1 in the names), then it should be around 2GB. Wait for that to finish, and it'll start pushing it to the phone automatically. Afterward, your phone has been factory reset, and will ask you to sign in with a Google account that has been previously linked to it. This will most likely be the one you were using before you tried to root. From there, it's like doing the first time setup of a new phone.
Sorry my recommendation is a month late for you, I only just had the same problem tonight. We should have been on the same firmware version, though, so if you're still looking for a solution, then give this a go. Hopefully it also helps people who get stuck in a similar conundrum. Good luck!
-Kafte
Simply Odin stock and start over make sure partition is uncheckeded
same problem
kafte said:
All hope is not lost. You may have done what I just did and tried to flash a root exploit inappropriate to you phone's firmware version. At this time, the latest factory firmware that you can revert to is rev02 (files with the string "G935TUVU4BQB1" in their name). If you're on the latest T-Mobile update, the you've got factory rev03 firmware, for which no online release is available. Basically, T-Mo users can't restore if we try to root and screw up. But don't panic yet. Hopefully you have a computer to install Samsung Switch on.
1) Download and install Switch, and start it up with your phone unplugged. When it shows the animation of connecting your phone, do so. It probably will list it as an unrecognised device, ignore that.
2)Next to the minimise button in the upper right, select "more", then "Emergency software recovery and initialization". Go to the second tab in the window that pops up, labeled "Device initialization". If you've got the T-Mobile version of the S7 Edge, your model number is SM-G935T (which I'm assuming since we're in the T-Mo subforum). If it rejects the model number, ensure that your internet connection is working; I experienced network issues at the same time and drove myself nuts for a few minutes.
do you have a option if the smart switch is not recognizing at all?
3) It then asks for your device serial number. If you know that, great. Otherwise, unplug your device. Perform a safe reboot by holding Home+Volume Up+Power, and release when a blue screen comes up informing you that loading custom OSes is dangerous. At this point, push the Home key (which the phone should say leads to barcode). The barcode screen will have your serial number on it, write it down. Safe boot the phone again (Home+Volume Up+Power), but this time press Volume Up to get back to download mode. Go back to Switch, which reset itself when you power-cycled the device, go back to that "more" menu, to the second tab. Input your model again, followed by the serial you just wrote down.
4) At this point, Switch should start downloading a pretty big file. If it's anything like the size of the other factory firmwares I tried downloading (the rev02 ones that won't work, with the G935TUVU4BQB1 in the names), then it should be around 2GB. Wait for that to finish, and it'll start pushing it to the phone automatically. Afterward, your phone has been factory reset, and will ask you to sign in with a Google account that has been previously linked to it. This will most likely be the one you were using before you tried to root. From there, it's like doing the first time setup of a new phone.
Sorry my recommendation is a month late for you, I only just had the same problem tonight. We should have been on the same firmware version, though, so if you're still looking for a solution, then give this a go. Hopefully it also helps people who get stuck in a similar conundrum. Good luck!
-Kafte
Click to expand...
Click to collapse
do you have a solution or alternative if the smart switch in not recognizing or do you have access to stock firmware been looking everywhere
Related
So, dumb self made a pattern that I don't remember. So my Vibrant is at the Too Many Pattern Attempts screen. I've tried to wipe the phone using vol up and down plus power but that doesn't remove the too many attempts screen at all. The only gmail account that I hooked up to my phone keeps telling me that something is incorrect yet I can log in to my gmail fine from my computer... What can I do? I tried to do Odin, but vol down plus power does nothing on my phone. It just continuously power cycles... When I boot into the recovery screen I can use Odin but it just hangs at checking files... Any suggestions?
Do you have coverage? Maybe the Google verification can't connect. It always worked on my myTouch and once on the Vibrant.
Sent from my Samsung Vibrant using the XDA app
Tmobile Galaxy S pattern locked out, can't root
I just bought my first Android device, the Samsung Galaxy S from Tmobile from the US (I live in China) last week. I have only used it a few days and my girlfriend thought the pattern lock would be a fun game to play. Result - locked out. I have the same problems as in the below thread:
http://code.google.com/p/android/issues/detail?id=4784
I tried the receive a phone call then hammer the home key; emergency call and go to search and many of these type fixes; however none have gotten me through. It seems they fixed the security problem here but didn't fix the username password problem as I'm sure the credentials I entered are correct and I have data service.
After giving up on these methods I tried doing a hard reset. BTW, on this model you must hold down volume up AND down buttons at the same time, then press the power button to get the reset screen.
I have cleared user data etc, but when I try to reset the phone I get the error message "setup.zip not found".
I understand that I now need to root the phone, so I tried the method explained here but without having access to the phone I need to load this setup.zip file on the SD (not the one with Avatar).
http://samsungvibranthacks.com/samsung-vibrant-hacks/how-to-root-samsung-vibrant-galaxy-s/
I already installed Kies (has Outlook sync functionality!) on my desktop so that I can access the internal memory as an external drive. However the phone's USB mode must be set to (it will prompt whenever I connect) to Kies mode. However since I am locked out of the phone I can't tell the phone to get into Kies mode, therefore cannot access the internal memory, therefore cannot load setup.zip, therefore cannot root, therefore cannot get past the pattern lock screen = useless phone.
I need to root the phone anyway so I can load a few Asian IME's that didn't come with the phone so don't mind playing with this, but since I'm new to Android it may be a while before I can get through since most root instructions either require access to the internal memory via my computer or access to the phone (past the pattern lock).
If I offer to make a paypal donation could I summon the help of one of the more experienced Android gods that frequent this forum that can help me get through this?
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Genesis1791 said:
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Click to expand...
Click to collapse
On one or two tries, when the device was attached to my laptop I got a yellow on black downloading screen but had no idea what it meant. How does this help me root it? In general the volume down+plus power button didn't do anything but reboot it.
I just downloaded the SDK last night for the last time and haven't succeeded in installing it so have still got a bit of learning to go before I can make it useful.
I have the phone back in my hand now so adding some details:
Holding volume up and down and the same time, then pressing powere gets me to the "Android system recover <2e>" screen with four options:
Reboot system now
reinstall packagages
delete all user data
delete cache data
I've tried all and none will get me out of the username/password screen after reboot. If I select "reinstall packages" it says:
E:can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
after mailing SAMSUNG by Mr.Alzubair
from ce4arab website
about the Death screen
this is the answer :
-----
Dear Alzubair ,
Thank you for contacting Samsung Electronics.
Reference number:2104286715
Regarding your case, kindly note that the image you have displayed on
the screen of your phone, indicates that the device has entered the
Recovery Mode. The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
In order to get out of the Recovery Mode, please follow the steps below:
Recovery Process
1.Remove the battery and reinstall it. Power On your Phone
- Phone display “Connection picture for Phone to PC”
2. Recovery Mode in Kies
If upgrade failed in upgrade step, you can see next Pop-Up
- Select "Yes”
Firmware Upgrade program progress to recovery mode.
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
5. Click “Next”
- Firmwareversion display
- Firmware file is downloaded to PC
6. Firmware update
- After Firmware downloaded, Click “Next”
- Firmware update start
Caution
- Never disconnect or turn off the
device in thisstep
- If so, recover the phone refer to
recovery section
7.Complete
- After Firmware update complete, the device reboot
automatically
- Click “Next” Button
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
I hope this has been of some assistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-4286715
reference number.
Kind Regards,
Aya Smith
Samsung Electronics UK
Customer Communication Centre
Tel.: 0845 726 7864 (All calls charged at Local Rate)
Homepage: samsung.com
[Product] GT-I9000
The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
Click to expand...
Click to collapse
Bwahahahhaahahahahh!!
cheetah2k said:
Bwahahahhaahahahahh!!
Click to expand...
Click to collapse
LOL XD
at least they help me
I just tried it ( by the Manual way ) and it Works
so this works on the semi-bricked, no 3-button combo enabled phones ??
.. let's say, after a bad/failed bootloader flash ?
someone please confirm ?
later edit:
from what I understand after reading this, Kies can force any (Phone--!--PC) SGS into recovery and/or download mode?
if so, can we "extract" this feature and make it into a stand alone solution for half-bricked phones?
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
franklin01 said:
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
Click to expand...
Click to collapse
Some SGSs can't access download mode from that screen because of the proper bootloader that's missing. (3 button combo fix needed, not so safe)
wish samsung also adds a feature to kies that fixes the IMEI =D
franklin01 said:
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
Click to expand...
Click to collapse
2day i triad it two times and it works
but from what i understand same thing happened to me today ..
i did the 3 times flashing way :
BE SURE THAT YOU disconnect THE CABLE!!
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
Then its work and downloading mode appear i installed an official Ver. by odin ( check on Re-Partition ) then it will work (work for me after the same thing that happened : No possibility to power on, no charging, nothing. )
Does this means that the phone has a secondary bootloader or what I dont get it, I already sent my phone to samsung so I cant try, I had my phone bricked stuck at a black screen after the S logo.
hang on... so it sounds like samsung is saying that phones that dont go into download mode straight away from vol-down, home and power need to keep holding the power button until the power cycles 2 times, then let go on the third?
i cant test it now because after i bricked my phone (black screen no power on or charge) i sent it back and i got a new motherboard with 3-button enabled... but this does make sense because when i had a 3-button disabled phone previously i did manage to get it into download mode from the phone-!-computer screen by trying different timings. it took a long time but eventually worked.
so it would seem if this is the case, that it is just a different boot loader and a different key combination to access download mode, but working nevertheless?
can someone test this?
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
stephengoo said:
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
We already knew it had a secondary boot-loader...
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions
This is what is patched to hotfix the 3BR in disabled phones.
3 times flashing way wont work for me, and at Recovery in Kies i cant see my Device!
Absolutly no USB!!!!
Sorry Guys!
So this forced download mode can be possible...
This guy here tried hard to explain same thing:
http://forum.xda-developers.com/showthread.php?t=812933
do you think it will work with korean version galaxy s?
No-Exit said:
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
[Product] GT-I9000
Click to expand...
Click to collapse
"all information has bee verified" means put phone in download mode and connect it to PC (can't do it without working 3 buttons combo).
"manually instead of using Kies" = same thing, doesn't work without 3 buttons combo.
This doesn't works if you didn't have 3 buttons combo enabled. I used heat trick instead and then patch aires P-SBL.
I sent my phone back because of this black screen of death. I could get into Download mode, and the other (vol-up) mode too, but no upgrading or changing firmwares worked to fix it. And Kies didn't see it, though Odin eventually did.
Wondering now if the Black Screen of Death was fixable after all, but then would Kies have to recognize it first?
I have a phone ! pc bricked phone right in front of me, I've tried this and a million other combinations, nothing works. I'm not being super pessimistic or anything it really doesn't work. I've left it with a phone repair store overnight and they couldn't fix it either. Im going to visit samsung/optus tomorrow.
edit:
I also want to point out that that message contains some horrible english supposedly from samsung UK
d47:
I am exactly in your shoes. Even with the overnight leave at a GSM repair booth-thingy. Im also considering handing it back to the retailer, but havent tried the heating up trick yet... Maybe its worth a try ?
Hi,
I've got my good old 9505 I bought right at release on which the Volume UP button (or more likely whatever hardware it's connected to, as the button itself works perfectly normally) has become stuck pressed.
That causes a little problem - I can't enter Download mode anymore (Normal power up enters recovery due to the stuck key, Vol Down cancels Recovery and boots normally).
I had a custom ROM and recovery on it, and in order to send it for repair I obviously want to put it back to stock status, so I have reflashed a stock MI8 image I found using ODIN, using the custom recovery's "Reboot in Download mode" command.
Now the problem is I have bad luck and likely had an incompatible modem, and after booting even with cache/data wiped I have the Samsung keyboard crashing constantly and WiFi won't work.
Of course restoring the stock image wiped my custom recovery, so I can't use the same trick to get back into Download mode and reflash another modem.
I can't use Mobile ODIN or reboot menus with a "Reboot Download" option, as those requires root, but... rooting needs Download mode.
I can connect to Kies, but for my region it unfortunately says the current ROM is already the latest.
Does someone have an idea I didn't think about?
is there a way to reboot to download mode via usb debugging?/adb shell or something like that?
I found something that suggested it, however while I've painfully been able to go enable USB debugging (with the UI that locks and the "Samsung Keyboard has stopped" messages that appear between nearly every tap) adb devices returns nothing. Maybe the same issues cause debugging to fail too...
make sure that all instances of kies are stopped and also try reinstalling the drivers?
OK, found an app called "Kingo Android Root" that works from the PC through adb, and managed to root it again. It took some time to connect, but once it did it went through the procedure OK.
Then I could transfer the apk for "Quick Boot" to the phone through MTP, and its reboot menu worked to reboot in Download mode
Got a new modem flashed, and WiFi is back. The Samsung keyboard is still crashing every 5 secs, but I'll just try reflashing the OS, never know...
now that you can get to download mode, you can just restore everything back to stock? no? should fix any fc's you're getting, unless they are related to the physical fault with the volume up button being stuck?
Yes, it's just a matter of finding the right stock ROM... :\
OK, the MKF ROM for my country I found here works perfectly fine.
Issue closed then, hope this will serve other people who might end up in a similar situation
Now to see how the service center reacts to a stock config but with Knox flag set...
good luck, and don't forget to let us know how you get on with the service centre/knox situation.
Good news, received my S4 after a one week turnaround (shipping included), and it was repaired under warranty even with the Knox bit set and me having dismantled it (thanks Sammy for not putting "warranty void" stickers, pretty much the first manufacturer I see who doesn't!)
I feel really dumb, but I've got a few new Tab A 10.1 SM-T580s for my work, stock ROM, not rooted. I loaded some device management software that allowed me to blacklist the Settings app (my fault for not paying attention to what boxes I was checking).
Where I'm at:
- Devices all bootloop at the 2nd Samsung screen.
- I can get into recovery mode (power + up + home) and have tried all the options. I can't reset to factory because the device management software blocks it.
- I can't get into download mode (power + down + home) no matter what I tried*. Device boots like normal and instead of download shows the 2nd Samsung logo briefly and then the device reboots (power + down soft reset) over and over until I let go. When I let go, the device will re-enter bootloop, unless it's plugged in. If it's plugged in, I get the battery charging icon, then a battery percentage indicator, then I can unplug the device and it will "turn off".
- Tried opening it up and pulling the battery connector and letting it sit for a bit. Did not make a difference.
*Here's the weird thing: I did somehow manage to get one of the devices into download mode, so I know it's possible. Once in download, I Odin'd the stock firmware, booted it back up, and it's been fine since. But for the life of me I can't figure out what magical steps I performed on this one device that I can't replicate on the other 3.
I would greatly appreciate any suggestions as to where to go from here. I'm leaning hard into buying/making a jig, but I'm hoping there's something simple I missed.
Thanks,
Chris
chrisk82 said:
I feel really dumb, but I've got a few new Tab A 10.1 SM-T580s for my work, stock ROM, not rooted. I loaded some device management software that allowed me to blacklist the Settings app (my fault for not paying attention to what boxes I was checking).
Where I'm at:
- Devices all bootloop at the 2nd Samsung screen.
- I can get into recovery mode (power + up + home) and have tried all the options. I can't reset to factory because the device management software blocks it.
- I can't get into download mode (power + down + home) no matter what I tried*. Device boots like normal and instead of download shows the 2nd Samsung logo briefly and then the device reboots (power + down soft reset) over and over until I let go. When I let go, the device will re-enter bootloop, unless it's plugged in. If it's plugged in, I get the battery charging icon, then a battery percentage indicator, then I can unplug the device and it will "turn off".
- Tried opening it up and pulling the battery connector and letting it sit for a bit. Did not make a difference.
*Here's the weird thing: I did somehow manage to get one of the devices into download mode, so I know it's possible. Once in download, I Odin'd the stock firmware, booted it back up, and it's been fine since. But for the life of me I can't figure out what magical steps I performed on this one device that I can't replicate on the other 3.
I would greatly appreciate any suggestions as to where to go from here. I'm leaning hard into buying/making a jig, but I'm hoping there's something simple I missed.
Thanks,
Chris
Click to expand...
Click to collapse
Since the problem is obviously the device management software, contacting their tech support would be my first step. None of us are going to be familiar with their software.
lewmur said:
Since the problem is obviously the device management software, contacting their tech support would be my first step. None of us are going to be familiar with their software.
Click to expand...
Click to collapse
I contacted their support, which is how I found out about the Settings blacklist issue. They said to contact Samsung to get the device reset. Samsung said I'd have to take the device to a retail chain, though it was unclear as to what the retail chain was going to be able to do that I couldn't with a copy of the firmware.
Also, the fact that I was able to get one of the devices un-borked makes me think the device management software shouldn't be blocking download mode, but I can double check with them.
Edit: FWIW, contacted the company (ManageEngine, since I didn't note it before), they said their software should not block the hardware key commands.
Thanks,
Chris
chrisk82 said:
I contacted their support, which is how I found out about the Settings blacklist issue. They said to contact Samsung to get the device reset. Samsung said I'd have to take the device to a retail chain, though it was unclear as to what the retail chain was going to be able to do that I couldn't with a copy of the firmware.
Also, the fact that I was able to get one of the devices un-borked makes me think the device management software shouldn't be blocking download mode, but I can double check with them.
Edit: FWIW, contacted the company (ManageEngine, since I didn't note it before), they said their software should not block the hardware key commands.
Thanks,
Chris
Click to expand...
Click to collapse
Pilot error.
I've never heard of any management software capable of preventing downloading mode.
It's just not possible.
Either you're not holding the buttons in the correct sequence or not holding for long enough.
If you can boot to recovery then just select 'Boot to Bootloader' from the list.
ashyx said:
Pilot error.
I've never heard of any management software capable of preventing downloading mode.
It's just not possible.
Either you're not holding the buttons in the correct sequence or not holding for long enough.
If you can boot to recovery then just select 'Boot to Bootloader' from the list.
Click to expand...
Click to collapse
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
Hold the 3 buttons in this order and ensure they are firmly pressed. If you fail to hold the HOME button in it will continually reboot.
HOME + VOL DOWN + POWER.
It's best if you can do this from Power off.
When the device starts up hold for another few seconds and then let go.
chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
It isn't a problem with the build.
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
This is the latest build from Samsung. Mine has that exact same build and it goes to download without any problem. I still say the problem is with the "device management software". THAT is what is different.
I'm confused as to how you are veryfying the builds if the device cannot boot?
ashyx said:
I'm confused as to how you are veryfying the builds if the device cannot boot?
Click to expand...
Click to collapse
The build shows in the recovery screen. But not the kernel version.
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.
lewmur said:
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.
Click to expand...
Click to collapse
It doesn't work like that. Update zip packages are signed.
For that to even have a chance you need to catch the OTA.
ashyx said:
Hold the 3 buttons in this order and ensure they are firmly pressed. If you fail to hold the HOME button in it will continually reboot.
HOME + VOL DOWN + POWER.
It's best if you can do this from Power off.
When the device starts up hold for another few seconds and then let go.
Click to expand...
Click to collapse
Tried this from a device with a dead battery charged up to over 20% (maybe needs more?), still boots up to normal Samsung start screen and loop.
ashyx said:
I'm confused as to how you are veryfying the builds if the device cannot boot?
Click to expand...
Click to collapse
I'm using the build and kernel off the one device I was able to reflash (which has rebooted unexpectedly a few times now, so that's concerning). I suppose it's not a safe assumption they're the same as the boot-loopers.
lewmur said:
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.
Click to expand...
Click to collapse
It does, and I did try that route, but as was noted, it doesn't validate the zip as signed. I'd assume the same result if I loaded the zip off the SD Card. And since that option mounts ADB in sideload only, I can't do much else with it.
I've re-contacted Samsung, and they insist that if I take them to the local Best Buy, there's a Samsung tech there that can get them working. So I'll take the devices there, and report back what I find out. I'm highly skeptical, but we'll see.
Thanks again for all the suggestions and help.
Chris
A quick update:
Took the tablets to the nearest local Best Buy, they looked at me like I had horns when I said Samsung sent me there. Of course, the Samsung rep (who everybody assumed was just a sales rep) was only there on weekends. So maybe others would have had better luck.
In this case, with them still under warranty, I called Samsung back and got them shipped out to a repair center to be flashed by Samsung.
So no clear answer one way or the other, I'm still a bit skeptical of the device management software preventing the download keys, but who knows. Hopefully they'll be back from Samsung shortly all shiny and new and I can try again (make sure to not disable factory reset in the future, I guess).
Chris
Just to final update:
Utilmately, lewmur was correct.
Devices came back from Samsung with their main boards replaced and I was able to get in to download mode...until I put the device management software on them. I re-contacted ManageEngine support, got a different person, and they pointed to a security setting called "Safe Mode" that their software provides that only applies to Samsung devices to prevent ODIN mode. Sorry to have wasted everybody's time on my not understand the software, but thanks again for the suggestions.
Chris
Hi. Browsed for ages and always come here for answers.
Here's my problem.
2x S8s. SM-950f.
Updated to most recent software through software update. Both phones were glitchy and crashing and just generally irritating after.
Factory data reset etc. This did not resolve the problems, also led to one of them having issues with FRP (annoying)
Used Odin to try and flash the latest firmware (from sammobile, UK BTU) after flashing both, they reset and powered on. Got stuck at the S8 screen.
Restarted then both were at the "an error occurred during update" screen.
Managed to get back to download screen. Re checked the software and model numbers, even that the bootloader was the correct version etc. All was fine.
Connected to Odin, shows that it is connected, but nothing happens when clicking start.
Now after attempting that, both phones will not power on.
(One will when placed on the wireless charger, but just sticks at S8 screen) and download mode or reset screen can not be accessed. So, not exactly happy. And totally out of ideas
Any suggestions, beyond taking it to a shop to see if anyone can help.
yes .....dont tuch the phones for 24 hours let the battery die ...it will...connect to pc and then try download mode....u may need to press combination for like 1 minute to get to download mode....flash twrp reboot directly into it when odin says successfully .....wipe system data ....dont turn on phone download any custom rom flash and enjoy.....it will trip knox but worth than getting a new board....
Okay, will give that a try.
TWRP?
TWRP install
https://dl.twrp.me/dreamlte/twrp-3.2.3-0-dreamlte.img.tar.html: Download link for twrp SM-G950F (dreamlte)
Just said, wait until your device powers off due battery insufficience. Plug cable and hold at the same moment vol(down)+bixby+power. Then press vol(up) at the warning screen to proceed to odin mode. Let it charging a while like 1 h. Then unplug it and plug it to your pc. In Odin select ap the previous downloaded file. Take your mobile in your hand. With one hand, prepare your fingers to vol(up)+bixby and with the other hand start the flashibg process. Be careful, and take your hand directly from the mouse if you clicked start in odin, and position your one finger to power button, but dont click. If odin start pass, press immidiately the buttons (vol(up)+bixby+power) and let it to start into recovery. If you arrived to recovery, reply to us if not search for help!!!
Good luck
memreb
Still trying to get them on. Powered on to download mode but only for a couple of seconds and switched off again.
Can't get them to power on. Buggered
simonboyle said:
Still trying to get them on. Powered on to download mode but only for a couple of seconds and switched off again.
Click to expand...
Click to collapse
i have the same issue with my s8 but when i boot in download mode the screen goes black but if i press volupe up it connect to odin with black screen you shoud give it a try
Will try that
Okay, downloaded TWRP, can get phone calls nected to Odin but when I extract TWRP it doesn't give a valid file type.
Am I being dumb.
No files appear that Odin will recognise.
Also just shows as "recovery" no .tar or anything
Ignore above. Corrupted download.
Sorted.
Now when flashing TWRP is gets to a fail due to
"Complete (write) fail
Hi you should try flashing official firmware
itac47 said:
Hi you should try flashing official firmware
Click to expand...
Click to collapse
The point of the thread us that I am.unable to do that.
So kinda useless post buddy.
Read the OP.
Anyone want two bootlooped S8s? Hahahaha
simonboyle said:
Anyone want two bootlooped S8s? Hahahaha
Click to expand...
Click to collapse
Not sure what stage your at and maybe some more useless ideas
1. Trying to flash twrp is kinda of useless if you can't get into your system need oem unlock for that.
2. Have you tried taking out Sim card and SD card and reboot.
3. If you can at least boot try smart switch as it has a emergency recovery option.
4. Trying rebooting in safe mode.
All been attempted