Related
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Matt.graham said:
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Click to expand...
Click to collapse
You could try to go back to stock and check if everything still works there.
Did you flash the correct modem/baseband for the ROM / your carrier? There is a thread in general for all the modems. Chances are with a KitKat ROM you need to update your modem. Read that thread and give it a go. The file is about 15mb and takes a minute to flash in Odin. Failing that go back to stock.
Nothing in status bar: that's what it looks like in stock, you can use 2 fingers for the quick settins. Installl WANAM XPOSED fromwork for more tweaks and options!!
Home button double tap: that's the way it works on the google edition, that's just it. BUT wanam xposed can change this with the Gravity Box module!! You could try the Echoe 2.2 kitkat rom it has xposed pre-installed.
Keep in mind things look blanker and less functional as you no longer have samsung touchwiz which adds a LOT of stuff to the stock experience!
One more thing: ALWAYS make a nandroid backup before flashing ANYTHING at all, you never know when you will need it. Backup the nandroid to your PC also just in case, things go missing/ get deleted! T
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Hey folks.
My samsung galaxy s4 i9505 with android 4.4.2 and i have rooted it few times and got back to stock.
The problems i am facing are
1. i lock the screen and then tryna turn back on but it never turns back on i have to continuously press the home screen in order to activate samsung s voice which in turn helps me to switch on the screen back. It takes almost a min or so to turn back on.
2.Its geting tooooooooooo slow omg i never expected this to happen.
3.The camera app sucks to the core the "processing" takes almost few seconds to take a pick.
Please help me how do i get rid of these.
I dont know if i can switch the rom to pure android lollipop if thats possible please do guide me to how can i do that.
or please guide me some rom which is prety fast and almost close to pure android which has all the apps installed which are required.
Try a factory reset first.
Lennyz1988 said:
Try a factory reset first.
Click to expand...
Click to collapse
I know that would temporarily fix my problem but i want that to be fixed permanently brother.
What makes you think its a temporary fix?
DSA said:
What makes you think its a temporary fix?
Click to expand...
Click to collapse
I have tried it sir.
Then you are doing something wrong
Setting the phone to the condition you bought it in is not a temporary fix
Did you make modification when you were rooted? That could explain why a factory reset doesn't work. If so, flash a 4.4.2 stock rom.
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
MikeDacre said:
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
Click to expand...
Click to collapse
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
ROMANTiC KiD said:
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
MikeDacre said:
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
Click to expand...
Click to collapse
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
ROMANTiC KiD said:
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the confirmation. I did exactly that and I can confirm that it did indeed work.
Thanks so much for the help.
Hi all,
Sorry to resurrect an old thread, but I am having this issue and the stock firmware flash isn't solving the issue. It is all very odd because it doesn't actually retain any kind of lock after flashing. I'm following instruction on here, but after locking gps on stock, then going to CM I cannot get a fix. It either had a massive radius on Maps, or it just locks to my home or work location.
Since trying much more I have managed to get the occasional satellite lock via GPS Locker, but even then as soon as I move from either my house or work, it can't find anything to lock onto and just defaults to a static location.
Is there anything you would recommend? I have 2 Samsung GS4's and they both exhibit the same problem. I have also tried this on an S4 Mini, but that retained lock just fine. I'm really confused as to what to actually try. If you could recommend anything I'd be very grateful.
Again, I'm sorry to res an old thread, but no one has been replying to the one I started for this issue :/
Your problem may be that there is some new issue with the newer firmware. I had success by first flashing the *old* firmware (you can download it from my dropbox here: https://www.dropbox.com/s/o3f3ynyezyy4yw9/L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5?dl=0) and then upgrading to the second to last firmware update for the GS4: which gives you Android 5 but without fixing the MMS bug.
After that I flash TWRP with Odin, and then do a full erase in TWRP followed by flashing the latest CM. That series of steps works for me every time, although I found that large changes to my physical location (e.g. flying to England from California) cause it to break again. I actually had to sit in a cafe in an English airport with my laptop out flashing my phone back to stock just so that I could use Google maps to get to my mother's house. It was pretty ridiculous. Because of that and other issues, I now just use stock. I hate it, but I do it anyway. Good luck.
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.