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

[krowley3]

So I'm up and running with no issues so far. I am wondering though about ART. I noticed the phone on first boot went pretty quick when you said it would take awhile. Also when I enabled developer options I don't see the option to choose between ART / Delvik. Maybe this is unique to TW but on all the ASOP Roms I tried there was an option in developer settings. Thanks guys! Good work!

I am not 100% sure ART is included in this. We were talking about this yesterday and I think there was some confusion. ART is possible, but I am not finding the proper lib to enable it included. We will dig into this more as time permits.

So how long does it stay on the red screen. Mines been sitting there for 20 minutes. Pulled Battery and restarted but still staying there...

Believe it or not, this is my eighth build of the deodexed version. Just making sure it is all good and all the crap was gone. I have flashed this rom more that you can even imagine and it never not booted once. I am seeing between 7-8 minutes with a complete wipe/format of everything. Some others also had issues booting the N7105 port. We tried everything to get them going and in the long run it took them Odining back to 4.1.2, unlocking the phone again, install recovery, install 4.3 firmware only and then flashing 4.4.2 before it would fully boot. I am not sure what exactly is causing this, but no one on this team has had a single issue booting/using any of our 4.4.2 roms. Hope this helps.

I'm stuck on the vzw red screen too. It hasn't been 20 minutes yet, but it didn't get stuck this long with the odexed version.

Sent from my SCH-I925 using Tapatalk


---------- Post added at 10:30 PM ---------- Previous post was at 10:27 PM ----------

Trying again, this time with latest Philz in place of twrp 2.7.0.1. Will report back.

Sent from my SCH-I925 using Tapatalk

---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------

Well, no luck with Philz either. Stuck on the vzw screen for over 10 mins. Going back to the odexed version and waiting for next release.

Sent from my SCH-I925 using Tapatalk

See my comment above.

Op says 20+ min....on the other hand mine went too quick but everything works as far as I can tell.

20 minutes was on the safe side. When I first began working on it, at first boot when setting up Google account, it would freeze, I have since fixed that in my boot that is currently uploaded.

Question... Why isn't the boot IMG and modem official when you have the leak?

Sent from my SCH-I605 using XDA Premium 4 mobile app

We were lucky to get the system dump. If we would have been able to, we would have got the boot.img and modem. Feel sorry for the people who actually take the OTA because there is not currently any options as far as rooting is concerned. We tried EVERYTHING. We wanted to at least get this out there so that we had a base to build off of. We can start modifying files now and they will be ready once I get the official tar and break it down. We did the best we could with what we had.

Mine went stupid fast.

A few minutes at most.

Same here. Hope you enjoy.

Mine also froze up on the red Verizon screen.

I went back into recovery, wiped cache & system (NOT data), then reinstalled the rom. That seemed to fix it.

Glad to see you are up and running.

got it up and running with a few random reboots. Went back because some apps have yet to support ART. force close sucks. Anyway to revert back to delvik? I dont see that option in developers options.

Disregard the ART comment because after looking at it, I dont believe it is included because necessary files are missing for it to work.

Is anyone else having problems with the SD card and certain things not being able to mount? I tried the SDFix: KitKat Writable MicroSD app and that didn't fix it so I did a fresh install and tried flashing EXternal_Storage_Fix.zip found over in the ported 4.4.2 ROM forum with no luck.

To give a few examples so far it's limiting me from using Solid Explorer, it just says unable to execute command, then I'm having problems downloading files from Google Drive, it just says download from Google Drive failed. Another one I noticed is the camera in Instagram didn't work because it said it can't find the SDCard or something like that. I understand this is a huge deal, but other than the weird SDCard issue everything else seems to be fine.

I am not having this issue. I do have the 4.4 issue where you cannot copy/paste to sdcard. I have not attempted to fix that on this rom yet, but will look into it when I have time. I do not use Instagram, but I was using Google Drive last night without any issues. Maybe try a clean install by including formatting internal memory. I use philz, wipe everything at least twice, format system, format data, format cache, format boot, and format data and data/media (/sdcard) before every install.

 

[vwftw]

Is anyone else having problems with the SD card and certain things not being able to mount? I tried the SDFix: KitKat Writable MicroSD app and that didn't fix it so I did a fresh install and tried flashing EXternal_Storage_Fix.zip found over in the ported 4.4.2 ROM forum with no luck.

