[ROM][I605VRUFND7][4.4.2]OFFICIAL STOCK ROOTED ODEX/DEODEX[6/19/2014]

[Mace68]

Oh! Yes I did, just forgot to mention those steps lol. Thanks for the quick response though!

I had similar issues. The way i solved it was to power off and pull out my external sd card, I then booted into recovery and formatted all partitions (including the internal sdcard) except for /modem and /boot. I then used the recovery option to reboot into download mode so I could Odin back to 4.1.2 (VRAMC3). Note: It will ask you if you want it to repair root when you go to reboot, I chose not to.

Once in Odin with the phone showing connected I loaded up KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 into the PDA slot and also loaded sch-i605-16gb.pit into the PIT slot. Loading the pit file should enable the Re-Partition checkbox. Should look like this:

With Auto Reboot, Re-Partition and F. Reset Time all (and only those) checked, I clicked start, waited, and everything was successful. The next step was to get back into download mode and Odin flash the 4.3 firmware located here: https://www.androidfilehost.com/?fid=23269279319198557 also using the PDA slot.

I then proceeded with unlock/root using CASUAL 515b and the steps listed in this thread: http://forum.xda-developers.com/showthread.php?t=2272066

After that everything went perfectly with getting 4.4.2 up and running.

Oh one more thing I had to do was install FolderMount and run it once to repair something that was not letting 3rd party apps write to the internal sdcard. I removed it after it applied the fix but it looks like it could come in handy in some situations.

This may be a whacky way of doing things and there are definitely no guarantees, but it's what worked for me.

 

[Sloopdawgg]

I had similar issues. The way i solved it was to power off and pull out my external sd card, I then booted into recovery and formatted all partitions (including the internal sdcard) except for /modem and /boot. I then used the recovery option to reboot into download mode so I could Odin back to 4.1.2 (VRAMC3). Note: It will ask you if you want it to repair root when you go to reboot, I chose not to.

Once in Odin with the phone showing connected I loaded up KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 into the PDA slot and also loaded sch-i605-16gb.pit into the PIT slot. Loading the pit file should enable the Re-Partition checkbox. Should look like this:

With Auto Reboot, Re-Partition and F. Reset Time all (and only those) checked, I clicked start, waited, and everything was successful. The next step was to get back into download mode and Odin flash the 4.3 firmware located here: https://www.androidfilehost.com/?fid=23269279319198557 also using the PDA slot.

I then proceeded with unlock/root using CASUAL 515b and the steps listed in this thread: http://forum.xda-developers.com/showthread.php?t=2272066

After that everything went perfectly with getting 4.4.2 up and running.

Oh one more thing I had to do was install FolderMount and run it once to repair something that was not letting 3rd party apps write to the internal sdcard. I removed it after it applied the fix but it looks like it could come in handy in some situations.

This may be a whacky way of doing things and there are definitely no guarantees, but it's what worked for me.

Thanks for the detailed response but sadly it didnt work

 

[Mace68]

Thanks for the detailed response but sadly it didnt work

Did you try a factory reset after the process? Check section 1 step 7 here: http://forum.xda-developers.com/showthread.php?p=34891181

Sent from my SCH-I605 using XDA Free mobile app

 

[Sloopdawgg]

Did you try a factory reset after the process? Check section 1 step 7 here: http://forum.xda-developers.com/showthread.php?p=34891181

Sent from my SCH-I605 using XDA Free mobile app

Yeah i did. I have not had any issues with booting into any AOSP roms. Its only the 4.4 touchwiz ones giving me trouble.

 

[Mace68]

Yeah i did. I have not had any issues with booting into any AOSP roms. Its only the 4.4 touchwiz ones giving me trouble.

Hopefully someone that has a solution will come across this issue. I don't really have much troubleshooting experience since everything just usually works for me most of the time. I'll post back if I come across anything that looks like it might help.

Sent from my SCH-I605 using XDA Free mobile app

 

