A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Pomaraczowy said:
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Sent from my Honor 9 using XDA Labs
hujialun2002 said:
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Click to expand...
Click to collapse
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Pomaraczowy said:
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Click to expand...
Click to collapse
We have already had a taste of Pie now,so for anyone who dont care EMUI 9 they can simply do with Treble Pie GSIs.Who cares about the ugly UI of Huawei?PE 9.0 and OpenKirin Pie AOSP are both doing quite great.
Sent from my Honor 9 using XDA Labs
Pomaraczowy said:
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
streetu said:
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
Click to expand...
Click to collapse
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Pomaraczowy said:
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Click to expand...
Click to collapse
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
streetu said:
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
Click to expand...
Click to collapse
Probably gonna do it soon.
Thanks for help.
For now, I'm up to B372, and still able to do whatever I want, fyi.
Keep on updating... and supporting the Apple wannabees of the Android world. They learned and stole the ideas they wanted from the community and now will completely lock out the devices, bootloaders, root methods, anti-rollback measures, etc.
Oh, and as for that "spying" part? Just search for "Huawei D.U.B.A.I.". Every single aspect, action, usage and telemetry of your device is logged and sent to Huawei's Big Data Analytics servers, and it's embedded on kernel and can't be disabled. Most i could do on my kernel was disabling it on GPU framework, but the rest remains. If i turn it off on kernel or eliminate it, the mobile comms framework is killed and sim card doesn't even get activated, turning your device into a small tablet at most... so you either accept it or get yourself another phone.
Since using Treble Roms gets rid of the "system" part of EMUI, like their store, services, etc, it's possible that the Analytics part is somewhat suppressed but i can't be sure of that.
My advice is, stop updating EMUI and go Treble. Or just sell your device and get another. Or just resign to the new Huawei's reality and forget this community.
Related
This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...
those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc
enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards
iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.
Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).
I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.
I found a simple fix, get Titanium Backup and freeze that crap app, done.
yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...
saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel
No source from motorola, nor updates yet.
Hello you can root your moto with magisk.
Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs
Thanks by the way. I found i way to root my Device.
Please do tell, how?
Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.
This is what I did. Yes..
Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.
THANKS!
Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.
a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.
Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.
yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant
Hi there, I have the GM1925 (Sprint) model of the OnePlus 7 Pro 5G.
I'm running stock OOS 10.0.3GM25CC, rooted with Magisk, substratum, and an unlocked bootloader.
It's been years since I've run a stock ROM, so I really have no concept of how OTA updates work (I've always just flashed updates via TWRP). A couple days ago I got a system update notification for a 199MB download, and I'm wondering if it's "safe" to apply it, or if I need to do anything special first.
From what I've read online here and in the OnePlus forums, the recommendation is to do a "full" local update (something like a 2GB download), however the sprint firmware for the GM1925 doesn't have such an option in the system updates settings.
Can I apply this update safely without losing any of my data? Is there a guide somewhere for how to apply and survive OTA updates?
Update: I'm now getting notifications from Google Play Services saying "Couldn't install update" despite the fact that I haven't *tried* to install it.
Any advice? Is it safe to install? I don't want to wind up with a brick that I'll have to reflash and set up again.
Narwhal73 said:
Update: I'm now getting notifications from Google Play Services saying "Couldn't install update" despite the fact that I haven't *tried* to install it.
Any advice? Is it safe to install? I don't want to wind up with a brick that I'll have to reflash and set up again.
Click to expand...
Click to collapse
From my experience from last incremental updates(onePlus7pro5g) I've just had to boot to recovery and flash twrp and magisk again..
You said you rooted and unlocked bootloader, just wondering if you could lmk how you did it, I have the same device and have been struggling.
Shooter7889 said:
From my experience from last incremental updates(onePlus7pro5g) I've just had to boot to recovery and flash twrp and magisk again..
Click to expand...
Click to collapse
When you say reboot to recovery and flash twrp again, do you mean reboot to the bootloader?
Did you do anything before applying the OTA, like disabling magisk mods?
EDIT: Also, do you have the Sprint model & firmware?
Cody719 said:
You said you rooted and unlocked bootloader, just wondering if you could lmk how you did it, I have the same device and have been struggling.
Click to expand...
Click to collapse
This is a bit off-topic I guess, but info to unlock the bootloader is here:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
You'll need a Windows computer to use the MSMTool in that thread. Also, pro-tip: uncheck the automatic reboot option in the MSMTool GUI to make your life easier when you have to reboot to the bootloader to run the fastboot commands.
If all goes well, you'll be running Android 9. Surprisingly that OS version claimed my phone was SIM-locked -- but applying the Android 10 OTA update fixed this issue. Then I rebooted to the bootloader, flashed TWRP, rebooted to recovery and flashed Magisk to root the phone.
Narwhal73 said:
When you say reboot to recovery and flash twrp again, do you mean reboot to the bootloader?
Did you do anything before applying the OTA, like disabling magisk mods?
EDIT: Also, do you have the Sprint model & firmware?
Click to expand...
Click to collapse
In developer settings I turn on advanced reboot options, so I can easily hold the power button and it shows all the options(power off, reboot, recovery, bootloader, screenshot). If u have twrp fully installed u can just click recovery and then reflash twrp and magisk and reboot. About disabling magisk mods, yeh I always disabled rice and all others that may cause problems. But on this latest 10.4 update, I had apparently done something where I cldnt even get my system updates to download it. So I just ended up msm'ing my phone and then BL unlocking, updating to 10.4,then doing magisk and mods..?
There's a great telegram group with all the info for gm1925/1920 onePlus7pro 5g, should def go check it out, alot of help there.
Shooter7889 said:
There's a great telegram group with all the info for gm1925/1920 onePlus7pro 5g, should def go check it out, alot of help there.
Click to expand...
Click to collapse
What's the name of that Telegram group? The only one I can find for the 5G version is the McLaren 7 Pro.
I've also got the Sprint oneplus 7g Pro 5G/gm1925, and I am getting the notification for the update but am not able to install it. There is no option for the full download in order to use the methods described for other models. Would really like to get this resolved without having to do a full rewipe and flash, that's for sure.
I'm still holding off on applying this OTA until I can get some more info. I also couldn't find the aforementioned telegram group
Bumping this thread because there still doesn't seem to be a good guide for stock OTA updates on the GM1925.
I'm interested in doing this aswell. I have OP7Pro Sprint too. Just bootloader unlocked and magisk nothing else.
Though I have software version NoLimits IDK if that can be OTA'd.
Narwhal73 said:
Hi there, I have the GM1925 (Sprint) model of the OnePlus 7 Pro 5G.
I'm running stock OOS 10.0.3GM25CC, rooted with Magisk, substratum, and an unlocked bootloader.
It's been years since I've run a stock ROM, so I really have no concept of how OTA updates work (I've always just flashed updates via TWRP). A couple days ago I got a system update notification for a 199MB download, and I'm wondering if it's "safe" to apply it, or if I need to do anything special
Can I apply this update safely without losing any of my data? Is there a guide somewhere for how to apply and survive OTA updates?
Click to expand...
Click to collapse
Basically you need to back up all your data and your storage card area off the phone. Then you have to relock the bootloader to apply the update.( Relocking bootloader will wipe the phone. )
After applying update, unlocked bootloader again root and restore your data and files.
you will have to do this everytime sprint/t-mobile releases update. If you want to stay up to date. And you will get the Google nag at least once weekly until you do
schn1tt3r said:
I'm interested in doing this aswell. I have OP7Pro Sprint too. Just bootloader unlocked and magisk nothing else.
Though I have software version NoLimits IDK if that can be OTA'd.
Click to expand...
Click to collapse
Same here, but what I want to do instead of waiting for the OTA update from Sprint it's to flash the original ROM from OnePlus but I'm not sure which version could be compatible.
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
HopelesRomantc91 said:
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
Click to expand...
Click to collapse
Wow, thanks for all this info. That is great that you were already able to root and get Magisk on there with minimal issues. This is pretty much what I do with my phones right out of the box. Regarding that link for Gapps, I read through the start of that thread and the package is definitely what we'll probably need for this phone. But, without a working recovery at this point, I don't think there is another way to install it.
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
CCivale said:
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
Click to expand...
Click to collapse
It's worth noting that I cancelled my Giztop purchase and bought from Aliexpress instead. Can't remember if I actually said that or not.
there is twrp, it is experimental
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
I couldn't find it, can you link it?
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
Can you link it?
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
ktitimbo said:
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
Click to expand...
Click to collapse
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
@HopelesRomantc91
Can you share the URL for unlock code request?
I couldn't unlock with global website...
I think I just used the global one here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/
Hello, I have patched boot img to my moto edge S 5g Chinese version and I have magisk root ok but if I restart the motorola it is lost and I have to reinstall boot parched, do you know why?
HopelesRomantc91 said:
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
Click to expand...
Click to collapse
Thanks for info . İs flashing g100 rom need root device or unlocking bootloader ?