Ok,,,,here is my plight...
about 6 months ago my s5 became unusable due to the fact that concrete and GS5's dont play well together...becoming more and more frustrated having to use an older phone (HTC ONE M7) i went ahead and threw caution to the wind and bought a new LCD digitizer for my GS5 and hoped for the best...
replaced my digitizer and VIOLA !! my phone booted and was exactly the same as it was the day before concrete and LCD collided..
after booting it up went in to check everything and all seems well....root was still good,,,just had to upgrade everything and move on..
my problem is that since it has been a while there have been so many changes as far as updates,,ROMs,,and other techniques i need to find out the steps to take and what would be my best plan of attack..
i am on MOAR v2.2 NE5 and when i installed that back when i first got the phone tripped KNOX,,but i dont think that is too much of a concern at this point...or is it ??
i have read alot of things about going to Lollipop but am not sure if i need to do anything except find a Firmware and flash it with Kies or if ODIN is a better way to go....it would be great if i were able to just jump right to MM but i know the chances of that happening are <0....
any help would be appreciated
thank you in advance
Well the latest version for this phone currently is Marshmallow, and there is a great mm n5 rom that is still a work in progress, but i reccomend downloading the full marshmallow restore tar file and using odin to update, then flash recovery, and then a rom of your choosing (currently the n5 rom or a version of cm13). But to flash a lollipop rom download the OK4 lollipop restore file (last version of lollipop 5.0) and do the same process.
hadn't heard much so i went ahead and downloaded an OK4 firmware and flashed with ODIN....works flawlessly setting up now
surprisingly enough,,,it kept all of my settings from MOAR.....hafta say that i am shocked.....gotta love Android
Related
I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build
am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/
ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...
SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.
Very Informative
i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse
Device was given to me as Marshmallow
SM-N915T
I am assisting a friend by rooting his samsung galaxy note edge. Problem is that when I placed the Hyperdrive rom onto the device I noticed wifi did not work. This was done with CWM
After fiddling around I went ahead and wiped the device and gave it back to him stock rooted. I explained the issue and he was content,
He is now back and refuses to not have this phone modded. I went ahead and rolled the device back to cok7 LOLLIPOP. I also installed an old TWRP version that stated it worked for this device.
I flashed the tekhd rom and noticed it had the same wifi greyed out problem. I then tried hyperdrive on cok7. Same thing.
So, I am thinking that it is the modem. Where and how can I fix the modem to be 5.1.1.?
I found this link http://forum.gsmhosting.com/vbb/f922/n915t-new-security-unlocking-not-done-solved-2026703/
with this http://d-h.st/mgXt
but it looks like dev-host is ALL BS as its impossible to download anything
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
i don't really know how to help you but I have the same same s5 as your and running mookee 7.1.1 and my cell service still works i dont know if its a problem with the latest update and i have not updated to pl1....so maybe that may give a hint.
bdawwgg said:
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
Click to expand...
Click to collapse
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
travioso said:
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
Click to expand...
Click to collapse
Interesting... I may have to set aside some time to do that. What stock version did you flash? Since I'm on PL1 firmware would you think that make a difference as to what stock youre going to?
I'll have to do some more research as to how I should go about flashing stock then unlocking the BL again. Not sure if I can because of my updated bootloader..
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Clayton993 said:
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Click to expand...
Click to collapse
Thanks!!! I'll Slowly start doing this after I post this. Hope to have a good outcome.
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Clayton993 said:
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Click to expand...
Click to collapse
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
bdawwgg said:
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
Click to expand...
Click to collapse
I've already ran a few different roms but haven't really found one I liked enough to stick with. I used Phoenix v15 for a few months then switched to the new 7.1 resurrection remix nougat ROM a few weeks ago. I'll probably go back to nougat unless I start having service issues again. Good luck
I'm still not getting either or one of the two data and cell service. SMS/MMS wont work. Still dont know what is wrong exactly. PF4 updated BL
Not sure if i need to flash a radio or something in odin to get service to work....
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Devansh_Droidgeek! said:
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Click to expand...
Click to collapse
OEM unlocked???
cooltt said:
OEM unlocked???
Click to expand...
Click to collapse
through developer settings? yes
Devansh_Droidgeek! said:
through developer settings? yes
Click to expand...
Click to collapse
follow this guide here