[lacoursiere18]

Yeah i did. I have not had any issues with booting into any AOSP roms. Its only the 4.4 touchwiz ones giving me trouble.

Hopefully someone that has a solution will come across this issue. I don't really have much troubleshooting experience since everything just usually works for me most of the time. I'll post back if I come across anything that looks like it might help.

Sent from my SCH-I605 using XDA Free mobile app

Hmm weird can't boot back into this huh?

I would suggest.. /this is what i do when my phone get funky.. go to the General Section.. Follow the directions for the Data Corruption thread.. Than after reflashing the LATEST philz.. reflash this ROM..

 

[Sloopdawgg]

Hmm weird can't boot back into this huh?

I would suggest.. /this is what i do when my phone get funky.. go to the General Section.. Follow the directions for the Data Corruption thread.. Than after reflashing the LATEST philz.. reflash this ROM..

Oh my....Gentlemen...it was a SUCCESS! Thank you so much for the help!

 

[Deejaydark]

Anyway I can get sdswap on this rom?

Beans Build 22

 

[RoyVegasPinoy]

Help flashing this bad boy

I need some simple help flashing this ROM. So the instructions say to "Download the ROM, Radio, and SuperUser.zip." Then I scroll down to the downloads post and see the following:

- New Modem/Baseband: NEW ND7 4.4.2 RADIO

- Deodex/No Knox Version: ND7_deknox_deodex.zip

- Odex/Stock/Rooted/Knox Version: ND7_odex_rooted.zip

- Debloated/Deodexed Version with updated core apps and external SD Fix: vrufnd7_debloat_build3.zip

Which one of those is the ROM, Radio, and SuperUser.zip? Which do I need? Also what does it mean to "Verify MD5 on all of them"?

I'm coming from TWRP recovery with CW11 flashed. Thanks!

 

[Rootabaga]

The ROM is either of the three you have listed. You will have to decide which one you want, deodexed, Odexed or debloated. The pros/cons of each have been discussed at length.

- Deodex/No Knox Version: ND7_deknox_deodex.zip
- Odex/Stock/Rooted/Knox Version: ND7_odex_rooted.zip
- Debloated/Deodexed Version with updated core apps and external SD Fix: vrufnd7_debloat_build3.zip

The radio is the first line you have listed:
- New Modem/Baseband: NEW ND7 4.4.2 RADIO

Superuser.zip is sort of hidden. Towards the end of the OP you will see a line that says:

IF NO ROOT FLASH THIS in RECOVERY

The word "THIS" is actually a link to superuser.zip 1.94

Verify the MD5 of each file using any of the free available MD5 checkers available online. Google it. Try MD5_and_SHA_Checksum_Utility.exe. It ensures that the file you downloaded is absolutely identical to the file on the server and hasn't been corrupted. Each of the above dowloads will have the MD5 value listed that you plug into your checker.

I don't think TWRP works with this. Last time I checked, you have to use Philz recovery. Easy enough. Just look for the latest version of Philz and flash it within TWRP. But then again, it has been a couple months since I was really researching this. That may have changed. You'll have to check

Happy flashing.

 

[RoyVegasPinoy]

The ROM is either of the three you have listed. You will have to decide which one you want, deodexed, Odexed or debloated. The pros/cons of each have been discussed at length.

- Deodex/No Knox Version: ND7_deknox_deodex.zip
- Odex/Stock/Rooted/Knox Version: ND7_odex_rooted.zip
- Debloated/Deodexed Version with updated core apps and external SD Fix: vrufnd7_debloat_build3.zip

The radio is the first line you have listed:
- New Modem/Baseband: NEW ND7 4.4.2 RADIO

Superuser.zip is sort of hidden. Towards the end of the OP you will see a line that says:

IF NO ROOT FLASH THIS in RECOVERY

The word "THIS" is actually a link to superuser.zip 1.94