To give a few examples so far it's limiting me from using Solid Explorer, it just says unable to execute command, then I'm having problems downloading files from Google Drive, it just says download from Google Drive failed. Another one I noticed is the camera in Instagram didn't work because it said it can't find the SDCard or something like that. I understand this is a huge deal, but other than the weird SDCard issue everything else seems to be fine.

I have the same issue with writing to storage. The External_Storage_Fix only fixes this for the external SD card, not the internal storage. If you flash the fix you will be able to write to /storage/extSdCard/ without issue. The internal storage is not working for a different reason, and I have yet to fix it on my device.

---------- Post added at 09:20 AM ---------- Previous post was at 09:06 AM ----------

Okay, I am not having any of the internal storage issues when using the 4.4.2 AGNi kernel for N7105. Here is a link:
http://forum.xda-developers.com/showthread.php?t=2602053

 

[jmart75]

I am not having this issue. I do have the 4.4 issue where you cannot copy/paste to sdcard. I have not attempted to fix that on this rom yet, but will look into it when I have time. I do not use Instagram, but I was using Google Drive last night without any issues. Maybe try a clean install by including formatting internal memory. I use philz, wipe everything at least twice, format system, format data, format cache, format boot, and format data and data/media (/sdcard) before every install.

I have the same issue with writing to storage. The External_Storage_Fix only fixes this for the external SD card, not the internal storage. If you flash the fix you will be able to write to /storage/extSdCard/ without issue. The internal storage is not working for a different reason, and I have yet to fix it on my device.

---------- Post added at 09:20 AM ---------- Previous post was at 09:06 AM ----------

Okay, I am not having any of the internal storage issues when using the 4.4.2 AGNi kernel for N7105. Here is a link:
http://forum.xda-developers.com/showthread.php?t=2602053

I took @krowley3 advice and used Philz instead of TWRP and was able to get it to work normally. However when I flashed philz_touch_6.41.6-i605.zip my phone would just bootloop on the first Samsung Note II screen. I had to odin back to 4.1.2 and go through all the steps to get my recovery working again. I actually went through that process 3 times. I my checksum and everything matched on the Philz recovery, but for some reason my phone did not like it. I switched to the previous version of Philz, philz_touch_6.26.6-i605.zip, and was able to get it to work. I wiped everything twice, installed the new ROM, and so far I'm able to use Solid Explorer which didn't work before, but I just tried to download a file of Google Drive and it failed. I can click on a file in Drive and open it, but if I want to download the file it won't work. I'm going to continue installing apps to see what other things are still acting up for me.

I installed the AGNi kernel that @vwftw linked too and as he stated it fixed the internal storage issues I was having. Not that Instagram is the most important thing, but I can say it's working the way it should be withe the AGNi kernel.

 

[scoobysnack]

OK signature lock screen is now working. Still working on the rest of AC.

 

[*Hooligan*]

Krowley, I will try again. I was not saying there was anything wrong with the ROM at all. It was just what I was getting. I was coming from Beansrom Version 26. I formatted Cache and Dalvik and formatted Data. I typically only use TW roms. I will try wiping system, data and all that like you said. I just didnt really want to Odin everything back. I havent had to re-odin anything since I rooted my Note 2 since I got it (when the note 2 first came out) except for MJ9. I really dont remember all the steps to re-do all that..lol...

Anyways, I will re-do it just to see what happens after system wipe and all. Typically this is what I do and never had a problem.

1. Factory reset
2. Clear cache and dalvik
3. Format Data.
4. Load Rom
5. Clear Cache and dalvik again
6. Boot and enjoy...

Never had an issue following these steps but like I said I usually stick to TW or something based from it. I will let you know though...

Thanks for providing some insight though and thanks to the team for providing the ROM for us ...

 

[jmart75]

Pretty Good

With the AGNi kernel things are working much better for me. The only problem I'm seeing so far, especially on apps with little to no permissions, is a "couldn't install on USB storage or SD card" error. It isn't a deal breaker, but it's annoying when you can update an app because of it. I'm currently formatting my SD card and going to start over. We'll see if that helps at all.

UPDATE: formatting the SD Card and then transferring the data back didn't fix my "couldn't install on USB storage or SD card" error.

 

