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
Related
What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App
jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.
Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.
I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.
I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10
How do you know whether you have a hardware locked Vibrant or not?
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk
Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?
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 ?
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might loose data if you did not Nandroid backup
I can't do any of those things
samesung said:
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might lose data if you did not Nandroid backup
Click to expand...
Click to collapse
Hi, it seems i haven't made myself clear enough ... i've tried the 2 key combinations as mentioned in the post .. but none of them have any special effect .. i have no way to boot into recovery mode or download mode.
So without download mode i have no way of using ODIN to reinstall stock firmware .. i am aware of how to use ODIN so if the download mode worked this whole thing would not be an issue for me since i could just do what you said in your reply.
But the problem is that it doesn't work ... so i dont know how to get into the phone and do stuff to fix it.
Also, i dont care about data such as photos and stuff ... the only thing i care about is my phone getting fixed!
Hope you can help or maybe someone you know for me
Florint45 said:
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
Click to expand...
Click to collapse
Hmm awkward, maybe you have hard bricked it? Idk maybe
MrHollywood said:
Hmm awkward, maybe you have hard bricked it? Idk maybe
Click to expand...
Click to collapse
Hmm, in the case of an hard brick .. what so you suggest i do ?
Do i go to the store to get it fixed. (my warranty actually expired 1 month ago) and in the case of needing such a fix .. how much do you think it would cost ?
Or do i wait for a solution from some guy on this page ?
Florint45 said:
Hmm, in the case of an hard brick .. what so you suggest i do ?
Do i go to the store to get it fixed. (my warranty actually expired 1 month ago) and in the case of needing such a fix .. how much do you think it would cost ?
Or do i wait for a solution from some guy on this page ?
Click to expand...
Click to collapse
First I would Google a solution, second I would wait about a week, who knows there might be a guy here who knows how to fix it, third of all and the end of all choices is to get it to a store, idk it might cost you at around 50-60 dollars. I once hardbricked my LG and they charged me 50 dollars. Let's hope your issues gets fixed without losing a lot of money.
MrHollywood said:
First I would Google a solution, second I would wait about a week, who knows there might be a guy here who knows how to fix it, third of all and the end of all choices is to get it to a store, idk it might cost you at around 50-60 dollars. I once hardbricked my LG and they charged me 50 dollars. Let's hope your issues gets fixed without losing a lot of money.
Click to expand...
Click to collapse
" Hard-bricked – it refers to the phone as totally jammed, unresponsive or no visible signs of starting to work as it suppose to be. No display at all. You can’t even access the Download Mode screen. The only resolution for this is by using the method called JTAG flashing, which is you are forcing to install the firmware back to the phone. The process that you are about to experience is not too easy; this includes disassembling the phone, some soldering job required and flashing by means of using a flashing device tool.
– This method means that you cannot save your device at all by yourself anymore. If you considered necessary to have your Samsung Galaxy Note 3 back to life, the best way for you to do is to bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty. "
The process explained afterwards involves "download mode" which i can't access ... so yeah .. guess il'l wait for a bit for a response that might help me .. otherwise ... il'l just take it to the store i guess !
also .. what do you think about this part: " bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty" ?
do you think it means explaining it to the dealer in detail what has happened .. or does it perhaps mean to act like a total fool and be like ; " umm .. is this supposed to be like this ?"
Hope you understood that one better than i, cause if i can get a free fix il'l be real happy !
Florint45 said:
" Hard-bricked – it refers to the phone as totally jammed, unresponsive or no visible signs of starting to work as it suppose to be. No display at all. You can’t even access the Download Mode screen. The only resolution for this is by using the method called JTAG flashing, which is you are forcing to install the firmware back to the phone. The process that you are about to experience is not too easy; this includes disassembling the phone, some soldering job required and flashing by means of using a flashing device tool.
– This method means that you cannot save your device at all by yourself anymore. If you considered necessary to have your Samsung Galaxy Note 3 back to life, the best way for you to do is to bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty. "
The process explained afterwards involves "download mode" which i can't access ... so yeah .. guess il'l wait for a bit for a response that might help me .. otherwise ... il'l just take it to the store i guess !
also .. what do you think about this part: " bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty" ?
do you think it means explaining it to the dealer in detail what has happened .. or does it perhaps mean to act like a total fool and be like ; " umm .. is this supposed to be like this ?"
Hope you understood that one better than i, cause if i can get a free fix il'l be real happy !
Click to expand...
Click to collapse
Yeah wait for a while. And what he meant was to lie lol to say you didn't do anything and somehow your device died, but unfortunately that only works when you have a warranty.
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Florint45 said:
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
Click to expand...
Click to collapse
Cheer up! Well not that much lol, I found a video that MIGHT be able to help you.
https://youtu.be/D2LZri5HT1E
Check it out and I am here if you want to ask some questions!
Maybe a USB jig will force the phone into download mode?
MrHollywood said:
Yeah wait for a while. And what he meant was to lie lol to say you didn't do anything and somehow your device died, but unfortunately that only works when you have a warranty.
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Cheer up! Well not that much lol, I found a video that MIGHT be able to help you.
https://youtu.be/D2LZri5HT1E
Check it out and I am here if you want to ask some questions!
Click to expand...
Click to collapse
It seems like we'll have to go with MIGHT since i just idetified it as being a stage 2 hard brick, i must have fiddled with it a little too much ... Hmm, the phone was getting old anyways and performance was faltering by the minute too. So i guess il'l check it out at the store if they can repair it for something like 50$ - 100$ .. otherwise, i guess il'l get myself a ****ty phone for now and wait for a new flagship smartphone to appear !
I was thinking about going for LG G5 .. good idea ? or do you have another suggestion
audit13 said:
Maybe a USB jig will force the phone into download mode?
Click to expand...
Click to collapse
Do you suggest buying one or making one myself (i found some guides about it ) .. which one do you think would perform best ? (assuming i make mine correctly)
Whether you make or buy doesn't matter as long as it does the job. I will say that a pre made jig is small and neat.
samesung said:
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might loose data if you did not Nandroid backup
Click to expand...
Click to collapse
hey in same position and want to do exactly as you mentioned,start from scratch again which infact i dont mind at all..problem is im unsure of how to do it as all i can get w h en trying all else button combo's battery pulls etc is the start screen of twrp that just loops ..
thanks in advance for reading this
give a try with Kies 3
connect your phone with pc and open kies. there you see "phone recovery guide". click on it and it will try to reinstall the whole firmware and bootloader etc. screenshot attached
I believe kies has been replaced with smart switch.
audit13 said:
I believe kies has been replaced with smart switch.
Click to expand...
Click to collapse
if i may ask what is a jig???i ive seen something mentioned a few times briefly in tutorials suggesting to use one and im running out of options.tried samswitch and kies and phone wont connect..furthest i can get is when booting to recovery it loops at opening Twrp screen and it wont go to download mode..any help greatly appreciated
A USB jig is a small device that will force the phone into download mode.
https://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
audit13 said:
I believe kies has been replaced with smart switch.
Click to expand...
Click to collapse
smart switch will not detect note 3 as it is developed for new devices like note 5 and onwards.
My note 3 and s4 worked with smart switch.
audit13 said:
My note 3 and s4 worked with smart switch.
Click to expand...
Click to collapse
ok. thanks for guidance. i will try it.
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
Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!