• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Themed ROM] NexBeast V1.1 (updated 5/27/2010)

How do I reset this poll!

  • Yes

    Votes: 63 80.8%
  • No

    Votes: 50 64.1%

  • Total voters
    78
That may have done it. The contents of the switchlnchr script are just as follows:

Code:
su
sysrw
busybox rm /system/app/Launcher.apk
busybox cp /sdcard/Launcher.apk /system/app
sysro
sync
 
That may have done it. The contents of the switchlnchr script are just as follows:

Code:
su
sysrw
busybox rm /system/app/Launcher.apk
busybox cp /sdcard/Launcher.apk /system/app
sysro
sync

sorry, my bad, i was running 1.0, but thought I was on 1.01. I flashed to 1.01 and it was there, although I still have to add the other script files....

question though, i installed the updated AWD launcher and I can't get my wallpaper to change, it'll do live wallpaper, but not an image like normal?

also, I did not run the script for updating from 1.0. I did wipe cache and data though. Is that necessary when updating the same ROM?

thanks a lot,
rlr
 
Tried overclocking one more time this morning, and again, didn't matter which kernal I tried, 800, 1000, 1.2, P3 or Bekit, the only thing this phone will run on this rom is the one it came with, the 600. (I had been using 1.2 kernals clocked at 1000 on the previous rom, worked great).

In the midst of this, the SD card died yet again, this is the 4th or 5th time I've had data corruption with this phone, (even before rooting) on the second SD card from Verizon.

Went back to stock 2.01 with the "live without fear of bricking" .sbf file. At first the SD card couldn't even be read in my card reader, after going back to stock, suddenly the phone would read the card. :eek: (promptly re-formatted). Went to Verizon, they agreed to ship another Droid given my SD card problems, possibly being a function (mis-function) of the phone not acting right with the cards. (Thank God that return to stock thing worked again).

Odd thing here, I thought I'd go ahead and let the system update to 2.1 for the day or two while I wait for the replacement, and once I accept the upgrade, it just sits at the "M", doesn't move passed it. I had to use the "live without fear of bricking" .sbf thing again so at least I'd have a functioning 2.01 phone while waiting for the replacement.

Thoughts and opinions greatly appreciated, thanks.
 
Assuming it does come with 2.1, I've been studying how to re-root. Let's say it does come with 2.1 and I load .sbf recovery, and it needs to be returned, do I just go back to 2.01 before returning it? Thanks Fab...

I think this is a hardware issue. Hopefully your replacement will be working well!

If it doesn't come with 2.1 preinstalled, you can easily root it with the file found here:

http://androidforums.com/all-things-root-droid/78548-how-easier-method-root-2-1-a.html

If it does come with 2.1, you can just .sbf SPRecovery on there and load up a custom ROM.
 
btw: does anyone know a procedure to 'extract' a currently in use wallpaper and/or the jpg image it was 'built' with. After going to 1.0, I cant find my wallpaper in any of the galeries, nor the 'orig' jpg used to build it. I want to ensure I 'keep' it cause it was an 'one of a kind' cam pic... ideas?
 

I sent myself a MMS from phonezoo. It had a 'download' button, that I clicked, and the sound played right away for me.

What kind of music file was it? Mine was .mp3

Assuming it does come with 2.1, I've been studying how to re-root. Let's say it does come with 2.1 and I load .sbf recovery, and it needs to be returned, do I just go back to 2.01 before returning it? Thanks Fab...

Yeah, just flash the 2.0.1 SBF and there's no way they can ever tell it was rooted.
 
just a forward from someone...sometimes i have to click download but not most of the time. but if i get just a regular mms and it comes thru i click on the play button to view the slideshow and no music plays. when i click at the bottom of the screen a bar shows up sayin how much time is left on the song or whatever...but i got nothing. and it says its playing. (yes my sound is up)
 
Cant find the thread anymore, but a week ago when I put on NexBeast V1.0 there was a procedure to 'fix' MMS so it could handle Video via messaging. I had to restore back to 1.0 due to some 'issue' with constant rebooting, and now, I need those instructions on how to 'reapply' the mms.apk.

Can anyone quote what steps were require or point me to the thread?
 
Does any know have the problem of/know what causes/how to fix the constant acore FCs that I get on BB. and NexBeast? some times its the home and some times its contacts but it always says acore.
 
The link is in the first post, under 'optional mods'. The mediafire link works, sometimes you just have to try more than once if it is being wonky.

Definitely being wonky...ill try internet explorer. Another question, since I have your attention lol.. is there a way of having working video playback, on the previous mms.apk that had all the settings? Allssoooo if you can answer this or if anybody can, is there a way of having a text message vibrate not go off during a call without unchecking it under the notification settings? thankuthankuthanku
 
Sorry, the only way I could manage to get video MMS to work was by not using the modified messaging app that had the extra settings.

In order to get those settings back, and also have the option to disable vibrating while on call, you would have to use a supplementary app such as Handcent or ChompSMS.
 
Well this is annoying.. I cant download the themed launcherpro from mediafire (today).. with firefox it just redirects me to a blank page, and with ie it redirects me to a http error page lol... uuuggghhh >.<
 
Help please,

Alright here's the scenario: Im coming from Droidmod because they arent doing shit and i havent gotten an update for almost 2 months now and im trying to flash the mod using Clockwork. I install the NexBeastV101.zip when i am in the Clockwork screen and i reboot my system but EVERYTIME i try it just goes into bootloop. I thought that it just might be the rom i am trying but EVERY rom i try and flash does the same thing. Is there something i am doing wrong?

Basically I go into bootloop no matter what rom i try and flash

Please help! (:
 
Help please,

Alright here's the scenario: Im coming from Droidmod because they arent doing shit and i havent gotten an update for almost 2 months now and im trying to flash the mod using Clockwork. I install the NexBeastV101.zip when i am in the Clockwork screen and i reboot my system but EVERYTIME i try it just goes into bootloop. I thought that it just might be the rom i am trying but EVERY rom i try and flash does the same thing. Is there something i am doing wrong?

Basically I go into bootloop no matter what rom i try and flash

Please help! (:

Welcome. Did you wipe data, cache, system and boot?
 
anyone else notice a decrease in performance lately? ever since i flashed to this, i noticed it was running choppier than Pete's BB. it runs fine at first when phone is first booted and also after i kill everything and free up memory in ATK, but after a while it starts to lag again. also noticed battery life was a little worse than BB.

not sure if this is because apps are taking up memory. when it gets laggy, i check ATK and it has only 40M left. seemed like it was an issue with the pete file but also not sure if it could be a SetCPU issue so i decided to disable SetCPU and restore an old pete file i had saved, and now its smooth again. memory killing now seems to be working more effectively. it stays at around 60M of free memory when i check ATK.

using P3 1ghz kernel.
 
Back
Top Bottom