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 all,
I've received my S7 Edge today(Exynos), yay.
All was working flawlessly until few moments ago, I was running 3Dmark, and before I even start to bench, while i was downloading the first scene The screen goes all black, then after 10 seconds, there's a message on top (in the same way a rooted phone would display "kernel is not seandroid enforced..."):
Bootloader Exception
[RST_START = 0x100000000 ]
[...]
Exception: do_handler_serror: SERROR(esr: 0xbf00000000)
[...]
I didn't install any rom, root or else, it's pure stock untouched. I tried to reboot phone using volume down+power, it reboots I think (screen goes all black) but quickly the same message appears...
I'm surely going to call phone operator to tell them that phone is KO, but if one of you guys has any idea that would avoid me to send back phone to warranty, it would be nice
Thanks !
@mods : Sorry for posting in wrong section
Try this...
https://www.youtube.com/watch?v=UV0Zp7F1LHs
I'd suggest a factory reset if the above fails.
Hold Power + Volume Up + Menu
Then use the volume keys to scroll to factory reset and select using menu or power buttons.
Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..
Mr_PoPoP said:
Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..
Click to expand...
Click to collapse
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).
Cst79 said:
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).
Click to expand...
Click to collapse
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c
Mr_PoPoP said:
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c
Click to expand...
Click to collapse
I'm stumped. I've never seen that before
From where did you order your phone?
thunderroid said:
From where did you order your phone?
Click to expand...
Click to collapse
A french mobile operator , Bouygues Telecom.
Can you do a factory reset from the Settings menu?
thunderroid said:
Can you do a factory reset from the Settings menu?
Click to expand...
Click to collapse
Nope, the phone doesn't boot anymore... it only displays the bootloader error message...
And no possibility to access reboot or recovery...
Maybe I can try to check with ADB, but my problem is that i would need to active USB debugging in settings ... but i can't do that
Return it. Nand flash died.
Sent from my iPad using Tapatalk
Yap, I think you have to return it.
hiepgia said:
Return it. Nand flash died.
Click to expand...
Click to collapse
Yep, I wanted to avoid it, but I don't see other reasonnable option. The phone didn't last more than 24h ... ok, it happens, I know ...
My previous (Still actual (sic)) Phone was a Note 3 and I installed so much roms, soft bricked the device so many times, but I could always restore it ... But not the S7 EDGE ... And I didn't spot any other user with same bootloader issue...
I've just sent back the phone for replacement, Thanks for all who replied to me in this thread
Oh and by the way : don't download 3DMark from play store , it will Hard brick your phone !!! (haha just kidding , i know it's not what caused my phone to die, I'm sure of it , however I won't try to install it anymore i think^^ )
Cheers XDA crew !!
Mine has done just the same. went to bed, woke up this morning and the same message as yourself.
Borgella said:
Mine has done just the same. went to bed, woke up this morning and the same message as yourself.
Click to expand...
Click to collapse
Sorry to hear that bro
Try things to troubleshoot if you wanna, but my advice : don't lose one day of trying to fix it, send it back directly to warranty...
I tried lot of things, key combination to reboot phone in recovery or download, I tried Kies, Odin, ADB....
I believe it's a real samsung bug that will happen to many people, So send it now before sammy is drowned under hard bricked S7 phones and start to have issues to provide replacement devices....
the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.
johanbiff said:
the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.
Click to expand...
Click to collapse
That is to correct the Screen Edge sensitivity
For anyone else who runs into this issue, I managed to fix my phone.
Holding the power and VOL down buttons for about 5-10 seconds will reboot the phone; if you hold home at the same time you can get into download mode (might take a couple tries).
From there, you can flash a new bootloader (BL option in odin) and then get back into recovery to do whatever you need to do.
Went from soft-brick to full restore in about ten minutes--not even a factory reset necessary.
Hope this helps!
so guys,
my S5 screen just went black from one moment to the other, the touch lights still go on but that's it. i still can take screenshots and get messages so it's still functional.
first time for me here since my coworker hinted me of this site. so not used to working with tech etc.
thank you!!
Does it work when you first power on the phone or enter download mode (Volume Down & Home & Power) from a powered off state ?
If not, sounds like a hardware issue
If it does, try booting into recovery (Vol up & Home & Power) and clear caches, then reboot, if that doesn't work, factory reset and try
If it still fails, flash a stock ROM from sammobile .com with ODIN
unfortunately it does not, can i get it fixed in another way?
You can use this
http://forum.xda-developers.com/showthread.php?t=2786395
To see your screen on a PC, but not easy to know what's wrong over the net, if it just suddenly happened, and you get no image at any point of the boot process, then something hardware has failed
Unlikely to be a lose connection if it just suddenly happened without any drop or knock
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