[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB] - Xperia Z Android Development

[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.

Related

[GUIDE] upgrade / root Gingerbread / Froyo, flash custom roms July/05

I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.​
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
​
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update​
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress​
What you need if you want to root your Gingerbread rom:​
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:​
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x​
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me​
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!​
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!​
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954​
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:​
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!​
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy ​
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless ​
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753​
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:​
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"​
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017​
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .

[Q] Jelly Bean Mini Project Noob

Hi all,
First I must point out I'm a bit of a noob at this flashing kernels/roms etc. I want to install Jelly Bean Mini Project | Android 4.1.2 on my xperia x8.
I rooted it ages ago with superoneclick. I got the rom here in the download section of this post and got the kernel here. Not sure how to proceed do i unzip the rom folder called "X8_JBMP-Release4"? I need a tutorial on what programs to use etc. step by step would be handy. I did look did look am continuing to look. Thanks in advance and sorry.
first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy
op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.
many tairsai
cascabel said:
op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.
Click to expand...
Click to collapse
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.
Yanisirl said:
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.
Click to expand...
Click to collapse
titanium backup is good. :thumbup: you can also enter cwm and make a backup there. otherwise, follow mass's instructions. don't forget to format system cache data in cwm after flashing kernel and before flashing rom. have fun with jb. :thumbup:
Just because i don't doesn't mean i can't.
MassStarvation said:
first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy
Click to expand...
Click to collapse
I have correct kernel and the JBMP not sure what GAPPS is.
Yanisirl said:
I have correct kernel and the JBMP not sure what GAPPS is.
Click to expand...
Click to collapse
google apps. i'm not sure about jbmp but naa's minicm10 has a zip file. flash it after flashing the rom.
Just because i don't doesn't mean i can't.
one more noob question
I was wondering about unlocking this phone from the network it is on. Should I get the code and do it first of will I still be able to do it if I wish after the upgrade. Sorry for the noob questions. Thanks for all the other help I have an idea of what to do now.
Sucess!!
Thanks a million guys got it up and running jellybean. First flash of kernel was just sticking on CWM recovery screen no buttons working. flashed back to a stock 2.1 (rom not my original one) and flashed the new kernel again and all went fine. Thank you so much for all this help and thanks to the folks who worked in the release of jellybean. I just need to figure out how to store apps on sd card. time for research.
Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?
U can odex to get more space..find it in android development, made by TeamMex..
If u're DRAGONFORCE lovers please hit THANKS button,,
Yanisirl said:
Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?
Click to expand...
Click to collapse
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store
MassStarvation said:
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store
Click to expand...
Click to collapse
No, it not missing,
strange...
Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:
Yanisirl said:
Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:
Click to expand...
Click to collapse
try a clean flash. i'm on 4.1 and i cam move apps fine. though i don't use the native app2sd.
Just because i don't doesn't mean i can't.
Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?
Yanisirl said:
Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?
Click to expand...
Click to collapse
just format system cache amd data after a full wipe (wipe cache amd dalvik too) and reflash rom.
Just because i don't doesn't mean i can't.
Thanks for the reply. I will try it in a couple of days as I'm busy with work and will post back here with the result.
moving apps
I booted into CWM recovery and used the advanced section to create a 1gb partition left swap size setting at 0 and that fixed the issue. I guess if I wasnt a noob I would have made a partition on the card in the beginning. Apps can now be moved except those that dont allow movement but I am using link2sd for those. Its cool to see jellybean on this phone. I get quite a few hangs/crashes using the browser, bluetooth earpiece connects fine but I cant hear calls on it and the countdown timer is erratic closing by itself quite often. Maybe there are some settings I need to tweak to get the best performance? Thanks again for all the help and replies by the way.

How to solve random reboots and other issues in Lollipop ROMs in S2 hd lte

UPDATED
Since these issues have been fixed in newer builds but as a s2 hd lte users, we have no option but to use older builds which have many issues. I found a workaround for them. If you are having wifi or other radio related issues, contact the ROM developer. This post can't help you. Flashing latest baseband helped me and could work well for you as well. Lets talk about two of the most common bug that haunts our device
1 Apps auto closing->( only for LMY48G builds,if you have newer builds,just flash gapps and reboot. to check go to about phone-> build number)
This is a webview related bug.
Download latest gapps from opengapps.org.
I prefer aroma installer as smaller packages don't have webview included,which will make the bugs worse.
Flash gapps. Dont forget to select 'android system webview' from the aroma installer.
Download the zip file from the
link
https://mega.nz/#!0d5Tiaja
Decryption key !JAG5Im-T75YN1CKIOiOcyDDaBH2ILD6dzwxw4xnhrBc
Extract "libwebviewchromium.so" and "libwebviewchromium_plat_support.so"
It is taken from stock samsung ROM and only works on armv7 devices.
Copy them to /system/libs using ESfile explorer or any other root explorer.
Overwrite the original file if asked.
give permission (-rw-r-r) to both file
Reboot to recovery
Flash this file "cm12.1 android system webview" from this thread(only for cm12.1, will cause bootloops in Xenon hd and resurrection remix)
http://forum.xda-developers.com/xperia-m/themes-apps/mod-google-android-webview-t3109216
Apps will now no longer auto close in your face without warning
((-> After testing for a month, I concluded that these steps are optional and use only if you want to have google android webview instead of cm12.1's built in 'android system webview'))
2) Now the most important part, random reboots.
This was reported on earlier builds of lollipop by many users.This is mostly caused by minfree that android uses to manage memory. If you navigate to sys/modules/lowmwemorykiller/parameters you can see 4 or 5 files. two of those files have wrong permissions. They are "adj" and "minfree".
If you give them (rw-r-r) permissions, you can adjust minfree values. the stock values are too aggressive and would cause constant reboots, freezes. Download romtoolbox, navigate to task manager, swipe left. you can choose to use any presets. i use 8,12,24,60,70,80 as minfree values.
Dont check "auto apply on boot" because you need to repeat this whole process after a reboot as those two files"adj and minfree" will be replaced from boot.img on boot by kern
Permanent fix: unpack boot.img. Navigate to ramdisc and open init.rc file in notepad. Find the line
chmod 0220 /sys/module/lowmemorykiller/parameters/minfree
chmod 0220 /sys/module/lowmemorykiller/parameters/adj
Change both values to 0644
save and close
Repack boot.img
Put it back inside the zipfile using winrar or use flashify from playstore to update boot.
I found tool to unpack qualcomm boot.img from this website. Full credits to the developer who made this tool.
http://www.droidbeep.com/how-to-unpa...-img-qualcomm/
download ROM toolbox and apply your preferred values
3. Low storage and optimizing apps(configuring ART compiler)
After google updated android runtime from JIT to ART, apps take up huge space and "optimizing app" takes forever. But there is workaround for that too.
1)Open build.prop in any text editor.
2) find these two lines:
dalvik.vm.image-dex2oat-filter=........(blah blah)
dalvik.vm.dex2oat-filter=...(blah blah)
3) Change both of these lines to
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=Verify-none
If these lines doesn't exist, in your build.prop,you have to add them manually
4) save your build.prop file
5) reboot to recovery and wipe dalvik cache
After this check your storage space, You will have plenty of storage left and optimizing apps should be faster. It works just like old JIT compiler from older android versions.
if this doesn't work for you, you have to edit these same lines from default.prop by unpacking boot.img
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
diabolicalprophecy said:
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
Click to expand...
Click to collapse
please, for e120s
OIAUser said:
please, for e120s
Click to expand...
Click to collapse
Please extract Boot.img from the zip file and send it. I don't have boot.img for e120s, or i can tell you how to do it yourself if you are interested.
Tell me how, I'll try to do it myself.
I will be very grateful
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
OIAUser said:
Tell me how, I'll try to do it myself.
I will be very grateful
Click to expand...
Click to collapse
I have updated the post on how to do it. You can find the required tool here with detailed instructions
http://www.droidbeep.com/how-to-unpack-and-repack-boot-img-qualcomm/
kdlinh said:
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
Click to expand...
Click to collapse
You can try wiping phone efs through odin in order to fix radio issues
1 Download stock jb rom
2 Check "phone efs clear". This is most important.
3 Click pda
4 click start
5 wait for phone to boot up
6 go to settings->software update to check if you are running latest jb build. Soft reboots and radio issues are usually caused by old baseband version.
7 Proceed with usual old way to install lollipop.
This way odin will wipe your efs settings to rebuild from scratch.
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
kdlinh said:
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
Click to expand...
Click to collapse
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
diabolicalprophecy said:
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
Click to expand...
Click to collapse
i have checked this efs box but failed :crying::crying:
kdlinh said:
i have checked this efs box but failed :crying::crying:
Click to expand...
Click to collapse
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
OIAUser said:
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
Click to expand...
Click to collapse
you get "libWebviechromium .so" file while installing gapps package. Go to opengapps.org and download aroma installer.
there are two files in the archive i uploaded, libwebviwechromium_loader.so and libwebviewplatsupport.so. You need to extract and replace those files in system-> libs after flashing gapps package. The built in webview will cause random apps shutdowns. this file is critical. You need libwebviewchromium_loader to start webview app. your system will not function properly without it.
diabolicalprophecy said:
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Click to expand...
Click to collapse
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
kdlinh said:
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
Click to expand...
Click to collapse
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
diabolicalprophecy said:
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
Click to expand...
Click to collapse
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
kdlinh said:
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
Click to expand...
Click to collapse
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
diabolicalprophecy said:
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
Click to expand...
Click to collapse
can you give me the links , at least what i can do now is tried to install your baseband
it will brick your phone. Its for E120L only

