Root [Rom] Newts OnE XxX beta (Sense 4 ICS 4.0.3) 4/2/2012

[scotty85]

So I'm thinking about flashing this Rom. I'm still S-ON and thought I was going to take the jump to S-Off, but I can't quite decide if I want to yet.

I am still on the GB firmware. I just want to make sure I've got everything straight on the install process if I'm still S-ON.

1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.

4. Here is where I'm lost. I know I need to flash the old firmware patch, and I need to flash the ROM's kernel. Is that the boot image part? Which order, old firmware patch and THEN kernel, or Kernel (bootimage?) and THEN old firmware?

Thanks!

1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch

no need to flash kernel(see #1 )

 

[icedice34]

no need to flash kernel(see #1 )

This confuses me........? See #1 where? I'm currently running Nils Business Sense, so I wouldn't think I'm on the same Kernel? I'm even more confused now...

*EDIT* Sorry, but it mentions several times installing the "boot.img" What is that?

 

[scotty85]

This confuses me........? See #1 where? I'm currently running Nils Business Sense, so I wouldn't think I'm on the same Kernel? I'm even more confused now...

*EDIT* Sorry, but it mentions several times installing the "boot.img" What is that?

YOUR #1... "1. fastboot boot Amon Ra"

i have only said about a million times now on various threads that if you fastboot boot amon,it can write the kernel and you s-on guys will not have to flash the kernel seperately.

it will work,i promise.

so if the rom scripts are set up for the s-off crowd for recovery to install the kernel,or if you are restoring a backup, if you fastboot boot amon,you will not have to falsh seperately.

all you have to do is:
1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch

thats it... no need to make it more complicated than that.

if you want to install the kernel anyway,becasue youre using a permanent recovery,you think im making the whole thing up,or whatever other reason( ),it doesnt really matter when you install the kernel,it just needs installed sometime before you boot. however,the most logical order to me would be:
1. boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch
5. flash kernel
especially if youre installing the the kernel as a PH98IMG becasue you are not hooked to a PC.

since you are reluctant to become s-off,id pretty highly recomend you to try it:
1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch

and see for yourself it works. it may sway youy one dirction or the other to know that you can install roms just as easily as if you were s-off simply by fastboot booting amon

 

[icedice34]

YOUR #1... "1. fastboot boot Amon Ra"

i have only said about a million times now on various threads that if you fastboot boot amon,it can write the kernel and you s-on guys will not have to flash the kernel seperately.

it will work,i promise.

so if the rom scripts are set up for the s-off crowd for recovery to install the kernel,or if you are restoring a backup, if you fastboot boot amon,you will not have to falsh seperately.

all you have to do is:
1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch

thats it... no need to make it more complicated than that.

if you want to install the kernel anyway,becasue youre using a permanent recovery,you think im making the whole thing up,or whatever other reason( ),it doesnt really matter when you install the kernel,it just needs installed sometime before you boot. however,the most logical order to me would be:
1. boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch
5. flash kernel
especially if youre installing the the kernel as a PH98IMG becasue you are not hooked to a PC.

since you are reluctant to become s-off,id pretty highly recomend you to try it:
1. fastboot boot Amon Ra
2. Wipe Cache/Dalvik/Factory reset/boot
3. Flash the ROM.
4. flash old firmware patch

and see for yourself it works. it may sway youy one dirction or the other to know that you can install roms just as easily as if you were s-off simply by fastboot booting amon

Scotty one thing I never do is doubt you! I was just confused. about the whole process. Here goes flashing Newts.

I'm a bit nervous about the whole S-Off thing mostly because I don't have the money to replace my phone if I brick it, and you've said over and over that being S-ON makes it nearly impossible to brick a phone. Thanks for all your help.

Again, I am curious though, what is the boot.img part? It is listed a couple times, but I'm not sure what it is and I can't seem to find anywhere that says.

 

[scotty85]

Scotty one thing I never do is doubt you!
i know,it was a joke
I was just confused. about the whole process. Here goes flashing Newts.
cool! let us know how you like it

I'm a bit nervous about the whole S-Off thing mostly because I don't have the money to replace my phone if I brick it, and you've said over and over that being S-ON makes it nearly impossible to brick a phone. Thanks for all your help.
thats completely understandable,and yes,an s-on hboot is nearly impossible to brick,since the phone is protecting the radio and hboot. dont let s-off care you tho,you will not brick an s-off phone if youre careful. you just need to be religious about md5 verifying any hboot flash that contains an hboot,and/or radios. as long as you use s off resposibly,it actually gives a greater amount of safety,since you can flash any ruu that exists,youre not limited to what youre on or newer like if your s-on,and you can install an eng hboot to give yourself extra fastboot commands. both things give more options for restoring a "soft bricked" phone.

Again, I am curious though, what is the boot.img part? It is listed a couple times, but I'm not sure what it is and I can't seem to find anywhere that says.
the boot image is the kernel. its listed for the s-on crowd that doesnt know(or just doesnt believe ) the fastboot boot recovery trick,and needs to manually install the kernel. as long as you either fastboot boot amon,or are s-off,you dont need to worry about the boot image part of the install directions

 

[icedice34]

Scotty one thing I never do is doubt you!
i know,it was a joke
I was just confused. about the whole process. Here goes flashing Newts.
cool! let us know how you like it

I'm a bit nervous about the whole S-Off thing mostly because I don't have the money to replace my phone if I brick it, and you've said over and over that being S-ON makes it nearly impossible to brick a phone. Thanks for all your help.
thats completely understandable,and yes,an s-on hboot is nearly impossible to brick,since the phone is protecting the radio and hboot. dont let s-off care you tho,you will not brick an s-off phone if youre careful. you just need to be religious about md5 verifying any hboot flash that contains an hboot,and/or radios. as long as you use s off resposibly,it actually gives a greater amount of safety,since you can flash any ruu that exists,youre not limited to what youre on or newer like if your s-on,and you can install an eng hboot to give yourself extra fastboot commands. both things give more options for restoring a "soft bricked" phone.

Again, I am curious though, what is the boot.img part? It is listed a couple times, but I'm not sure what it is and I can't seem to find anywhere that says.
the boot image is the kernel. its listed for the s-on crowd that doesnt know(or just doesnt believe ) the fastboot boot recovery trick,and needs to manually install the kernel. as long as you either fastboot boot amon,or are s-off,you dont need to worry about the boot image part of the install directions

Sweet. I've got it installed and so far I'm a big fan. Thanks again for all your advice.

 

[scotty85]

Sweet. I've got it installed and so far I'm a big fan. Thanks again for all your advice.

awsome! sense 4.0 is neat,aint it?

im still an AOSP fan at heart,but since i run cm9 on my sensation its kinda fun to run the sense roms on the rezound

 

[icedice34]

awsome! sense 4.0 is neat,aint it?

im still an AOSP fan at heart,but since i run cm9 on my sensation its kinda fun to run the sense roms on the rezound

Is there a stable cm9 for rebound? I had CM7 on my moto droid x and loved it!

 

[scotty85]

Is there a stable cm9 for rebound? I had CM7 on my moto droid x and loved it!

i wish! the cm9 roms that currently exist dont have working RIL,so no voice.text or data

closest we can get to AOSP currently is senseless roms like slimrom,cleanrom dev edition,or conrom desensed.

coming out riught with the gnex and ICS,all attentions have been to ICS. AOSP gingerbread was no longer a big deal so no one has even bothered with cm7 or AOSP GB. GB is old news,lol.

supposedly someone on xda has gotten voice and 1x data working on AOSP,so hopefully there is light at the end of the tunnel

 

[icedice34]

i wish! the cm9 roms that currently exist dont have working RIL,so no voice.text or data

closest we can get to AOSP currently is senseless roms like slimrom,cleanrom dev edition,or conrom desensed.

coming out riught with the gnex and ICS,all attentions have been to ICS. AOSP gingerbread was no longer a big deal so no one has even bothered with cm7 or AOSP GB. GB is old news,lol.

supposedly someone on xda has gotten voice and 1x data working on AOSP,so hopefully there is light at the end of the tunnel

That's too bad! I loved my cm7 droid x.

Question for you all. Anyone had any luck with the mikmik settings and hardware keys? Seems no matter what I change in there it doesn't affect anything.

 

[scotty85]

That's too bad! I loved my cm7 droid x.

Question for you all. Anyone had any luck with the mikmik settings and hardware keys? Seems no matter what I change in there it doesn't affect anything.

i havent even messed with them,lol...

it wouldnt surprise me that they are not really working yet,i believe emphasis at this point is simply in getting the rom smoothed out and functional. keep watching and hopefully there will be new releases where those settings will work

 

[al23]

Sweet. I've got it installed and so far I'm a big fan. Thanks again for all your advice.

For the 3.2.1 update (the 11 MB file), this can be flashed immediately after the main file (the RLS 3.1.2) and before the firmware patch?

 

[scotty85]

For the 3.2.1 update (the 11 MB file), this can be flashed immediately after the main file (the RLS 3.1.2) and before the firmware patch?

yup,that should work fine.

for you s-on guys that want to flash and and are allready on 3.1.2,you may want to re-flash the fimrware patch after flashing the rom update. or just be prepared to return to recovery and reflash it if you flash the rom update and your sd card disapears

 

[icedice34]

I seem to be having an "issue" that I'm not sure about. My syncing data icon seems to always be on. Anybody else noticed this? Is this killing my battery with constant background sync?

 

[scotty85]

I seem to be having an "issue" that I'm not sure about. My syncing data icon seems to always be on. Anybody else noticed this? Is this killing my battery with constant background sync?

mine used to be on fairly often as well... id say it prolly is doing something,how much it may be affecting your battery life im not sure.

now i just keep sync off,and manually sync if i add a contact or calander event. if you dont have alot of stuff that you need to automatically sync,you might try keeping it off.

 

[icedice34]

mine used to be on fairly often as well... id say it prolly is doing something,how much it may be affecting your battery life im not sure.

now i just keep sync off,and manually sync if i add a contact or calander event. if you dont have alot of stuff that you need to automatically sync,you might try keeping it off.

I get a lot of email. Manual sync of that would be annoying. It's weird it wasn't on until sometime today and now it won't shut off. Also, it used to spin I think, and now its not moving.

 

[scotty85]

I get a lot of email. Manual sync of that would be annoying. It's weird it wasn't on until sometime today and now it won't shut off. Also, it used to spin I think, and now its not moving.

hmm,yeah i dont think i really had that issue. i used to see it come on frequently,but i dont believe it stuck on permantly.

 

[scotty85]

hmm,yeah i dont think i really had that issue. i used to see it come on frequently,but i dont believe it stuck on permantly.

i turned my sync back on last night. i realized it was preventing my weather app from updating. so far its not been on excessively,but ill watch it during the day today

 

[icedice34]

i turned my sync back on last night. i realized it was preventing my weather app from updating. so far its not been on excessively,but ill watch it during the day today

Hmmm...so I installed Friday or Saturday. Realized Sunday afternoon sync was off. Turned it back on. That's when the logo came on. Tried reboots, shutting sync off, airplane mode, etc. Etc. Nothing changed. Last night went to bed with it on. This morning it appears to work like its supposed to, only showing when something is syncing. I'm guess maybe it just took 3 days to get everything synced? Weird...

 

[scotty85]

yeah that is wierd. ive had my sync on since i posted that,and ive only seen icon a couple of times. maybe you had alot to sync

 

[esmith818]

I'm liking this ROM, but I don't see the wireless tether option that is touted as being included. I see Verizon's hotspot app, but I assume that is still tied to their pricing, correct? I also see a post on the mikmik site that suggests that the boot.img file must be flashed for the tethering to work, but I did not flash that file per Scotty's advice when using a temporary recovery. Do I need to flash the extra file in order to get tethering working and/or do I need to download a 3rd party tethering app to make that work?

EDIT: I read the OP on this thread and it solved my problem.

 

[ntrnlerror9]

your prollem is flashing the GB patch before you flashed rls 3.1.2

you do not need to flash rls3. just 3.1.2,then the GB patch,then the kernel.

if you have successfully flashed the boot image,then you might get away with just flashing the rom and patch. if not,youll need to flash the boot image again.

i strongly recomend fastboot booting your recovery. that way the seperate kernel flash is not needed.

-fastboot boot amon
-full wipe,flash rls 3.1.2
-flash GB patch
-reboot

the rebooting is a classic sign of mismatched firmware,i.e, not flashing the old firmware patch.

trying to figure out what exactly is meant by "fastboot boot amon"

 

[icedice34]

trying to figure out what exactly is meant by "fastboot boot amon"

Amon is the recovery, amon ra. You'll need to read through scottys noon friendly root guide start to finish (sticky on this forum) and it should give you a better understanding

 

[Amaroth]

Read the noob guide but I never figured out how to get adb to work and I still dont understand 'fastboot boot amon'..
been on cleanrom de for many months now but kinda miss sense. guess i'll stick to just flashing the extra kernal. don't know if I am even going to change my cleanrom tho, just trying to wrap my head around how to do it in case i want to..lol

 

[NEXTLOVER]

Just installed this one & it's really sweet Not much different fr. the stock GB/3.6 one but it's smoother (no glitches or snags when scrolling) & my temp.'s been pretty low compared to the stock one. Battery life... we'll still have to see over the weekend. Will have a chance to test it out when I see the ex in-laws & know f'shure won't get a chance to leave 'em W/e sucks already.

Is it all right to delete the 3 zip files that we moved to the root of our sd cards? The ROM is like 600mb If not, that's fine! & does the Pandora widget work? For sum reason, I can't get it to work. I'll try again.

But so far, so good & this is coming fr. the neophytes of all noobs of ROM installers lol.