Database Users

[Solved] Did I hose myself (Knox poblem?)

So, the other day, as samsung was pushing more bloat to my phone, I decided I had had enough Redit told me I could just delete most things from root, I did so by following the instructions from a google search of how-to-root-and-flash-cwm-recovery-on-sprint-galaxy-s4-on-android-4-3-tutorial (except, of course, the back up part)
then, without paying attention to the list of removable apps, I took out Samsung hub, And then the problems start. The phone still works: Except every second or so, i get told that the hub has stopped. The phone isn't bricked, but it is basically worthless with the message popping up constantly.
According to my settings, everything is still stock (L720VPUFNAE) Although I think just rooting it was enough to pop the Knox bubble. I'm not working on getting that rom to try to re-flash back to stock (I thought i had did this over night, but it seems like i had slightly different roms when I was doing this early in the morning)
I also tried installing the Samsung Hub apk, but I get an error stating that X app wasn't installed. I have not been able to find a source for this app while googling.
I've tried finding a custom rom to use, but most of the ones I THINK are good/will work, don't install via odin, and for some reason when I try to boot into recovery, it just sits indefinitely @ the samsung galaxy screen.
Am I just stressed and frustrated, or am I truly hosed?
Edit: I'm currently working through http://forum.xda-developers.com/showthread.php?t=2307531 as my next attempt
Edit: for some reason Philz recovery isn't ever entering a recovery mode for me, it just sides @ the samsung screen forever

Akuthia said:
blablabla I deleted something what I shouldn't and now my phone is faulty, but I do not want/can reflash using Odin and CWM :crying::crying::crying:
Click to expand...
Click to collapse
You still can install Mobile Odin from google Play, copy ROM to SD card and try to flash it in that way...

spamtrash said:
You still can install Mobile Odin from google Play, copy ROM to SD card and try to flash it in that way...
Click to expand...
Click to collapse
I get it, i deserve the sarcasm, I broke rule 1 of upgrades. (one of) the problems I'm having though is finding the right file to flash to. Just looking for a little bit of advice as to what files I need to get back to " Normal" I know I should be able to flash to another rom, why when I use Philz Recovery it doesn't do what it's supposed to, is beyond me right now. Odin mobile requires the PDA file, correct? That seems fine to getting back to stock, but most of the custom roms I've found or are at least interested in are just files that are installed via recovery...which for some reason I don't have access too, right?

Akuthia said:
That seems fine to getting back to stock, but most of the custom roms I've found or are at least interested in are just files that are installed via recovery...which for some reason I don't have access too, right?
Click to expand...
Click to collapse
Correct. If I'd be you, I'd go to sammobile.com, and I'd start from full stock flash. It shall restore recovery. It it would work - you'd be OK to go with custom.

spamtrash said:
Correct. If I'd be you, I'd go to sammobile.com, and I'd start from full stock flash. It shall restore recovery. It it would work - you'd be OK to go with custom.
Click to expand...
Click to collapse
Ok, Sammobile has been efforting for about an hour. Has an hour to go. I also got CWM and am going to see if I can flash a rom with it. Transfer of those files is taking a while as well.

Akuthia said:
Ok, Sammobile has been efforting for about an hour. Has an hour to go. I also got CWM and am going to see if I can flash a rom with it. Transfer of those files is taking a while as well.
Click to expand...
Click to collapse
Got back to stock. Text messages gave me a fright for a bit was sending me a message they were undeliverable via another code text # one of those 4 or 5 digit things)

Akuthia said:
Got back to stock. Text messages gave me a fright for a bit was sending me a message they were undeliverable via another code text # one of those 4 or 5 digit things)
Click to expand...
Click to collapse
Good. Now, a small lesson for the future, if I can:
if you want to remove something, DO NOT delete software, use Titanium Backup and freeze apk first instead.
This will give you opportunity to check if you have frozen something important. :good:

spamtrash said:
Good. Now, a small lesson for the future, if I can:
if you want to remove something, DO NOT delete software, use Titanium Backup and freeze apk first instead.
This will give you opportunity to check if you have frozen something important. :good:
Click to expand...
Click to collapse
Thats the thing, i HAD made a backup in titanium of all my system apps, just so i could roll it back, but for some reason, it wasn't listed when the fan got hi by you know what.

Akuthia said:
Thats the thing, i HAD made a backup in titanium of all my system apps, just so i could roll it back, but for some reason, it wasn't listed when the fan got hi by you know what.
Click to expand...
Click to collapse
I DID not mentioned BACKUP.
I mentioned FREEZING.
Backup is another copy, which you may, or may not install.
FREEZE is that all files are present, but the application is not listed in system.

Firmware partiton request

Hello guys!
I'm in need of a help here. I have selected the infamous USA radio band on my Moto X Play XT1562/EU/6.0.1 and now only have access to 4G network, no calls available.
As i don't have access to a a computer atm, can anyone make a backup of modem and fsg partition using Partitions Backup app, upload it, or send it to me privately.
I know about the erase modemst1/2 commands, they work, i purposely selected the USA band again, to see, if i can fix this problem without a computer. I don't really understand why such a thing is so hard to revert...
I tried flashing the modem firmware with Flashfire by extracting the FW files from stock ROM, but no success so far. Maybe if i use the PB app and try restoring the partition from there, it would revert back to normal EU band. I'm highly doubtful this works though.
I would appreciate if anyone would make that backup and upload, any other suggestions on how to revert the problem without using fastboot/adb would be appreciated.
Thanks in advance.

