Related
Is my device bricked?
Had device inserted into keyboard and plugged in all night. Batteries should all be full.
Light on keyboard is green.
Cap Lock light comes on when pushed.
Computer makes camera shutter sound when "camera" button is pushed.
Nothing happens when holding power button down for 5, 10, 30, 60 seconds.
Same when holding power button down with volume up for 5, 10, 30, 60 seconds;
nor with power button down and volume down button for 5, 10, 30, 60 seconds.
Have a run into an permanent apx bootloop? (not sure what that is but doesn't sound good).
Have removed all usb and micro usb drives.
I have never rooted the device; recently did a clean factory install and had it working fine.
When plugged into my linux desktop, I was able to access it. I've created /media/transformer mountpoint, ran sudo chmod -R 755 /media/transformer
and then
sudo mtpfs -o allow_other /media/transformer
but then receive the error message:
"Transport endpoint is not connected"
This is new.
Then travelled to the USA and plugged in device to recharge at JFK at at least 2 places. None of the plugs worked. JFK was somewhat waterdamaged from recent floods. Could this have fried the device through a power surge?
Can't think of what else to do than perhaps let it power down completely and then try again.
Any suggestions would be greatly appreciated.
I purchased the device in Canada and now an living in Morocco so sending it back for an Asus RMA would be very difficult and likely more
expensive then purchasing a new Nexus to replace.
Do I now have an expensive paperweight?
Desperation?
I'm thinking of following the directions found at a tabletroms forums site that I can't post here becuase of xda forum rules, but it calls for "Nvflash Unbricking and forever root!" but would first hope there to be some simplier answer.
I've read a lot of other XDA posts and googled many a version of this question, but nothing seems to help, except, perhaps, for the link above.
Luckily, I always back up everything so nothing on the tablet is irreplacable.
Is it time for desperate measures?
Screen Visible when plugged into a HDMI TV
Going out on a limb, I plugged the HDMI cable into the TV and up pops the screen of my tablet, fully functional, battery levels OK, brightness on full and all working as it should...
...except that nothing is showing on the screen except pitch black.
Next step -- factory reset? or could this by a hardware misfunction?
I'm going to try a factory reset and see what happens. If it does not come back to life, I'll know it's a hardware malfunction and wait until I can return to Canada for an RMA, unless anyone else can think of something?
Factory Reset Did Nothing
... simply now have a factory reset tablet that can be only viewed when attached via an HDMI cable to another screen, while the screen itself, is blank.
Does that confirm an hardware problem?
I'll have to check my warenty, but my bet is that it too, just expired.
From what you described, sounds like your screen is broken.
Lingering Question...
Before turning this over as the tablet attached to the TV so the girls can watch programs from the NAT box; is there any hope that (A) reflashing a new ROM might breath life back into the old girl/tablet or (B) is there a way to do a quick fix via opening up those Torx T5 bezel screws and looking for a loose wire of two (not able to soder something that complicated).
Would that work or am I the one with the screw loose?
Broken Screen = RMA or paperweight?
So if the screen is broken, I either have to return it and hope it's under warenty, or find and replace a new screen (hmmmmm beyond perhaps what I can do) or leave it as an expensive keyboard / mouse with computer capability on an HDMI TV and if you touch the black screen in the right place -- which still works! -- then I can control the external video.
Solar.Plexus said:
From what you described, sounds like your screen is broken.
Click to expand...
Click to collapse
filosofic said:
So if the screen is broken, I either have to return it and hope it's under warenty, or find and replace a new screen (hmmmmm beyond perhaps what I can do) or leave it as an expensive keyboard / mouse with computer capability on an HDMI TV and if you touch the black screen in the right place -- which still works! -- then I can control the external video.
Click to expand...
Click to collapse
Sounds like a wire has come off or you have what is called a dry joint which happens when a soldered cable doesn't take properly, I very much doubt the screen is kaput
hi every body!
I have an original shield tablet, also it effected by kill switch.
I try to delete the TegraOTA.apk by following the instruction of @Bogdacutu http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489 then it's ok for a month.
But the trouble is when I change the IMEI (successfull) then update OTA3.1.1 via recovery. At this time, any thing also ok, but I did't delete TegraOTA.apk again, then turn on wifi for try to get OTA4.0 directly. unfortunately the tablet was shutting down after one minutes, then automatically boot to recovery before change to black screen . I understood that skill switch is activated!!! Although IMEI different !
Now when connect to PC, it become a APX device, in details http://forum.xda-developers.com/wiki/Nvflash
I try for some of solution but all of them not work. Also solution of @carlompms
good evening,
I received my recall tablet yesterday, before connecting the new one, I installed a new rom, for now I have 2 tables to work.
in the process I do not know what I did my tablet brick in apx mode.
for exit apx mode I connected to the PC, press power button until you hear the disconnect sound on pc(tablet turn off)
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
It may work for you too
Click to expand...
Click to collapse
Then if @Thepiewarrior, if you can read this post, please instruct for me that, how can you clear your trouble before: http://forum.xda-developers.com/shield-tablet/help/unlocked-bootloader-rooting-shield-t2995472 tks.
So, after my trouble, every one should remember that, must be deleted the TegraOTA.apk before go to online, then maybe all of solution try to change IMEI may be should't work.
Now, I waiting for some of solution from the expert (such as nvflash...), maybe there're some of member like me...
Hello,
So I have a bricked KGL MTCD unit. During the update process with Malaysk's most recent FUSE 5.1 ROM, the ignition was turned on, causing the screen to briefly go black, then back to the Android robot with the update status bar, and a second later the unit died.
I read in another thread that I started regarding this that it is possible to debrick an Android headunit using drivers and the RK Batch Tool. I downloaded everything from the Rockchip.nl site.
When the unit is hooked up to power only the button lights light up and that's it. No response whatsoever.
I tried hooking it up with a male-male USB cord to my Lenovo T410 laptop but there is no response from Windows regarding recognizing a USB device.
I have tried every USB port. I've tried both ports on the device and still nothing.
I have tried USB only and external power too. Nothing works.
I have also tried connecting a different, 100% working KGL unit. I hooked it up to power, then tried both USB ports and the computer doesn't recognize any.
Can anybody please tell me how to restore this thing?
Do I need to install the drivers into Windows first? I thought my PC would surely recognize the device and THEN ask for drivers. How do I go about installing them?
Thanks in advance
EDIT!!!!!!!!!!
DEBIRCKED THE UNIT WITH MALAYSK'S METHOD FROM THIS POST http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Unbricking MTCD GS
My MTCD GS RK3188 800x1024 Android 5.1.1 radio in my W220 Benz is also bricked.
It came with ROM v. 1.34 I think. So I flashed the most recent OEM ROM I could find (I think v. 1.73) through Settings/About/System Upgrade, hoping to be able to root the radio so I could use Titanium Backup.
Everything went swimmingly and all was good with the world.
Except I still couldn't root through recovery. So I tried to flash Malaysk's most recent GS pre-rooted ROM.
About half way through the process, the screen unceremoniously went black.
Now the radio is bricked. Only the button lights illuminate.
I tried several methods of rebooting into recovery, but nothing happened.
I read the HuiFei page, searched the XDA forums and the Internets generally and still could not find a solution.
I connect the radio to my computer via USB and tried to use the RKTools program, and still no luck.
I hope I missed something somewhere in my searching, so I beg of you: If anyone out there knows how to unbrick this unit, please, PLEASE share your knowledge with me.
Thanks in advance.
I just tried to update my Xtrons unit from a firmware on their site. Update finished 100% and upon reboot the screen was just black!!! There has to be a way to unbrick these. No way am i tossing out a $400 unit! I have a PF73AA4A which i believe is a RK3188 quad core 16g. Please help!
Solved! Mtcd unbricked!
@NaviPR, @shawndak and anyone else suffering the same fate:
I quite accidentally figured it out! Here's what I did (sorry, I tend to over-include information)
It started when I found a link on the Android TV Box forum about debricking RK3188 TV boxes. There was a process where the NAND was reset and then set to Mask Mode by shorting pins and pressing buttons; then the firmware was flashed with RK Batch Tool.
So I loaded RK Batch Tool and driver onto my Windows 10 computer, brought the head unit in and removed the bezel to expose the SoM.
Sadly, this SoM used a different NAND chip that did not have visible pins. So I started messing around.
At first, I couldn't get the PC to recognize the HU after trying the standard recovery process. Finally, out of frustration and without expecting any results, I tried one last thing. These are the steps:
1. Download Rockchip DriverAssistan v.4.4 and RockChip Batch Tool 1.4 zip files.
2. Extract files from each into separate directories.
3. Run Driverinstall.exe.
4. When done, run RKBatchTool.exe
5. Load your desired firmware into RK Batch Tool by pressing the dots button after the "FW Path" field.
6. Power the HU by connecting the 12V (yellow), ACC (Red) and ILL (orange) wires with 12 volts with a benchtop power supply. (Orange isn't really necessary, but it made me feel better to see the lights on.)
7. Connect the HU to the computer with a USB cable.
8. Press and release reset and wait 10 seconds.
9. Press and hold the power button for 10-15 seconds as if you were turning it off normally.
10. Release the power button and within 1 or 2 seconds press and hold it again for another 10-15 seconds until you hear your PC indicate it's loading a driver. At this point RK Batch Tool should show a connected device and the number 1 will light up blue.
11. Press the "Restore" button on RK Batch Tool. The number 1 will flash yellow while it uploads the firmware.
12. When done, repeat steps 8 and 9. The splash screen and logo screen should show up after a short while.
13. After unsuccessfully waiting a long time for it start the launcher, press reset.
14. Wait for HU to boot up and go into whatever flavor launcher you are using.
Two things to note:
1. It was helpful using a power supply with a current meter so you can actually see the current drop that indicates it's ok to release the power button and press it again.
2. When the firmwareI sideloading completed, RK Batch Tool showed a red error message "<Layer 2-6> Download Firmware Fail." Do not worry. Disregard the error message and continue with the steps.
I hope this works as well for you as it did for me.
Let me know and feel free to contact me if you're having trouble. Good luck! :laugh: :laugh:
@ibdegen
Thanks for the help, I followed your guide to the letter but unfortunately it didn't work.
Here's what I did:
- laptop runnin' Windows 7
- tried both USB ports in the unit - 3G and USB
- installed the drivers, installer said everything went fine
- I'm using a tabletop power supply which is working fine
Here's what happens:
I power UP the HU, doesn't matter if I plug in USB or 3G.
This unit is totally bricked. Only the lights in the buttons work.
I press Reset and RELEASE IT right away. When pressed the lights go off, upon depressing they turn back on.
I wait 10 seconds, I press hard on the power button, the lights go off but come back on around 10 seconds later.
I depress it, lights go off, I press hard again within a second or two, lights go on, and then nothing.
I've done this many times and nothing works.
I started frantically pressing the Power button out of frustration and I think I heard the standard "new USB device connected" sound of Windows 7 ONCE, but nothing really happened.
Wife has the car at work right now so cannot try this until later. My unit is a MTCB. Do you think your method will still work? I saw the RK3188 Android TV Mask mode as well but didn't want to risk it since the person i bought it from is willing to attempt a repair/replacement. I found the proper MCU GS file and will flash that with a 5.1.1 Fused Rom so i can use the full internal space! Will report back if all goes well. Thank you
Also noticed i cannot flash a MCU alone with the batch tool. update_5_1_1_FUSE_1024X600_RK3188_04_MAL_06_09_2016_MTCB This is the closest firmware I can find that may work for my MTCB GS unit. Will it work?
Possible Extra Steps
NaviPR said:
@ibdegen
Thanks for the help, I followed your guide to the letter but unfortunately it didn't work.
Here's what I did:
- laptop runnin' Windows 7
- tried both USB ports in the unit - 3G and USB
- installed the drivers, installer said everything went fine
- I'm using a tabletop power supply which is working fine
Here's what happens:
I power UP the HU, doesn't matter if I plug in USB or 3G.
This unit is totally bricked. Only the lights in the buttons work.
I press Reset and RELEASE IT right away. When pressed the lights go off, upon depressing they turn back on.
I wait 10 seconds, I press hard on the power button, the lights go off but come back on around 10 seconds later.
I depress it, lights go off, I press hard again within a second or two, lights go on, and then nothing.
I've done this many times and nothing works.
I started frantically pressing the Power button out of frustration and I think I heard the standard "new USB device connected" sound of Windows 7 ONCE, but nothing really happened.
Click to expand...
Click to collapse
@NaviPR
Sorry it didn't work. I'm encouraged if in fact the computer chimed.
First try the same thing, but hold the buttons longer, e.g. reset 10 secs, power 20 secs. after reset release.
Also, I did 2 other things before the hard off/on process but didn't think they were related. Maybe they are:
A. Try to get into recovery by:
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button; within 2 seconds press it again and hold another 10-15 seconds; release
4. If no boot logo shows up after a minute or so, try the hard off/on procedure.
B. Reset the NAND chip (I found nothing to confirm this is how it's done. I just assumed.)
1. Remove the front bezel to expose front of SoM board. Be careful not to damage the ribbon cables.
2. There are 2 pairs of silver test-point looking dots on each side of the NAND chip (see picture)
3. With power disconnected, short each pair individually.
4. Do A again. Then do my hard off/on procedure, holding the buttons longer.
Again, the key is to get the PC to chime and RK Batch Tool to show a connected device.
I don't know if the difference between Windows 7 and Windows 10 had anything to do with it, but you may want to consider it. Maybe try an older RK Batch Tool version with Win7. Also, try a different USB cable.
Hope this helps.
MTCB vs MTCD
shawndak said:
Wife has the car at work right now so cannot try this until later. My unit is a MTCB. Do you think your method will still work? I saw the RK3188 Android TV Mask mode as well but didn't want to risk it since the person i bought it from is willing to attempt a repair/replacement. I found the proper MCU GS file and will flash that with a 5.1.1 Fused Rom so i can use the full internal space! Will report back if all goes well. Thank you
Also noticed i cannot flash a MCU alone with the batch tool. update_5_1_1_FUSE_1024X600_RK3188_04_MAL_06_09_2016_MTCB This is the closest firmware I can find that may work for my MTCB GS unit. Will it work?
Click to expand...
Click to collapse
@shawndak-
I'm sure the MTCB HU uses a different SoM board. With any luck, it's the board that has a NAND with exposed pins like the one in the RK3188 TV Box unbrick thread. If so, try the following procedure:
-Reset NAND by shorting pins 5&6.(See picture)
-Open RKBatchTool.
-Press and hold Reset / Short pins 7&8 / Plug in USB cable at same time (requires 2 hands or contortionist LOL)
-Release Reset after device appears in RK Tool.
According to the thread I borrowed this procedure from, the HU should only be powered through the USB cable. However, if it doesn't work that way, try connecting it to a separate power supply and turn it on after plugging in USB cable.
Good luck!
PS. Sorry, I don't know if the FUSE firmware will work on the MTCB. @Malaysk has separate sections for MTCB/MTCC firmware and MTCD firmware, so you may want to confirm that you sourced the firmware from the correct section.
PPS. I want to credit the author of the TV Box thread, but I can't find it again.
UNBRICKED!!!! I hooked up the laptop with the drivers installed and batch tool open. Loaded the firmware. Then i did this exactly,
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button
Boom computer recognized the device. I pressed restore and it flashed the unit in about 5 minutes. Then it booted up!!!! Feeling invincible I loaded the 5.1.1 rom over the 4.4.4. Everything worked! I have Android 5.1.1 on a PF73AA4A MTCB GS MCU!!! So when are we getting Marshmallow? lol Nougat? The Fused rom is amazing, so much room for activites!!! Thanks everybody!
@shawndak Tried your method, doesn't work.
Try a different computer. You said a male to male cord, are you using a usb to usb B (mini) and plugging it into the front of the unit?
Make sure you have the most updated tools as well https://androidmtk.com/download-rockchip-factory-tool. You have to install the drivers!!!! They are located at the bottom of that page!
@shawndak The unit doesn't have a front USB, only back USBs.
NaviPR said:
@shawndak The unit doesn't have a front USB, only back USBs.
Click to expand...
Click to collapse
Whats the model? Can you send a link or a picture?
@shawndak It's just a KGL model for a pre-lifting W203 Mercedes-Benz without a front USB.
I've already unbricked that one + two other units using @Malaysk's other method http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
It worked 100%, although I had to use a USB drive.
All you have to do is create a recovery card using the program from the post, get a USB drive, load some factory firmware onto it, then insert the card into the GPS slot and the pendrive to the USB. Then, if the card initializes recovery but gives you an error message, remove it - it will go into regular recovery mode - and update from the USB.
NaviPR said:
@shawndak It's just a KGL model for a pre-lifting W203 Mercedes-Benz without a front USB.
I've already unbricked that one + two other units using @Malaysk's other method http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
It worked 100%, although I had to use a USB drive.
All you have to do is create a recovery card using the program from the post, get a USB drive, load some factory firmware onto it, then insert the card into the GPS slot and the pendrive to the USB. Then, if the card initializes recovery but gives you an error message, remove it - it will go into regular recovery mode - and update from the USB.
Click to expand...
Click to collapse
Very interesting. Perhaps slow format those cards and attempt it again. If not try a warranty claim with whomever you bought it through. Good luck!
@shawndak I don't think the card is at fault here.
Anyway, read Malaysk's guide and follow it to the letter. In case your unit gives you an error message saying that you have to remove the card, do it and you will be dumped into regular recovery mode with the USB stick still plugged in. Just load the firmware from there.
Like I said, I've unbricked 3 KGL units using this method.
@NaviPR
Did you try both of my alternative methods?
It shouldn't matter that the USB port is not on front other than having to remove the HU to access the rear ports.
Admittedly, I also have a W203 so I know it's not as easy as removing the HU from a W220.
However, it sounds like @Malaysk's method is better because you don't have to remove the HU, etc. Is that right?
Wish it popped up during my search. Would have saved me a lot of time if it worked.
Nevertheless, since @ShawndaC and I were successful with my solution(s), maybe yours bricked under different circumstances.
using malaysk technique I can fix 60% of bricked devices I get
another 40% need the hardware repair and parts.
I repair many head units daily
shawndak said:
UNBRICKED!!!! I hooked up the laptop with the drivers installed and batch tool open. Loaded the firmware. Then i did this exactly,
1. Turning 12V on while holding the power and reset buttons.
2. After 5-10 seconds, release the reset button and keep pressing the power button for another 10-15 seconds
3. Release the power button
Boom computer recognized the device. I pressed restore and it flashed the unit in about 5 minutes. Then it booted up!!!! Feeling invincible I loaded the 5.1.1 rom over the 4.4.4. Everything worked! I have Android 5.1.1 on a PF73AA4A MTCB GS MCU!!! So when are we getting Marshmallow? lol Nougat? The Fused rom is amazing, so much room for activites!!! Thanks everybody!
Click to expand...
Click to collapse
5.1 working normaly or lil bit lagY?
I've tweaked it a bit so it's running pretty dang good. I'd wait for the update that's coming out soon!
My brother recently moved out and he left me with his old phone, a Pixel 2. I would like to factory wipe it in order to sell it, but the screen is completely broken. It still boots up and works fine, but the screen shows no output and tapping doesn't register. Is there a way to wipe the phone via fastboot? The bootloader is locked, phone is unrooted, etc.
I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps
ice711 said:
I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps
Click to expand...
Click to collapse
The only issue with that is that I have no clue if it actually worked. I can check if the device is in fastboot to get the ball rolling, but after that there is no haptic feedback or anything to let me know it is wiped. Thanks for your input though. I tried doing it but I'm not sure if it actually did anything
ice711 said:
I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps
Click to expand...
Click to collapse
I'm pretty sure I was able to wipe it using this method - the phone now shows up as an empty storage device and adb devices no longer shows any devices. The fingerprint sensor (its how i've been trying to find what state the phone is in) also has no feedback when touched now. Thanks for the solution my friend!
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Also having same issue
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Strongo said:
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Click to expand...
Click to collapse
No, unfortunately my phone is still stuck on that exception red text (not a single green one like the one i found online).
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
The only solution I could find that could help me in the future is that 1. Phone is dead, eMMC and motherboard cannot start. 2. Since the phone could be (difficultly) tore down, the best bet is that you find a data recovery center (not Samsung since as I found out they don't do data recovery, but they simply change everything giving you a new phone basically or they change the motherboard, so deleting everything) or a data recovery specialist so that you could disassemble the phone, remove the memory, and read the content on a chip reader.
In this case maybe there's a chance to recover the simple data you have (photo, video, music, documents and something else that has a recognizable header) but probably everything else is lost.
I would be more than happy to be proven wrong since I'm not an expert but it's been 2 weeks and I received no answers.
Iztooi said:
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Click to expand...
Click to collapse
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes. Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
cooltt said:
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
Click to expand...
Click to collapse
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes.
Click to expand...
Click to collapse
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
Click to expand...
Click to collapse
The fact is that it doesn't power off and on multiple times, but just one time.
Iztooi said:
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
The fact is that it doesn't power off and on multiple times, but just one time.
Click to expand...
Click to collapse
I'm this case you'll need to use ADB and side load to flash a new bootloader.
cooltt said:
I'm this case you'll need to use ADB and side load to flash a new bootloader.
Click to expand...
Click to collapse
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Iztooi said:
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Click to expand...
Click to collapse
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
cooltt said:
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
Click to expand...
Click to collapse
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Iztooi said:
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Click to expand...
Click to collapse
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
cooltt said:
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
Click to expand...
Click to collapse
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Iztooi said:
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Click to expand...
Click to collapse
I assume youre in upload mode. Press only power button for 20 seconds
kpwnApps said:
I assume youre in upload mode. Press only power button for 20 seconds
Click to expand...
Click to collapse
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Iztooi said:
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Click to expand...
Click to collapse
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Iztooi said:
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
Click to expand...
Click to collapse
kpwnApps said:
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Click to expand...
Click to collapse
I already did that, but sadly it didn't work.
Iztooi said:
I already did that, but sadly it didn't work.
Click to expand...
Click to collapse
Then it might be an UFS hardware fault
kpwnApps said:
Then it might be an UFS hardware fault
Click to expand...
Click to collapse
I have the exact same problem. This is the closest thing I could find on the internet I could find regarding diagnosing it. Had to make an account just to reply. I was thinking it was a OS problem for the longest time, but I suspect that it may be a hardware problem after all. My s7 did this to me the morning of Jan 9. Set it down and came back to it, reboot with bootloader error, red text only, no combinations of buttons work etc. I see that two others in the thread had theirs fail around the same time as well.
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
draco18 said:
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
Click to expand...
Click to collapse
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Iztooi said:
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Click to expand...
Click to collapse
I was wondering if you installed any apps recently and how full your internal memory was. I believe my phone was around 90% full of the 32GB, had no warning symbol about how full my memory was though. Friend was saying I should of got a warning if my memory was getting near capacity. I installed F-droid recently and used it to download Adaway app. Deleted F-droid and deleted Adaway since I couldn't get Adaway to work. Never rooted my phone. I was curious if you also did anything similar to what my phone did since we're in the same boat. Otherwise the only things we share in common is we set it down and it reboot with this bootloader error.