[nlysurferdude03]

Krowley, I will try again. I was not saying there was anything wrong with the ROM at all. It was just what I was getting. I was coming from Beansrom Version 26. I formatted Cache and Dalvik and formatted Data. I typically only use TW roms. I will try wiping system, data and all that like you said. I just didnt really want to Odin everything back. I havent had to re-odin anything since I rooted my Note 2 since I got it (when the note 2 first came out) except for MJ9. I really dont remember all the steps to re-do all that..lol...

Anyways, I will re-do it just to see what happens after system wipe and all. Typically this is what I do and never had a problem.

1. Factory reset
2. Clear cache and dalvik
3. Format Data.
4. Load Rom
5. Clear Cache and dalvik again
6. Boot and enjoy...

Never had an issue following these steps but like I said I usually stick to TW or something based from it. I will let you know though...

Thanks for providing some insight though and thanks to the team for providing the ROM for us ...

Like you, I never had a problem until trying this 4.4.2. update. Typically, you're doing the right steps. But, when everything you know isn't working, no matter how many countless hours you've been trying, sometimes it's just not gonna work without starting over from scratch from the beginning. I didn't want to do it either but it took a whole half an hour to go back to stock and get this rom up and running first try no problems.

Like you, I didn't want to go all the way back to square one, because I didn't think there was an issue with my phone or flashing process, and every other rom was flashing fine. Little did I know it wasn't the flashing process, but it WAS indeed the phone. Sometimes things get messed up somewhere along the line with all these updates. There's a thread at the top of the development section, and original development section that will get you where you need to be as far as getting back to 4.1.2, rerooting and unlocking the BL, updating your recovery and the mj9 perams, and then you should be good to flash this rom without issue. Good luck, and hopefully you don't continue spinning your wheels trying what you've been trying unsuccessfully.

 

[*Hooligan*]

Like you, I never had a problem until trying this 4.4.2. update. Typically, you're doing the right steps. But, when everything you know isn't working, no matter how many countless hours you've been trying, sometimes it's just not gonna work without starting over from scratch from the beginning. I didn't want to do it either but it took a whole half an hour to go back to stock and get this rom up and running first try no problems.

Like you, I didn't want to go all the way back to square one, because I didn't think there was an issue with my phone or flashing process, and every other rom was flashing fine. Little did I know it wasn't the flashing process, but it WAS indeed the phone. Sometimes things get messed up somewhere along the line with all these updates. There's a thread at the top of the development section, and original development section that will get you where you need to be as far as getting back to 4.1.2, rerooting and unlocking the BL, updating your recovery and the mj9 perams, and then you should be good to flash this rom without issue. Good luck, and hopefully you don't continue spinning your wheels trying what you've been trying unsuccessfully.

Lol....yeah I knew there was a thread to help with walking you through starting over. I really don't have the time to do it right now. I retried it by wiping everything but still got the same results. I'm sure it's probably just the phone though. I'm on nephilim right now checking it out. When I get more time to spend I'll probably start fresh. It's all good.

I've just started a new business (spa) and all my spare time is spent with it right now.

Hooligan

Sent from my SCH-I605 using XDA Premium HD app

 

[Dugall12]

I came from SR 4, backed up using Krowley's modified CWM did a factory reset, wiped cache and Dalvik installed this with no issues. It booted up within 4 minutes and is working fine. I did have a few glitches though when playing audio over Bluetooth, but otherwise everything appears ok. Thanks for the update gentlemen.

Sent from my SCH-I605 using XDA Free mobile app

 

[athack]

IM on n3bula 3.9 now, has anyone had any issues flashing this using twrp v2.7.0? debating on flashing this or the l18 other 4.4.2 rom the ported with s5 features any opioions on the 2 would greatly be appreciated?

 

[rostar17]

Install from 4.1.2 custom rom

Can I install this from Jedi X20 4.1.2 VRAMC3 to this rom without locking my bootloader? I was under the impression that updating the firmware any higher that VRAMC3 would lock the bootloader making any custom recovery and custom rom installation impossible. Is there a 4.3 firmware with the bootloader unlocked that I can flash with odin?

Thank you

 

[Protocol114]

IM on n3bula 3.9 now, has anyone had any issues flashing this using twrp v2.7.0? debating on flashing this or the l18 other 4.4.2 rom the ported with s5 features any opioions on the 2 would greatly be appreciated?

