Database Develop

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

[Q] What's NOT getting wiped when I flash?

I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
Sounds like /data isn't getting wiped or formatted.

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.

Failbringer60 said:
I did a full wipe for the initial install. But for the newest build i wiped system only and flashed on top of the previous build. I can do a full wipe again and reinstall the newest build to see if it corrects my issues. But i can assure you i wiped everything when i installed the previous build.
Click to expand...
Click to collapse
shinobisoft said:
Umm... I'm seen a bunch of references in your posted log that refer to the old sdcard path ( as in stock, /storage/external_SD. New path is : /storage/sdcard1 ). This is telling me that you did NOT format your /system and or /data partition when you installed CM for the first time. Obviously the only way to remedy this is to do a fresh installation following the instructions I posted in the OP.
Click to expand...
Click to collapse
shinobisoft said:
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.
Click to expand...
Click to collapse
I changed the "auto restore" setting so it won't automatically install my apps and tried another "clean" install with the same results. It's almost like I'm restoring from a previous back up! I made sure to wipe and format everything twice just to be certain. Installed only CM and gapps zips, wiping dalvik and cache before booting system. My result was the same as previous..... Choose language.... WiFi connects, and my settings restore.... I am NEVER asked to login to my Google or Cyanogen account(s)......
I'm about to back up and wipe everything, use fastboot to format the partitions? Ideas? Thoughts? Suggestions?
Perhaps restore my "rooted factory ROM" from TWRP back up and start from there? Or restore from .kdz?

Maybe try a factory reset from Settings after installing? Kind of a long shot but that's what I had to do after flashing back to stock when nothing seemed to have changed ...

.3.2.4 Rollback Images

Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image

Reserved

Thanks @ggow !

Thanks for this man.

What are the benefits to go back to 3.1.0 as 3.2.4 is fully rootable and necessary for Nexus 2.0?
I'm still using 3.1/Nexus 1.4 and planned to update the device to 3.2.4/Nexus2.0. But now I'm wondering if I just should keep the current installation.

Unlocked bootloader!

what steps do i take if i m using nexus 2.02 on stock slot?
i have the original stock image 3.2.4 backed up in TWRP if it helps

Warning
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use file (with md5 hash: 0f9f3b084500b888fc66415a8539a341) to rollback attempt! If you downloaded file Apollo Rollback Image before and want to use it later, please redownload, @ggow just posted corrected file (with md5 hash: 119b5004e96a41eb073c8b324712fe23)

jeryll said:
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use this file to rollback attempt!
@ggow you forgot to edit build.prop file, so after anyone boot from this file (md5 hash: 0f9f3b084500b888fc66415a8539a341), kindle will not continue with downgrade to 14.3.1.0 :crying:
No harm done for me, as I backuped everything I can, but beware, if you dont want problems (I found extremely difficult install anything through adb on this installed/running rollback ... you can try edit build.prop file to correct values for downgrade by yourself, but messing with build.prop is highly risky and small mistake and brick is for sure, so you have been warned) WAIT for ggow to upload correct rollback image, or correct edited build.prop for downgrade
Click to expand...
Click to collapse
I have taken the file offline, Sorry about that @jeryll, will correct file and re-upload.

The corrected Apollo rollback image is uploading now. I'll post the new link in the morning.
Sent from my Kindle Fire HDX using Tapatalk

nymica said:
Unlocked bootloader!
Click to expand...
Click to collapse
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?

ands2 said:
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?
Click to expand...
Click to collapse
Yes full TWRP recovery and yes we can effectively install any ROM we want.
Credit goes to @vortox for making it possible with his signature bypass tool.

Corrected Apollo Image
@jeryll,
The corrected Apollo Rollback Image is up.

Thanks
ggow said:
@jeryll,
The corrected Apollo Rollback Image is up.
Click to expand...
Click to collapse
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP

ggow said:
Hello All,
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Click to expand...
Click to collapse
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work

2. Flash the appropriate file for you device
Does it mean: Flash the appropriate (rollback) file for you device (in safestrap) (to Stock ROM slot)?
ggow said:
Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image
Click to expand...
Click to collapse

@shadowcliffs - yes flash the rollback image to the stock slot...

Guess the file has to be flashed to Stock ROM instead of any other rom slot.
andPS2 said:
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work
Click to expand...
Click to collapse

shadowcliffs said:
Guess the file has to be flashed to Stock ROM instead of any other rom slot.
Click to expand...
Click to collapse
Correct

Hi,
Thanks of all your efforts on this. Is it possible to flash the roll back image any other way than installing and using safestrap ?

Issues with Flashing Roms Onto Kindle 7"

Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!

Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear

Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?

IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?

crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/

Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.

Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.

Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.

I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.

Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?

Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.

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