I have an old glaxaxy ace which i decided to root and i kind of failed. By failed, i mean that when i attempt to boot up the phone with the power button, the screen gradually goes from the samsung logo to white- white bars appear and slowly fill the screen going up to full brightness. I fiddled around a bit, trying to install the stock os that came with the phone (i think it was jelly bean 4.12), and i managed to delete recovery mode. No idea how, but it simply shows the samsung logo and then turns off when i try to get into it. I have never rooted or flashed which is why i was trying on this old galaxy ace (that is like £50 nowadays).
Anyway, how can i recover recovery mode -lol-. My laptop doesn't recognise it (before it recognised it as an external storage device) and i don't renember what the model is.
Wiryfuture said:
I have an old glaxaxy ace which i decided to root and i kind of failed.
Click to expand...
Click to collapse
Which Galaxy Ace, is it? And more details on the phone if you can
Related
Hello,
I'm new to the community. I generally work on PC but a friend brought me this Samsung Galaxy tab 7.0 Plus that turns on but is stuck at the "Samsung Galaxy tab 7.0 Plus" splash screen when it first turns on. I have tried the" Power+Vol up" to reset to factory but it seems to go too-quickly and then I am back to square one because nothing changed. I dont know if my friend or his kids tried to do anything crazy with this so I don't have much more info.
What I am asking... I want to get this tab back to factory, or at least a working ROM. any advice is helpful but please keep in mind I have never really worked on these devices, the one thing I do know is if I jump to conclusions I can brick the device.
Thanks in advance. If more info is needed please ask.
did you try with a retore power + vol down with Odin
http://www.sammobile.com/firmware/?page=3&model=GT-P6210&pcode=XAR&os=1&type=3#firmware
choose between 3.2 honeycomb or 4.0.4 ICS
I got the same problem before !!!
http://forum.xda-developers.com/showthread.php?t=1827942
There is my solution
I had a very similar problem to both of you and noticed that the /data (instead of /efs) directory/partition "didn't exist" according to the boot screen when i entered the default recovery mode. i partitioned it and ran a factory reset and it finally booted.
and all just in time to pull the factory US ICS update
Hi,
I installed CEBERUS V5 ROM in my Galaxy Ace without any problem, it works perfectly, when installing it on my brother's phone, it did everything OK until the last reboot in ClockWorkRecovery, the phone restarted as spected but it got stuck with the Samsung Galaxy Ace logo, it doesn't do anything else. I can't access recovery or download mode, it shows exactly the same samsung screen when doing the key combinations for each case.
When I plug it to power it doesn't show the battery image, it automatically turns on and shows samsung logo again. If I plug it to my PC it's the same and the PC doesn't recognize any plugged device. I took the battery and tried again thousand of times, and nothing seems to get that screen out.
Is there anyway I can solve this?
In case there's no chance to fix it, I have a warranty for the phone, is there anyway my provider can notice I tried to install a custom ROM?
Anyway I would prefer fixing it myself, please can you give me some advice?
Thanks a lot!
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
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
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.