Database Users

Samsung galaxy Grand2 SM-G7102 hangs on start screen and NO touch

Hello everyone, I'm new here
I have a Samsung galaxy grand2 SM-G7102.
I performed a root for my device (most probably with Kingo root), I cannot remember if I have unrooted it or not.
The device notified me about a firmware upgrade to kitkat, I tried it several times and failed after complete download.
A fail message from the device told me to use Samsung Kies to perform the upgrade.
after upgrade with Samsung Kies, I found the device with the following problems
- Hangs on start screen and takes too long to startup (about 20 minutes) and gets too hot​- After startup, there is NO TOUCH. the device is not responding to touch, but the power and volume keys are working ( I can enter download or recovery boot)​
I downloaded the official kitkat ROM for my device. and searched the forum to flash the ROM using Odin. I did flash the ROM several times with no success , I got the same result.
what can I do to get my device to work again?
thanks in advance

Hi amr
Sorry I have bad news
I hate to tell bad news but I feel I have to so you stop searching...
You bricked your screen touch by flashing a wrong root files...
I tell you this because I have the some problem with my galaxy star
Here is the solution from other forum
"Hi, I had the same problem and the only one solution I've tested is changing the touch driver on the touch module. All you need is a broken touch (the donor) and a lot of patience.
Step1. Disassemble the working phone.
Step2. Carefully take out the touch module (here you need a lot of patience and time). DON'T TRY to change the driver on the assembled phone because the display will be destroyed. I speak from experience.
Step3. After the module is out unplug the touch panel from the display and blend out the driver.
Step4. Now you can change the driver. NEVER try to change the driver when it is on the display.
Step5. After finished changing the driver repeat all the steps in the reverse order.
It is working 100%."
He said working 100% but I say do it at your own risk or just take your phone to repair
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from my g7102 CM12.1 5.1.1 r8 using tapatalk

Thanks salimtn for your reply
BUT
FIRST: I forgot to mention that I have replaced the device touch (not the screen only the touch) with a non-original one.
SECOND: I searched the forum for a similar problem and I found a very similar one with galaxy mega here:
http://forum.xda-developers.com/galaxy-mega/help/galaxy-mega-4-4-2-4-4-4-touch-bootloop-t2922542
the guy made a video to fix the problem with software solution which can be summarized in the following:
- copied twrp recovery, update superuser, and a custom ROM called megafire - all zips - to internal phone memory
- installed philz touch with odin
- installed twrp through philz !!
and through twrp did the following
- update superuser
- wipe all caches
- factory reset
- installed ROM
- factory reset
AND it worked for him, I am new here, and I wish if someone can help me figure out a customization for this solution to match my Grand 2 problem, thanks again

My friend I had replaced the device touch too and this problem started on non officials touch
The problem now is how we could find this megafire ROM???
I have galaxy star and they didn't make for it a custom ROM yet
Any way a suggestion for you
Try to follow the process but instead of flashing mega fire ROM try cm11 or cm12 ROM or any other ROM and maybe you will be lucky
UPDATE
I saw the thread mentioned and the videos and they said you can use cm11 ROM so just check the thread again for proper procedure
Search grand 2 forum for philz and trwp recovery
Then go on and try
Just make sure you to choose the right recovery and supersu because some maid for 4.3 and some for 4.4
Sent from my SM-G7102 using Tapatalk

Salimtn, thank you again, I just saw your kind reply, I'll try this and update the reply

amr.alamir said:
Salimtn, thank you again, I just saw your kind reply, I'll try this and update the reply
Click to expand...
Click to collapse
OK [emoji106]
Sent from my SM-G7102 using Tapatalk

G900-F: Used TWRP to install xposed framework, now stuck on logo screen

I used TWRP to install xposed framework v86. I clicked the reboot now button after flashing it. My phone was stuck on the logo screen for 40minutes before I took out the battery. Now whenever I turn it on its just stuck on that screen. I also flashed SuperSU before but my phone worked perfectly fine after that. I'm completely clueless so any help would be appreciated! My S5 runs on Marshmallow (6.0.1). I've seen people mention reactivation lock and mine says off when in the downloading screen if that helps at all

What ROM are you using; and also which xposed version did you flash? There are different xposed zips for touchwiz roms. You can try running the xposed uninstaller.

blubbermonkeys said:
What ROM are you using; and also which xposed version did you flash? There are different xposed zips for touchwiz roms. You can try running the xposed uninstaller.
Click to expand...
Click to collapse
I flashed xposed-v86-sdk23-arm.zip. I installed xposedinstaller_3.0alpha4.apk before. I can't put the xposed uninstaller onto my phone since my computer won't recognise my s5 unless its fully on (not in recovery mode or stuck on the logo screen)

