Database Develop

Downgrade Kitkat Asus Memo Pad ME572CL

guys, can anyone knows how to revert to android 4.4.2 android 5.0.1 with? updated firmware bass headphones disappeared, this problem occurs not only at me. who are important sound in the headphones do not advise upgraded. ASUS disappointed by this update.

ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.

BerndHhn said:
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
Click to expand...
Click to collapse
I tried to downgrade the firmware. but in the new android 5.0.1 bootloader and recovery, and this does not take recovery firmware based on Android 4.4.2. And here is the update on the official website for ME572C, but only TW version, WW firmware not yet available. http://www.asus.com/ru/supportonly/ASUS MeMO Pad (ME572C)/HelpDesk_Download/

Yeah
I installed this night.
Sound is fine.
Tested on Audio Out and Bluetooth, but unfortunately no root possibility yet.

It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too

Frisian said:
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Click to expand...
Click to collapse
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.

Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
Thats awful for you. Can't you get into any recovery anymore? Perhaps flash the 5.0.1. again?
I'm not going to try to downgrade but I wish I hadn't installed lollipop. I really like this tablet and everything worked perfectly. Now I have to rotate the screen manually. I cheked the sensors with a diagnostic tool and they are working fine. It's the software. It isn't known what triggers the bug so it could happen at any time or never. Nice work google.
Hopefully we'll have root and custom mods in the near future.

Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
If you can boot back into the download screen, you can probably reflash the newest firmware.

pWEN said:
If you can boot back into the download screen, you can probably reflash the newest firmware.
Click to expand...
Click to collapse
does not work, bootloader killed, dependent on Intel Inside logo.

Hi, i try at the moment downgrade from the me581cl. It looks good. You can look at my thread Root with downgrade for the intel developer tool.
The highest importent file is the ifwi.bin.
You can it flash with fastboot flash dnx .....

Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) with the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.

kanagawaben said:
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) to the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
Click to expand...
Click to collapse
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....

gmaxjp said:
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
Click to expand...
Click to collapse
I did a factory reset and the WW 5.0.1 seems stable again now. Would still like to return to a rooted 4.4.2 if possible though.

Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.

Myuboku said:
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Click to expand...
Click to collapse
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....

gmaxjp said:
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
Click to expand...
Click to collapse
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.

Myuboku said:
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Click to expand...
Click to collapse
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.

tycoo said:
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
Click to expand...
Click to collapse
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat

Myuboku said:
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Click to expand...
Click to collapse
Ya, that might be true.

tycoo said:
Ya, that might be true.
Click to expand...
Click to collapse
Also as i know, there is a person who has service firmwares. As he explained, when flashing service lollipop firmware, it somehow unlocks bootloader(i can be mistaken at this part), and makes it possible to install any android firmware.

Can't load recovery after flashing Stock image 5.1.1

Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.

I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.

dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.

chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.

Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!

The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.

chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.

NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.

chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?

Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.

That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.

chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.

Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.

How to root my Sony Xperia Z3 compact?

Dear XDA-developers,
Today I spend numerous hours in trying to root my xperia z3 compact.
I currently have MM 6.0.1 D5803 installed on it with 23.5.A.0.575 the netherlands T-Mobile version. I have tried the following: Kingroot, iroot, kingoroot etc but it is all not working. I also used adroid sdk and changed the fastboot driver. I am able to fast boot etc.
Could anybody help me out with rooting this device? Love to hear from you guys.
Kay

It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.

Similar issue in Switzerland
M1chiel said:
It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.
Click to expand...
Click to collapse
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?

jassi0709 said:
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?
Click to expand...
Click to collapse
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot

Didgesteve said:
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot
Click to expand...
Click to collapse
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah

jassi0709 said:
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah
Click to expand...
Click to collapse
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.

Didgesteve said:
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.
Click to expand...
Click to collapse
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...

jassi0709 said:
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...
Click to expand...
Click to collapse
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before

Didgesteve said:
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before
Click to expand...
Click to collapse
Thank you for your answer. Really useful! I've finally managed to room and install that I wanted!
If you have such permission, I would suggest to edit the guide in: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
by adding the following:
7. Just select the name of the fw you downloaded and click on "Flash". Note: select both wipes in case you are coming from different android version.
43. Open Flashtool and select the non-pre-rooted fw (this is 23.1.A.0.690), but DESELECT system: in "EXCLUDE" make sure you check the checkbox next to "SYSTEM", flash it.
I will put this comment on the relative guide too!
I don't want to abuse of you kindness but I am currently searching for some CPU+GPU clock and voltage changer. Is there any efficient application that you can suggest me?

* G925VVRS4DQD1 * Full Odin Nougat 7.0 Firmware *

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.

Good source for firmwares?

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.