Database Develop

Flashing Werewolf rom

Hi i just did wipe and formatted system. Now i got (status 7) error and installation aborted when installing rom from external sd_card. :crying:
What should i do now i noticed 6.0.2.8 ver cwm.

Hallako said:
Hi i just did wipe and formatted system. Now i got (status 7) error and installation aborted when installing rom from external sd_card. :crying:
What should i do now i noticed 6.0.2.8 ver cwm.
Click to expand...
Click to collapse
install cwm 6.0.3.1

How
Flying_Bear said:
install cwm 6.0.3.1
Click to expand...
Click to collapse
I tried searching how to install it but can i boot now?
Is there way to install it with older cwm ?
sorry i am little new with android devices.
and ofc i dont have backup

Hallako said:
I tried searching how to install it but can i boot now?
Is there way to install it with older cwm ?
sorry i am little new with android devices.
and ofc i dont have backup
Click to expand...
Click to collapse
install rom toolbox from google play store, install latest cwm from there, and then flash werewolf rom

but
Flying_Bear said:
install rom toolbox from google play store, install latest cwm from there, and then flash werewolf rom
Click to expand...
Click to collapse
But i cant boot now when formatted system

Re flash official 20a with kdz flasher then

Flying_Bear said:
Re flash official 20a with kdz flasher then
Click to expand...
Click to collapse
i am now trying but when i start update flasher crashes when extracting kdz.
log
oblem signature:
Problem Event Name: APPCRASH
Application Name: KDZ_FW_UPD.exe
Application Version: 1.0.4.4
Application Timestamp: 4ac2a689
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7bafa
Exception Code: e06d7363
Exception Offset: 0000b727
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1035
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

><
You can do several things:
If your adb is working, i think you can push latest cwm to recovery partition. Find dexters topic on how to do it, but instead of 6.0.2.8, download latest from cwm website and push it.
Alternatively, download zaiben rom, put it on sdcard ext and flash it, then use rom manager etc.
Another thing you can do is search for topic "fixed cm flashable", and flash that cm, then update to latest.
There is one more way, you can edit cm's zip and delete lines checking for device id.
Good luck

Flying_Bear said:
><
You can do several things:
If your adb is working, i think you can push latest cwm to recovery partition. Find dexters topic on how to do it, but instead of 6.0.2.8, download latest from cwm website and push it.
Alternatively, download zaiben rom, put it on sdcard ext and flash it, then use rom manager etc.
Another thing you can do is search for topic "fixed cm flashable", and flash that cm, then update to latest.
There is one more way, you can edit cm's zip and delete lines checking for device id.
Good luck
Click to expand...
Click to collapse
Oh right ill try all i can.
Thanks for helping and that luck is needed.
i got it working after adb push latest cwm and then cm.

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!

nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.

After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.

Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472

Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?

Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.

Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.

Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.

zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?

please fix dead links

dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.

please fix dead links

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1

After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now

lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.