Not possible. Get a computer, download whatever brand stock rom, extract the required files and flash it. You can find more information on this in the General section as there are threads regarding stock firmware downloads.

Alright, thanks for the answer. I'm still puzzled as why this is so hard to revert though.

hightechlowlife said:
Alright, thanks for the answer. I'm still puzzled as why this is so hard to revert though.
Click to expand...
Click to collapse
When you flash system it ovewrites the target location and deletes what was previously there. In order to revert it you need to flash the original, and the easiest way to do so is with a computer. If you had made a backup before making changes then you wouldn't be in this situation mate

mazhdini said:
When you flash system it ovewrites the target location and deletes what was previously there. In order to revert it you need to flash the original, and the easiest way to do so is with a computer.
Click to expand...
Click to collapse
I understand, but still, just one click and it lets overwrite such critical information all too easily, if i was a total noob and not knew how to use google i would be very frustrated. Also, it's a bit of a security flaw in disguise IMO. People with bad intentions can just tap the code on the phone, change the band, and there you have it. The owner would have no calls and no idea what has happened. This is something that phone makers or devs need to take in considersation and possibly change it or remove the option alltogether. I understand laypeople are not supposed to mess with these unknown codes, but curiosity won't let us stop doing stupid things.

it's a bit of a security flaw in disguise
Click to expand...
Click to collapse
Do you frequently hand your phone over and let people reprogram it?
It's not a flaw, it's a feature. Not a useful one to the end user, but a feature none the less. That is like blaming an oven manufacturer, or the water company when you burned yourself on boiling water on top of it.

Alright, well i did exaggerate a bit but, still. Too easy to mess up and not so easy to revert is my point. I don't even understand why this feature is available. What purpose does it serve? Who wants to permanently switch to USA band without having an option to switch back to the old one. This is a bit mystical.

[Bricked]Like a Boss(err... complete imbecile)

So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?

Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.

H4X0R46 said:
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
Click to expand...
Click to collapse
Dang I was kind of afraid of that MSM tool thing, I'm going to have to do a little reading on that. That's one thing I've never done on an Android for sure.
Thank you
... On another note conveniently my Laptop keys ZXCVM just stopped working WTF! Not cool timing, I just bought it.

Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

Sipi1302 said:
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
thank you all for your replies, however I'm beginning to get really frustrated. I'm trying to use the MSM tool and how do I frickin run an .exe when the damn thing is a .rar format, the instructions under that thread are not particularly descriptive. Do I extract it? do I have to run something in a window somewhere? if my device is in EDL and the port shows Qualcomm HS-USB QDLoader 9008 (COM6) is that good?

OMG!

Causical said:
OMG!
Click to expand...
Click to collapse
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!

H4X0R46 said:
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
Click to expand...
Click to collapse
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.

This has got me wanting to repeatedly dropkick myself in the larynx.
....#slowassWiFi

Causical said:
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
Click to expand...
Click to collapse
Yes, you are doing it right.
I would use 7zip but winRAR is fine. Dont know why someone would be using that in this day and age... but hey, it works...
I have also read other random threads that says that the file is corrupt. If you cant get a good download let me know and I will upload my collection of files. Send me a PM if you need me to upload. It wont be for a couple hours though...

Apparently they're all corrupt. I just downloaded 9.0.11 after doing .12 first and I'm getting the same errors in WinRAR

Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.

Causical said:
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Click to expand...
Click to collapse
Was it Ok with 7Zip?

Scott said:
Was it Ok with 7Zip?
Click to expand...
Click to collapse
No lol, but it's a little more clear that the file is corrupt I suppose ?
Edit: Hey I'm going to try the recommendation of the other guy ^^up there with the fastboot ROM, I don't think it will work because I don't think fastboot is recognizing my boot, but guess we'll see... I'm just curious do you recommend doing the flash-all-partitions-fastboot.bat? Or the "Big One" flash-all-partitions.bat...I feel like I'm on the verge of really slipping deeper into the abyss here.

Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh

I think I used flash all bat and that work for me but phone was reset to factory settings after that
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Causical said:
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
Click to expand...
Click to collapse
im glad it worked, have the same filing as you when I brick phone and then make him work again.

Sipi1302 said:
I think I used flash all bat and that work for me but phone was reset to factory settings after that
Click to expand...
Click to collapse
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
... All this because I didn't want a pesky warning notification gyollee dude, that allowed me to get absolutely nothing else done on my day off work lol.

Causical said:
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
Click to expand...
Click to collapse
you welcome, Im glad I could help.Now you will know for the next time hehe:laugh:

I think MSM tool would still be valuable to know how it works, but let's hope I don't need it.

At least you are up and running!
But yeah, the MSM tool is pretty easy to use. If you ever used ODIN on a Samsung phone it would be familiar.

How do I fix a bootloop?

The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.

Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!

SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img

WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.

I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?

arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)

Wifi/bluetooth keep trying to turn on but fail everytime.

When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!

A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.

Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.

dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.

bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.

@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.

So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?

bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?

blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.

bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?

bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.

bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device

dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.

bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?

dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?

bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.

Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.

dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.

bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point