Verify the MD5 of each file using any of the free available MD5 checkers available online. Google it. Try MD5_and_SHA_Checksum_Utility.exe. It ensures that the file you downloaded is absolutely identical to the file on the server and hasn't been corrupted. Each of the above dowloads will have the MD5 value listed that you plug into your checker.

I don't think TWRP works with this. Last time I checked, you have to use Philz recovery. Easy enough. Just look for the latest version of Philz and flash it within TWRP. But then again, it has been a couple months since I was really researching this. That may have changed. You'll have to check

Happy flashing.

Thank you Rootaba! This is very helpful.

Edit: Gonna give it a try!

 

[RoyVegasPinoy]

Alright I've successfully done everything up to the point where I am to flash the radio. Using Philz recovery, I've wiped, flashed the ROM, rebooted to recovery, flashed superuser. When I try to flash the Radio, it gives me the following:

-- Installing: /storage/sdcard1/ND7_radio.zip
Finding update package...
Opening update package...
Installing update...
Verifying your device
assert failed: getprop("ro.product.device") == "
t0ltevzw" || getprop("ro.build.product") == "t01
tevzw" 11 || getprop("ro.product.device") ==
"t0ltecdma" || getprop("ro.build.product.device == "
t0ltecdma" || getprop("ro.product.device"
) == "i605" || getprop("ro.build.product") == "i
605" || getprop("ro.product.device"")) == "
SCH-605" || getprop("ro.build.product") == "SCH
- I605"
E: Error in /storage/sdcard1/ND7_radio.zip
(status 7)
Instsallation aborted.


What should I do? Thanks.

 

[lacoursiere18]

Alright I've successfully done everything up to the point where I am to flash the radio. Using Philz recovery, I've wiped, flashed the ROM, rebooted to recovery, flashed superuser. When I try to flash the Radio, it gives me the following:

-- Installing: /storage/sdcard1/ND7_radio.zip
Finding update package...
Opening update package...
Installing update...
Verifying your device
assert failed: getprop("ro.product.device") == "
t0ltevzw" || getprop("ro.build.product") == "t01
tevzw" 11 || getprop("ro.product.device") ==
"t0ltecdma" || getprop("ro.build.product.device == "
t0ltecdma" || getprop("ro.product.device"
) == "i605" || getprop("ro.build.product") == "i
605" || getprop("ro.product.device"")) == "
SCH-605" || getprop("ro.build.product") == "SCH
- I605"
E: Error in /storage/sdcard1/ND7_radio.zip
(status 7)
Instsallation aborted.


What should I do? Thanks.

assert failed: getprop("ro.product.device") == "

Did you change or edit your build.prop?? It is failing bc your build product name was modified..

 

[RoyVegasPinoy]

assert failed: getprop("ro.product.device") == "

Did you change or edit your build.prop?? It is failing bc your build product name was modified..

Edit: I remember changing my build prop a while back when I was trying to make google wallet work. How do I restore it?

 

[shadowdweller]

I was wondering if anyone is having battery drain on this ROM? I do use two xposed modules.

I tried SlimRom today. I liked it but it didn't have a lot of the features I've gotten use to from Touchwiz, so I decided to come back. I'm waiting for the kinks to be ironed out of AllianceROM but in the meantime, the thing I liked most about SlimRom was the default dpi. By default, that ROM uses a dpi setting of 245 as opposed to 320 in this ROM. I've edited the build.prop and changed the lcd density to 245 and it looks sweet. However, when I go to use the dialer, it is sitting mostly to the left side of the screen off center. Is there a way to change the dpi for the dialer and any other program?

Thanks for taking your time to read this post.

 

[PhilDX]

I was wondering if anyone is having battery drain on this ROM? I do use two xposed modules.

I've been running the odexed version for a little over a month now and the batt has been fantastic. I was running CM11 before this but I had a recurring radio related wakelock issue that couldn't be resolved. I miss AOSP but got tired of the problems.

FWIW, I don't use exposed.

 

