Related
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 all
Came across a Samsung Galaxy S5 I've now taken the liberty of trying to get working...
The phone was purchased from eBay I believe - brand new and in original packaging. The instruction manual is Japanese, as is parts of the ROM so I'm assuming Japanese origin.
The model number in the phone settings is quoted as SM-G900F, under the back case of the phone the model is quoted as SM-G900J, on the box and at places in the ROM it's quoted as SCL23. Which is it??
User has never modified the phone firmware/recovery or flashed the device. The device has knox 0x01 and a custom ROM on it which perhaps the seller installed?
All the following problems started around mid day yesterday, user was not doing anything unusual with the device - just regular usage.
The problem
Wake lock started mid-day yesterday according to the graph in settings. Continues after phone restart
At the same time, sending and receiving text messages became extremely slow/delayed. The phone just shows the spinning icon next to any text that is being sent (same in Hangouts and Messages) and the text takes 10 minutes to a few hours to come up on another device. Sending texts to the phone is also just as slow. (phone calls work fine)
Mobile data is working without issue
Google Play store does not load - eventually shows that the login is not valid after a long wait
Snapchat does not load correctly
All other apps appear to be functioning
All files in private mode have been lost, adding files to private mode seems to delete them when private mode is disabled (nothing shows up once the mode is enabled again)
Unable to install APK files locally, after clicking on the APK nothing comes up
Phone no longer shows up on PC as a media device or filesystem. Computer does recognize the phone in device manager - although I think it's coming up as something other than what it normally comes up as
"Reset to factory" accessed from inside the phone's settings does nothing when the button "delete all" is pressed
Samsung "smart switch" PC software sits on "connecting to device...." until it times out.
Samsung "smart switch" emergency recovery/initialization options ask for model number and serial number - only IMEI and model is printed on the box. Under the battery there is only IMEI. Inside back case on phone it says only the model. In the settings of the device it has a serial number listed which is around 8ish characters in similar form to 123456a78. None of these numbers are accepted by smart switch as the serial number. (device is not even plugged in to PC, why do they need the serial/model?)
What I've tried
Booting in to recovery - there doesn't appear to be a recovery. Holding the usual button combination brings me to a single screen with a long paragraph in Japanese and a yellow escalation mark with two options. Pressing up volume key restarts the device and the down volume key enters download mode/ODIN
Smart switch software on PC
Resetting the device to factory settings - a bit difficult with no working recovery and the option in the phone settings not working
Found a recovery/root to flash that promised a stock recovery and root (I really just wanted a stock recovery or A recovery) on these forums, flashed via ODIN and device restarts immediately to ODIN saying "device could not boot" in red at the top. Turning device on every time resulting in this "could not boot" - still the same screen shown when recovery buttons are held
Flashed a recovery (looks successful on PC and in ODIN on phone screen) not CWM, the other starting with a T whose name eludes me right now - phone boots up normally in to the buggy system immediately after flashing but doesn't usually boot up when restarted or turned on normally. Still the same screen shown when trying to boot in to recovery
In about 12 hours, if nobody suggests anything else, I plan to flash a stock ROM or cyannogen mod in the hopes that this fixes whatever issue is happening here.
Any ideas?
Thanks in advance!
Turns out SM-G900F roms and recoveries are not compatible with this device despite it saying SM-G900F in "about phone". I had to flash an SCL23 recovery that I found here http://forum.xda-developers.com/showpost.php?p=60291007&postcount=31
Factory wipe did the trick!
So there I was, using Cloudy 3.3 on my G2 international model (d802) when I thought to myself: Why wouldn't I change the ROM. I guess I got bored of it and while in the past year I tried almost EVERY ROM (at least every 5.1 lollipop ROM and these new marshmallow ROMs) I wanted something different this time. I remembered that Flyme OS system and wanted to give it a go. I found one here on xda site, I think it was Flyme 4.1 or 4.0 or something like that but I decided to go for a ,,newer" version of the system.
I found Flyme OS on this site: http://www.flyme.cn/firmwarelist-14.html
And as you can see the entire site is in Chinese but I managed somehow and downloaded it. I had TWRP 3.0 installed and I think I know the thing or two about flashing ROMs on this device. The whole installer is AROMA based and even though it was in Chinese I managed to flash the system. And that's when I knew I f****d up. After I installed it and it booted up, I figured that I'm not really into the whole Flyme interface and wanted to revert to stock. But I couldn't!
1. I no longer have download mode, when I stick USB cable and hold volume up it shows me an animation of ,,download mode'' but then in upper left corner appears a message saying ,,boot secure error'' or something like that and then it shows me a black screen.
2. I no longer have my TWRP recovery installed.
- I can't use 3rd party apps to restart my phone into recovery because this OS is NOT rooted! And I can't even root it because there's no method for it. I tried the default rooting method for MEIZU phones which include you logging in to your Flyme account and all of a sudden ,,root permissions'' option appears in your settings - DIDN'T HAPPEN. I also tried other different methods but to no avail. It just can't be rooted. - Even when I turn the phone off and try to do the hard reset thing with simultaneously holding power + volume down button - it won't show me the LG's default ,,factory reset'' screen which could potentially lead me into TWRP. It just boots normally!
So, the conclusion:
I flashed an unknown Flyme OS system for LG G2 from a Chinese site and it works decently good but when it installed - it turned my G2 completely to a MEIZU phone. I have no clue on how to revert it and PLEASE I would appreciate any help given. Before giving your opinions in the comments, do read every sentence I wrote above.
Thanks in advanced.
duff105 said:
So there I was, using Cloudy 3.3 on my G2 international model (d802) when I thought to myself: Why wouldn't I change the ROM. I guess I got bored of it and while in the past year I tried almost EVERY ROM (at least every 5.1 lollipop ROM and these new marshmallow ROMs) I wanted something different this time. I remembered that Flyme OS system and wanted to give it a go. I found one here on xda site, I think it was Flyme 4.1 or 4.0 or something like that but I decided to go for a ,,newer" version of the system.
I found Flyme OS on this site: http://www.flyme.cn/firmwarelist-14.html
And as you can see the entire site is in Chinese but I managed somehow and downloaded it. I had TWRP 3.0 installed and I think I know the thing or two about flashing ROMs on this device. The whole installer is AROMA based and even though it was in Chinese I managed to flash the system. And that's when I knew I f****d up. After I installed it and it booted up, I figured that I'm not really into the whole Flyme interface and wanted to revert to stock. But I couldn't!
1. I no longer have download mode, when I stick USB cable and hold volume up it shows me an animation of ,,download mode'' but then in upper left corner appears a message saying ,,boot secure error'' or something like that and then it shows me a black screen.
2. I no longer have my TWRP recovery installed.
- I can't use 3rd party apps to restart my phone into recovery because this OS is NOT rooted! And I can't even root it because there's no method for it. I tried the default rooting method for MEIZU phones which include you logging in to your Flyme account and all of a sudden ,,root permissions'' option appears in your settings - DIDN'T HAPPEN. I also tried other different methods but to no avail. It just can't be rooted. - Even when I turn the phone off and try to do the hard reset thing with simultaneously holding power + volume down button - it won't show me the LG's default ,,factory reset'' screen which could potentially lead me into TWRP. It just boots normally!
So, the conclusion:
I flashed an unknown Flyme OS system for LG G2 from a Chinese site and it works decently good but when it installed - it turned my G2 completely to a MEIZU phone. I have no clue on how to revert it and PLEASE I would appreciate any help given. Before giving your opinions in the comments, do read every sentence I wrote above.
Thanks in advanced.
Click to expand...
Click to collapse
Bump.
C'mon guys, there has to be someone who could possibly try to help
duff105 said:
C'mon guys, there has to be someone who could possibly try to help
Click to expand...
Click to collapse
Did you tried going to recovery mode by completely shutting off your phone and then pressing volume down + power button simultaneously. If goes into recovery mode as you said you have no twrp installed. What does it shows and also what happens when you connect your phone to pc in recovery mode?.
P.S i recovered from a similar issue like you on my sprint g2
qasim799 said:
Did you tried going to recovery mode by completely shutting off your phone and then pressing volume down + power button simultaneously. If goes into recovery mode as you said you have no twrp installed. What does it shows and also what happens when you connect your phone to pc in recovery mode?.
P.S i recovered from a similar issue like you on my sprint g2
Click to expand...
Click to collapse
I tried going to recovery with my phone being completely shut down, however, it simply turns the phone on. No button combination gets me into recovery anymore. As if it simply vanished from my phone (the recovery, of course). It doesn't show the default ,,Factory data reset" option when I hold volume down + power button whilst turning the phone on. No options whatsoever. So I didn't even get the chance to connect it to the PC while in recovery, since there's no recovery installed on my phone.
duff105 said:
I tried going to recovery with my phone being completely shut down, however, it simply turns the phone on. No button combination gets me into recovery anymore. As if it simply vanished from my phone (the recovery, of course). It doesn't show the default ,,Factory data reset" option when I hold volume down + power button whilst turning the phone on. No options whatsoever. So I didn't even get the chance to connect it to the PC while in recovery, since there's no recovery installed on my phone.
Click to expand...
Click to collapse
install quick boot. and try to access to recovery. maybe it will help.
otherwise... kingroot ... if your phone is not rooted. google for autorec for your model phone. it will install the recovery again
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
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