My mistake .... the build.prop edits did remove the ED2 update requests. NOW I have the EE4 update trying to be pushed to the phone and I thought it was still the ED2 .... Will taking the EE4 kill the root? I am running the stock ED1 root rollback Odin with edited build.prop
why are you still avoiding ed2 to begin with? it was rooted weeks ago.
Related
This stuff is not for the faint of heart !! Bricking a $300.00 phone is stressfull !!
Okay ... after much trial and error, this is what I did and I have what looks to me to be a stock rooted EE4. I am sure it is not stock as I used imnuts' debloated tar but that's fine, it is working and not trying to send me an update.
Okay, regardless of what I went thru to get to this point, these are the steps I took to have the phone updated to EE4 and rooted.
via Odin 3 I rolled the phone back to ED1 using the [ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18] file found in the Dev forum.
The phone re-booted and was again a stock rooted ED1 and it was trying to push me the EE4 update. I DID NOT update the phone OTA.
I immediately took the battery back out and went back into Odin and flashed imnuts' debloated ee4 file found at [ROM][06-10-2011] EE4 Debloated V4.2.1 in the dev forum.
When re-booting after this flash, the Samsung logo stayed on the screen for what must have been a good 8+ minutes. There was a sexy female voice that would occasionally talk to me and soothe my nerves during this process. The phone rebooted !!
After flashing I rebooted and the phone was trying to push the ee4 update to me. I went into 'about phone' and checked and what it showed was
Baseband Version
i510.06.V.EE4
SCH-I510.EE1
Build number
SCH-I510.ED1
I then went into the build.prop editor using SGS Tools and changed all instances of ED1 to EE4. I believe there are 5 of them to change.
After saving the changes I rebooted the phone. Upon re-start, I went back in and checked the build number and it is
SCH-I510.EE4
The phone is not attempting to send any system updates and it IS rooted.
I then went into it with Titanium and deleted a lot of the useless pre-installed apps.
So far so good. It looks to me like it's where I wanted it.
Dude, that's complicated. But if it works, then it works. Cant complain against that, huh?
Here is what I did.
Flash back to stock ED1 rooted. Take the OTA update, flash droidxcon's ee4 package 3, flash kejar's sdcard fix, flash imnuts debloated v4.2.1, and boom. You're rooted EE4 with EE4 basebands.
After that, I flashed Gummy.
LOL... I think it's actually less complicated than I am wordy !!!
Rollback to ED1
Flash imnuts debloated EE4
Edit build.prop
That's all there really was to it.
That gives EE4 Basebands and EE4 Build
The rest of the book was just me explaining the process I took in checking everything.
But like ya said, it's the end result that matters !!
I recently installed the Altered Beast ROM and the system update notification recurs ad nauseum. I know not to install the update, but I'm wondering if there is a way to turn off the notification so I don't have to deal with it constantly.
It sounds like you never did the OTA to EE4 or never flashed the EE4 factory ODIN to update your baseband.
http://forum.xda-developers.com/showthread.php?t=1172182
You shouldn't be getting any update notifications after your baseband is
i510.06 V.EE4
SCH-I510.EE1
Check under about phone in the settings menu.
No, I think you flashed EE4 altered beast without updating your baseband(modem) the network sees your baseband isn't up to date and is trying to update.
You need to flash the ODIN I linked to update your baseband. Then if you want Altered Beast flash that. It doesn't include the EE4 modem.
Acctually you could just flash this http://forum.xda-developers.com/showthread.php?t=1181827 to update the radio and you should be good to go.
Hey guys, so I just recently updated my Cappy from 2.3.4 to 2.3.5 KK4 using a couple of the forums found here on XDA. Question, though:
I attempted to apply the Fugu Root Mod before flashing to 2.3.5. When flashed, it showed the red Fugu fish, and then bootlooped on me until I pulled the battery. After that, I flashed the 2.3.5 update. Apparently, Fugu has failed on part of my own error, because I don't have SU, BusyBox, or any of the Fugu mods, and the kernel in the phones "About" section shows "2.6.35.7-I897UCKK4-CL614489."
The question: I don't really care to give rooting another go, and I've discovered the "fugumod" folder in my SD's directory. Of course, the file tells me not to delete it, but is it safe to do so being that the root was not applied?
Thanks in advance!
I'm gonna be gettin a G-Nex & givin the Charge to my wife. I took it back to stock, rooted it and de-bloated with TiBu. I had been using the imnuts-nofullbatt-debloated421.zip but it's not working with this stock OTA ROM rooted. Is there a fix version out there that wil work with this?
I just rooted my phone on android 2.2.2, but I was wondering if I can go back to android 2.3.6 without my phone unrooting?
I've rooted 2.3.4 then updated to 2.3.6 and still had root, lots of variables there though.
soo you think it will work
Yea, if you have root and do an OTA update, you should still have root.