My Galaxy s+ is in trouble. I flashed CM10.1 on it, wich worked fine, but then i wanted to flash the gapps, and now i'm stuck in cmw bootloop. I can't select anything in cmw, so the only thing i can do is get it into download mode. My pc does see the phone, but the problem is, odin doesnt.
Pleas help me guys...
Wolfkie40 said:
My Galaxy s+ is in trouble. I flashed CM10.1 on it, wich worked fine, but then i wanted to flash the gapps, and now i'm stuck in cmw bootloop. I can't select anything in cmw, so the only thing i can do is get it into download mode. My pc does see the phone, but the problem is, odin doesnt.
Pleas help me guys...
Click to expand...
Click to collapse
Have u tried different versions of ODIN? I had same problem and that help for me.
---------- Post added at 02:08 PM ---------- Previous post was at 02:02 PM ----------
ODIN Multi Downloader v4.43
That worked for me.
Related
Hi all, I've mistakenly installed CM10.1 P3100 on my P3110, so I tried to flash the original 4.1.2 version using ODIN P3110. All went well, but when it starts,it stays in the samsung logo. Does anyone know how I can fix it?
Excuse me for my bad English
keeper94 said:
Hi all, I've mistakenly installed CM10.1 P3100 on my P3110, so I tried to flash the original 4.1.2 version using ODIN P3110. All went well, but when it starts,it stays in the samsung logo. Does anyone know how I can fix it?
Excuse me for my bad English
Click to expand...
Click to collapse
have you tried a wipe data/factory reset? can you get in to recovery or download mode?
[EDIT] When i have boot loop i always flash back to ICS 4.0.4 and never had a problem with boot loop after (not saying this will be the same for you)
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
also check here for guides on just about everything
http://forum.xda-developers.com/showthread.php?t=1722745
squ89r97 said:
have you tried a wipe data/factory reset? can you get in to recovery or download mode?
[EDIT] When i have boot loop i always flash back to ICS 4.0.4 and never had a problem with boot loop after (not saying this will be the same for you)
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
also check here for guides on just about everything
http://forum.xda-developers.com/showthread.php?t=1722745
Click to expand...
Click to collapse
I've flash recovery and later I flashed CM10.1. Now my galaxy tab works ok. Thx for your help!
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Installed CWM 6.0.1.0 and rooted this device then installed a 10.1 nightly, wiped dalvik and all but now device boots straight into recovery after samsung 10.1 logo.. I've already tried flashing back to the stock rom using Odin, flash went fine but now it just boots into stock recovery instead of CWM.. also a bit of weirdness to it.. when i click on reboot system it just turns the device off instead of "rebooting", i've tried wiping everything and nothing seems to work.. was for sure the stock rom from sammobile would do the trick but nope ... any suggestions? Thanks.
Perhaps flashing v6.0.3.3 might work. :beer:
http://forum.xda-developers.com/showthread.php?p=41159669
dynospectrum said:
Perhaps flashing v6.0.3.3 might work. :beer:
http://forum.xda-developers.com/showthread.php?p=41159669
Click to expand...
Click to collapse
Thanks for the help but this didn't work either flashed with odin just keeps going to recovery when booted ...
Neoborn1 said:
Thanks for the help but this didn't work either flashed with odin just keeps going to recovery when booted ...
Click to expand...
Click to collapse
Did you ever figure this out?
I have a 5113 doing the exact same thing. I posted a thread on here but i dont think anyone has an answer.
---------- Post added at 07:59 PM ---------- Previous post was at 07:46 PM ----------
http://forum.xda-developers.com/showthread.php?t=2404899
Above is the thread that details what is happening with mine. Sounds like the same issue to me.
i rooted my Samsung Galaxy Quattro i8552 yesterday by installing cwm(miracuously i tell you) but after i started phone the cwm got erased and stock recovery got rewritten, so now i have stock recovery. I installed lcd modder and changed the dpi and it said restart and since then phone is not starting. I can goto recovery and download mode and i started adb and deleted the build.prop file from /system. now i cant push it also. Can somehow help me start the phone. I have no backups or cwm but i mite be able to get cwm installed somehow. any suggestion?
rico25new said:
i rooted my Samsung Galaxy Quattro i8552 yesterday by installing cwm(miracuously i tell you) but after i started phone the cwm got erased and stock recovery got rewritten, so now i have stock recovery. I installed lcd modder and changed the dpi and it said restart and since then phone is not starting. I can goto recovery and download mode and i started adb and deleted the build.prop file from /system. now i cant push it also. Can somehow help me start the phone. I have no backups or cwm but i mite be able to get cwm installed somehow. any suggestion?
Click to expand...
Click to collapse
since your able to get into download mode, get odin and download the stock firmware from Sammobile and find the correct phone model/carrier/country and flash it in odin.
rico25new said:
i rooted my Samsung Galaxy Quattro i8552 yesterday by installing cwm(miracuously i tell you) but after i started phone the cwm got erased and stock recovery got rewritten, so now i have stock recovery. I installed lcd modder and changed the dpi and it said restart and since then phone is not starting. I can goto recovery and download mode and i started adb and deleted the build.prop file from /system. now i cant push it also. Can somehow help me start the phone. I have no backups or cwm but i mite be able to get cwm installed somehow. any suggestion?
Click to expand...
Click to collapse
Is your phone a Verzion phone, sounds like a bootloader issue.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
mrwetwork said:
Is your phone a Verzion phone, sounds like a bootloader issue.
Click to expand...
Click to collapse
check this out it might help..
forum.xda-developers.com/showthread.php?t=2449258
mrwetwork said:
Is your phone a Verzion phone, sounds like a bootloader issue.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
check this out it might help..
forum.xda-developers.com/showthread.php?t=2449258
Click to expand...
Click to collapse
its a dual sim phone which is gsm, verizon is cdma
ok thanks,i reflashed it and it worked, plus i flashed stock one so i got warranty back and ota updates also started ^^
So basically, my device was rooted perfectly fine, i then flashed twrp and ever since my galaxy s6 (SM-6920F) only loads the samsung/galaxy s6 logo, which is the first screen, it will stay on there until the phone has died. I can boot into download mode, i have tried numerous way to fix such as the stock firmware, whenever try that i odin it fails, tried lots of methods to solve this but nothing seems to work and i just dont know what to do now
kuky6789 said:
So basically, my device was rooted perfectly fine, i then flashed twrp and ever since my galaxy s6 (SM-6920F) only loads the samsung/galaxy s6 logo, which is the first screen, it will stay on there until the phone has died. I can boot into download mode, i have tried numerous way to fix such as the stock firmware, whenever try that i odin it fails, tried lots of methods to solve this but nothing seems to work and i just dont know what to do now
Click to expand...
Click to collapse
You probably flashed the wrong TWRP.
---------- Post added at 08:27 AM ---------- Previous post was at 08:26 AM ----------
Try booting into recovery
so u can not go in download mode?
asadnow2k said:
so u can not go in download mode?
Click to expand...
Click to collapse
I can get into download mode yes, but not into recovery?
yasteellutch said:
You probably flashed the wrong TWRP.
---------- Post added at 08:27 AM ---------- Previous post was at 08:26 AM ----------
Try booting into recovery
Click to expand...
Click to collapse
Can only boot to download no recovery, if i did use the wrong twrp would retrying with perhaps the correct version fix the problem?
kuky6789 said:
Can only boot to download no recovery, if i did use the wrong twrp would retrying with perhaps the correct version fix the problem?
Click to expand...
Click to collapse
It's possible. If you can get into recovery then you can install a custom ROM then your boot problem is solved
yasteellutch said:
It's possible. If you can get into recovery then you can install a custom ROM then your boot problem is solved
Click to expand...
Click to collapse
Finally I went onto the twrp page got the new and correct version for my phone then as the flash was finished managed to power in to recovery, kept all my data, thankyou
kuky6789 said:
I can get into download mode yes, but not into recovery?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24459283995310257
flash with this firmware and post results.
kuky6789 said:
Finally I went onto the twrp page got the new and correct version for my phone then as the flash was finished managed to power in to recovery, kept all my data, thankyou
Click to expand...
Click to collapse
Np
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
yasteellutch said:
Np
Click to expand...
Click to collapse
Be careful next time
To be completely honest I realy don't have a clue what I was doing lol but anyhow It boots up with red letters up top saying custom binary blocked by frp lock what's can i do to fix it I'm new to all this thanks in advance
What you have done is after changing your recovery you have gone to developer options and unticked OEM unlocking after that you have rebooted. To fix this flash lollipop/marshmallow pda file through odin.
Prashanthc said:
What you have done is after changing your recovery you have gone to developer options and unticked OEM unlocking after that you have rebooted. To fix this flash lollipop/marshmallow pda file through odin.
Click to expand...
Click to collapse
Okay thanks I'll give it a try hope I can fix it is just learned about rooting so I'm in the learning proses
I think I bricked my phone.
Same thing happened to me. My little daughter unticked OEM unlock i didn't know. Now phone is not booting. Flashing MM firmware by odin fails. Smart switch says unsupported mobile. Any help will be helpful.
This work to me, in my galaxy sm-j710mn , only follow the steps and flash the recovery
I unbricked mine when i did that by reflashing back to stock firmware. Just have to leave the oem unlock tab alone after your done rooting or have twrp.
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
bichitrax said:
Same thing happened to me. My little daughter unticked OEM unlock i didn't know. Now phone is not booting. Flashing MM firmware by odin fails. Smart switch says unsupported mobile. Any help will be helpful.
Click to expand...
Click to collapse
Try flashing with a different version of odin. If nothing happens try a different computer or reinstalled samsung drivers and restart.
Davidargentina said:
This work to me, in my galaxy sm-j710mn , only follow the steps and flash the recovery
Click to expand...
Click to collapse
Thaks friend..anyway I managed to get rid by flashing the latest firmware through odin.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
[/COLOR]
Try flashing with a different version of odin. If nothing happens try a different computer or reinstalled samsung drivers and restart.[/QUOTE]
Thanks for help..BTW I managed to boot by flashing only latest firmware.
Use smart switch emergency software recovery in download mode. See if it helps.
rajnikant574 said:
Use smart switch emergency software recovery in download mode. See if it helps.
Click to expand...
Click to collapse
I was able to boot after flashing the latest firmware.
BTW smart switch could not recognise my device at that time.