[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient

[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location

lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone

server stilll unreachable.

Unable to mount 'data,storage,system'

How do i fix this, i dont know what is wrong. CM12 wont flash, even though it is on te device.

Mention your current recovery (PhilZ/ TWRP) and version.

sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
It is TWRP recovery v. 2.8.5

sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
Thanks for the reply, but i fixed it, I just formatted the data again, then copied cm12 onto the phone, flashed it, then it booted up!

unable to mount system after deleting os accidentally
pliz help

Even I am having the same problem. When I flash it says " E unable to mount "/system" I gather from googling that it is malformed partition issue. But I am not able to find fixes for it. Please help

I think the problem was with the Cm 12.1 zip. I installed another rom.zip file (Blisspop rom) and it is working fine now.

[RECOVERY][OFFICIAL][sagit] TWRP 3.2.2-0 for Xiaomi Mi 6

Team Win Recovery Project
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
FEATURES:
FBE Decryption support
MTP support
ADB root
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-06-10
Last Updated 2018-07-07

FAQ
FAQ:
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).

Reserved

Nice

Praying for good developers working on Mi6
Thx for TWRP

thanks

Thanks a lot for your work.

Any comparison to ValoXis / cofface version?

Thanks

Thanks a lot for your work!
Can I disable dm-verify with this revovery when using official MIUI rom?

Can not be backed up

.nice thank you !
Maybe lineage is next ? ?

Any reason why it asks me for a password?
Thanks!

Yeah, Parth its here
Now it's time to xiaomi to release kernel sources

Successfully re-flashed from ValoXis version via official TWRP app.
Thanks Strix!

Tried to restore from backup, This is the thing what I backed up :
1. Backup1 : boot, recovery, EFS
2. Backup2 : system, system image, data, cache
I tried to restore from backup2 first from failing the installation of China dev ROM. Wipe system, data, cache, dalvik, and do the backup.
It's booted okay (it uses the custom boot animation I picked), but at the end / near the end of the boot animation, there's low battery sound played, then the device is switched off.
Tried again to wipe everything, restore backup2, then backup1, I got the same "low battery" sound notification.
In the end I had to reflash Xiaomi.eu ROM and start fresh.
So what actually happened there?

Hello, after installing twrp this one does not stay, do you have a solution? thank you

Thanks a lot for your work!

I hope Sagit can get recovery by ZCX
Sent from my Xiaomi Mi 6 using XDA Labs

TWRP 3.1.1-1 release:
Fixes the nandroid backup/restore issue
(Notice: backups made using old recovery builds still won't restore fine)
Other updates
Also for some of you've have been wondering,
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).

Permanently Closed

XDA:DevDB Information
Permanently Closed, ROM for the Samsung Galaxy S4
Contributors
TheGingerSage, arter97 , dkcldark, zahidm & kiffmet
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Downgrade to OD3 + TWRP 3.x.x Recovery
Based On: Stock Build OD3
Version Information
Status: Testing
Current Stable Version: FINAL
Stable Release Date: 2019-01-20
Created 2019-01-19
Last Updated 2020-05-31

Permanently Closed

Permanently Closed

Thanks for your good work. In the future Can One UI get port to s4?

nhihoppro said:
Thanks for your good work. In the future Can One UI get port to s4?
Click to expand...
Click to collapse
I will totally try my best! Please check back later today for the final that TOTALLY HAS SAMSUNG'S PIE EMOJIS!!!
-> ***Also in order for all the new Emojis to pop up you need an updated keyboard like GBoard. Some of the new ones do show up in stock Samsung Keyboard but not all of them.

nhihoppro said:
Thanks for your good work. In the future Can One UI get port to s4?
Click to expand...
Click to collapse
EVERYTHING IS ALL DONE! PLEASE TELL ME IF IT WORKS!
Please follow all instruction carefully thanks for checking it out! ?
TheGingerSage said:
-> Download the install files you will need.
All Downloads
*THIS INSTALL PROCEDURE REQUIRES PC*
-> Extract the I9506XXUDOD3_I9506NEEDOD4_I9506XXUDOD3_HOME.tar.md5.7z + RESTORE ALL PARTITIONS + Saved Presets.7z via computer or with ZArchiver on Android Device.
COMPUTER REQUIRED
->On the the computer use ODIN to completely restore LRX22CI9506XXUOD3 Then I need you to boot and completely, setup the phone inside of stock meaning disable all the apps you want to disable, and the sign into google play store.
--> Place the ViPER4Android folder to the root of the Galaxy S4.
--> Place the JamesDSP folder to the root of the Galaxy S4.
--> Create a Backup of just the boot partition in TWRP to genorate the unique folder id in your TWRP Backups folder.
--> Place the folder RESTORE ALL PARTITIONS in the folder next to the (Name of the backup name you create above) folder, found in /data/media/0/TWRP/BACKUPS/*****/
-> Setup Mode...
-> Use ODIN again to flash TWRP
--> Restore Latest Final (*On top of the signed in google play store stock *Do not wipe data or factory reset!)
--> Boot to success!
--> Install Noox FX.apk
-> Video Tutorial...
This is an old video and all the settings changed due to JamesDSP being added to the SDK
So for now view the video to get a general idea while I make a new video for you!
https://www.youtube.com/watch?v=-_iz4opSvqY
Nevermind
Follow this video the sound is actually in it!!! Please use over ear or ear buds
https://www.youtube.com/watch?v=t4SLs37WT3o
-> Music...
Hip Hop
Metal
Click to expand...
Click to collapse

nhihoppro said:
Thanks for your good work. In the future Can One UI get port to s4?
Click to expand...
Click to collapse
The only way we can get it ported is if we find an Android 9.0 with the same chipset (Very unlikely) but keep your eyes peeled and let me know if you find one

Have tried to install, but I can't, I have followed this steps:
1. With ODIN, I have installer this file: I9506XXUDOD3_I9506NEEDOD4_I9506XXUDOD3_HOME.tar.md 5.7z
2. Then, I have booted my device, and then Installed TWRP with ODIN.
3. Then, I copied the ViPER4Android and JamesDSP folder into the root directory of my phone.
4. Then, I did a boot backup, and copied the RESTORE ALL PARTITIONS Folder into the folder where the other backup folder is.
5. Then, I Restored the RESTORE ALL PARTITIONS backup, and then I bootes into the system again.
Idk if I'm forgetting to do some step that is in the tutorial, but I can't find the way to install this I'll be very pleased if someone helps me.
thx in advance

Dedede_ said:
Have tried to install, but I can't, I have followed this steps:
1. With ODIN, I have installer this file: I9506XXUDOD3_I9506NEEDOD4_I9506XXUDOD3_HOME.tar.md 5.7z
2. Then, I have booted my device, and then Installed TWRP with ODIN.
3. Then, I copied the ViPER4Android and JamesDSP folder into the root directory of my phone.
4. Then, I did a boot backup, and copied the RESTORE ALL PARTITIONS Folder into the folder where the other backup folder is.
5. Then, I Restored the RESTORE ALL PARTITIONS backup, and then I bootes into the system again.
Idk if I'm forgetting to do some step that is in the tutorial, but I can't find the way to install this I'll be very pleased if someone helps me.
thx in advance
Click to expand...
Click to collapse
It is actually quite hard to install this, so sorry for the late reply give me a few hours and I'll record a video tutorial of the full install procedure.

TheGingerSage said:
It is actually quite hard to install this, so sorry for the late reply give me a few hours and I'll record a video tutorial of the full install procedure.
Click to expand...
Click to collapse
:good:

Dedede_ said:
:good:
Click to expand...
Click to collapse
What is currently on the GS⁴ you plan to install this on? Is it custom or is the latest stock build on it?
EDIT: go ahead and flash the stock image provided in my zip. Then after it reboots to stock revocery and does its little thing immeadiately boot back into stock revovery and format /data after that reboot to download and flash twrp. Go ahead and re setup the restore of the all partitios 7z now when you do a restore unclick all the options and restore only the EFS partition then reboot into the still unbooted stock image you odin flashed. Make sure cellular wifi etc works (If the downgrade was unsuccessful then some of those will break) if the downgrade was unsuccessful then do the same thing above except omit the EFS restore and instread boot after you factory rest in recovery.

TheGingerSage said:
What is currently on the GS⁴ you plan to install this on? Is it custom or is the latest stock build on it?
EDIT: go ahead and flash the stock image provided in my zip. Then after it reboots to stock revocery and does its little thing immeadiately boot back into stock revovery and format /data after that reboot to download and flash twrp. Go ahead and re setup the restore of the all partitios 7z now when you do a restore unclick all the options and restore only the EFS partition then reboot into the still unbooted stock image you odin flashed. Make sure cellular wifi etc works (If the downgrade was unsuccessful then some of those will break) if the downgrade was unsuccessful then do the same thing above except omit the EFS restore and instread boot after you factory rest in recovery.
Click to expand...
Click to collapse
Once you have stock with no modifications fully functional go ahead and sign in to google and disable the apps you dont use. Here in a few I will post an updated final TWRP image and new preset zip that has my final config that works well on all music tpyes and speaker types.

Last Resort Install Procedure of Just the Audio
Permanently Closed