username14 said:
I flashed xposed-v86-sdk23-arm.zip. I installed xposedinstaller_3.0alpha4.apk before. I can't put the xposed uninstaller onto my phone since my computer won't recognise my s5 unless its fully on (not in recovery mode or stuck on the logo screen)
Click to expand...
Click to collapse
Try put the uninstaller onto an SD card and flash from there? Anyways If you are running stock samsung touchwiz use this xposed build instead, as the official build is incompatible the samsung roms.

blubbermonkeys said:
Try put the uninstaller onto an SD card and flash from there? Anyways If you are running stock samsung touchwiz use this xposed build instead, as the official build is incompatible the samsung roms.
Click to expand...
Click to collapse
Unfortunately my phone doesn't recognise an SD card after my friends sim got stuck when he was using it on a holiday and he had to use a fork to push it out. Do you have any other suggestions?

username14 said:
Unfortunately my phone doesn't recognise an SD card after my friends sim got stuck when he was using it on a holiday and he had to use a fork to push it out. Do you have any other suggestions?
Click to expand...
Click to collapse
Well then. I guess you can use USB-OTG? Or you can try this to get it to boot, and transfer the files from there.

Just flash the same stock ROM over the top with ODIN

blubbermonkeys said:
Well then. I guess you can use USB-OTG? Or you can try this to get it to boot, and transfer the files from there.
Click to expand...
Click to collapse
Thanks. I followed this link (http://highonandroid.com/android-ro...android-in-a-bootloop-with-no-os-using-adb/2/) from the page and did everything it said. However when I put in
cd downloads
cd fastboot
adb devices
into the command prompt I get this back:
"'adb' is not recognized as an internal or external command,
operable program or batch file."
Do you know how to fix this so I get this screen instead?
{
"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"
}

*Detection* said:
Just flash the same stock ROM over the top with ODIN
Click to expand...
Click to collapse
Thanks I'll give that a go

Thanks flashing a stock rom worked!
In case anyone comes across this thread having the same problem follow this tutorial and just download the S5 rom for your country/operator on sammobile:
https://www.youtube.com/watch?v=HVLyjeqPtn0

Galaxy J5 SM-J500FN stuck on boot screen after flashing custom ROMs

Hello to everyone,
I hope that someone can help me at this point where i'm stuck on bootscreen after i flashed an custom ROM.
So, let me tell you my story.
I have a little of experience with flashing custom ROMs. And on my personal phone (Galasy S5) i succesfully installed over and over again custom ROMs. I really like the ROMs from AOSP Extended. They are covering all of my needs. So today i have an Samsung Galaxy J5 SM-J500FN. It is having some problems with the capacitive buttons(Back and multitasking buttons); those are playing however they want, so you can realise that entering in some app and your phone exiting fro it by itself is very annoyng. So on my S5 i have an option that can disable those buttons for good. And i wanted to install the Android &.1 Nougat offered by AOSP Extended today. So i ve got the TWRP from the official website for the right model of the phone (J500FN) and put it succesfully on it. I downloaded the ROM from official AOSP website, and succesfully installed it on the phone whithout any error. Then i installed the GApps nano, again with 0 errors. And when i was relaxing a little bit hoping that everything it s allright, when i wanted to boot up the phone, it froze up at boot screen (At the moment with that logo with Samsung ... powerd by Android). Then in a couple of seconds it started to turn to an green screen and then to an white screen. At this point, everything is frozen. So i removed the battery and entered in recovery mode(TWRP). There was no problem (only with those capactive buttons that i want to block).. But anyway, i donloaded several ROMs and nothing so far. I tried with anoter TWRP version, samething, stuck on boot screen.
Until my first atempt to flash the custom ROM, the phone worked just fine, only that those buttons ware going crazy. But now, i can't start it up in every mode i can think of.
Can anyone help me with this, please?! Any ideea of how to slve it?
TWRP version 3.1.1-1 j5 nlte
Firmware version: AospExtended-v4.5-j5ltexx-20170816-2007-OFFICIAL
Phone version: SM-J500FN
Tried with various TWRP versions and ROMs. Installing with and without GApps. All the results were the same like in the pictures below:
1) Start up like a normal Android phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) The the big surprise
3) Getting colorfull
4) Advancing...
For now, i can flash with Odin any version of TWRP, i can flash from TWRP any firmware, but i cannot get it boot up normally.
I don't have any backups from stock firmware so, please don t ask me about that.
Thanks in advance...

Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15

garylawwd said:
Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15
Click to expand...
Click to collapse
I downloaded all the files i found out there to try see if anything is changing ))
I will try your solution later. Thank you for your reply

