Database Info

DI18 update for non-stock files/kernels - *now with deodexed ROM!*

For those who removed stock files/apps and can't update with the normal update, here's a modified version that will work for you.
This update will not trash your recovery or root. You do not need a stock kernel for this update.
It will restore the required stock files/apps and update your modem from DI07 to DI18.
Update to DI18 - flashes new DI18 kernel
md5: ebfe0a1d4e59819a1fa35ff115f2b1b2
Update to DI18 - keeps existing kernel
md5: c686afd641f502bc88fc79796500592c
It's been tested on my phone and a few others and confirmed to be working. This also removes mobileAP i9000 modifications fully and restores stock build.prop (so you won't get the fingerprint assert).
DEODEXED ROM BELOW
Stock DI18 Deodexed FULL ROM update v3
This is a FULLY STOCK deodexed DI18 ROM update.zip! Flash with clockworkmod and you will get the -full- DI18, kernel and modem from DI18. It is not pre-rooted.
md5: f23c9fce3304145f0e8665a97dd1b863
Stock DI18 Deodexed FULL ROM update v3 *no kernel or modem*
md5: a54036b554b4ae8df20e5f685a88fcbd
Changes:
v3 - fix phone and camera FCs (thanks noobnl!)
v2 - removes existing .odex files and clears your dalvik-cache to solve FCs with various apps. If you flashed v1, you can fix it without reflashing
v1 - initial release
Use One click root 2.2.5 to root this ROM (w/ superuser support). I may post a pre-rooted ROM later.
*Additional Notes*
If you're on a fully stock ROM, then you don't need my update and can use the official Samsung DI18 update
Standalone DI18 modem updater, works regardless of what modem/baseband you have installed - md5: 4f897cf5a82d11926be68bd2594d0cf3
Standalone DI18 kernel updater, will flash stock DI18 kernel - md5: bb057a476af2e236cc34224c8b537226
Bluetooth will break if using non-DI18-based kernels. Upload speeds will not improve without a DI18-based kernel.

Just what I need thanks bro
Sent from my SPH-D700 using Tapatalk

I can personally attest to this working. Still retained root. Still have Bose v2 and mixup running. Everything is exactly the same before the update. Thank you!!!!
Sent from my SPH-D700 using XDA App

Dude your awesome. This worked great and only added email and mobile ap. Didnt add anything else. Question tho can i still use noobnls rom with this new update or do i have to wait for a compatible one?
U need a donate button i would give u a few bucks for this. Now i expect a update like this every ota update lol jk. Great work bro.

Works like a charm. However, speeds didn't improve for me, and now it says my build is Tha Boss Rom - MixUp kernel. Even though I've never installed/flashed Boss. Nice work either way.

Thank you, this worked perfectly!

Does it work with themed roms?

Just installed the update, and everything seems to be working fine. Is the Firmware version still supposed to read "2.1-update1"?
id_twin said:
Works like a charm. However, speeds didn't improve for me, and now it says my build is Tha Boss Rom - MixUp kernel. Even though I've never installed/flashed Boss. Nice work either way.
Click to expand...
Click to collapse
Installing just the MixUp kernel will make it read that - the kernel was made custom for that ROM.

Thanks ragnarokx, good to know.

ragnarokx said:
Just installed the update, and everything seems to be working fine. Is the Firmware version still supposed to read "2.1-update1"?
Click to expand...
Click to collapse
Firmware hasn't changed.
I'm gonna make a second version that also updates your kernel, since this update did actually bring a new kernel. But many of you probably wanna stick with your custom kernel, so I'll just offer both up.

id_twin said:
Thanks ragnarokx, good to know.
Click to expand...
Click to collapse
np.
also, i just noticed this update breaks the vanilla lockscreen mod i even tried reinstalling it.

Worked like a charm. Thanks!

Awesome, Thanks!

Firon said:
Firmware hasn't changed.
I'm gonna make a second version that also updates your kernel, since this update did actually bring a new kernel. But many of you probably wanna stick with your custom kernel, so I'll just offer both up.
Click to expand...
Click to collapse
Yep sticking with the fluff kernal its treat me well.
@Firon Do u know if i can still use noobnls andomedia rom with this new update, since its based off the d107?

Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.

