Database Info

[Q] help! think i bricked my tf700

help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S

prasse said:
help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S
Click to expand...
Click to collapse
How long did you let it sit on the Asus screen?
Which recovery and version?
I've seen my tablet take 45 minutes to boot on older versions of TWRP after a ROM flash.
This hasn't happened for quite a while however.

This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?

sbdags said:
This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?
Click to expand...
Click to collapse
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s

prasse said:
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s
Click to expand...
Click to collapse
Do yo usee ANY number flying about giving any indication as to what bootloader you're on? sbdags made an important point -- you'll need a current bootloader version to get the more recent ROMs working.
Oh, and ehh... please use interpunction -- you know, periods and commas and stuff. It makes a sentence that much more readable and understandable.

okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?

sbdags said:
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?
Click to expand...
Click to collapse
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.

prasse said:
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.
Click to expand...
Click to collapse
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.

sbdags said:
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.
Click to expand...
Click to collapse
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?

prasse said:
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?
Click to expand...
Click to collapse
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
How do you know you're on TWRP if you can't get into recovery?

sbdags said:
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?
Click to expand...
Click to collapse
okay thank you for the explanation, but no i dont have fastboot avaliable.... got the same screen as before.

ngionla appearance
Thats OK said:
How do you know you're on TWRP if you can't get into recovery?
Click to expand...
Click to collapse
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.

prasse said:
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.
Click to expand...
Click to collapse
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
{
"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"
}
Is it anything like the above image?

Thats OK said:
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
Is it anything like the above image?
Click to expand...
Click to collapse
Ye almost the excat same, i Can upload a picture when i get home... But no i dont know the difference between, your mentioned wipes sorry :s..

If it looks like that what happens when you push volume up on the RCK icon?

sbdags said:
If it looks like that what happens when you push volume up on the RCK icon?
Click to expand...
Click to collapse
see thats the difference, i only got the two last icons wipe and usb : /

That sounds like you do not have any recovery available. If you connect the tablet to the computer via SUB and pick the USB option, what happens?

Isn't the fastboot built into the bootloader? It should be always possible to recover if you can get to the recovery select screen and select fastboot, shouldn't it?

[HELP] Verizon S3 won't go to Download Mode.

Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!

You're being unclear. You say you have a Verizon GSIII but also say you have an international GSIII, which is it?
For download mode, pull the battery then try again but hold it for like 15-30 seconds.
Sent from my SCH-I535 using xda app-developers app

Make sure you are not connected to your computer until after you get into D/L mode. I know if I am connected to the PC before I try to enter D/L mode it will not work.

ColdKill3r! said:
Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!
Click to expand...
Click to collapse
You have to make sure your USB cable isn't connected while trying to put into download mode. Also hold Power, Volume Down and home button until phone vibrates and then release. Hope this helps

Hey, guys.
Thanks for the replies.
Anyway... I have it disconnected from the USB and I also have already tried the battery thing, but none of those things worked.
I have 3 S3's, one of them is an international model, which I have rooted myself and everything worked (download mode), but the other 2 are the Verizon version (SCH-i535) of the phone isn't working - even though I've tried taking of battery, memory card, sim card, no USB cable connected. I have USB debbuging and everything that I need to have activate, but it won't go into download mode. I wonder if it's blocked (which I doubt, since I've seen people saying they rooted the Verizon S3).

Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
{
"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"
}
Team Kernelizers; Kernel tweaking at its finest.

It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
luis86dr said:
Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
Click to expand...
Click to collapse

help mine doesn't go neither
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help

misstq said:
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help
Click to expand...
Click to collapse
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)

Download mode
ColdKill3r! said:
It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
Click to expand...
Click to collapse
Home...Volume Down...Power...vibrate...hold until warning message about using custom ROMs appears. Then press
volume UP and I get the green Android robot and this message "Downloading...Do not turn off target !!" Upper left
corner of screen reads in tiny red text "ODIN MODE"
followed by PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Does the above mean that I am in Download Mode? When I plug in the USB cable there is no response.
What does "Do not turn off target !!" mean?
If I AM in Download Mode at this point I should be able to use heimdall at the command line, but here are my responses
at the command line:
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ heimdall detect
heimdall: command not found
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall detect
Device detected
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall print-pit
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
As seen above it seems like there's an attempt to connect to my S3 but the libusb error: -3 sent me off searching about for a solution
and I found something about installing libusbx-1.0.17.
Followed the instructions in the INSTALL file
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
#1 seemed to work, #2 "make" returns the following:
[email protected] ~/Desktop/libusbx-1.0.17 $ make
make: *** No targets specified and no makefile found. Stop.
So, that's where I am stuck. Does #2 mean that I should type "make" and the specify a file as "target"
Anyone know where to go next?
The wiki says "Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary."
I don't object to rooting my phone, but if this heimdall method is the CM recommended method I'd like to get it to work. Suggestions???
Thx,
kb

