detection of generic screen Samsung? - Galaxy Grand 2 Q&A, Help & Troubleshooting

I have grand 2 -> SM-G7105,
the LCD was broken, I changed (with tactil and glass), but it remains fixed on the samsung logo SM-G7105.
When disconnecting the connector of the screen: start I hear start "boot audio", but when the screen is connected it will not boot: juste logo Samsung Sm-G7105 (not boot),
* I tested several Rom kitkat and recovery (unofficial) but not to go into the recovery (at least flash a custom rom kind cyanogen etc).
*** Do you have a solution to elevate the detection of generic screen Smasung?
I had almost the same problem on the "i9205 Galaxy Mega 6.3" I managed to change the cwm recovery and put a custom rom
But with the Grand 2 impossible it is completely blocked.
video for my seller:
https://www.youtube.com/watch?v=QJfKmYTH_Gc

Related

i337m Issues - Unable to Boot

Hi Everyone,
I am going straight to the point:
- Rogers Galaxy S4 (I337m)
- when purchased couple of months ago, it was on factory firmware - I337MVLUAMDJ
- I decided to read about the running i9505 roms as per posting here - http://forum.xda-developers.com/showthread.php?t=2295557 - I am not a newbie to any rooting & tools used - e.g. ODIN, TWRP, CF-AUTOROOT, etc. etc. I started with the CF-AUTOROOT and all went well.
- it had the latest TWRP installed via ODIN - openrecovery-twrp-2.6.3.0-jfltecan.tar - as per: http://techerrata.com/browse/twrp2/jflteca
- last night, the phone was perfectly running Omega v12 Jelly Bean 4.2.2 (Based on firmware ZHUDMI1 Android 4.2.2 (Date: 12/09/2013)),
- it was running with Kernal from: http://forum.xda-developers.com/showthread.php?t=2289140 (Ktoonsez Touchwiz JELLYBEAN 4.2.2 VERSION)
- everything was working perfectly - WiFi, Data, Calls, etc.
- overnight the phone's battery drained , and when I went to charge it and boot it this morning - it was stuck on the Samsung Galaxy S4 logo - weird right?
- so I tried the following:
- tried to boot into TWRP - no luck
- the phone does boot in Download Mode , which is great
- because the phone boots into Download Mode, I downloaded the factory (non-rooted) ROM - I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar
- MD5 was verified and ODIN completed without any issues
- The phone is still stuck in Samsung Galaxy S4 logo screen, it doesn't go anywhere else?
- What to do? Please help?
P.S. When ODIN is finished, it reboots and initially it loads the factory recovery and you see the android with the gearbox circling (lol), and then you see under the android image a blue bar - going across (indicating something was completed) and it reboots - at this point, it gets stuck on Samsung Galaxy S4 logo screen.
Also, when it is in download mode: it says the following -
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: Enable
Please help, & thanks in advance!
I have the same problem recently. I flashed through Odin. It says passed, but still the bootloop and not able to get into recovery.
You should try Kies firmware emergency recovery, or firmware update. It worked for me. Weird.
Did you do a factory reset in recovery after Odin?
Figured It Out...
Hi Guys!
This is going to sound funny and weird, but the problem is ... overheat/overload battery issue!
I realized the USB cable that comes with S4 accidently had a splice on the cable (I believe it could be because of my near-sharp corners around my desk, whereby, my cable makes contact). For whatever reason, when I charge using this faulty cable, the battery gets very hot and the battery percentage fluctuates. (was at 60% then drops to 20% then goes to 40% ... all within few minutes of each other...weird)
I am sure the battery itself has a circuit board, I was thinking it could have been damaged.
Anyways, I threw that spliced cable in the garbage and replaced with another OEM USB cable and the phone started to work fine.
Also note, I was reading another thread about someone flashing the wrong ROM, and they kept the battery separate from the phone for approx. 5 mins - 10 mins, and it resolved the issue.
So, basically that's what I did, keep the battery separate from the phone for that long and it worked.
But I will definitely change the battery with a fresh new OEM, I am not going to take any chances.
Thanks again all for your ideas. I am sure I would have resorted to that if this didn't work.

[Q] n9005 display burned?

Hey!
Today when I were writing on whatsapp my n9005 display began to svanish and becomes green and white, i can boot it into odin download mode and even into recovery, when i boot it i can see that it booted and it loads, so i think the motherboard should be ok, is the display broken or something else? Can i simply buy a new one with frame and substitute it?
n9005 - rooted - no warranty ( cause the guy who sold it did ran the knoxxxx )
Thanks

