Ok, a long story here.
My son dropped his Samsung Ace2x s-7560m phone. The screen cracked. I bought a replacement screen through a reputable seller on ebay.
After installing the screen, the s7560 starts, but freezes on the Samsung screen, then boots over. This goes on and on.
I rooted the phone and flashed a 7562 stock rom to the device. The only difference between the two devices is that the 7562 is a dous phone.
The flash went well, and after rebooting, the phone boots up. It starts out as a 7560, then the screen flickers and becomes the 7562 duos.
The phone boots up. I can surf online using wifi, and the screen reacts as it should for the whole screen.
Now, when I try to call out the call does connect, but I can't end the call. The phones network does not work at all.
I have tried to enter into the recovery and can , but only by using adb. The key combos don't work. I can get the phone to boot into download mode.
The bootloader still shows as a 7560, and the software shows as a s a 7562. I think what is happening is the seller from ebay has sold me the duos screen instead of the 7560. He has refunded the money, and told me to keep the screen, so now it has become a bit of a challenge that I will defeat.
I am wanting to get the phone working. I have found a rom called kyleopen, but all the download links are removed or not working. I can put other files like cwm into the download file. When I try and access the sd card, I get an error that it can't mount it.
So..
Is there a custom rom that works on both the 7560 and the 7562 that can be installed using odin?
or:
Is there a way to flash the bootloader to be a 7562 model?
Is there a way to correct the screen issue..whereas I can still use a 7560 rom, and the screen will be detected.
As stated, I am trying to run the 7560 with a 7562's screen. I am guessing the digitizer is a bit different from device to device, and that the 7560 is just not recognizing the screen as being there. I have tried to flash the stock 7560 rom back onto the phone, but get the same issue..won't boot past the samsung screen.
Is there a file to alter to get the 7560 to accept the screen as the right one? I know the screen does work with the phone, and think the network issues I am having is because the duos feature of the rom flashed to the device.
Anybody have any ideas?
freakybaby said:
Anybody have any ideas?
Click to expand...
Click to collapse
Maybe too late.
In a call, usually if you can´t finish the call is because the proximity sensor is not working and didn´t detect that you separate the phone from your face, or when you disassembly and reassembly the phone you forgot the plastic mount of the infrared detector.
Did you get the two lines working? I mean, both phones are exactly same board and rest of the spares, but s7562 uses two sim cards, in a s7560 flashed with s7562 firmware are both sim cards works?
WBR
freakybaby said:
Ok, a long story here.
My son dropped his Samsung Ace2x s-7560m phone. The screen cracked. I bought a replacement screen through a reputable seller on ebay.
After installing the screen, the s7560 starts, but freezes on the Samsung screen, then boots over. This goes on and on.
I rooted the phone and flashed a 7562 stock rom to the device. The only difference between the two devices is that the 7562 is a dous phone.
The flash went well, and after rebooting, the phone boots up. It starts out as a 7560, then the screen flickers and becomes the 7562 duos.
The phone boots up. I can surf online using wifi, and the screen reacts as it should for the whole screen.
Now, when I try to call out the call does connect, but I can't end the call. The phones network does not work at all.
I have tried to enter into the recovery and can , but only by using adb. The key combos don't work. I can get the phone to boot into download mode.
The bootloader still shows as a 7560, and the software shows as a s a 7562. I think what is happening is the seller from ebay has sold me the duos screen instead of the 7560. He has refunded the money, and told me to keep the screen, so now it has become a bit of a challenge that I will defeat.
I am wanting to get the phone working. I have found a rom called kyleopen, but all the download links are removed or not working. I can put other files like cwm into the download file. When I try and access the sd card, I get an error that it can't mount it.
So..
Is there a custom rom that works on both the 7560 and the 7562 that can be installed using odin?
or:
Is there a way to flash the bootloader to be a 7562 model?
Is there a way to correct the screen issue..whereas I can still use a 7560 rom, and the screen will be detected.
As stated, I am trying to run the 7560 with a 7562's screen. I am guessing the digitizer is a bit different from device to device, and that the 7560 is just not recognizing the screen as being there. I have tried to flash the stock 7560 rom back onto the phone, but get the same issue..won't boot past the samsung screen.
Is there a file to alter to get the 7560 to accept the screen as the right one? I know the screen does work with the phone, and think the network issues I am having is because the duos feature of the rom flashed to the device.
Click to expand...
Click to collapse
try this install firmware for s7560 then flash cwm recovery and after that boot into recovery wipe data/factory reset then go to advanced menu in recovery and then wipe dalvick cache . reboot phone. now it should boot with no problem
sadman2 said:
try this install firmware for s7560 then flash cwm recovery and after that boot into recovery wipe data/factory reset then go to advanced menu in recovery and then wipe dalvick cache . reboot phone. now it should boot with no problem
Click to expand...
Click to collapse
So I have reflashed with the 7560 rom. I am back to a boot loop. I can't get to recovery..I was only able to do that in ADB, but can't boot up for adb right now.
ANy other ideas..or ways I can get into recovery. I can get the download screen using the buttons, but not the recovery.
Means reflashed the rom using a stock firmware and ODIN?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
freakybaby said:
So I have reflashed with the 7560 rom. I am back to a boot loop. I can't get to recovery..I was only able to do that in ADB, but can't boot up for adb right now.
ANy other ideas..or ways I can get into recovery. I can get the download screen using the buttons, but not the recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=45767157#post45767157
here have all the faq for this phone and the links. download daverq18 root pack and follow the instructions. then you should succesfully boot into cwm recovery
Hello. I Was wondering if someone can help me with a dilemma......... i recently got my mega a month ago. I then decided to root my mega (As i do with all my android devices)The rooting process worked out great. The phone booted.....Everything's all peachy! root was successful! After about 3 weeks i wanted to record my screen. By the way i was running kitkat on my mega. So i installed a screen recording program. i wanted to record the screen so i started the recording..... but it wasnt recording. it kept saying an error message i think it when like gpu is not supported and change to cpu something like that! i thought nothing of it... so i changed the settings to gpu then to cpu (Not knowing what i was doing) after it failed to record again i threw the towel in and quit. i then played one of my mobile games(FNAF2) after i lost the game i went back to the homescreen and the homescreen was acting up... it was in landscape mode when i had the phone upright. it was bugging me to the point where i just rebooted my device. i tried rebooting my device BUT IT WAS IN A BOOTLOOP! i had no idea what was going on. So i tried to restore the backup and it was restored but it was still in a bootloop. at this point i was freaking out! when i went home that day i put the device in download mode and flashed the stock firmware but it failed and didnt work. but when the phone rebooted it booted up and my phone was on activation screen and it was in a different language. then i soon found out that my touchscreen wasnt responding! neither was the home button or back button. i really dont know whats going on. kies does not work i tried emergency firmware initializing and kies didnt read it i tried reinstalling kies and my phones drivers 4 times and it was a no go...... but i finally found a english firmware and i flashed it but it failed and said something like dev_not supported or something so that didnt work either..... i booted up my phone and the language was back to english and my touchscreen wasnt working neither was my home buttons or anything. i also tried installing custom roms but everytime i try to install them it says it completed installing but when i boot up my phone its the same activation screen. i really need help anything that can help will be greatly appreciated. also everytime i boot up it always says set warranty bit:Kernal
I have been given an S7 SM-930FD [Dual Sim] that was supposed to be bricked. It wouldn't boot into anything but I have successfully got it into download mode and been able to successfully flash a stock ROM downloaded from Sammobile [several times] with no errors. Each time I have used the full set of AP,CP,CSC files and the previous owner is not sure what ROM it was on or what he tried to install. I have tried different versions of the firmware for this model for various android versions and regions simply to try and get it to boot, but without success. I have tried HOME CSC and CSC files too.
But each time it starts to install the update / reboot it hangs. Either when it installing the update on the blue screen with the robot and its "erasing" - small rotating symbol just stops and nothing happens OR it loads to the GALAXY S7 normal boot screen then hangs.
When it hangs it will only respond to one key combination Power + Vol Down. It then "switched off" and will not reboot in any mode. When I say "switched off" I mean the screen goes black. However if I then connect the charger, it won't show the charging symbol UNLESS I leave it for a few hours and the battery goes flat. It will then charge and I can boot into download / recovery mode but normal boot starts installing the update and it will hang all over again. On one occasion it hung with and black screen and blue flashing light but again no key combinations worked and I had to wait for the battery to drain.
Also tried Smart Switch Emergency Recovery. Even with the drivers freshly installed it does not recognise the phone, it does accept the model number during initialisation, but once the S/N is entered it comes back and says it can't find the model, S/N or IMEI in the database!
I have researched the web for hours and watched every relevant youtube video and tried their suggested key combinations etc and they just don't work.
So I'm hoping someone can help me resolve this frustrating situation, not least because of the delays between attempts!
Presumably as I can consistently get it into download mode there is a solution out there somewhere???????
What am I doing wrong? Should I be looking at a custom ROM or trying something else?
All help appreciated.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.