What are you trying to do? Root? Install cm? I think there are much better ways to do what you're trying to do, but you need to be clearer.
Sent from my SCH-I535 using Tapatalk 2

No download mode.
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.

utter madness said:
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.
Click to expand...
Click to collapse
I'm going to direct you post your question in the Sprint S3 Q/A section as continuing here will cause confusion since our Verizon S3 has TW 4.3 and we are presently locked down to the point where we are unable to use a custom recovery.
CWM defaults to naming backups in the year 1970 so that looks right at a cursory glance. Last thing, your recovery is very out of date, given how KitKat works with our Verizon S3, you need a newer version of CWM to flash KitKat. Post in the Sprint section and be as specific as you can be as to what you want to accomplish.
Merry Christmas!

SS S3
skywalk3r89 said:
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)
Click to expand...
Click to collapse
Thank you so much , I followed your way and succcessed

the walkingdead said:
Thank you so much , I followed your way and succcessed
Click to expand...
Click to collapse
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Hey Sandman,
Thanks for the suggestion.
But since there are hundreds of S3s still being sold, and hundreds of buyers looking for support like this, shouldn't we supply this topic if someONE some where might need thsi?
Like I just did on my New bought a NEW a month ago
Huh?

Idol 3- Stuck In Bootloop After Flashing boot.img

Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL

More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)

CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.

No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)

You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.

what about off warranty repair by alcatel service in your country?

N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.

famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases

Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse

[Help] S8+ G955F Screen unresponsive, computer won't recognize phone which means. RIP

