Samsung galaxy Grand2 SM-G7102 hangs on start screen and NO touch - Galaxy Grand 2 Q&A, Help & Troubleshooting

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

Related

[WARNING!] Do Not flash Any ROM until you can get the 3 buttons DOWNLOAD MODE working

[WARNING!] Do Not flash Any ROM (firmware) until you can get the 3 buttons DOWNLOAD MODE working, there is a FIX for that.
Visit the SGS Wiki for details on how to get into the Download Mode
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode
You'll be saving yourself a lot of tears by installing the 3 button SPL fix before you flash the new Froyo or any other ROM you want to try out on your phone.
Follow the instructions on this topic to get your 3 buttons working again
{
"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"
}
ODIN method http://forum.xda-developers.com/showthread.php?t=785201
If ODIN gives you butterflies in the belly, you can try the alternative "SAFE" method via
update.zip http://forum.xda-developers.com/showthread.php?t=821698
Enjoy! ...& Happy Flashing
Note: if you are already bricked and you did not apply the Fix before hand, then your only alternative is to send the phone out for repair, or you can make your own JIG cable to unbrick you phone via ODIN following this guide:
[HOWTO] [REF] Make your own homed made JIG cable for phones without 3-button combo
Hi there,
The Odin method posted originally by Richtofen seems to be MIA on this forum. I wanted to try that method as in the thread another user with the same phone as me confirmed it had worked for him. Now, however the link is invalid and this only happened in the last few days (???)
Does this mean the more recent, Hiemdall method is now the preferred way of doing the 3BR fix?
Cheers,
Xav.
Bump? Does a link to Richtofen's method still exist?
I didn't have the 3 button modes on my phone. After updating to Gingerbread via Kies (which overwrites the bootloaders) the 3 button modes worked.
So... if it is the first time you are upgrading, just try to go to Gingerbread through Kies - though I do not know if all regions get the recovery and download modes.
jutezak said:
I didn't have the 3 button modes on my phone. After updating to Gingerbread via Kies (which overwrites the bootloaders) the 3 button modes worked.
So... if it is the first time you are upgrading, just try to go to Gingerbread through Kies - though I do not know if all regions get the recovery and download modes.
Click to expand...
Click to collapse
Yeah, I'm here in Australia and there's been no update to Gingerbread via Kies - just checked again recently after an update to Kies - still reports that the 2.2 firmware I have is the "latest"
However, from other posts and messages here, it seems if I'm willing to risk a jump straight to a Gingerbread ROM, then the 3BR is also fixed as part of the process. Need to do some more reading I guess.
Cheers,
Xav.

[Q] Is my phone completely bricked? Pixelated screen when I boot my rooted Defy XT

{
"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"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.
Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app

[Q] Can't boot any ROM!

Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"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"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app
Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken

Yoga 2 1050l efi fault after OTA. Only DNX mode left,no recovery/Fastboot. Hardbrick?

[SOLVED] I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and now i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
{
"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"
}
SOLVED
daverob79 said:
I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and no i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
Screenshot on imgur.com/gnUBeXS
Click to expand...
Click to collapse
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
daverob79 said:
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
Click to expand...
Click to collapse
Ok, so I was able to flash this rom and boot the tablet. But when i get the OTA the tablet crashes...
The OTA was YT2-1050L_USR_S100192_1511191319_WW52_ROW
Now trying YT2-1050L_USR_S100081_1507241439_WW52_ROW, will update with results

			
				
Can it be that the OTA did not have all the right files. Or did the root process do something so that I can only flash stock roms?
I am really not getting any wiser on this intel world. Only been playing with Samsung, Nexus(LG/ASUS) and HTC
Any thoughts? Anyone??
And I can't post images, sorry for that :c
forgot this,
Thanks ionioni
after you flash remember to set your region code before taking any ota's (on the first Android boot go to Contacts and in the search contacts box input ####59930# and if it shows a two letter country code then you're good to go, if it shows 'unknown' then you need to set a country code, input in the same box ####6020# and chose a country, yours or a close one, tablet will reboot)
Click to expand...
Click to collapse
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
corasman said:
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
Click to expand...
Click to collapse
I did
Now I have my tablet back!
Seems like there is a big difference between the ROM's (the YT2_1050L_USR* files)
Maybe we should have a tread with all the different ROM's?
I found this on Androidfilehost: Link to downloads for Lenovo Yoga Tablet 2 by ionioni
But how do you see the difference between different roms. Many are big files even if they are not stock roms (with radio, droidboot, bootloader, bios etc)
Now I have 1050L_S100255_160113
Is this the latest ROM?
I think the differences are in the file names...after YT2 it tells you which file is for which model.

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.

Categories

Resources