you have to use clockwork to flash it

hookerforjesus said:
Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.
Click to expand...
Click to collapse
Try the zip from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=796885
I was like you, rooted but no other changes. I just renamed that file to update.zip put it on my sd card and did a stock recovery. Worked perfectly and didn't affect root.

hookerforjesus said:
Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.
Click to expand...
Click to collapse
for the stock recovery u have to rename the zip to update.zip.

Well, this really sucks. I installed and now my stock music app wont open. It keeps force closing on launch..
I had music mod installed before i updated, and now i cant get it to run even after reinstalling.

Bluetooth not turning on after this flash..anyone else?

Back to Honeycomb with Nandroid

I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.

crankerchick said:
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
Click to expand...
Click to collapse
I would really advise that you flash the most recent EOS wingray. Rom #36 and the GApps (Google System apps) package version 10. It seems to be more complete than the ota update, it's easier to flash and you preserve your root and recovery.

Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!

crankerchick said:
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
Click to expand...
Click to collapse
True, that.
EOS wingray version 36 with the version 10.1 GApps really fixed most of the remaining issues. There should be a new nightly and there is a new GApps 10.2 to flash today.

[Q] JB update and custom kernel

Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app

Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible

Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2

Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse

andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!

Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.

To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:

andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?

Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?

Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!

A few questions about flashing and kernels.

Since I want to flash the thalamus kernel on my Nexus S with JB, I have to be on a rom and given that no JB factory image is available yet I don't really get what I should do.
When the OTA came out I was on a deoxedex, zipaligned, etc. stock rom of ICS, so, in order to elude the error status 7 issue I flashed the 4.0.4 factory image from google and then flashed the OTA update.
If I want to flash a JB rom, do I have to re-flash an ICS rom? And if so, can it be a non-stock rom or I would get the error status 7 message again?

No. You just need to make sure you have a custom recovery, like CWM. I was on ICS and then flashed a JB ROM with no issues.

chronophase1 said:
No. You just need to make sure you have a custom recovery, like CWM. I was on ICS and then flashed a JB ROM with no issues.
Click to expand...
Click to collapse
Well, factory images just came out so it's fine now.

Haha. I was JUST about to post that. Good news for everybody.

Proper way to Flash Jelly Bean ROMs?

Trying to solve a lag/crash issue with any ROM I install on my or my wifes phone. Reading the forums I've seen references to needing to install the official Jelly Bean RUU before flashing a Jelly Bean ROM like Viper XL, etc.
To do this, do I need to be S-OFF first?
Both our phones are already rooted (never took the 2.20? update, so never any issues with root).
Would it be something like this?
S-OFF the phone.
Install Jelly Bean RUU
Re-root
Install Jelly Bean ROM
Thanks!

that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?

Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X

ECEXCURSION said:
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
Click to expand...
Click to collapse
cwm ftw!!!
do the touchscreen driver downgrade like ECEXCURSION said though.

DvineLord said:
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Click to expand...
Click to collapse
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.

jburkco said:
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
Click to expand...
Click to collapse
You'll want to:
s-off
run ruu
update if your ruu doesnt include the latest update.
ruu will not relock your bootloader nor do you need to relock so no need to unlock or reroot.
fastboot flash recovery. i suggest twrp 2.3.x
then you can downgrade your touchscreen if you intend to use an older recovery or an aosp rom but i like to think the updates made improve things so i wouldnt downgrade unless you need to for an aosp rom or older twrp version.
flash whatever rom you like! if you just want stock rooted boot to recovery after flashing and it will prompt to root your rom when you go to reboot from within recovery.
good luck and have fun!

Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0

jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
-JB touchscreen firmware does not work with AOSP roms. Your touchscreen won't function.
-TWRP 2.4.x seems to cause problems with flashing for a lot of people.

jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
you need to downgrade touchscreen driver so you can use non-jb sense roms such as aosp roms and ics sense roms. he meant to say twrp 2.3 vs 2.4, twrp 2.4 can give many users random issues. i personally haven't had a single issue with official cwm.

Okay but since I'll be using ViperXL, the touchscreen wont be an issue. Thanks for all the help everyone.

2.4 doesnt properly wipe partitions and remnants are left behind causing issues.