Database Users

Bootloader, root, Stock ROM and other issues!

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)

Trying to enable WiFi Calling on my Note 4 N910V

I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!

Modify_inc said:
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Click to expand...
Click to collapse
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.

kevintm78 said:
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
Click to expand...
Click to collapse
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!

Modify_inc said:
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Click to expand...
Click to collapse
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
1. Power down, pull the battery for 3 seconds, then boot into Download Mode
2. Using Odin, flash the BPA1\CPD1 hybrid firmware
3. Once that's done flashing reboot to recovery and factory reset. Then reboot and let that firmware install
4. Once you've gotten past all the setup part you'll want to power off again and boot to download mode again
5. Using Odin, flash the CQI2 aboot and then reboot. From this point on the process is the same as before.
6. Enable developer options, turn on USB debugging and turn on "allow unknown sources" in the security settings.
7. At this point, you'll want to have your spare SD card in and go ahead and open a command window from the same location that you have the samsung_unlock_n4-fix file in. In my case it was in my download folder and the easiest way to do that is to open that window, hold down the shift button, then right click. You should see an option that says "open command window here" then click that to open.
8. Once you open the terminal enter this command: adb devices
9. Then this command: adb push samsung_unlock_n4-fix /data/local/tmp/
10. Then install kingroot and let it start rooting. Be sure to keep the terminal open and your phone connected.
11. Once kingroot starts the rooting process do not let the phone go to sleep. Just keep a finger on the screen.
12. When kingroot gets past 50 -60 percent, enter this command in the terminal: adb shell
13. If you enter adb shell and it gives an error or says your offline, just unplug the Usb from your phone and plug it right back in. Then enter the adb shell command
14. As soon as kingroot says you're rooted, enter this command in the terminal: su (You have to grant root permission on the phone and continue)
15. Then this command: cd /data/local/tmp/
16. Then this command: chmod 777 samsung_unlock_n4-fix
17. Then this command: ./samsung_unlock_n4-fix
18. Once the scripts starts it will ask you if you want to continue, just type out: yes
Then it will do it's thing, back up your bootloader, and then power your phone down when it's done.
19. Once powered down, PULL OUT YOUR SD CARD, and boot back into Download Mode
20. Using Odin, flash Twrp and immediately boot into recovery when Odin reboots your phone.

kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
Click to expand...
Click to collapse
Thanks for all your help, I finally got around to upgrading it. Everything went smooth and I am finally running MM 6.0.1 but unfortunately, I still can't find the feature for Wi-Fi Calling. I do now have a Advanced Calling option under Settings, which I believe you must have to use WiFi Calling, but I can't find the WiFi Calling anywhere to enable it. I must say, I'm really disappointed, yet still proud of myself that I didn't brick my phone in the upgrade process.
So, any suggestions as to why I can't find WiFi Calling on MM 6.0.1?

So no one has any ideas why I would still not have the wifi calling after installing the 6.0.1 MM? Is there a security or other update that I now need to install to get this feature? I installed the Jasmine v6 rom, if that makes any difference. Is there a way I can install 7.0 Nougat on this device, and would it likely provide the wifi calling feature or likely be a waste of time and effort?
I'm using Safelink with my Verizon phone, but they are no help, though they do say they support wifi calling as long as I can enable it on the phone. Is it possible Verizon could tell me what I need even though I don't have service with them but do use their towers?
Sorry for so many questions, I just really need wifi calling and can't understand why I don't have the option for it using 6.0.1.

I found an app named WiFi Calling while browsing through my phone directory. It looks like a system file, so shouldn't that mean the phone should have it? Is my Jasmine ROM keeping it from working or is it likely something else?
I'm now using Jasmine v7, if that makes any difference.

Help! Now my wife has no phone
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
Click to expand...
Click to collapse
I tried to do the same for my wife since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
I made a complete backup using TWRP before attempting this upgrade. So, can I just restore it or are there other steps I need to perform before I attempt to revert back?

Did you ever get this resolved? I have been having an issue since mid-July where my phone does not send or receive texts or calls within half a mile radius of my office but otherwise works great everywhere else. I don't have to be in the building...I can be standing in the parking lot, parked at a nearby building/area, or driving down the street in vicinity of the area and nothing. When I try to send a text, I get a message stating there's no service. When I try to call, the phone goes from 4G with four bars to 4G with zero bars and is stuck on "dialing". When I end the call, it goes back up to four bars.
I have tried contacting Verizon many times and they tell me I need to enable WiFi calling but I don't have the Advanced Calling option in my settings. I am also running 5.1.1 on a rooted SM-N910V. Today when I spoke to them, they told me that even though my phone shows 4G, I really only had 1G service. I find this explanation ridiculous because if this was the case, I would have problems in other areas too and not just in the middle of the 8th largest urbanized area in Louisiana (while elsewhere in the same urbanized area, the phone works great). They told me I needed to do a system update which will cause me to lose root.

Did I just brick my device trying to root?

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!

Stuck on fRomFuture B201 - Help!

Hey guys! Been running fRomFuture build 201 on my VKY-L09 and haven't updated in like one year.
Right now the phone is on the june 2018 security patch and I cannot update. I would like to go back to stock.
I have tried like a dozen methods last night: HWOTA, HURUpdater, HiSuite, FunkyHuawei's unbrick tool etc. I think I am missing something here.
FH's unbrick tool does not go past the "wait 5 minutes" step, it just hangs.
The HWOTA... Well I changed the script a bunch of times for it to work properly but it seems that it flashes TWRP, then boots to it and waits for ADB and hangs. If I interfere with ADB and kill-server and start-server, the daemon cannot start any more. I tried like 3 separate twrp versions because of that and think it might actually be my adb to blame.
Saw a bunch of guys explaining how to do the dload method, but didn't manage to actually try it out.
The secret menu code method just does not see the UPDATE.APP file.
I am lost and desperate.
Can anyone please let me know what I am missing? Am I using the right build? Or is there a specific build I should be flashing to replace this old rom I am stuck on? FirmwareFinder said that most of the ones I tried were approved for install. For instance B185
P.s. the DNS method fails because my router is PPPoE and has the upstream WAN settings all greyed out. The FH Connectify method is utter crap and won't work. Traffic gets routet to a dead end if I change any dns settings.
Also HiSuite says that it can't fix my phonr lmao.
Phone can boot in fromfuture, I can install twrp on it, I just dunno how to get back to stock.

Solved with HWOTA.

Help: My LG H990 DS only enters Fastboot and now the device changes to US996

Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...

Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope

aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs

cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...

I ended up flashing whole rom again and everything is back to normal