Broken QuickWindow Sensor

Hello Everyone!
i will try to describe my problem in point by chronological order
- I broke display of my D802 with Cloudy G2 (KK) with possibly quickwindow option turned off (i do not remember), rooted and unlocked bootloader, and mounted a new one.
- Between broke and mounting new display elapsed 3 months, so i tried to reset Cloudy over system settings, for installing all apps and setting from begining.
- After that i had booloop, so i tried to go into TWRP, but every time i tried, logo of TWRP was showing for half of second and then screen was black (but backlight was working)
- After few times i tried to boot phone and it booted, but quickwindow clock shows up without possibility to unlock phone, so i tried to install cloudy g2 3.3 with quickwindow option off in aroma installer.
- After installation LG logo appered for quater of second and screen goes blank. In computer device was detected as QHSUSB_BULK, so i unbricked it without problem
- but after that there was need for install system over lg flash tool, so i installed original KitKat, but in "Firmware Update" screen there weren't red word Rooted. It seems to had locked bootloader and unrooted after QHSUSB_BULK repair.
- Then i booted clean original new KK, but there is also QuickWindow clock directly after booting system!
So for now i had:
- Kitkat
- Locked Bootloader
- Stock Recovery
- No root
- No usb debbuging (no adb)
- All time quickwindow clock
I tried to go into clock, weather, camera from down button and touch any soft button but there is no possibility to get into system and turn on usb debbuging for root, install recovery and install any CM based software to use phone like a charm.
I tried to unmount sim card, front and rear camera, proxmity sensor, take battery from inside to outside case f phone, antena wires and make a distance between mobo and case but no diffrence. Tried to use quickwindow case but it's not working....
AND FOR NOW when i am writing this problem screen turned on with noob system tips and system booted and i turnet on quick windows case! But it's not full solve.
Any ideas what may be a problem? I looked for photos and service manual of D802 and i know which one part on motherboard is magnetic sensor (becouse quickwindow working by magnet) but it's is not fired like other parts.
Sorry for not good English. I hope that you understand everything

Please Help ! I think i've bricked my Samsung A20

I thought of testing out different custom ROMS available for my device (Samsung A20 ) just to see what fits me, So I tried to flash a custom ROM "Havoc OS", right after flashing a ROM from XDA under my phone's section which is another custom ROM which i guess is ported from S20 " https://forum.xda-developers.com/galaxy-a20/development/ultimate-q-s20-v2-rom-t4104667 " and installed the ROM it worked fine, but after flashing Havoc OS, It boots up but the screen goes black after few seconds after displaying the Samsung logo... Knox... Powered by android and all that but goes off quickly and the black screen starts to appear, i tried holding down the power button and volume down together and also power button + volume up but nothing seems to work, i.e it won't get me into recovery or download mode. I tried using Odin while the phone is connected but even then it didn't show up on Odin's log as well. Please help :crying:
Update: The problem was fixed: I left the device to stay in the boot loop and the battery drained and then when I connected it to the power brick when the battery is completely drained i was able to boot into twrp recovery without a problem. ( Also i did this after removing the memory card )
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369

SM-N910F Blackscreen after flash / Odin = Pass - looking for help

Hello community,
A good friend of mine asked me to support him with his "bricked" Note 4.
I tried now for a few hours (usually im experienced with stuff like that) without any success.
Downloadmode is accessable. Odin (3.09) says most of time 'pass'.
I flashed the following stock roms:
N910FXXU1DRI2_N910FOXA1DRI1_DBT_(Germany) [We are from germany] 1 File.
Odin tells me: pass, Phone reboots in recovery mode, installs a system update, processbar filled half, "earasing", reboot into recovery and display stuck on black after retry to install a system update.
I already tried to debrick - after reflash the PIT file, the Note4 stuck in the Note4 Splashscreen with a blue LED blinking but nothing more happens. [Debrick XDA Thread] (should it?)
I tried also the N910FXXU1ANK4_DBT_4Files Firmware but same behavior (black screen after system update - the phone must turned on since the power button doesnt react - I need to pull of the battery for reboot).
Any hint for me what Im doing wrong? This devices drives me crazy ...
Is the device hardware broken maybe? What do you guys think?
Thank you for reading
Best regards
/nepixl
Have you tried to install a custom recovery instead first?

Categories

Resources