Samsung Galaxy J320FN (2016) broken screen shenanigans - Samsung Galaxy J3 (2016) Questions & Answers

Hello
I hope I haven't posted this in wrong section.
I have Samsung Galaxy J3 (to be exact J320FN 2016). Its screen is broken and is completely black. Sometimes if I press the screen harder or move my finger over the screen I can get it to show some colors. Digitizer is also broken so touching the screen does nothing except showing a pretty pallet of puke green colors.
I extracted all of the needed data but two things remain. SMS messages and one single app https://www.apkmonk.com/app/com.callsoft.notes/ and a dozen of notes written in that app. I can't access my SMS or app by connecting to PC and then copying all the data.
I tried a different approach. First, I tried using this https://forum.xda-developers.com/showpost.php?p=53482464 and then I tried using this https://github.com/Genymobile/scrcpy
Both programs work fine but they both show a message that my phone is unauthorized. I've been stuck there for about 10 days. I can't authorize my phone no matter what I do. My phone is rooted and whenever I try something there is a dialog box on my phone's screen that asks me should I accept this connection but I can't touch it because the screen is broken (also the screen is mangled so I just see a part of that dialog box).
Aside from broken screen, phone works fine.
Does anyone know how can I authorize my phone? I know my way around Windows but I am a little bit a newbie when it comes to Androids so if you know something try to explain it as detailed as you can so I could follow the instructions.
I don't care that much for the phone, I just need that data back.

I did it on my own. I will now describe the process of how I did it.
My power button was dirty as hell so it was useless. I took out the battery and then I poured just a little bit of alcohol over power button. After that I kept pressing and fiddling with power button (with battery still out of course). This cleaned the grime and dirt under the button. Then I used a hair dryer and evaporated all the remaining isopropyl alcohol.
Next step, I already had ADB installed. There is a great guide over here for this particular model on this very forum but it does not let me post the link for some reason, it is easy to find, really.
So I assume by this point you have Odin, ADB installed and TWRP recovery downloaded like that link said that I posted.
I tried to flash TWRP again. Fire up Odin, click AP, find TWRP, set the phone to download mode by holding home+power+volume down. When there is something on screen press volume up which will bring you to download mode. Then press Start in Odin. Note, I had my bootloader unlocked previously so be sure that yours is unlocked too.
Now that I flashed a completely new TWRP I now turned off my phone by pulling battery out. Then I pressed home+volume down+power button for like 2 seconds then I would let go the power button and I would keep home and volume down pressed for like next 3-4 seconds.
I plugged in USB cable and waited for Windows to play that "connected" sound. At first times when I would connect it, it wouldn't register anything. That meant I didn't boot it at all. Then I tried it two-three more times and I finally booted the thing in recovery.
While in recovery mode I connected the phone to PC and then I ran ADB. I entered "adb devices" and instead of "unauthorized" it said "recovery". Ok, now we are making some progress
While I was in recovery I first copied this code into ADB.
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
You type in ADB shell first and then copy all three lines by simply right clicking and pressing copy and then you right click into ADB window and pressing right click and then paste and ENTER. I am not sure if it did something but it was worth a try. It seemed to be stuck after that but better to do it.
While still in recovery mode I did one more thing. I found "adbkey.pub" file. It is located in C:\Users\USERNAME\.android copy it from there and paste it into directory where your ADB is. Then run ADB again and be sure to type first "adb devices" to check if your phone is still in recovery mode. Then type this "adb push adbkey.pub /data/misc/adb/adb_keys" without qutation marks.
This placed an RSA key into the phone that authorized my phone and PC to communicate. As a result when you run something on the phone from PC, that popup to accept a key won't appear anymore, you can do now with your phone as you wish.
They I typed in "adb reboot" which booted my phone normally. I tried running scrcpy program first (last link in my post) and it displayed my phone screen. You can now use mouse to touch your phone screen and use right click to go back and wake up your phone when it turns off the screen and you can use scroll like you would your finger. From this point on it was very simple to take what I needed.
I hope this helps somebody.

