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

Root white widow 4.0?!?!!?

Hey man, I installed that and I can't get past the boot screen.. it just stays at the splash. Then I tried to reinstall my previous ROM and I crash every time it loads.

I restored my nand, same thing.. hmm

Uh-oh.

I'm now wondering what setting you have for OC, and whether your have "on boot" checked.
 
After the 4th try I finally got it working. Thanks for the help.

Frisco, I don't even know where to check for the OC now.. where can I do that?
 
What overclocking utility did you install?

If it's SetCPU just fire it up and look at the settings.
 
I keep seeing 710 and 528 (or 478) mentioned as the safest fast settings. You have to increment up to it, though, as your device and other settings, etc, may warrant lower settings.

Some report higher settings working ok. But "it ran ok at 768 then froze up.." can be seen at more than one forum on the subject.

Mine's at 710/528 after about half a day of testing on lower settings, gradually working my way up. So far so good (third day).
 
After trying to flash White Widow 4.1 twice, I had to recover back to Senseable 3.1.

The flashing of WW 4.1 stalled at the point of the animated blueish, multicolored design, with the animation moving, but for 12 minutes, which was as long as I cared to wait.

Could this be an md5 checksum problem? I have not checked that.. and I am not sure yet how to do that (although I've done it many many times with linux distro iso files, etc).
 
After trying to flash White Widow 4.1 twice, I had to recover back to Senseable 3.1.

The flashing of WW 4.1 stalled at the point of the animated blueish, multicolored design, with the animation moving, but for 12 minutes, which was as long as I cared to wait.

Could this be an md5 checksum problem? I have not checked that.. and I am not sure yet how to do that (although I've done it many many times with linux distro iso files, etc).

Did you wipe all. The sd ext3,davlik and factory reset ? The initial boot does take a considerable amount of time. I have not timed but in my case it was long enough for me to walk away for a bit and come back.
 
It could be that the whole zip didn't download. I ran the MD5 checksum on the WW zip I downloaded and it didn't match what Andrizoid posted, so I didn't flash that ROM. I have also noticed that on his new site he doesn't have the MD5 posted. I will not flash this ROM until he posts that and both of the MD5's match. As for checking these, I downloaded a program from the net. I believe it was MD5summary or something like that.
 
Did you wipe all. The sd ext3,davlik and factory reset ? The initial boot does take a considerable amount of time. I have not timed but in my case it was long enough for me to walk away for a bit and come back.

Yeah, the first boot on all the other ROMs I've flashed did take about 3 to 5 minutes (it warns of seven minutes in the original rooting guide). But I sat and waited for twelve minutes on the WW.

I'll redo.. the wipe thing was a step, but I don't recall doing the second, davlik one.

Thanks for the reminder.
 
Uh.. welllll.. lol ..

.. this White Widow is the first ROM I've had deal breaker problems with (no offense at all intended at the dev); it just won't let me use the touch screen where it says to touch the android to continue.. the trackball works for the SU choice before that, but no touch.

I'll fool with it for a while longer.. not sure what to do.. but it's making me miss my Senseable 3.1.
 
I've got Frisco's password. Don't tell a soul.

Love,

Smacky

You're nuts! I love it! :D

Andrizoid...I have one issue that is becoming sort of a big deal for me. When talking on bluetooth, the screen goes to sleep. No big deal there. Well, if I try to wake it up to, say turn the in-call volume up or down or to try to look something up, I hang up on the person. Is there any way to set the ROM so that one press wakes the phone and a second press hangs it up? Also, what happened to the "number block" on the dialer? That was a very handy feature that I used in 3.1.
 
Uh.. welllll.. lol ..

.. this White Widow is the first ROM I've had deal breaker problems with (no offense at all intended at the dev); it just won't let me use the touch screen where it says to touch the android to continue.. the trackball works for the SU choice before that, but no touch.

I'll fool with it for a while longer.. not sure what to do.. but it's making me miss my Senseable 3.1.

It would appear that the Eris is a fickle beast. I have not had an issue with this ROM yet. I wonder what the differentiating factor is there is a touchscreen fix on site but I believe that is for the lights.

The only issue that I have had was the setup wizard not closing but I could back out so all was good.


One thing to look at would be the SD card. Do you have a partition (ext2 or ext3) set up for Apps2SD to work. It is baked in and if you don't have the proper partition, I suppose it could cause issue. That's me flying blind. Maybe Andrizoid will be around soon.

I am a heaver user and I have been flashing ROMS on many different phones over the years. This one has been a good one for me. If you can get it running then you will see what the hubub is over.


@JrzDroid. Didi you get it running ?
 
Running this rom for a few hours now and at first it was getting really hot but once everything was installed and I had everything set to how I wanted it and put the phone down it has returned to normal temps and stayed there.

Swype was also very un-responsive after the intial install but after a few minutes it's working flawlessly.

I have yet to try the theme but i do have it on the phone im just unsure of if it will make me loose my "scene" and how difficult it is to go back and fourth from the theme to not theme. Once these questions are answered by my searching I will definitely check out the theme.
 
Back
Top Bottom