I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.
malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.
Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha
I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk
This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.
Good one... Hackberrybold
Related
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
EDIT:
Here's the deal; my main problem was with Wifi not working. The Stock MF9 Kernel was not working, but the 4.2.2 TW Kernel found here finally did.
did you try this?
leaderbuilder said:
did you try this?
Click to expand...
Click to collapse
Yes. Nothing changed when I did that. I suppose that I should call out that I am currently on MF9.
dante042 said:
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
Click to expand...
Click to collapse
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
I have read that the WiFi issue may be a Kernel issue.. Did you try a different TouchWiz kernel and see if it worked out?
Sent from my SPH-L720 using XDA Premium 4 mobile app
lmayes69 said:
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
Click to expand...
Click to collapse
This is actually what I was trying to do, sadly. Titanium was backing up my info to the phone storage rather than the SD card, and I had to do a data wipe to get to MJA, so I lost them. I figured I could restore to my MF9 backup to redo them, and that's when the trouble started.
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
rosa styhome
dante042 said:
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
Click to expand...
Click to collapse
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Scott02 said:
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Click to expand...
Click to collapse
Scott, check my first post. I edited it with a link to the page with the kernel I used. Make sure that you choose the correct kernel for your Android version. The MF9 and MJA designators have nothing to do with which kernel you need, so make sure to check in your "aboout phone" section to find out what android version you're running. Using the 4.3 kernel on 4.2.2 will cause a bootloop, which is easily fixed by flashing the correct kernel.
Hello every one ...I got new problem in my new phone s4 i9500 ..suddenly loss vibrat touch during using the phone in custom rom ...I flash sokp at first custom rom and got that issue then flash hassan rom based on stock at first flash the issue present but flash it again and then work after that flashed aicp rom and after some days today the vibrat gone even in recovery mode ...what can be the problem ? My phone still new 1month ago ..can it be from kernal philiz ?? Thanks for any suggestion
any suggestion or throw my phone from window ......software or hardware problem ?????
Hi Ammar,
I think your problem is in software. If I were you, I install cwm or twrp recovery, do all wipes including system, preload and internal memory, then flash the latest official firmware with Odin. If problem stands still, I do all wipes agaün and install the latest official firmware again. Even if this is does not work then I decide the problem is hardware based.
abdullahmk said:
Hi Ammar,
I think your problem is in software. If I were you, I install cwm or twrp recovery, do all wipes including system, preload and internal memory, then flash the latest official firmware with Odin. If problem stands still, I do all wipes agaün and install the latest official firmware again. Even if this is does not work then I decide the problem is hardware based.
Click to expand...
Click to collapse
thanks for reply my friend ...i will try by odin and see
Software problem mate.
Try coming back to the stock rom and revert.
It should work on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Software problem mate.
Try coming back to the stock rom and revert.
It should work on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
thanks ..i will try surly but what can be the problem from cm based custom roms or from apks if you know about that
ammarsg said:
thanks ..i will try surly but what can be the problem from cm based custom roms or from apks if you know about that
Click to expand...
Click to collapse
Well I cant comment on what went wrong.
I was on slim rom once and my vibration Intensity was tooo too low. Because of that was missing calls.
Or you can download an app for checking vibration. Once my proximity sensor and speaker stopped working, i ran a test and everything was back to normal.
Try test you android from the playstore and see if that test works.
Well here is the app
But again as I said, let us know if this is happening on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
Once my Wi-Fi stopped working on a Cyanogenmod based rom. I flased stock firmware many times but it didn't work. Then I installed cwm recovery and do all wipes then it worked. As you understand, such wierd things might happen sometimes that we couldn't understand.
i sent my phone to company and told me that vibrate engine is broken and they change it and now work good but what is the problem that caused this i dont know exactly ...as they said either by drop the phone or by water but non of these happend with my new phone
thanks guys for help
ammarsg said:
i sent my phone to company and told me that vibrate engine is broken and they change it and now work good but what is the problem that caused this i dont know exactly ...as they said either by drop the phone or by water but non of these happend with my new phone
thanks guys for help
Click to expand...
Click to collapse
We are human being and as you know human is not perfect. So anything produced by human is not perfect naturally. If you could't find a reason for fault of a device then this is the only and certain reason :laugh::good:
I have Verizon Galaxy Note 3, and my problem is that Wifi button is greyed out and simply wouldnt turn on.
I have done a lot of homework so far, and before, I had 4.3 Jelly Bean, and Wifi being greyed out started around 2 weeks ago (early Dec/2014 - until then, it worked fine).
So I updated to 4.4.2 Kitkat thinking software issue, but wifi is still not working.
I had already searched for hours, and did many things to try to isolate the problem.
*I tried Safe mode
*Reset Cache/Factory several times
*Battery in-n-out, SD card in-n-out, any external peripherals i had alrdy taken everything off and tried
*Tried Alliance/Jasmine/Eclipse ROMs, but still same
*Not router issue @ home since Phone Wifi simply wouldn' turn on
I thought of downgrading back to 4.3 Jelly Bean, but there were many articles saying I can not downgrade, so I think it's out of option.
I now think it's hardware issue, but can not confirm... went to Verizon store too, and the guy just feels it's more software by 51/49, but the ultimate problem is that I just can not 100% ID what the exact problem is - software or hardware.
I really don't want to spend $ for another phone... I also feel it is Kitkat since I also found many articles with Note 3 Kitkat wifi problem, and I read a lot of them, but couldn't really find any solution to my specific issue.
My understanding is that I have 2 options - wait for proper fix by Dev/Samsung for Kitkat firmware or get a new phone
I really did everything I can within my power, and making this post is my last resort...
Hope I can shed some light from experts or anyone who knows any more beneficial details so that @ least i can try to sort my options and situation more clearly...
Thanks much in advance!
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Or flash nc4 in odin.
KennyG123 said:
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Click to expand...
Click to collapse
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
ok, i did already check out your thread before, and when i had tried to download 4.3 (1st one), it had me download like .exe file, and these kind of files tend to be virus/spyware so i just didn't... i also read many posts about how i can NOT downgrade to 4.3 from 4.4 so software wise, my current understanding is that I am **** out of luck until someone fixes firmware... or am i wrong? I guess I am trying to be proven wrong, and hope someone can show me a solution to my weird unique problem...
Btw, already on NC4 (I had updated to NC2 firstly, and Jasmine got stuck on bootloop, so I got NC4 and used Odin, then it fixed the bootloop)
Merry Xmas, huh?
P.S. Thanks for replying on Xmas day, lol
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
drewcam888 said:
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Click to expand...
Click to collapse
Yes, running nc4 right now
KennyG123 said:
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
Click to expand...
Click to collapse
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
You have lots of things wrong in the above. So to keep it simple just get OFF of the alliance ROM, get back on the NC4 ROM and modem. If nothing else...go back to the Verizon store and have them totally wipe and reflash the phone. You can also do that at the Samsung section of a Best Buy store.
Sent from my Note 3 via Tapatalk
KennyG123 said:
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
Click to expand...
Click to collapse
baseband ends in nc4 and base version also nc4...
drewcam888 said:
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Click to expand...
Click to collapse
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Gl2u81 said:
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Click to expand...
Click to collapse
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
KennyG123 said:
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
Click to expand...
Click to collapse
yeah... wifi doesnt turn on... i'll settle as hardware issue, not software and move on with my life...
Warranty replace it and be done.
Hi guys,
Just rooted my S8 and installed TWRP, using STOCK Samsung ROM, AQH3. I noticed in the Camera that "Selective Focus" is not working anymore. I didn't change anything else, just rooted the device and installed Notorious Kernel, before doing this the Selective Focus was working OK. So does anyone know what happened? Any help would be highly appreciated, I really like this shooting mode. Thank you!
EDIT: To clarify: before this I got sometimes the error, but mostly of the time it worked well. Now after rooting the phone and installing TWRP it doesn't work at all in any conditions, even with different subjects.. I've heard someone reporting this issue in another thread, but I can't remember at all
Root these days is nothing but problems.
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Flash stock firmware through Odin and then check again if this solve the issue.
Also which method of root? Magisk or SuperSu?
I used Magisk. Anyway if I'll flash stock firmware through Odin I'll lose TWRP and root and everything else right?
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Seems like kernel related issue
Mmmh so you suggest to try changing kernel and/or flashing the stock one to see if the issue persists?
Hi guys
I have a spare phone now my son upgraded, the S5 SM-G901F. I thought it wound be fun to install another software, possibly more up to date. So I first set out to root it but I haven't played around much with this sort of thing for long while.
I googled and found it seemed to be Odin to use so I downloaded 3.10. Also downloaded cf root. I went into download mode and when I plugged it in, the light in Odin lit up showing successfully connected. When I added the cf file and clicked start it went through some steps but stuck at Recovery. Img and wouldn't progress further.
I tried multiple times, tried a different cable and USB port and also Odin 3.07 and a different cf file even though I think it was the same one but from a different site. All no better.
Originally I bought it a few years back, used from a colleague. I think it was a carrier phone, EE iirc, and I had to get a code to unlock the SIM to use with mine. Maybe that also means it's software is locked?
Any help much appreciated
Thanks, marc
No one guys?
Please help
Marc
Please help
marc.knuckle said:
Please help
Click to expand...
Click to collapse
well to be honest, i would need to spend some time, "Googling" your model .... . I believe , your S5 is a Dev phone, meaning, it was not set up for any carrier, just for running demo's and such. IF this is true, I have no true answer for you.
Odin yes, you need that, that is true! (Believe 3.07, 3.09 and 3.10 work the best for these phones. Had tried a very newer version, several month back, and it did not do the job.. something like 3.14 or 16)
I recommend going to Sam Mobile, and run your model # through them. They will give you all the info about your model and possibly the latest firmware for it.
Sorry that I can not give you all that you are needing. I just don't know a ton about those S5 Plus models. (( I had to even look 'em up too) the plus has a slight better chip was well as graphics, but again, I dont know of any that actually work on a modern carrier like sprint, Verizon, T-Mobile , etc.)
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
marc.knuckle said:
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
Click to expand...
Click to collapse
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
marc.knuckle said:
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
Click to expand...
Click to collapse
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate
It's stock recovery at the minute
marc.knuckle said:
Cheers mate
It's stock recovery at the minute
Click to expand...
Click to collapse
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
marc.knuckle said:
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
Click to expand...
Click to collapse
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Thanks mate