Hello, so I downloaded my phones stock firmware (G9006v) and it had a lot of chinese bloatware and after some time it started saying "unfortunately google play services has stopped working" and after some time nothing from google works, even google play doesn't open up. I rooted my phone using CF auto root and then I wanted to install TWRP to install custom ROM, but then I learned that I need to enable OEM or bootloader, but when I go to developer settings there's no OEM unlocker or something like that, I watched a lot of videos, but couldn't figure it out. I saw that I can use ADB, but that's very complicated (for me). Isn't there a bit easier way to unlock bootloader? And by the way, when I go to recovery mode there's a line that says: reboot to bootloader, when I press on it, it just takes my to download mode (maybe it should do that, I don't know). I really need Your help, cause I want my phone back. Thank You
1. if not OEM-unlock, bootloader is unlocked (which is, for ALL S5 models except North American Verizon, T-Mobile AT&T, etc.)
2. flash a recovery in download-mode with Odin.
Related
Hello!
I've recently got into a big problem while doing stuff I don't know much about (and probably in the wrong way, because of that...). So, let's get to the problem, shall we?!
Well, I wanted to root my Moto G4 Plus (XT1640) but I had never done anything like it, so my phone was basically the way it came out of the factory. Before all of this, my phone was using Nougat 7.0.1 (I do OTA updates). I installed TWRP and followed the steps (even some from this forum). However, at that point my phone was boot-looping in the screen "Your bootloader has been unlocked, your device can't be trusted. Your phone will boot in 5 seconds.". Despite the warning, my phone didn't boot. After a while, screen got black and the only way I could use the phone was while in the bootloader. Then, I've made wipes through the Recovery, hopeful that it'd help, but it didn't. Finally, I surrendered and went looking for an original stock ROM I could flash and maybe get things working again. Found SOME ROM that's probably the right one ("XT1640_ATHENE-RETBR_MPJ24.139-50_cid50_subsidy-DEFAULT_CFC.xml.zip") (I'm from Brazil, btw). Great, downloaded, followed steps in the forum to flash it, great, it boots again! Can login to Google, default settings stuff, etc... HOWEVER.
Then, with my phone working again, I wanted to get rid of the nasty boot screen that said my device can't be trusted, etc. So I looked it up and tried to reflash the same stock ROM as above, but now doing it so I could re-lock the bootloader. To do that, I repeated the flashing commands but added the command "mfastboot oem lock" at the end (also used "mfastboot oem lock begin" as the 1st command). Then the CMD said I had to retype the command to apply. Did that, but then the following message showed: "Waiting for signed boot.img, enter the command again" or something like that (didn't printscreen, sorry). Then I reentered the command a 3rd time and then it said "Please flash a signed ROM" or something. So, basically, it failed. After that, repeating the command just showed the last message again. Unhappy, but hopeful, I entered "mfastboot reboot" to reboot my phone. So, got back into the phone (still with the nasty "Your bootloader has been unlocked" warning) and then I basically gave up. I'm now trying to install an OTA update (for Nougat, since the ROM I installed is 6.0.1) but the WiFi download is REALLY slow (and the problem is not my internet, since I've tried downloading a couple of files in my PC to test it).
So my biggest fear is that I have a ROM that's not REALLY meant for my phone (despite looking EVERYWHERE for it) and that's causing problems with the WiFi. Maybe the OTA update is just slow in the server-side, but I'd like to know. Is there a way to get the ROM I got when I bought the phone (that EXACT SAME ONE)?! I wonder if there's a problem because of Motorola/Lenovo regional things. Otherwise, the phone works (gets 4G signal, making calls and downloading Play store updates is as far as I've tested for now). And I would also like to know if there's a way to relock the bootloader in my case(since when I tried those errors I've mentioned above happened)? What I seemed to have done is downgrade a version (since I was in Nougat and then installed a stock ROM that's 6.0.1) and I don't know where to go from here. Thanks a lot, guys! Sorry for the long post, I just wanted to describe the events in order.
There is no official source for you to get a rom. This is not a nexus. I wonder why people always want to relock bootloaders! (it seems in your case only for the 5 seconds warning). As far as i know only modem can differ but roms...
Do you still have TWRP?
if so: if you are on an N modem right now try to flash an N custom rom. If you are on an M modem flash an M custom rom.
KEEP YOU BOOTLOADER UNLOCKED and also:KEEP "OEM UNLOCKING" in developers options ENABLED AT ALL TIMES! (the last step will prevent you from a 72 hours lockout from your Google account.)
There are other ways to get rid of the bootloader warning. (flash a custom logo.bin)
Just wanted to share that I have working Android Pay with my rooted Nexus 6 XT1003.
Phone Info:
Nexus 6 XT1003
Bought it from ebay for $180 (from China)
Android version: Nougat 7.1.2
LineageOS version: 14.1-20180202-Nightly-shamu
Process:
Unlocked bootloader
Fastboot boot'd latest twrp (no install)
Wiped the phone and installed latest LineageOS from their site + gapps package with twrp
Upon first boot, skipped all account setup and first boot setup
Accessed developer settings and enabled "OEM unlocking"
Back to fastboot boot twrp
Flashed SU package provided by LineageOS
Ran Fastboot OEM lock command
Waited what seemed like 20 minutes for the first boot to complete
Setup phone as normal
Opened Android Pay and added my card
Now a few more details.
Before using this at the store, I enabled root for apps in settings for an app "System app remover (ROOT)" Excellent app, get it here: ( https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp )
After this with root still enabled, went to the store and attempted to pay with Android Pay.... "THIS PHONE CAN NO LONGER BE USED FOR PAYMENTS" - That was a huge let down and I was sad.
I thought right off the bat, DUH! Disable root in developer settings..... no dice, same error.... but my bootloader is locked and root is disabled....
I followed the google message and sent feedback in the app and said "My bootloader is locked and root is disabled"
Now I didn't really expect this to work with Google's security with this service.
I went to the store a few days later with root still disabled, after a reboot or two and tested it... IT WORKED!
I wonder why it didn't work the first time? Maybe because I had not restarted my phone after disabling root? Maybe because I cried to Google? (doubt it)
I'm going to re-enable root at some point and test it out again to see if a simple restart after disabling is what fixes this.
Does Android Pay work for you?
My Android Pay works on current Lineage OS, but I never flashed root. I did install TWRP as normal. Otherwise I did the same as you. (Doesn't help you answer your question, though, sorry.)
I have magisk installed and android pay works fine with it.
OEM unlocked too.
los+magisk 15.3+universal-safetynet-fix-v2-beta-5= work fine
Disabling root access in the developer settings and rebooting worked for me.
I just got an SM-G975F/DS ~ seems like the Taiwan version.
My current issues:
Can't disable emergency alerts!!!
Can't clear voicemail notification from tray. Infuriating.
No hosts file override (need this for app development & Adaway)
Samsung bloatware
I don't give a f*ck about Knox or Samsung Pay but I like the stock camera so I have a few questions about the root process.
First it seems like this is the process just to have root in with Stock ROM. Please correct me if I'm wrong.
For randoms reading this: THIS WILL NOT WORK ON USA Snapdragon VERSION
Enable OEM Unlock from developer menu.
Boot into download mode (Plug in PC connected USB cable while holding Bixsby Button + Vol Down)
Unlock bootloader by pressing volume up and confirming (not actually unlocked yet due to Samsung trickery)
Quick setup OS with Internet connectivity knowing it's gonna be wiped again.
At this point Samsung's Vaultkeeper service should detect OEM unlock and finally actually unlock the bootloader.
Install Magisk with this guide.
So it seems like this process would patch just the AP partition with Odin while keeping the ROM and Recovery stock.
So here's the questions.
If I continue to run stock ROM with Magisk with this method any official OTA updates must be done manually or I risk bricking the device?
If I install TWRP and try out some roms and don't like them can I go back to stock?
Is it possible to flash stock rom WITHOUT Magisk after doing all this?
I plan on writing some simple guides on this when I'm done since the current ones are a bit confusing so I would appreciate some clear and concise answers the the above questions.
Thanks all!
Hello, I really messed this up... I haven't rooted a phone in over 5 years, but just ordered a moto g7 from google fi because I wanted to play around with rooting and rooted apps again.
Setup:
-got moto drivers, adb, set developer mode, unlocked bootloader
I had tried to just root using the "simple?" method of using Magisk with the lolinet firmware files. I used the PPO files in the Official/FI dir. I thought that I had seen an error when flashing the magisk modified boot.img that there was an issue or that it wasn't valid, I (stupidly) assumed that this was like the notification you get after unlocking bootloader about invalid key or whatever. When trying to boot up it would just keep boot looping, and I went into hard panic mode... I saw other people had mentioned using retail or retus firmware on the google fi variant, so I proceeded to try to just flash those stock boot.img files after the fi one hadn't worked. I then finally got it to boot up fully, I don't even remember which firmware it was (retail maybe) and felt a little bit better about it, but had also seen that some people had said it wouldn't have the full functionality of network switching if I wasn't using the fi firmware. So... back to the fi firmware...
I was able to get it booting up on stock fi firmware, and to be honest I should have stopped there and given up on root, because I'm guessing I would have been perfectly fine up to that point... I again tried magisk modified fi firmware to no avail, and was having trouble getting back on stock fi for some reason... I followed a post to reset to stock and relock bootloader ***I'm guessing this was my major fault***, I must not have been paying enough attention to the command prompts doing this, but I think this is where I messed something up royally. It was able to boot, but then it said it had updated software to the 'PPOS' variant which I thought was strange... After attempting to reflash stock fi and then magisk fi boot.img it is failing and won't even get to boot loop.... when trying the slew of commands to flash full stock firmware I keep getting issues with the "_a" partition being not found.
At this point I can't get to recovery, or boot after attempting to flash a number of times. Any help would be appreciated, even if it is just a confirmation that I f'd this device and to stop wasting my time and give up on ever having a rooted device again lol.
Thanks for your time, and let me know if there is additional info to provide that may help.
Edit: Current status:
"Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software Repair Assistant."
in Bootloader logs, but I don't know what software repair assistant it is referring to, i have tried connecting to pc.
Edit 2: Or I'm just a complete idiot and needed to re-unlock bootloader with the code like previous... which I totally should have known, but again, I'm an idiot...
So, now that I've got it booting up, do I attempt reflashing a magisk img or just admit I'm too stupid to do this? Or should I go with twrp which seemed like more steps and potentially more issues to run into?
Sorry for the scare and immense stupidity!
Hi everyone, i’m having an extremely weird issue with my Samsung J5 Prime (SM-G570Y/on5xelte). First of all; sorry for bad english, this post will be a bit long.
So i want to unlock OEM, to install custom recovery and custom ROM (and being able to login with google account from gms (Google Play Service app)).
i activate developer options.
Then go to Settings > Developer Options, but OEM Unlock is missing (i did'nt have the screenshot of the settings), i already try every method to reappear it but nothing worked.
Trying my luck, im rebooting my phone to download mode, on there i didn’t see any text that says OEM Unlock, i tried to flash OrangeFox Recovery using ODIN. And suprisingly it worked, i even double-checked it by actually booting to recovery. i did'nt expect it to work though...
Then i install RadicalQuack Custom ROM, and do some root-level customization.
But as soon as i try to login Google account from Google Play Service (this didnt affect web login or any other login) on Stock/Custom ROM, and reboot the phone... my phone was FRP locked, i was shocked because my configuration isn’t even backed up.
I have to flash stock rom in download mode, get to setup, login google, remove the account, then i can get rid of FRP lock.
And at this point is where everything is confusing.
If i use stock rom without any changes, the "OEM Unlock" option is'nt appearing at all.
But if i use custom ROM (in this case i use RadicalQuack), the "OEM Unlock" option Appears (until i remove "ro.frp.pst" in build.prop)
So i can do anything but CANNOT login using Google Account from Google Play Services or get FRP locked and All data destroyed.
Now my question is, is it safe to enable "Unlock OEM"? Because i dont know if OEM Unlock is currently enabled or not, i dont know how to check if the bootloader is actually locked, i dont want to get locked forever on samsung stock and bloated shtt again.
PS:
Somehow... i can login Google account without getting FRP locked by:
Unlocking OEM (on the custom ROM ofcourse, since it won't be visible on stock ROM anyway...)
and removing "ro.frp.pst" (especially "ro.frp.pst=/dev/block/persistent") on /system/build.prop, /system/vendor/build.prop, /vendor/build.prop
what did you do?
Hiii, what did you do? I need to unlock oem un my j5 prime
Same Problem Happens to me But Now How you use custom rom without getting frp lock please Tell I Have Also J5 prime And Same Happens to me also I need to flash stock rom from which my custom rom get erased