Related
Guys
I have tried to downgrade from stock MM to stock KitKat via odin for various reasons(battery,smoothness etc).
Every time it fails on bootloader step.
If anyone can provide me with kitkat bootloader and kitkat modem for the N910U it would be very helpful.
~~~N910U TGY HongKong based
If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.
There are many a users who claim they are able to revert back from LP to KK and plenty youtubers show it.
I dont claim they are genuine but atleast one out of them would/may be genuine, so whats wrong in giving a try.
Anyways you have the files?
decron04 said:
If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.
Click to expand...
Click to collapse
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back
galaxyYtester said:
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back
Click to expand...
Click to collapse
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.
its_me_Sandy said:
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.
Click to expand...
Click to collapse
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/
galaxyYtester said:
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/
Click to expand...
Click to collapse
Thanks for the detailed one.
i believe the issue is with snapdragon vs exynos processor, as i have followed the same procedure but iam unable to pass the sboot.bin step in odin, it fails there.
not sure on unlocking bootloader as i am rooted, tried few custom roms and kernels too, so i believe it may be unlocked.
did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?
MatiasETirimaco said:
did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?
Click to expand...
Click to collapse
Except for internal storage, all.
Actually you can't downgrade from stock mm to kk on n910u, your phone bl was locked when you flash 6.0 bl, but you can downgrade to 5.1 LL.
sorry for my bad English.
You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.
decron04 said:
You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.
Click to expand...
Click to collapse
OMG!
Really? I cannot back to KK from MM ? I have the 910c. It's already came with LP...
If I try I can kill my phone or I just will get a error message ?
Thank you!
You can't kill your phone. It just won't allow you to install the KK bootloader. Same goes for all exynos phones. Once you leave KK, there is no turning back. That's why I made sure to get a snapdragon. Sorry to be the bearer of bad news.
Hello!
Here is the full G925VVRS4DQD1 Odin manual update to 7.0 Nougat for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 5.1.1 or 6.0.1.
https://www.androidfilehost.com/?fid=529152257862722630
If for whatever reason you want to downgrade or don't like 7.0, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on Verizon logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that.
G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500
G925VVRS4CPL3 (6.0.1) - https://www.androidfilehost.com/?fid=673368273298921946
G925VVRU4CPK2 (6.0.1) - https://www.androidfilehost.com/?fid=385035244224407601
G925VVRU4CPD2 (6.0.1) - https://www.androidfilehost.com/?fid=24566454284190657
G925VVRU4BOK7 (5.1.1) - https://www.androidfilehost.com/?fid=24269982087018504
G925VVRU4BOG9 (5.1.1) - https://www.androidfilehost.com/?fid=24052804347845467
Thanks a lot! I downloaded one from sammobile but there was one only one file, modified date 4/07...
I notice the files within the zip from your link mention REV02 and are dated 4/26.
G925V_G925VVRS4DQD1_VZW_USA_v7.0_IMEIAUTHORITY.COM.zip
2.54 GB (2,732,088,886 bytes)
MD5: 145a137d2c639b30ef5addac9094f331
I have attached the results from HashMyFiles for the 4 within the archive (Filename, MD5, SHA1, CRC32, SHA-256, SHA-512, SHA-384, Modified Time, File Size).
@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.
Hi there. I installed the new update on my s6 edge 7.0 via verizon software updating tool.am noticing the sound quality of mt s6 edge has been changed.before the sound quality was thick and now its not that thick anymore.i want to bring back the thick quality sound on my s6 edge.there is setting called sound quality and effects but i cant manage to get back that sound quality i had with 6.0. Is there anyone who able to notice this change in the sound?
blkt said:
@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.
Click to expand...
Click to collapse
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
That is very good to know. Yeah I noticed it about the firmware naming convention but I had no idea what the value means (or the character before revision bit, U has become S). My phone out of the box was on G925VVRU3BOG5, so I guess I could go all the way back to G925VVRU4BOG7 if "needed" lol.
One of my fears about Nougat is about all the work they did to automate and place updates into the background. This could allow disabling of downgrades, or anything else at the discretion of Samsung and/or the carrier. I think this has already been done in Marshmallow, just on a smaller scale for security fixes. Anyway, it seems to me like an attack vector waiting to happen: less control over my phone combined with an easy way to break things. Imagine all the troubleshooting fun we will have.
So I upgraded to nougat. I'm having battery issues and just want to go back to marshmallow. but I'm having problems. The nougat rom installs just fine with odin. But when I try with any of the 6.0.1 roms it was failing. Then I noticed that re-partition was chcekd. So I unchecked it and now it goes through the process just fine. But now the complains with dm-verity verification failed. I can install nougat on it no problem. It's just the downgrade that's not working... any clues?
toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!
MrMike2182 said:
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!
Click to expand...
Click to collapse
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.
strandedhuman said:
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.
Click to expand...
Click to collapse
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
No Worries. Finally figured it out. Good luck to you
MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse
I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Thanks!
--
Furry cows moo and decompress.
WyrdWyrd said:
I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Click to expand...
Click to collapse
I haven't been keeping up, but now curious. Verizon shows DQH1 as current (a 7.0 build), while sammobile and androidfilehost show four builds available (all 7.0).
Ok, so I updated my G925V with nougat, now I'm just wondering if anyone has come out with a way to root this build? That's what I'm waiting for. Plz fill me in when that happens. Thanks.
MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse
I've been wanting to get one too. Which box plus tool do you use?
Delgoth said:
I've been wanting to get one too. Which box plus tool do you use?
Click to expand...
Click to collapse
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com
MrMike2182 said:
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com
Click to expand...
Click to collapse
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol
raven213 said:
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol
Click to expand...
Click to collapse
You unfortunately cannot downgrade the bootloader once you updated to 6.0.1 you lost the ability to go back and there's so far, no way possible to do it.
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
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.
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.