[Rudy_Ruettiger]

I was wondering if anyone is having battery drain on this ROM? I do use two xposed modules.

I tried SlimRom today. I liked it but it didn't have a lot of the features I've gotten use to from Touchwiz, so I decided to come back. I'm waiting for the kinks to be ironed out of AllianceROM but in the meantime, the thing I liked most about SlimRom was the default dpi. By default, that ROM uses a dpi setting of 245 as opposed to 320 in this ROM. I've edited the build.prop and changed the lcd density to 245 and it looks sweet. However, when I go to use the dialer, it is sitting mostly to the left side of the screen off center. Is there a way to change the dpi for the dialer and any other program?

Thanks for taking your time to read this post.

Xposed has a DPI per app module. Also some 3rd party dialers in the play store will work for the smaller DPI as well.

 

[wolfballz]

Since I bought my note 2 from a buddy of mine it was already OTA updated to 4.4.2 ND7. Is there a Odin tar file of ND7 4.4.2 that is rooted and deodexed? I used ghettoroot and am currently rooted but I want to deodex. I followed the thread for deodexing ND7 but after rebooting it would hang on the Verizon logo. I'm assuming Philz recovery won't work since I'm locked down.

 

[DaveKnowsAll]

I was wondering if anyone is having battery drain on this ROM? I do use two xposed modules.

I tried SlimRom today. I liked it but it didn't have a lot of the features I've gotten use to from Touchwiz, so I decided to come back. I'm waiting for the kinks to be ironed out of AllianceROM but in the meantime, the thing I liked most about SlimRom was the default dpi. By default, that ROM uses a dpi setting of 245 as opposed to 320 in this ROM. I've edited the build.prop and changed the lcd density to 245 and it looks sweet. However, when I go to use the dialer, it is sitting mostly to the left side of the screen off center. Is there a way to change the dpi for the dialer and any other program?

Thanks for taking your time to read this post.

I wouldn't call it battery drain issues, so much, as draining like stock. I have greenify running to smooth things out a bit, and the AGNI kernel, but no matter what I do it just doesn't hold the battery like a good custom ROM would. R3D's, for instance, get's much better battery life for me, but the gps won't work so I'm stuck with this for now.

 

[Mace68]

I had similar issues. The way i solved it was to power off and pull out my external sd card, I then booted into recovery and formatted all partitions (including the internal sdcard) except for /modem and /boot. I then used the recovery option to reboot into download mode so I could Odin back to 4.1.2 (VRAMC3). Note: It will ask you if you want it to repair root when you go to reboot, I chose not to.

Once in Odin with the phone showing connected I loaded up KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 into the PDA slot and also loaded sch-i605-16gb.pit into the PIT slot. Loading the pit file should enable the Re-Partition checkbox. Should look like this:

With Auto Reboot, Re-Partition and F. Reset Time all (and only those) checked, I clicked start, waited, and everything was successful. The next step was to get back into download mode and Odin flash the 4.3 firmware located here: https://www.androidfilehost.com/?fid=23269279319198557 also using the PDA slot.

I then proceeded with unlock/root using CASUAL 515b and the steps listed in this thread: http://forum.xda-developers.com/showthread.php?t=2272066

After that everything went perfectly with getting 4.4.2 up and running.

Oh one more thing I had to do was install FolderMount and run it once to repair something that was not letting 3rd party apps write to the internal sdcard. I removed it after it applied the fix but it looks like it could come in handy in some situations.

This may be a whacky way of doing things and there are definitely no guarantees, but it's what worked for me.

Okay, I had to go through all this again and I have verified (twice to be sure) that if you hang indefinitely at the boot logo and cannot get any further after flashing any 4.4.2 ND7 TW ROM you need to format/wipe your internal sd card (/data/media) under "Mounts and Storage" using Philz latest recovery (6.48.4), not TWRP. Seems the two recoveries might format partitions differently and the TWRP method doesn't work in this case.