[CLOSED] [STOCK] [DOWNGRADE] [08-Mar] Revert back to older firmware (v309 till v339) via TWRP

Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1809.331[/U] on primary device. Also I will try to help out in case of issues.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system downgrade.
How to ,
Backup important app data like whatsapp chats etc.
Download older modified system update file - FROM THIS POST.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Thank you soo much ...was really waiting for it..
Question
AVinaSh_S said:
This thread is for those who are on stock rooted rom with TWRP installed and want to have system downgrade.
How to ,
Backup important app data like whatsapp chats etc.
Download older modified system update file - FROM THIS POST.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Click to expand...
Click to collapse
Thank you so much for the answer Sir AviNash. I've got a question, if I swipe to factory reset, all my downloaded apps would be gone? Or their settings only? I am hesitating to downgrade because I am thinking that it would lost all my downloaded apps including the data. Am I correct sir?
MJorgeAbad said:
Thank you so much for the answer Sir AviNash. I've got a question, if I swipe to factory reset, all my downloaded apps would be gone? Or their settings only? I am hesitating to downgrade because I am thinking that it would lost all my downloaded apps including the data. Am I correct sir?
Click to expand...
Click to collapse
Yes .. factory reset will remove all app setting and app data. You will need to backup appdata on cloud.
Storage data on SD card will not be touched. To be safe .. backup data on Internal Storage as well.
AVinaSh_S said:
Yes .. factory reset will remove all app setting and app data. You will need to backup appdata on cloud.
Storage data on SD card will not be touched. To be safe .. backup data on Internal Storage as well.
Click to expand...
Click to collapse
Now my phone is on v331, and this 331 version is bad,.. worse than the 327, but instead of downgrade to 327, I prefer to wait for your "334 upgrade file for 'UBL-TWRP&Root' user" like you did with the 331
Ty Avinash
Thanks for this
sir,can you give a tutorial to edit firmware updates for flashing on twrp?
AVinaSh_S said:
This thread is for those who are on stock rooted rom with TWRP installed and want to have system downgrade.
How to ,
Backup important app data like whatsapp chats etc.
Download older modified system update file -FROM THIS POST.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP :https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Click to expand...
Click to collapse
hi..I've just downgrade to 327.
And your guide is superb, as usual. Everything is smooth. Big thanks!
Wheres downgrade rom file?
simpang said:
Wheres downgrade rom file?
Click to expand...
Click to collapse
Hmmm
Maybe look in post #1
Or just click here
Boomshiva said:
Hmmm
Maybe look in post #1
Or just click here
Click to expand...
Click to collapse
Lol,i cant see..
What's the best version till now, I am on January update but after a day or two the phone stops working and have to restart.
jassalmithu said:
What's the best version till now, I am on January update but after a day or two the phone stops working and have to restart.
Click to expand...
Click to collapse
Latest update 339 is proven to be stable and reliable release. Probably it's your phone hardware issue.
Maybe you can try to clear the cache first. If that does not work then try reset the phone. If still doesn't work then bring it to service center.
THREAD CLOSED on request of OP!

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

Categories

Resources