I wiped cache and system from 2.7.0.1, coming from SR 4. Didn't even wipe Data. Retained all my apps and the OS functions perfectly fine.

It's still probably a good idea to do a full wipe, but I don't want to have to download all my apps... again.

 

[Deejaydark]

Im coming from beans build 22. Do a full wipe with latest philz recovery. Install kit kat. Reboot... and all I get is a red screen with the verizon logo pulsating for well over 20 mins (I just let it sit to see how long it will take) am I missing something?

"Beans Build 22"

 

[webleeper]

I am not 100% sure ART is included in this. We were talking about this yesterday and I think there was some confusion. ART is possible, but I am not finding the proper lib to enable it included. We will dig into this more as time permits.

Believe it or not, this is my eighth build of the deodexed version. Just making sure it is all good and all the crap was gone. I have flashed this rom more that you can even imagine and it never not booted once. I am seeing between 7-8 minutes with a complete wipe/format of everything. Some others also had issues booting the N7105 port. We tried everything to get them going and in the long run it took them Odining back to 4.1.2, unlocking the phone again, install recovery, install 4.3 firmware only and then flashing 4.4.2 before it would fully boot. I am not sure what exactly is causing this, but no one on this team has had a single issue booting/using any of our 4.4.2 roms. Hope this helps.

Im coming from beans build 22. Do a full wipe with latest philz recovery. Install kit kat. Reboot... and all I get is a red screen with the verizon logo pulsating for well over 20 mins (I just let it sit to see how long it will take) am I missing something?

"Beans Build 22"

I was on the same boat as you... I followed @krowley3 instructionson flashing back to 4.1.2 and everything worked

 

[Deejaydark]

I was on the same boat as you... I followed @krowley3 instructionson flashing back to 4.1.2 and everything worked

Beans build 22 is 4.1.2

"Beans Build 22"

---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------

And im using the mj9 baseband

"Beans Build 22"

 

[JeramyEggs]

Something gets corrupted on the data side when flashing, and using titanium back up. Most likely if you are getting the red screen, you should follow the advice. It doesn't take too long, and you start from a completely clean slate.

Sent from my SCH-I605 using Tapatalk

 

[rufflez2010]

Can I install this from Jedi X20 4.1.2 VRAMC3 to this rom without locking my bootloader? I was under the impression that updating the firmware any higher that VRAMC3 would lock the bootloader making any custom recovery and custom rom installation impossible. Is there a 4.3 firmware with the bootloader unlocked that I can flash with odin?

Thank you

There are plenty off MJ9 ROMS out there, they require a MJ9 Firmware to be flashed via odin to get WiFi to work. This is a modified version that doesn't update the bootloader. I'm using the MJ9 Firmware with all of these ROMs without issue. Hopefully someone will be able to extract the Radio from the official build soon. Unfortunately anyone receiving this update via OTA will not have a rooted device and therefore can't have us DD the Radio. I don't know if maybe it can be extracted from the download if someone can catch the Download link whenever that happens to the masses.

 

[Dugall12]

Had to revert back.

I was able to get this installed with very little difficulty coming from SR 4 Remix. Had some Bluetooth issues while playing audio then later on in the day I was getting system process not responding and 5 reboots in a row. Then my backups didn't work, tried fresh install SR 4 Remix, had errors, finally installed and suck on boot animation. Had to Odin all the way back and unlock again.

Sent from my SCH-I605 using XDA Free mobile app

 

[brentsten]

I flashed this from the latest beans build (build 26) through philz recovery. Wiped data, cache, dalvik before flashing and after installing this, it sat on the red Verizon screen for less than 5 minutes before booting up. I was getting frequent reboots until I flashed the agni kernel for the N7105 and now everything works perfectly. Boeffla sound is stellar through my car aux input, Wifi works, extsdcard works, haven't tested bluetooth or miracast yet. Everything is definitely snappier with the new kernel and no more random reboots. Gps locks fairly quick, but isn't 100% accurate.. There's a small bubble around me where I "might" be. Thanks for the rom!

 

[drewcam888]

So initally the stock keyboard had the symbols in the visible background of each key. In my disabling of the rom I have remived that feature. Any guesses on what I turned off that caused this.