Anyone know a secure procedure and a custom recovery compatible?
marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.
Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.
This process worked for me. Moto G7 Plus, International Unlocked version.
This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.
Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.
Related
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Note: when I and others have tried the "Local upgrade" feature with older OxygenOS international releases (e.g. 9.0.5), it would cause the T-Mobile device to brick and get stuck in the "Device mismatch" bootloop. This time it's different! Was able to re-lock bootloader after sideloading the full official 9.0.7 OTA and retain all functionality. It is likely we will even be able to take official OTA upgrades after this...if so, I consider this a full conversion
I followed @Dark Nightmares guide and did it the fastboot way and loaded TWRP, Magisk, etc and my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
TheKnux said:
I followed @Dark Nightmares guide and did it the fastboot way and loaded TWRP, Magisk, etc and my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
Click to expand...
Click to collapse
What module from Magisk did you use?
TheKnux said:
my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
Click to expand...
Click to collapse
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
AnonymousTipster said:
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
Click to expand...
Click to collapse
Welp, count me in! This sounds great.
AnonymousTipster said:
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Click to expand...
Click to collapse
Can you please elaborate where we can find the local upgrade feature? Also, can we have the link to the ota zip ?
Thanks so much in advance!
Hmmm is this for real..?? Any way to verify??
I guess the only way to tell would be when next ota comes out if it updates without issue.
Nileshdd said:
Can you please elaborate where we can find the local upgrade feature? Also, can we have the link to the ota zip ?
Thanks so much in advance!
Click to expand...
Click to collapse
Settings->System->System updates->"Gear icon"->"Local upgrade"
Use the "full ROM" zips here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
https://forum.xda-developers.com/on...oneplus-6t-t3860953/post78026655#post78026655
OnePlus also publishes them here, but they're usually a bit delayed (still haven't posted 9.0.7 for example):
https://www.oneplus.com/support/softwareupgrade/details?code=9
AnonymousTipster said:
Settings->System->System updates->"Gear icon"->"Local upgrade"
Use the "full ROM" zips here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
https://forum.xda-developers.com/on...oneplus-6t-t3860953/post78026655#post78026655
OnePlus also publishes them here, but they're usually a bit delayed (still haven't posted 9.0.7 for example):
https://www.oneplus.com/support/softwareupgrade/details?code=9
Click to expand...
Click to collapse
Does the local upgrade factory reset the phone? I want to avoid it.
AnonymousTipster said:
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
Click to expand...
Click to collapse
Look up "liboemcrypto disabler" under Magisk downloads. Correct me if I'm wrong. Play Store said my device was not certified until I flashed this and rebooted and now it says it is certified. Besides, I'm not too worried about flashing updates manually with the way I converted, cause like you said in a few posts below, OnePlus hasn't uploaded 9.0.7 yet, it was much easier to go the route I did rather than wait for OnePlus to upload it. Anyways, thanks for this guide, I'm sure a lot of people (including myself if I decide to go this route) will find it useful.
---------- Post added at 05:49 AM ---------- Previous post was at 05:46 AM ----------
flexor224 said:
What module from Magisk did you use?
Click to expand...
Click to collapse
It's called "liboemcrypto disabler".
AnonymousTipster said:
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Click to expand...
Click to collapse
I did the local upgrade. It went just fine.
Now, will lead 2) cause a factory reset? I am trying to avoid it if possible
Nileshdd said:
I did the local upgrade. It went just fine.
Now, will lead 2) cause a factory reset? I am trying to avoid it if possible
Click to expand...
Click to collapse
relock bootloader wipes data. im doing it becuase i dont use root for anything. i only had magisk to hide the unlocked bootloader from my banking/streaming apps.
i followed op instructions and will be the guinea pig when new ota is released. will report back. thanks to oneplus backup software its not too painful to restore.
so which msmdownload tool would you use after such conversion?
headcreepz said:
so which msmdownload tool would you use after such conversion?
Click to expand...
Click to collapse
Not sure I'd assume the T-Mobile one. BUT on prior conversion before the local upgrade was possible, the fastboot oem lock wouldn't work. I was surprised when it worked when I did it last night. We'll know for sure if it's fully converted when next ota is released
After this potential conversion are the imei numbers listed differently in the settings or are they still the same?
yujikaido79 said:
After this potential conversion are the imei numbers listed differently in the settings or are they still the same?
Click to expand...
Click to collapse
Still the same
This is interesting, thank you for the info! I didn't even know we get a partial version of oxygen for T-Mobile models. Since I just received my unlock token today, my qestions are:
1. can I flash the latest oxygen os (dark nightmare guide) and if I do will that be the full version or do I have to follow your route which is 0.6? Then do the device upgrade?
2. Is there a guide to go back to stock T-Mobile rom?
3. Does flashing oxygen or any other rom retain USA bands? Because I saw a post having network problems...
Again, thanks bro!
moist_line said:
This is interesting, thank you for the info! I didn't even know we get a partial version of oxygen for T-Mobile models. Since I just received my unlock token today, my qestions are:
1. can I flash the latest oxygen os (dark nightmare guide) and if I do will that be the full version or do I have to follow your route which is 0.6? Then do the device upgrade?
2. Is there a guide to go back to stock T-Mobile rom?
3. Does flashing oxygen or any other rom retain USA bands? Because I saw a post having network problems...
Again, thanks bro!
Click to expand...
Click to collapse
U can flash using darks guide. Go to 9.0.6 then do the local upgrade to 9.0.7 for this potential full convert
Suggesting this because local upgrade may be what is doing the conversion if it actually is doing what we think it is.
There is a thread also by dark called msmdownload tool. Brings u back to full TMobile out the box stock
I have not had any issue with network. TMobile in NJ
Waiting on dark and a couple others to chime in.
Also I guess it can be tested if someone goes to 9.0
5, then local.uograde to 9.0.6, then see if ota comes in and works to 9.0.7. I should have done this last night but I went and relocked bootloader while on 9.0.7. If I'm.bored my next day off I'll do some testing.
TheKnux said:
Look up "liboemcrypto disabler" under Magisk downloads. Correct me if I'm wrong. Play Store said my device was not certified until I flashed this and rebooted and now it says it is certified. Besides, I'm not too worried about flashing updates manually with the way I converted, cause like you said in a few posts below, OnePlus hasn't uploaded 9.0.7 yet, it was much easier to go the route I did rather than wait for OnePlus to upload it. Anyways, thanks for this guide, I'm sure a lot of people (including myself if I decide to go this route) will find it useful.
---------- Post added at 05:49 AM ---------- Previous post was at 05:46 AM ----------
It's called "liboemcrypto disabler".
Click to expand...
Click to collapse
Akron huh? I am canton. This doesn't fully convert the phone. We all discovered this last update. It just allows us to use the upgrade option or flash in twrp. It still doesn't give us access to critical partitions. Whether or not flashing these OTA zips really do flash the critical partitions or not I dont know. I think it does, and it is sort of a fluke or else the ota zips would brick us still. So either way its great we dont have to use the slow strenuous fastboot method. Also, fyi, just to be sure, after one has flashed the full fastboot firmware package, you can dirty flash the whole ota via local upgrade just to be sure we are upgrading those critical partitions as well. Someone should try to do a dump before and after and compare the different partition sizes to see and verify if this does indeed update the critical partitions.ie, hyp, rpm, abl, xbl. etc.
I got the T-mobile REVVLRY+ today, and naturally, I wanted to put the stock motorolla firmware on it. Partly to see if I could, partly to get rid of the T-Mobile bloat and see what Motorola features T-Mobile had removed.
Everything went swimmingly, I have PPW29.98-107 installed, I even have WIFI Calling. What I did lose, however, is VoLTE. I did use TWRP to perform a backup before flashing, so I tried restoring it to get a better look at how VoLTE works in the T-Mobile firmware. This is where things got hairy. I stupidly only backed up boot, system, and data. When I use TWRP to restore them, I get stuck in a boot loop. The built in boot loop fix in TWRP didn't help.
1. Any ideas on getting as close to stock as I can with only the boot, system, and data partitions?
2. Does anyone have access to a REVVLRY+ that would be willing to do a full backup that I may try to restore?
*Edit* SO I used the code *#*#4636#*#* and VoLTE provisioned is enabled, so maybe I do have VoLTE?
*Edit 2* Google Pay doesn't work, even after locking the bootloader. The device says that the operating system has been modified. Still trying to get it to restore.
FOUND IT!
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
serris-chan said:
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
HOW to
Hi, I just picked up the Revvlry+. Do you have step by step to install the Stock Moto firmware? I miss some of the features of the Moto. Also, was it easy to restore the TMO firmware just in case?
did you make any progress into the volte research? im on a unlocked xt1965-2 and using metro but i dont get volte in any of the stock roms or custom roms. i have tried flashing the modem from the stock tmo rom which didnt really do anything. i will probably try to flash the entire tmo rom tonight and see if it boots. im thinking if i get volte in the tmo rom and backup the persist, vendor and efs. then if i restore them onto a working cutom rom with volte enabled, volte should work.
i have also read about different scenarios in where you have to install workarounds to enable volte on treble roms. like installing the ims.apk to route the calls to volte and flashing a volte enabler to inject the correct files into the vendor partition.
my other device is a moto g5 plus which has numerous volte issues when switching between stock and custom roms or between different versions of android.
Did you use the Moto G7 Plus TWRP? I just picked up a Revvlry+ and I'm looking to root to install lawnchair or pixel launcher as a system app.
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
ghostdogg49504 said:
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
Click to expand...
Click to collapse
Are you saying with a Tmobile Revvlry, you were able to just go to the Motorola bootloader unlock page, paste your unlock codes, and presto as if it was just a normal Moto phone? If so, that is awesome!
I am thinking of swapping my Moto G7 Play with a Revvlry because of the 3gb RAM and NFC (the size of the G7 Play is perfect, I don't want to be forced to carry around a giant phone), but would love to flash the stock Moto G7 Play ROM over the Tmobile version. Not sure I'm willing to risk it, but if anyone has tried, I'd love to hear about it.
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
ultracoolguy said:
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
Click to expand...
Click to collapse
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
tri_cchan said:
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
Click to expand...
Click to collapse
nice man
Relocking Bootloader
Would I do the OEM lockbootloader command to lock it back
Can confirm flashing Moto g7 play firmware on T-Mobile revvlry. Caveat, you can no longer take OTA's and NFC is broken. Also can be bootloader unlocked through the Moto website.
Wouldn't you need to flash the G7 plus firmware for NFC to work?
guitardoc64 said:
Wouldn't you need to flash the G7 plus firmware for NFC to work?
Click to expand...
Click to collapse
That makes sense, the SD632 is NFC capable however I'm on the G7 play not the plus (I know, I know wrong forum)
I can't get the stock rom to work. It just bootloops every time. I tried all 3 versions. Any ideas?
Hey friends, would one of you kind sould who own the Revvlry+ be kind enough to post this Wallpaper?
Thanks in advance!
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Did you manage to restore it with firmware? Because I have a bootloop and I'm looking for a solution
quiet boy
I just solved the problem I had like 4 crazy hours with solve bootloop, the problem that I commanded automatic flash, not flashing the vendor partition and then flashed the manual vendor partition
mfastboot flash vendor vendor.img and ready
edit:
for users with Revvlry+ variant (XT1965-T) use this Flash.bat
Hi,
I hope somebody can give me a hint.
I just got a used p20 pro with open bootloader but stock rom.
Unfortunately the Google security check has some "problems" with this situation and doesn't allow me to use several apps like Netflix, Google pay, etc.
So I'm looking for a way to easily fix this problem, the phone will be used by my parents.
Either lock the bootloader or "hide" it probably.
But how - I don't have the bootloader code - and I'm not too much into android rooting...
Usefull hints are appreciated.
Merry xmas
Mounty
You're on thin ice my pedigree chum..
Avoid flashing anything that would allow a block of any kind which is an absolute reality.
Having used absolutely every ROM and OS from 8.1 to 10
My advice. Flash AOSIP and then ask in thread to get safety net working.
Literally nothing else it worth your time.
Unless you're strange and like EMUI.
In such case, stuck with stock.
Just be aware you're in a position that a lot of people would kill for.
Google have done some **** stuff to make people who have unlocked bootloader a nightmare. I don't think there is a way to hide it unless you use Magisk
mounty77 said:
the phone will be used by my parents.
Click to expand...
Click to collapse
If they are not some kind of advanced users, unlocked bootloader has exactly 0 added value for them. Search the forum for flushing methods, the ones that will warn you that this method re-locks the bootloader, flush the latest stock ROM for your region and live a happy and calm life.
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Horayken said:
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Click to expand...
Click to collapse
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
mounty77 said:
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
Click to expand...
Click to collapse
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
thx for your offer/advise. I’ll try this way - it sounds most promising to me.
Can I do this on the mobile only, or do I need a pc?
Where / How do I find the ramdisk recovery?
BL Lock
I can lock (yes, lock) your bootloader for free.
Contact me at Telegram (@AntiEngineer), you don't need to open up your device.
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
unfortionatly I wasn´t sucessfull till now.
At https://openkirin.net/ is a very usefull description availaible but I´m still searching for the RAMDISK Extract. I found that database where you can donwload several versions, but mine wasn´t provided there
https://pro-teammt.ru/en/online-firmware-database/
My Version is:
CLT-L29
10.0.0.138 (C432E3R1P3log)
Anybody knows where I can download that`?
Best regards
mounty
@mounty77
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
Click to expand...
Click to collapse
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
mounty77 said:
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
Click to expand...
Click to collapse
Installing a "RECOVERY_RAMDIS.img" patched with Magisk is rooting the phone.
I´m fine if i have to root it to hide the open bootloader
I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2
All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
I'd recommend around sammobile and samfw. These are the two sources I use the most
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((
My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).
Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?
You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata
DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse
WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell
schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.