Related

Home Button Broken (here is a fix)

If your G1/HTC dream's home button stops working, here is a fix (kinda). Whenever you turn your phone on it takes you to recovery (Home+Power=Recovery), here is a fix I found after an hour of Googling and ****.
Method number two got me back into my phone, but if it turns off I need to be at a computer using fastboot to turn it on.
It's better than nothing, Rogers is pissing me off. A week after the 1 year warranty and this breaks on me. Anyone know any permanent fixes or is it a hardware issue.
RichieDaze said:
I have the same problem with the home key being stuck after humidity entered my phone. Which boots me straight to recovery mode. I have managed to recover my phone with the following steps:
YOU MUST HAVE ADB AND FASTBOOT INSTALLED IN YOUR PC!!!
1) If your phone has the home button stuck, you can't update or confirm anything with the Cyanogen Recovery! Because you need the Home button to confirm. So you must revert your Recovery back to JF's Recovery to use the recovery properly in this case.
2) I have tried for weeks to make the system bypass the recovery and have succeeded. YOU MUST REBOOT YOUR PHONE FROM RECOVERY TO BOOTLOADER. So use ADB to reboot in to Bootloader mode ( adb shell reboot bootloader ). Now that your in Bootloader mode, use the FASTBOOT commands ( fastboot reboot ) and voila, it bypasses the recovery.Make a script on your Winbows or Linux to make it as easy as one click!
If I have helped, please say Hi to my Android or give me a link to a replacement Daughter board...
Click to expand...
Click to collapse
I seem to have a similar problem.
But some how, it boots up properly once in a while. But even after it boots up, I cannot go anywhere except the home screen.
If the home button is stuck, this is expected right?
Dont you have this problem?
I suggest you take the phone apart and replace the broken button.
Another thing that might be a little EASIER (without actually *fixing* anything) is to write your boot.img into your RECOVERY partition. If you need recovery, you can always "fastboot boot recovery.img". Having the regular boot image in the recovery partition *should* make it boot normal with a stuck home button. This way you don't need fastboot to normal boot the thing.
I tried opening it.
I opened the screws on the back side. But I could not figure out how to get to the home button from inside.
For some reason, I can boot in properly. (It goes into recovery sometimes. But if I switch off and wait for sometime, I can boot normally.)
My main problem is that once I boot, I cant get anywhere from the main home screen.
smileey said:
I tried opening it.
I opened the screws on the back side. But I could not figure out how to get to the home button from inside.
For some reason, I can boot in properly. (It goes into recovery sometimes. But if I switch off and wait for sometime, I can boot normally.)
My main problem is that once I boot, I cant get anywhere from the main home screen.
Click to expand...
Click to collapse
That makes sense, since as soon as you launch anything, the stuck home button will return you to home.
You may want to try harder to take it apart. You need to remove the circuit board in the "chin".
Do you know how to get access to the chin?
I could not figure that part.
When I opened the screws on the backside, I could not see anything that would lead me to the chin.
smileey said:
Do you know how to get access to the chin?
I could not figure that part.
When I opened the screws on the backside, I could not see anything that would lead me to the chin.
Click to expand...
Click to collapse
Here's the service manual:
http://mikechannon.net/PDF Manuals/HTC Dream SM (A04).pdf
It will walk you through a complete disassembly and reassembly.
Thanks a ton!!
I will try and see if I can do something about the button
Is there a better way than opening up the phone? The home button on my G1 stopped working, so, I unrooted the phone, but now it's stuck on the Triangle/Exclamation point screen. I've been able to do Alt S, (Alt+w doesn't work, I think the w is also broken), but I can't reboot because it asks for home and back button to reboot. Any other suggestions?
Ok guys, this is not a pretty solution but what you can do is re-map your phone so the camera button acts as a home key and home key does nothing. It's a hack but it's a simple one and sure beats the hell out of replacing the whole phone.
Here's a thread with directions.
I tried remapping my home button to the camera button and once in the os it works, but still boots into recovery everytime and doesn't let me wipe, flash,etc with the camera button. It aborts....
Also, a quick tip I learned......If u keep booting into recovery just go to console and type reboot android. It'll boot normally.
Sent from my HTC Dream using XDA App
with the remapping the keys make sure you push all the .kl files and if you want to remove the home button from working at all remove the home button line from the .kl file.
You should also make sure that you re-map your home button to do nothing, otherwise it will not work.
Thank u jj972 for that quick tip atleast I can get out of recovery mode....

Help, its dead

My vibrant died today qq
I was trying to install an additional language, and pushed a libwebcore.so file to /system. Was doing that using a Terminal emulator
Probably did it wrong or whatever.... now, the phone boots to the Samsung vibrant screen and freezes like that.
I tried to enter download mode and flash the stock rom thats on this forum, but odin keeps saying "File analysis..."
Also *dont know if this helps* in the download mode screen, it says
"Appling Multi-CSC
Installing Multi-CSC"
Any help? Is my warranty voided? what do i do
thats not the download screen, that is the recovery screen. the download screen has a big triangle with an android and a shovel. you have to have your odin program up and running, first, then take your phone and remove the sim card and external sd card. once this is done, with the phone powered off, connect the usb cable to the phone from the computer. once connected, hold the volume down button down while pressing the power button. continue to hold the volume down button down until it loads into download mode. it will actually say download mode
basataom said:
My vibrant died today qq
I was trying to install an additional language, and pushed a libwebcore.so file to /system. Was doing that using a Terminal emulator
Probably did it wrong or whatever.... now, the phone boots to the Samsung vibrant screen and freezes like that.
I tried to enter download mode and flash the stock rom thats on this forum, but odin keeps saying "File analysis..."
Also *dont know if this helps* in the download mode screen, it says
"Appling Multi-CSC
Installing Multi-CSC"
Any help? Is my warranty voided? what do i do
Click to expand...
Click to collapse
If you boot into recovery you should be able to open an adb shell and remove libwebcore.so. It's more than likely not bricked, but libwebcore.so is causing a bootloop, which results in a black screen and lit up touch buttons.
arghhh thanks for trying to help me out
I cant seem to enter download mode, it just stays on the vibrant black screen
and I can't do adb shell, because it shows the device is offline.
I'm losing my mind
Recovery mode, not download mode. Power + Volume Down + Volume Up. Hold all three till it says Vibrant, then let go.
In recovery mode, Odin just says "file analysis...."
You're not using odin, and besides, odin is for Download mode only. Recovery should give you options to Reboot, Reinstall Packages and a few others using the vol/pwr buttons on the phone, you should be able to access adb while the phone is in recovery mode.
hmmm Thanks for trying to help me, i really appreciate it.
I'm in recovery mode, and still says "error: device offline"
Well, crap. I forgot stock recovery isn't adb aware. You'll need to somehow push fakeFlash to the internal memory.
Not sure how to help you from here, but basically you're just going to need to get that new lib off the phone. May have to warranty it out.
This is really killing my brain cells
I just wish i could access download mode, but the bootlock is not letting me, i think
(check your pm bahnburner)
basataom said:
This is really killing my brain cells
I just wish i could access download mode, but the bootlock is not letting me, i think
(check your pm bahnburner)
Click to expand...
Click to collapse
Checked and replied. Sorry you can't get to boot.
Would it be possible to get a clockwork recovery update.zip from someone and somehow get that on my sd (I know I probably cant mount it with the phone off) and then "reinstall packages"
Just wondering
I'm having the same problem
once i get into adb shell, what commands do I use to remove libwebcore.so?
UPDATE: I managed to reflash the stock firmware, however I'm still having the same problem. Any ideas?
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
rm -r /system/libwebcore.so
Try this.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (turns the screen on when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
This *should* get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
This fixed my 'odd' brick.
andershizzle said:
Try this.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (turns the screen on when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
This *should* get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
This fixed my 'odd' brick.
Click to expand...
Click to collapse
SO I'm having some difficulties, trying to revert back to stock using Odin, got into download mode, got the appropriate files from another thread, odin seems to be hanging on "file analysis", any suggestions?

HELP - Flash gone bad (looping recovery mode)

OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!
http://forum.xda-developers.com/showthread.php?t=741027&page=3
Wrong section. This belongs in general...
Sent from my messenger rabbit
UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.

F**king vibrant

Ok I've looked everywhere, maybe not well enough but I have and I can't find the answer to my question. I installed the new official 2.2 on the 10th when it came out in canada here. My phone has worked "ok" for the past 2 days. (lots of new force closes and some major lag in some spots that didn't happen in 2.1) but that's besides the point. Today i was trying to set up a new wallpaper and all of a sudden the screen started flashing on and off. I couldn't do anything to stop it except pull the battery. Now when I turn on the phone it just flashes the opening screen that says "Galaxy S blah blah". and the only way I can stop that is pull the batt. I've tried hard resetting and all that but it always gets stuck at the openning screen. Now I'm still noobish to android stuff. Was too scared to flash anything before the official so if you have any advice that involves other programs/pc i'd appreciate a point in the direction of a walkthrough.
I'd hate to have to send it in and wait the 2 months it takes samsung canada to get it back to me.
Thanks.
http://forum.xda-developers.com/showthread.php?t=732458
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
canadianrider said:
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
Click to expand...
Click to collapse
Look up the "jig" solution. That will be guaranteed to set your device on Download Mode.
It was the same problem with my Vibrant. Solved with JTAG controller. But you'll waste your warranty in that way. Try jig solution first
Adb?
Sent from my SGH-T959 using XDA App
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
canadianrider said:
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
Click to expand...
Click to collapse
option 1
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB...
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears... once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready... (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
8) Your phone will reboot into the download screen... go back to ODIN - A com port should now appear for your phone...
9) Click start and wait for your phone to do its thing
Option 2
***First you must have ROOT***
Download Terminal Emulator from the Market
open terminal emulator
**you may need to change to default android keyboard for proper inputting
1.) type "su" and press enter
a dialog box will appear asking for root access and say yes (obviously)
2.) type "reboot recovery" and press enter
at that moment, ur phone should reboot into Download Mode to load Alternate firmwares for like Eugene's Vibrant4 ROM etc......
this it what it should look like...
#su
#reboot download
Option 3
or you can download and install quick boot from the market which you then can make a shortcut to reboot into recovery with just one click
Sometimes it takes more than one try to get into download mode. I just take the battery out for a little while. Put it back in and hold only the volume up and down buttons while it is off and plug in the USB cable.
One thing though, when holding down the up and down volume buttons, it is very easy to mistakenly press the power button because it is exactly opposite of it.

key combination won't work for download mode

No matter how many times I have tried, the combination of Vol Down+Home+Power together does nothing, the phone just continues to load normally, I cannot access download mode.
My S5 (G900F) is on Android 6.0.1, which was the last software update for the phone, I would like to try 7(Nougat) but can't get anywhere near rooting or flashing.
The phone functions fine as it is, but for the last ?? Years I have used Windows Phones so android of quite alien to me but more preferable than apple. I would like to check out what's available in different builds.
anyone any ideas why it won't let me in, USB is enabled and it is in developer mode.
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Eggleston11 said:
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Click to expand...
Click to collapse
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
comuscomp said:
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
Click to expand...
Click to collapse
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Eggleston11 said:
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Click to expand...
Click to collapse
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
comuscomp said:
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
Click to expand...
Click to collapse
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Eggleston11 said:
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Click to expand...
Click to collapse
No, I can't get into download or recovery, I have tried with the 3 key combo and using ADB, the first still refuses to work and the ADB doesn't find the device.
Smart Switch won't connect nor will Odin.
Lineage 14-1. and open-gapps-arm-6.0-micro.
I had opened a new thread before I got your reply, how do I include your answers into that tread? "Bricked after attempted Update: Help".

Categories

Resources