Develop Bugs

Bricked SM-T705

Hi all Xda members and developers. I need your help.. My Tab S 8.4 (T705) appears to be brick. It suddenly restarts itself and stuck with black screen. When I tried to enter Download mode, it shows me below info instead of normal Download mode:
SDCARD MODE
UP KEY: NORMAL BOOTING
DOWN KEY: DOWNLOAD MODE
(See picture attached)
But when I press volume key Up or Down, it does not do anything. Trying to enter any other mode (such as Recovery mode) does not do nothing either.
It appears to be brick and I am not sure what to do with this.
Please help.
UPDATE 2
Last night I could not find any solution and could not even turn off the screen, so I left it on and went to sleep. When I woke up this morning and check it again, the batter was dead. So I plug in charger and it show the charging logo and then I tried to turn it on..... and volla.. it boots back to normal state... Interesting but this is really what happening.
UPDATE 1:
I found some information on some certain Galaxy S3 devices which had the same/ semilar problem. In this case, the phone could boot from SD Card.
I think It may work if there is anyone who could help dumping the Tab S T705 bootloader (I am so sure how this is done anyway) to empty SD card?
Millions thanks ahead...

Samsung is ****
what rom did you have?
Try to connect your tab with odin to flash stock rom

rowihel2012 said:
Samsung is ****
what rom did you have?
Try to connect your tab with odin to flash stock rom
Click to expand...
Click to collapse
Errrrrr!
How can he flash stock ROM if he can't put it in download mode?
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
vichet007 said:
Hi all Xda members and developers. I need your help.. My Tab S 8.4 (T705) appears to be brick. It suddenly restarts itself and stuck with black screen. When I tried to enter Download mode, it shows me below info instead of normal Download mode:
SDCARD MODE
UP KEY: NORMAL BOOTING
DOWN KEY: DOWNLOAD MODE
(See picture attached)
But when I press volume key Up or Down, it does not do anything. Trying to enter any other mode (such as Recovery mode) does not do nothing either.
It appears to be brick and I am not sure what to do with this.
Please help.
Click to expand...
Click to collapse
Do you have an sd-card in the unit?
If so what happens when you remove it?

Odin does not detect it since its not download mode. This SD Card mode is very new to me.
Sent from my SM-N900 using XDA Free mobile app

vichet007 said:
Odin does not detect it since its not download mode. This SD Card mode is very new to me.
Sent from my SM-N900 using XDA Free mobile app
Click to expand...
Click to collapse
I'll ask again
Do you have an SD-Card in the unit?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What happens when you remove it?

pinsb said:
I'll ask again
Do you have an SD-Card in the unit?
What happens when you remove it?
Click to expand...
Click to collapse
There is no difference or change when the SD-Card is in device or not. I've tried to enter download mode both cases (with and without SD card inside). Thanks.
Sent from my SM-N900 using XDA Free mobile app

Hey I just noticed this thread and skimmed through it very quickly. Same thing happned to mine a couple weeks back. SM-T705 with the same screen. Mine happened after an overnite charge when I powered up the device. I'm running SuperSamsung rom v2. Long story short, I tried everything to boot into recovery and reset the device. Through some research, I found out that I needed to reset the battery, which would have been simple if our batteries were removeable. Here is how my device was reset. Hold POWER + VOLUME UP + VOLUME DOWN = BATTERY RESET - You will need to do this for at least a minute for it to reset. Good luck and hope this helps.
BTW mine was reset after the battery had been completely discharged
Sent from SM-T705

Try enter download mode and try flash through Odin if it let's you but all Samsung's can be easily restored
See if you can get a USB JIG or something for the T705 there very helpful for fixing bricked devices
TAPATALKED WITH MY TAB S 8.4

i had got the same Sdcard mode too, anyone know how n why? is it a sign that the soft or hardware over tweaked? - am using SM-T705 IRON Rom 1.1.5

Help! I soft bricked my Pumpkin head unit and need help fixing it!!!

I have a pumpkin rk3188, 2gb ram, 32gb nand, 7" head unit (http://www.autopumpkin.com/car-dvd-...-gps-obd2-wifi-3g-steering-wheel-control.html) and I tried to get @Malaysk rom on it, but it wouldn't let me into bootloader or recovery no matter what I did, even with root bootloader just rebooted system and recovery went to recovery but just ran a factory reset script without giving me any options. So I tried to flash a factory image using the gps sd and naming it update.img, now the boot logo is different and it's stuck in a boot loop and I still can't get into bootloader or recovery. And I've tried to put another update.img on the sd card, but it does nothing. Is there anything I can do or am I sol?

I did the alt prtscr I trick with a USB keyboard plugged in n seem to have gotten to some menu but it's off the screen for some reason. I can see the edge of a highlight bar that I can move with the arrows up n down, n a thin line at the end of the list, whatever the list says idk. There's 7 options tho, it seems like the first attempts to boot, the second n third do something bit idk what, n the rest just return to this menu. It's orange btw. I'm going to upload pics of what I see. Can anyone help me figure out what this menu is n if I can use it to fix me unit? Thx!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS990 using XDA-Developers mobile app

Same here bro. Flashed malaysk rom. Lost the recovery.

chezimus said:
Same here bro. Flashed malaysk rom. Lost the recovery.
Click to expand...
Click to collapse
I GOT IT!!!! I got it back up n running the pumpkin firmware!!! Idk about u man, but I figured out/git lucky with the orange recovery or bootloader I had n couldn't see the writing. I got the official firmware from pumpkin for this unit n downloaded the right mcu img, put them both on the sd card n put it into the GPS slot, then used the keyboard to get to the orange screen n the option that worked was the 3rd one down. It took a while, 15-20 minutes of nothing but a black screen, but it finally came back up with the boot logos. It was stuck at the boot logos again so I reset n did the alt prtscr I trick again to get to recovery again n it wiped n reinstalled the img n bam it worked! Slow first load but it worked! Let me know if u need the files or help.
Sent from my VS990 using XDA-Developers mobile app