Hey guys! Posting here will be my last effort into trying to save my phone. I've tried everything... But before I get into that let me give you a little bit of background:
Phone is rooted with Magisk, I have a ROM on it (RENOVATED ICE 13.1). I had Xposed Framework on it with a handful of modules. Phone was running smoothly but I restart it to apply a Magisk module (WhatsApp Emoji) to systemlessly replace the stock Android Emoji with WhatsApp Emoji. When the phone restarted I no longer could interact with the screen, meaning that the display ins't registering my touches or reacting to them. Tried to unlock the phone with fingerprint but I can't because I have to put my 4 digit pin because the phone just restarted. Can't put my 4 digit password because the screen is not responding to my touch, swipes or anything. Power button + Vol down, battery disconnect and phone reboots. I try to access to TWRP just to realize I no longer have it on my phone for some strange reason. Which means it got deleted somehow or most likely it got corrupted and doesn't want to pop up. So.. No access to TWRP. I can't clean dalvik cache, format the phone or reinstall the ROM. All that is a perfect recipe for factory reset from Odin but my computer doesn't recognize my phone.
Things I've already tried:
Try to unlock the phone with Bixby voice (Sends me back to putting my pin).
Connect a mouse to try to click the pin numbers (Mouse doesn't turn on).
Connect a keyboard to try to put my pin from there (Keyboard also won't turn on).
Tried booting in safe mode (No difference at all from normal mode, same problems, same everything)..
Tried to access to TWRP (No TWRP access).
Tried to factory reset from Odin (Computer won't recognize the phone).
PD: I'm aware that Odin can be picky with cords and ports and the possibility that my computer may be missing some drivers and because of that won't recognize the phone but that is not the case.. I just successfully factory reset another S8+ from a friend and my computer and Odin recognized his phone instantly, so I know for a fact that my computer is alright. I wish I could say the same about my phone. I suspect the unresponsive screen is a software problem, the screen has zero damage, no falls, no reasons to believe is a hardware malfunction. To my eyes this phone is dead and have no foreseeable repair. I know there isn't much to do but feel free share any possible via of solution.
Thanks!

This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Sent from my SM-G955F using Tapatalk

adewfaw said:
This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Click to expand...
Click to collapse
Maybe it's an app you unintentionally installed. Do you have a theming app or something similar?
---------- Post added at 07:49 PM ---------- Previous post was at 07:46 PM ----------
vulkhead said:
Hey guys! Posting here will be my last effort into trying to save my phone. I've tried everything... But before I get into that let me give you a little bit of background:
Phone is rooted with Magisk, I have a ROM on it (RENOVATED ICE 13.1). I had Xposed Framework on it with a handful of modules. Phone was running smoothly but I restart it to apply a Magisk module (WhatsApp Emoji) to systemlessly replace the stock Android Emoji with WhatsApp Emoji. When the phone restarted I no longer could interact with the screen, meaning that the display ins't registering my touches or reacting to them. Tried to unlock the phone with fingerprint but I can't because I have to put my 4 digit pin because the phone just restarted. Can't put my 4 digit password because the screen is not responding to my touch, swipes or anything. Power button + Vol down, battery disconnect and phone reboots. I try to access to TWRP just to realize I no longer have it on my phone for some strange reason. Which means it got deleted somehow or most likely it got corrupted and doesn't want to pop up. So.. No access to TWRP. I can't clean dalvik cache, format the phone or reinstall the ROM. All that is a perfect recipe for factory reset from Odin but my computer doesn't recognize my phone.
Things I've already tried:
Try to unlock the phone with Bixby voice (Sends me back to putting my pin).
Connect a mouse to try to click the pin numbers (Mouse doesn't turn on).
Connect a keyboard to try to put my pin from there (Keyboard also won't turn on).
Tried booting in safe mode (No difference at all from normal mode, same problems, same everything)..
Tried to access to TWRP (No TWRP access).
Tried to factory reset from Odin (Computer won't recognize the phone).
PD: I'm aware that Odin can be picky with cords and ports and the possibility that my computer may be missing some drivers and because of that won't recognize the phone but that is not the case.. I just successfully factory reset another S8+ from a friend and my computer and Odin recognized his phone instantly, so I know for a fact that my computer is alright. I wish I could say the same about my phone. I suspect the unresponsive screen is a software problem, the screen has zero damage, no falls, no reasons to believe is a hardware malfunction. To my eyes this phone is dead and have no foreseeable repair. I know there isn't much to do but feel free share any possible via of solution.
Thanks!
Click to expand...
Click to collapse
Did you try to uninstall the drivers then reinstall. Try to reset straight from stock recovery if you can still get to it.

eddyo1993 said:
Maybe it's an app you unintentionally installed. Do you have a theming app or something similar?
---------- Post added at 07:49 PM ---------- Previous post was at 07:46 PM ----------
Did you try to uninstall the drivers then reinstall. Try to reset straight from stock recovery if you can still get to it.
Click to expand...
Click to collapse
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.

vulkhead said:
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.
Click to expand...
Click to collapse
I'm sure you tried to go into download mode then connect it to Odin right?

adewfaw said:
This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Your case sounds like a software malfunction, try to stock reset everything with Odin and you should be good!

vulkhead said:
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.
Click to expand...
Click to collapse
Try this odin
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501

eddyo1993 said:
I'm sure you tried to go into download mode then connect it to Odin right?
Click to expand...
Click to collapse
Yes sir! My phone goes into download mode perfectly but Odin doesn't detect it. That's my main problem, I wouldn't be here If I could stock reset from Odin.

vulkhead said:
Yes sir! My phone goes into download mode perfectly but Odin doesn't detect it. That's my main problem, I wouldn't be here If I could stock reset from Odin.
Click to expand...
Click to collapse
Yeah I'm sure. Had the same issue before I'm trying to help out. If you don't need it then good luck.

eddyo1993 said:
Try this odin
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
Click to expand...
Click to collapse
Thanks a lot for taking your time, I just tried you Odin and didn't work, I've also tried all these:
{
"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"
}

vulkhead said:
Thanks a lot for taking your time, I just tried you Odin and didn't work, I've also tried all these:
Click to expand...
Click to collapse
I'm curious when you do Power+Bixby+Vol. Up what does it do in place of taking you to TWRP

eddyo1993 said:
I'm curious when you do Power+Bixby+Vol. Up what does it do in place of taking you to TWRP
Click to expand...
Click to collapse
It does nothing, it just perform a normal reboot that takes me back to where I'm stuck: the lockscreen.. I can see my wallpaper there, some notifications.. I can access to the camera by double pressing power button, I can access to Bixby, powermenu.. All that stuff. :crying:

vulkhead said:
It does nothing, it just perform a normal reboot that takes me back to where I'm stuck: the lockscreen.. I can see my wallpaper there, some notifications.. I can access to the camera by double pressing power button, I can access to Bixby, powermenu.. All that stuff. :crying:
Click to expand...
Click to collapse
I'm wondering how were you able to get into safe mode if the touch screen wasn't responsive. You can reset your phone through the maintenance menu by doing the Power+Vol. Down for 10 seconds wait till it goes black hold power button again till you feel a light vibrate.

eddyo1993 said:
I'm wondering how were you able to get into safe mode if the touch screen wasn't responsive. You can reset your phone through the maintenance menu by doing the Power+Vol. Down for 10 seconds wait till it goes black hold power button again till you feel a light vibrate.
Click to expand...
Click to collapse
I didn't have to use the screen at all to go into safe mode. You can enter safe mode by rebooting your phone, pressing Power until Samsung logo appears and quickly release Power button while press Vol Down until the phone finish the reboot. Unfortunately safe mode does nothing for me. I understand that Power+Vol Down virtually disconnect the battery to make a reboot, I didn't understand very well the part of accessing into the maintenance menu. I tried what you said but my phone but performed a normal reboot.

You may have to repartition and install the latest stock via Odin. When nothing works, repartition works well.

bluheart said:
You may have to repartition and install the latest stock via Odin. When nothing works, repartition works well.
Click to expand...
Click to collapse
Can't use Odin because phone doesn't get recognized by Odin nor the computer itself.

Just a stupid thought and may not help
Have you tried logging into your Samsung or Google account and tried to use the ' find my phone' feature. I believe you can unlock or at least wipe your phone using this. I've never used it so don't know if it will work or not.

spawnlives said:
Just a stupid thought and may not help
Have you tried logging into your Samsung or Google account and tried to use the ' find my phone' feature. I believe you can unlock or at least wipe your phone using this. I've never used it so don't know if it will work or not.
Click to expand...
Click to collapse
I didn't found such feature

send it to samsung, if you're lucky they will fix it under warranty.

lynxblaine said:
send it to samsung, if you're lucky they will fix it under warranty.
Click to expand...
Click to collapse
My phone had his malfunction while rooted. WARRANTY VOID: 1 (0x030c) Sadly I loosed any right to warranty.

j3 2017 dont boot after flash

hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution

ntamvakeras said:
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
Click to expand...
Click to collapse
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!

BigZ1 said:
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
Click to expand...
Click to collapse
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks

BigZ1 said:
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
Click to expand...
Click to collapse
I did that but nothing is happening. Only volume down home end power combination works

{
"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"
}

Did you hold the keys down continuously? That is to say, until you either get recovery mode (or in your case bootloader mode)? If you let go of the key combo after seeing the Samsung J3 screen, you let go too soon. I've always had success with getting into recovery that way. Try it again.
If you truly can't start up in recovery mode, I think you may have wiped out your recovery partition. I'd suggest you use Odin to flash it again.

I just tried booting into recovery mode and then reboot to system. If you can get to that point, you are home free. If you can't get to recovery mode, I think your best bet is to try to reflash with Odin. Maybe you got a bad download. Consider getting a fresh download and reflashing with Odin.

One more thing you might be able to do. IF you had usb debugging enabled, you could connect the phone to your pc, and issue a fastboot command "fastboot reboot" which would reboot you into the system.
This reqires some level of technical skill and some setup work to get fastboot installed (on windows) or if you have a Linux computer, fastboot is probably already installed.
The above is only going to work if you had the developers option for usb debugging turned on before you flashed the phone, and even then it may or may not work, depending on how far the phone gets while booting.
I think at this point, your best option is downloading a fresh copy of your system image from Samsung, and reflashing it with Odin. Hoperfully it will still connect to Odin, since it's already in bootloader mode.

This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green screen

ntamvakeras said:
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green scree
Click to expand...
Click to collapse

After you flashed it, and rebooted the phone, how long did you wait for the phone to boot into system? It takes a long time (like maybe 15 minutes) for it to get to the point where you do the initial configuration. If you can try flashing with Odin again, give it at least 15 minutes to get through it's initialization process. That might be what went wrong. Just a guess on my part, but that's what I think. Let me know if it works.

VID_20220727_202947.mp4
drive.google.com

ntamvakeras said:
VID_20220727_202947.mp4
drive.google.com
Click to expand...
Click to collapse
I did all this but nothing happens I don't see the Samsung logo only a green screen. I upload a video to see what I doing

I wish I could help you. I think you are doing everything right. This problem exceeds my knowledge. Maybe someone else smarter can help you.

OK thanks a lot for your assistance

ntamvakeras said:
OK thanks a lot for your assistance
Click to expand...
Click to collapse
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.

BigZ1 said:
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
Click to expand...
Click to collapse
I did it but nothing happened. The matter is that the phone don't power on after flash. I don't know what else to do

Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.

ntamvakeras said:
View attachment 5669359
Click to expand...
Click to collapse
Will never boot FRP lock and OEm are On i think a account is hanging to the phone , boot in recovery samsung mode and wipe data factory reset from there , reboot

meric57 said:
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
Click to expand...
Click to collapse
HI I did that because I have done a lot of experiments in this phone. I know that is wrong but I did that as last way to recover the phone