All done!
So, guys, my problem wasn-t from the firmware model, because i tryed many.
Thanks to
garylawwd
Click to expand...
Click to collapse
i flashed with Odin ''BootLoader version 5.1.1'' and everything after that was pretty simple.

Touch screen is all haywired during TWRP

Hi, I was installing Evolution X rom.
Now this is not a ROM problem or any tool. I'm telling the series of events.
So I was installing the ROM, and I was using the All in One tool for MiA1.
So I booted into TWRP, but the touch was all messed up.
Like if I click on the top of the screen, the bottom gets click, if I click on center, top gets clicked.
If I somehow manage to go inside of it, like the filemanager, if I click on back button, it take me inside the directory.
The touch is all haywired.
I somehow manage to install the stock PIE March build.
But how do I fix this.
I really want to try Evolution X Rom.
Kindly let me know.
Thanks.

Have you tried a different TWRP? What about boot TWRP Using fastboot commands?

Gamestrav said:
Have you tried a different TWRP? What about boot TWRP Using fastboot commands?
Click to expand...
Click to collapse
Yes, I tried different versions, old to new.
And fastboot command too. But no use.

shaikhatik0786 said:
Hi, I was installing Evolution X rom.
Now this is not a ROM problem or any tool. I'm telling the series of events.
So I was installing the ROM, and I was using the All in One tool for MiA1.
So I booted into TWRP, but the touch was all messed up.
Like if I click on the top of the screen, the bottom gets click, if I click on center, top gets clicked.
If I somehow manage to go inside of it, like the filemanager, if I click on back button, it take me inside the directory.
The touch is all haywired.
I somehow manage to install the stock PIE March build.
But how do I fix this.
I really want to try Evolution X Rom.
Kindly let me know.
Thanks.
Click to expand...
Click to collapse
Hey,
have you found a solution? I have the same problem...

shaikhatik0786 said:
Hi, I was installing Evolution X rom.
Now this is not a ROM problem or any tool. I'm telling the series of events.
So I was installing the ROM, and I was using the All in One tool for MiA1.
So I booted into TWRP, but the touch was all messed up.
Like if I click on the top of the screen, the bottom gets click, if I click on center, top gets clicked.
If I somehow manage to go inside of it, like the filemanager, if I click on back button, it take me inside the directory.
The touch is all haywired.
I somehow manage to install the stock PIE March build.
But how do I fix this.
I really want to try Evolution X Rom.
Kindly let me know.
Thanks.
Click to expand...
Click to collapse
1. Try back to official ROM first, you can found it here, in my case I'm using MIUI V.10.0.24.0
2. Let it boot to system, enable usb debug then unlock your bootloader again ( fastboot oem unlock in fastboot mode)
3. Flash TWRP official or unofficial using minimal adb, for hotboot first I'm using TWRP from here
4. EVOX 4.7 that I use, you can found it here
Spoiler: Screenshot
{
"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"
}
Hope that help

Boots only to TWRP - Need help fixing

Hi there. About a year or so ago I went about flashing my Tab but it went wrong and now all I can do is get it to boot to TWRP. Would someone be so kind as to tell me step by step what to do to get it back working? I'd prefer it to go back to stock ROM without TWRP or other 3rd party flash programs but I'll take what I can get. Help appreciated.
This is what I get when it boots:
{
"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"
}

Bump.

fuzzyreets said:
I'd prefer it to go back to stock ROM without TWRP
Click to expand...
Click to collapse
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?

DHGE said:
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
Click to expand...
Click to collapse
I got a reply! Thank you!
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.

fuzzyreets said:
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
Click to expand...
Click to collapse
What was the goal when you started down the path of installing TWRP? It seems like you might have been part way there if you got that far?
There are Lineage install instructions here. <-- More importantly Odin Download if you don't already have it.
If you decide to try Lineage, the latest builds require new firmware found here. It can also be obtained by returning to stock and updating.
Anyways If you are in TWRP, in the restart menu there is an option to restart to download. If will reboot to a black screen, just hit the power button once when the screen goes off. Before you do this, you need to obtain stock firmware, from somewhere. (Sammobile or something like that) You will also need Odin, link above.
As with anything proceed at your own risk.
Once you have those files, you can extract the firmware. They will be labeled and go into those spots in Odin, AP, BL, CSC, then you should be able to hit start. I'm going from memory, as I haven't had to restore mine since I got it (and looking at the files in stock firmware file).

Idk how relevant this is anymore but I had this same issue after I install lineage 18, there's a multi-disabler zip I got awhile ago that fixes all my flashing problems related recovery loop. Just Google that zip, flash it then format and restart. That what I've done easy fix, this assumes you followed the basic steps to properly flash whatever it is you're trying to.