I've been fighting the same problems. I would love the files too. Which mcu img did you use.

For my pumpkin unit it's a bin file, they call it project-car.bin. There's a mcu updater that uses bin files in the settings. The stock recovery doesn't recognize mcu.img sadly. I uploaded the project-car.bin here (https://drive.google.com/file/d/0B2T5FQZ-WJDQS3hXVFFFTnIwaGc/view?usp=drivesdk) and you can get the stock rom from pumpkin here (https://mega.nz/#!lc9HAbLK!nAIsEvYnSwqCV47vCmMRKBVivygxaJbGD3KPV0pxvZ8)
Sent from my VS990 using XDA-Developers mobile app

They same thing happened here too. Just a boot loop and no way to get into recovery with the buttons.
Could you please tell how the mentioned trick works?
alt prtscr I trick with a USB keyboard
Click to expand...
Click to collapse
Thank you very much in advance!

Could you please tell how the mentioned trick works?
Use a USB keyboard attached to the head unit's USB port. Either port should work. After powering the HU or resetting, press and hold the alt and prtscr keys, then press and release the "i" key. It should then boot into recovery. If not, repeat.

Hello， can you tell me what can bus options you have in factory settings. Mine have only BMW 1，2，3，4 . no another car. And reverse camera is to black.
Thank you.

Fix Blootloader and Logo

I have a problem with a Nexus 5x and I wanted to see if you can help me. I would really appreciate it
Yesterday I answered a spam call . And from there and I had problems, I was slow, I quickly downloaded the battery and suddenly it went out, hence it is no longer the Google logo.
I am not so new in this. I tried to enter the recovery mode and delete everything, but it will not let me enter, it returns to Fastboot mode.
- Have the boot manager blocked.
- I do not have the OEM option open.
-I can not enter the recovery mode.
- The PC if it recognizes it by Fastboot mode
What I can do?
I hope you can help me. Thanks for your attention.

al3al3al3jandr0 said:
I have a problem with a Nexus 5x and I wanted to see if you can help me. I would really appreciate it
Yesterday I answered a spam call . And from there and I had problems, I was slow, I quickly downloaded the battery and suddenly it went out, hence it is no longer the Google logo.
I am not so new in this. I tried to enter the recovery mode and delete everything, but it will not let me enter, it returns to Fastboot mode.
- Have the boot manager blocked.
- I do not have the OEM option open.
-I can not enter the recovery mode.
- The PC if it recognizes it by Fastboot mode
What I can do?
I hope you can help me. Thanks for your attention.
Click to expand...
Click to collapse
When you try to enter recovery mode what does it look like? Can you post a picture?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
When you try to enter recovery mode what does it look like? Can you post a picture?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
1.- I put in fastboot mode
2.- I give it in recovery mode
3.- The logo starts and from there it repeats repetitively in the logo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So it never gets to recovery. It just tries to reboot? Without oem unlock I'm not sure what you'll be able to do.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
So it never gets to recovery. It just tries to reboot? Without oem unlock I'm not sure what you'll be able to do.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It never starts, it just stays there.
There is some way to force it to start?

al3al3al3jandr0 said:
It never starts, it just stays there.
There is some way to force it to start?
Click to expand...
Click to collapse
Not sure if this would really help but keeping your phone in the refrigerator for few hours would let you turn it on. Then quickly enable the USB Debugging and OEM Unlocking. I had the bootlooping issue and freezing the phone really worked in terms of enabling the USB Debugging and OEM Unlocking. Then you should be able to sideload an update.

Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset

I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?

If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....

73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!

I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.

droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.

Question Hard bricked Mi Pad 5, while installing windows 11

Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)

mdve123 said:
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
Click to expand...
Click to collapse
Sorry to hear that, please share your steps to disaster to let others know how to avoid this.
I assume that you used default Windows installer that broke your ufs gpt, instead of the installer you should have been used dism.
At this stage only a service may help you, they will put the device in edl mode and flash a stock firmware.

I think the only way to bring it back to life is to get it into EDL mode and force flash stock rom.

but to get to EDL first have to get to fastboot, i dont think it will work, also tried...

mdve123 said:
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
Click to expand...
Click to collapse
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.

serdeliuk said:
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
Click to expand...
Click to collapse
Very useful info thank you! Just ordered a deepflash cable, hopefully i will find a workaround to flash in EDL.
If not, i'll try to get it done under warranty. I do not want to risk a keylog or a scam.

I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked

RoyPH9903 said:
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
Click to expand...
Click to collapse
You should download the latest MIUI Stable Fastboot update corresponding to your region (global, eeaor other) from this thread https://forum.xda-developers.com/t/miui-updates-tracker-xiaomi-pad-5-nabu.4328591/ , decompress the tgz file with 7zip or another software, and then, with your device in fastbboot mode, execute the flash_all.bat file within the folder you extracted. This should work even with a locked bootloader.
Good luck

I get this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RoyPH9903 said:
I get this error
View attachment 5883229
Click to expand...
Click to collapse
Well, maybe I was wrong and you need an unlocked bootloader for this method to work. You could try to unlock it again with MiUnlock https://en.miui.com/unlock/download_en.html . Otherwise, I am out of idea.

I tried it and it didn't work, it tells me that I have to enable my miui account.

RoyPH9903 said:
I tried it and it didn't work, it tells me that I have to enable my miui account.
View attachment 5883255
Click to expand...
Click to collapse
Well, then I'm out of ideas. Maybe you should see what the seller's support can do.