Related
Will putting Magisk on My ZTE A2017G with unofficial Lineage 14.1 get passed Safety net and allow me to use apps like Android Pay?
Sent from my ZTE A2017U using Tapatalk
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
P650SE said:
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
Click to expand...
Click to collapse
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Supersilver-Haze said:
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Click to expand...
Click to collapse
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGApps, followed by Magisk 14.0 and anything else you'd like to install before rebooting.
P650SE said:
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGapps, followed by Magisk.
Click to expand...
Click to collapse
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Supersilver-Haze said:
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Click to expand...
Click to collapse
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
P650SE said:
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
Click to expand...
Click to collapse
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Supersilver-Haze said:
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Click to expand...
Click to collapse
Haha, that's quite alright. Feel free to let me know should you have any further problems with the Axon 7. I'm a new owner but have a lot of experience with previous Android devices such as the LG G4 and OnePlus One.
P650SE said:
Haha, that's quite alright. Feel free to let me know should you have any further problems.
Click to expand...
Click to collapse
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Edit: disregard the I figured it out I had it permanently on LTE so I wasn't able to make or receive calls on LTE it seems
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Hmm, i'm not sure about that one because I didn't use the phone for making calls when I was running LineageOS on my Axon 7. If you installed the Android N modem before flashing the ROM it should work fine in theory. Maybe you can find someone else in the LineageOS thread who's having the same issue.
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
FuzzyDunlop9 said:
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
Click to expand...
Click to collapse
I also had problems getting Viper4Android to work on this device. For me it would install fine, but the audio effects made no difference in apps like Spotify and YouTube, despite having the deep-buffer fix enabled. Try using this version by ahrion instead, it works for me! (Just make sure you remove anything relating to previous installations of V4A beforehand!)
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I don't know how much difference it would make, but installing the Official build of LineageOS is probably slightly better. The method of switching from Unofficial to Official is basically the same as what I posted previously in your other discussion thread:
1. Make sure your apps and files from Unofficial LOS are backed-up.
2. Download the Official LOS ROM and copy it to either the internal or expandable SD card storage on the Axon 7.
3. Download the latest GApps arm64 ZIP for Android 7.1 from OpenGapps and copy it to either the internal or expandable SD card storage on the Axon 7.
4. Reboot the phone into TWRP custom recovery.
5. Enter the 'Wipe' menu and wipe the partitions /data, /system, /dalvik and /cache. (It might not be 100% necessary to wipe /data since you're just switching to an official build of the same ROM, but it is still advisable. You could try installing the ROM without wiping /data, but you may encounter some issues!)
6. Switch the the 'Install' menu and flash Official LOS, followed by the OpenGApps ZIP.
7. Reboot the device.
Like I have mentioned to the others in the J3 Emerge community, I had this done just didn't have the opportunity to upload it until today. This is a Deknoxed and Deodexed base for custom ROMs for users who are currently on the QI2 stock firmware. And since I did nothing but remove the odexes(including the one on the boot img iirc which is why it comes up with the typical custom kernel message on bootup) and removed Knox, I'm not posting this as a DevDB thread as Samsung did all the heavy lifting so to speak.
[url]https://androidfilehost.com/?fid=745849072291691412[/URL]
And yes, this can be flashed as is but as always, you do so at your own risk. I will not replace your device and neither will Boost Mobile nor Samsung in the event of data loss, corruption, theft, fire, pod people, etc.
Please do not mirror this zip without express permission from me.
I believe this COULD be used on VMUS and SPRINT as well, but because I do not have the Emerge from those carriers. Also, from what I see it can only be rooted using SuperSU in Systemless mode or Magisk.
How can i get wifi working after flashing this?
evilgold said:
How can i get wifi working after flashing this?
Click to expand...
Click to collapse
If you're not on QI2 when you flash this, it won't work. No idea how to fix it unless you use the QI2 ODIN package to "upgrade" which is found on AFH under the user the_yankee, iirc. Not at pc so can't verify this. Have stuff to do rn so can't get on one.
SammaelAkuma said:
If you're not on QI2 when you flash this, it won't work. No idea how to fix it unless you use the QI2 ODIN package to "upgrade" which is found on AFH under the user the_yankee, iirc. Not at pc so can't verify this. Have stuff to do rn so can't get on one.
Click to expand...
Click to collapse
Thanks! that's exactly what i was missing, I guess i was using a different version before, flashing the QI2 first did the trick.
I think I will put together a set of zips that can be used to get any of the three we are all on,working on the various versions. All a user will need to do is pick their carrier and flash it in TWRP after first boot that way the system writes the csc directory. I will post you all a link when I get them built. They are sorely needed and long over due.
SammaelAkuma said:
I believe this COULD be used on VMUS and SPRINT as well, but because I do not have the Emerge from those carriers. Also, from what I see it can only be rooted using SuperSU in Systemless mode or Magisk.
Click to expand...
Click to collapse
help how to flash this zip??
help me understand please
please help me. i used the A|1 sprint Rom and soft bricked my phone and stuck in complete boot loop. it goes as far as recovery screen in TWRP and reboots. i have tried to download official Rom from your links through google drive but for whatever reason they wont download.
please help me i just need an official J327P ROM. Odin keeps getting stuck on "setup Connection"
worked for my sm-j320p boost thank you
bro, what part of the Q 12 stock did you flash in odin? im guessing the bootloader but it keeps failing on me and i'm just a bit confused on the stock Q12 i downloaded i got 5 slots last 2
look like sprint packages to me so hopefully someone can clue me in on which slots are needed to so my wifi will work please! thanks in advance
evilgold said:
Thanks! that's exactly what i was missing, I guess i was using a different version before, flashing the QI2 first did the trick.
Click to expand...
Click to collapse
is it possible to uninstall this rom?
I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194
I have searched XDA and Google and cannot find the answer to my question below regarding my S5 G900V (KLTE).
I would like to restore an EFS partition made on TWRP 3.0.0 to see whether it helps my Unknown Carrier issue on custom ROMS (stock is fine). However, on TWRP 3.2.3 the EFS partition(s) don't show up and instead show the error "Unable to locate partition by backup name: 'efs1' / 'efs2' / 'efs3'." If I go back to TWRP 3.0.0 , these EFS partitions show up, but I don't know if it is safe to flash these considering the error on the new version and reports via Google of EFS/IMEI corruption relating to TWRP 3.0.2-1.
So please advise if you think it is safe to flash these older EFS partitions on TWRP 3.0.0 made on the same old version. The goal is to avoid IMEI corruption and fix my issue with Unknown Carrier on custom ROMS by using the oldest EFS backup I have from 2016.
Thank you!
Anyone? Thanks!
drewcu said:
Anyone? Thanks!
Click to expand...
Click to collapse
I've never done this before on my klte device but, you may be able to locate or obtain some member guidance within the following thread.
https://forum.xda-developers.com/showthread.php?t=2737448
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
drewcu said:
Anyone? Thanks!
Click to expand...
Click to collapse
IMHO, your EFS Partition is fine, you only have to update your bootloader and modem to the latest version available for your variant.
zlazaar said:
IMHO, your EFS Partition is fine, you only have to update your bootloader and modem to the latest version available for your variant.
Click to expand...
Click to collapse
Thanks. I've got the latest modem QL1 from https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630. And I've experimented with older versions also.
Also I'm on the unlocked bootloader QB2 from the unlocking procedure most people use https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529. I've also tried QC2 from jrkruse's S5 file collection and neither one changes things in terms of my custom ROM woes. Like I said, stock is fine. No one else seems to have the same issues I have with delayed texts stemming from the unknown carrier on custom Lineage or AOSP 7/8.x ROMS I've tried.
I can point to 2 possible causes for this:
1) My IMEI is 15 characters on stock but is missing the last number 0 on Lineage. I added it back using an IMEI Xposed module on Lineage and that didn't change matters.
2) On stock Verizon TW, I rooted and installed Xposed. I have an Xposed module called Firefds Kit which has a number of TW tweaks, but it comes with a catch. If I even run the app (not just apply additional changes), I no longer receive texts or calls. If I then flash the system ROM via TWRP, the tweaks stay applied but I again get texts/calls. No idea what Firefds screwed up on my phone, but at least I can keep the important tweaks and get calls/texts. Not sure if this somehow is affecting my texting on custom ROMs too. No issues with making/receiving calls or sending texts on Lineage -- it's just receiving texts. Sometimes they come in normally, and other times they're 10-15 minutes delayed. Have tried everything I can think of https://forum.xda-developers.com/galaxy-s5/help/delayed-texts-unknown-carrier-custom-t3838392. That's why I want to restore an older EFS, thinking that it will be before the Xposed module did anything to the system.
Thank you!
drewcu said:
Thanks. I've got the latest modem QL1 from https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630. And I've experimented with older versions also.
Also I'm on the unlocked bootloader QB2 from the unlocking procedure most people use https://forum.xda-developers.com/ve...testers-required-easier-root-method-t3561529. I've also tried QC2 from jrkruse's S5 file collection and neither one changes things in terms of my custom ROM woes. Like I said, stock is fine. No one else seems to have the same issues I have with delayed texts stemming from the unknown carrier on custom Lineage or AOSP 7/8.x ROMS I've tried.
I can point to 2 possible causes for this:
1) My IMEI is 15 characters on stock but is missing the last number 0 on Lineage. I added it back using an IMEI Xposed module on Lineage and that didn't change matters.
2) On stock Verizon TW, I rooted and installed Xposed. I have an Xposed module called Firefds Kit which has a number of TW tweaks, but it comes with a catch. If I even run the app (not just apply additional changes), I no longer receive texts or calls. If I then flash the system ROM via TWRP, the tweaks stay applied but I again get texts/calls. No idea what Firefds screwed up on my phone, but at least I can keep the important tweaks and get calls/texts. Not sure if this somehow is affecting my texting on custom ROMs too. No issues with receiving calls or sending texts on Lineage -- it's just receiving them. Sometimes they come in normally, and other times its 10-15 minutes delayed. Have tried everything I can think of https://forum.xda-developers.com/galaxy-s5/help/delayed-texts-unknown-carrier-custom-t3838392.
Thank you!
Click to expand...
Click to collapse
I'm really sorry, can't help you as vzw devices are a pain in the a**
Mine is G900T and i don't have any problem with recent custom roms.
You can, maybe, find a solution in the Verizon forum.
Sorry once more.
drewcu said:
Thanks. I've got the latest modem QL1 from.........
Click to expand...
Click to collapse
Just a thought...
Did you try downgrading to TWRP v3.0.0-0, Restore the EFS and then upgrade TWRP to the latest one again?
I can only assume that it may work but, it's something that I, personally, would try if necessary.
Just a Suggestion...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Ibuprophen said:
Just a thought...
Did you try downgrading to TWRP v3.0.0-0, Restore the EFS and then upgrade TWRP to the latest one again?
I can only assume that it may work but, it's something that I, personally, would try if necessary.
Just a Suggestion...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks - yeah I did mention in my OP that I contemplated doing this, just was gun-shy given the risks. Today, I finally decided to just go for it and restore my old TWRP backup via 3.0.0. No issues restoring both the EFS and modem from a couple years ago. The stock VZW TW ROM QL1 worked just fine after this, however, I was surprised the Baseband was still showing QL1 rather than PF4 which was the old version of the modem. Hence, I am not 100% sure the restoration was complete for both the EFS and modem despite the output from TWRP 3.0.0.
Sadly, I went back to Lineage and the delayed text and unknown carrier issue persists despite my EFS supposed restoration. But I'm glad I tried at least and am no worse off and am again back on stock.
Thanks!
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