ppbb

Been having a lot of trouble flashing new roms. Curently running tazz froyo v1.0. Have been able to root, flash many different types of roms (2.1, froyo etc)

But lately been wanting to try out Nonsensikal v4.6 but for some reason cannot get it to load. It'll either get stuck onthe white screen or if it does make it past the boot freezes during the boot animation and will remain stuck for a long time. Have let it go for 30-40 minutes. Batt pull, both wipes reflash and same thing.

So it has to be corrupted downloads. Tried on different computers, same results. Reformatted my card (was already no partitions, fat32 for froyo).

I would like to figure this out as i really want to try nonsensikal ( ran v 3.4 and loved it)

Any ideas? Battery is always fully charged when flashing. Sd card is good.

Maybe it's a computer issue?

Appreciate any responses.
Thannks

scary alien

ppbb,

You didn't mention anything about the wipes. Are you doing both the "Wipe data/factory reset" and the "Wipe Dalvik-cache" wipes before flashing a new ROM?

Frisco

"..both wipes.."

It would not hurt to wipe factory, dalvik and sd:ext, ppbb.

I suspect a corrupted zip, but secondly to not fully wiping.

But a redownload of the zip, to a pc, not through a router onto a laptop, and a check of the hash (md5 checksum) would be a good idea.

ppbb

sorry forgot to mention i do both wipes religiously. data and dalvik. the dev for Nonsensikal does not list the md sums for his roms. he has been really helpful, but we both think its got to be the download.

Frisco, I do use a laptop thru a router. I'll try hooking up my desktop direct to the modem (bypass the routers) and see if I can get a clean download.

what else could it be? Has to be a bad download right? I can nand restore back to tazz v 1.0 with no issues.

Thanks for chiming in guys!

Frisco

The third wipe.. do the sd:ext wipe as well in this case.

scary alien

ppbb,

Let me know which version you downloaded and I'll download it and post the MD5 sums that I get for it if you want. At least that way, you could compare it to your download and that would tell you whether we both got the same file or not. You could also compare the MD5 sum of the file on your laptop vs. the MD5 sum of the file on your phone to make sure that they are the same.

Cheers!

ppbb

scary alien,
Thank you for helping. Much appreciated!

I downloaded V 4.6 Blue.

Frisco, thanks I'll try that too.

doogald

Sometimes if you try to download again it will just pull what it downloaded from your browser's cache. Try clearing cache in your browser, delete the file that you already downloaded, and try again.

The other option is that there are three versions: blue, black and vanilla. Try downloading a different one and see what happens maybe?

scary alien

Okay, here's the scoop:

c:\temp>md5sum "nonsensikal v4.6 blue.zip"
df1e87b2e5d3303248f83073d8f78ea4 *nonsensikal v4.6 blue.zip

You can also check the MD5 sum of this file as it exists on your phone's /sdcard via Astro (long-press, file details) or my app (verify your file's MD5 checksums!) and compare that to what you and I got.

Hope this helps!

doogald

I did the download and calculated the same MD5 hash.

ppbb

first of all let me say, killer app. i got the correct md5 sum. my sum matched yours as well as doogalds.

what to look at next? Could my phone be on its way out? It works and functions fine otherwise. Just cannot load this rom. maybe try a different sd card?

ppbb

same thing happens on blue or black versions.

ppbb

btw i am on windows vista

doogald

Try flashing a 2.1 ROM (nandroid restore if you have one). When you know that is running (you do not have to load it all up - just make sure that it is working.)

Then go back to recovery, wipe and flash nonsensikal.

Just a strange thought that it is a froyo to froyo thing ...

ppbb

i have xtr beta 4 on nandroid. i'll try it tonight. thanks for the help guys.

xAusTiN

Happened to me before, I deleted everything off my sdcard, save anything you really need and then delete it. Reboot into recovery then, wipe everything and then flash. Then add back anything you saved from sdcard after your rom boots up.

__________________
Droid Eris > All

ppbb

i have an 8gb card that is not partitioned. i'm probably using maybe 2 gb of the card with over 5 gb free.

I'll give it a shot. Really want to figure this out and try the blue theme.

Thanks again everyone for the help!

ppbb

tried everything suggested.

this morning did 3 wipes (data,dalvik, ext) flashed.

booted up, stayed on the white screen 3 skaters for a few seconds went right into the cyanogen mod animation. was going good for about 2 minutes, then restarted the animation again.

then it just froze again and its been frozen on the cyanogen mod animation (the little circle that goes around the circle isn't moving)

so it seems i am getting closer. its not hanging on the white screen/3 skaters.

ppbb

crap.

battery pull.

wiped again.

re-flashed

now stuck on white screen/3 skaters

i think my phone is ****ed. it won't flash any new roms. i can only nand restore.

all downloads are good.

sd cards are formatted correctly. not running out of space. battery is fully charged.
the only other thing it could be has to bethe phone/hardware right?

Frisco

Have you considered "re-rooting?"

I think that if those issues were in my phone, I'd pretend like I'd never rooted and go to the original root regimen, not to the "universal" ones, and start over.

GUIDE: From stock 1.5 to the latest root 2.1

ppbb

i was originally a leaker. rooted with the wagslav method. will the method you described work for me?

Frisco

I think that the best way for a leaker to go is this one:

Universal Eris Root for Dummies!

contrary to what I said above, which had 2.1 OTA in mind.

ppbb

well i already started the first method you described. i am already rooted. the PB00IMG is loading now into my bootloader.

should i stop? i am starting to lose my mind.

ppbb

okay i re-rooted . all appears to have gone well.

ran the pb00img

ran the adb commands to push recovery to my phone

rebooted into a stock htc/sense ui (wow brought back memories and why i don't like sense)

booted into amon ras recovery - did my wipes

flashed nonsensikal v4.6 blue

on the white screen, waiting . . .


EDIT: stuck on white screen for 5 minutes. normal ? or should I battery pull?

Last edited by ppbb; August 28th, 2010 at 10:33 AM.

scary alien

be patient...give it time...

if no joy, try flashing a known good ROM and stay away from the blue one

ppbb

10 minutes on the white screen. when would you guys pull battery? 1 hour?

how long is reasonable before i should pull batt etc?

scary alien

I think you've reached your limit on the blue ROM...(a few minutes, tops on the 3 skating androids)...10 minutes is still too long and 1 hour is way too long.

I would return to one of your good Nandroid backups or a known, good ROM that you are happy with.

Looks like we really need eu1 to diagnose what might be going on here...I've got no clue...

Last edited by scary alien; August 30th, 2010 at 09:55 PM. Reason: correct myself :)

ppbb

so being stuck on the white screen for 10-15 minutes is normal?

it never goes into the boot animation, it just stays at that white screen.

i'm nand restoring back to cyanogn tazz 1.0

i have been able to attain root, flash so many roms. but lately it won't work. its not like i don't have any experience with this, but this is a new development and i cannot figure out other than hardware issues.

i can nand, but cannot go forward with any new roms.

Last edited by ppbb; August 28th, 2010 at 11:10 AM.

Frisco

How are you getting the zips to your root folder?

Which ever way it is, try another way in an effort to isolate the problem in the chain of events..

..for example, if you're downloading the zips to your computer and then dragging them to your / folder after connecting the USB cable, try downloading the a zip to your phone and then going into Root Explorer and moving the file from the download folder, or which ever folder the zip arrives into your device, to the / folder..

..then (with a fully charged battery, 80% at the least) power down and flash that zip.

scary alien

No, I don't think 10 minutes is normal--I was thinking of when it gets to or past the boot animation...I've read that some ROMs take a very long time to load compared to other ROMs. I just didn't want you to give up that soon.

I'm downloading and about to install "nonsensikal v4.6 blue.zip" myself, just so I can time things and let you know. I'll get back to you with the results (assuming it works for me ).

Frisco

Also, I'm wondering if you've watched the progress of the flash process; there is a progress bar on the lower screen, behind the white text scrolling up as each process invokes and then completes.

Have you seen any error messages along with a message saying something to the effect of "attempting...success" as if something had to be worked around by the system to complete the flash?

ppbb

on my pc i've been dragging them from the folder to the sd card folder. i also copied and pasted.

i'll try the download to phone idea.

i'm at a total loss right now.

is there some kind of diagnostic i can run via adb? i really think my hardware is faulty.

Frisco

I'm looking at system logs and such on my phone now .. I'll post back if I can find anything related to the flash of the zip (I'd love to find an error log of some sort ).

Last edited by Frisco; August 28th, 2010 at 11:40 AM.

scary alien

Okay, I installed the ROM with no problem (went pretty fast, actually):

Total time: 10 minutes

Don't know how illustrative this is, but at least now ya know.

mhotovec

This is the same type of behavior my phone had when I tried a 32gb card, it would do half of about any process and then crap out. It sometimes booted - sometimes not, it sometimes could see what was on the card (or not), it took me several tries to get a ROM to flash (any of this sound familiar?). So I'm wondering if the card is somehow bad or going bad, has a bad sector (or whatever the SD card equivalent is to a sector). You mentioned that you reformatted your SD card, did you do this via phone or PC? Regardless of the answer to that question, try reformatting using the other one. I'm also wondering about doing a full reformat (not 'quick') using the PC.
Alternately, if one is available to you try another SD card to see if it behaves.

scary alien

mhotovec,

Fresh eyes and fresh perspective (and hard-won experience)! Great ideas.

I've only got my original 8GB card on my phone...perhaps ppbb is using a newer, larger one (bigger than 16GB?) since he's flashed a lot of ROMs and has a lot of Nandroid backups? In either case...very good suggestions.

ppbb

All of the times above match my phone except for the white screen 3 skaters. I reformatted a new sd card in my computer (previously did reformats in the phone) loaded nonsensical black, wipes, flashed rebooted. Now been stuck on the white screen for at least 5 minutes.

What would cause it to just hang at the first screen?

ppbb

Pulled battery, pulled out the sd card. Rebooted. Now it hung on the white screen for about 3 minutes. Then went into the boot animation. It's been spinning on the boot animation. Round and round.

Hasn't gotten to the set up portion yet. Been at least 6-7 minutes on the boot animation (double of scary aliens time table)

Frisco

I wonder if your sd card is corrupted.

mhotovec

I know this sounds strange, but it's fixed a problem for me before and proved (to ME at least) that a wipe/factory reset is really not the same thing as a factory reset.
Try doing a factory reset. The instructions below are swiped from Frisco's factory data reset thread.

- Shut down your device.

- While holding down both the volume-down toggle and the send or "phone" button, press the power button.

- Wait a moment, and a screen will come up: read the print completely and follow directions, it'll walk you through the simple process.

Last edited by mhotovec; August 28th, 2010 at 01:05 PM.

Frisco

I like the way people are coming in and offering this user so many different ideas based on their experiences.. Android Forums at its best.

Last edited by Frisco; August 28th, 2010 at 01:09 PM.

ppbb

did this. now just waiting. its on the white screen again. i guess since this is a factory reset that it hangs on this screen and takes a while?

i'm gonna walk away for a bit and get some fresh air.

mhotovec

bated breath....

andrizoid

if this doesnt work pull a logcat for us and we can get an idea of where the flash is failing and go from there

__________________
Andrizoid's Space is online! Come stop in and say hi!
Check out my stuff on Rom Manager!

erisuser1

That was suggested to him yesterday on XDA. We'll see - I don't know if nonsensikal starts adbd up right from the get-go, so that approach might not work.

It is interesting from a somewhat academic perspective, and if he enjoys the debugging/learning process, then why not... but there are plenty of good ROMs to choose from; I would have just given up and used a different ROM by now

Interesting thread, though.

eu1

__________________
Please don't send me PMs - post your questions so others may benefit from any answers given.

Last edited by erisuser1; August 28th, 2010 at 02:55 PM.

ppbb

update

ran the logcat as suggested by bftb0 at xda forums. the logcat returned nothing. I let the adb command run for over 15 minutes. nothing. no report, nothing on the screen

After doing both wipes, flashing t boots up into the white 3 skaters screen and just hangs there forever. Battery pull, reboot and it gets to the cyanogen mod boot animation but that just goes on and on - I've let that go for close to 1 hour. Its like it is looping in the boot stage and can't get past a certain step.

i was able to flash cyanogen tazz 2.0 over 1.0 (the only stable froyo rom that will load and work for me) and it flashed over with no issues other than the camera (which I was abe to fix by uninstalling the camera and adb push the new camera apk - as suggested by Tazz)

I'm going to lick my wounds and admit defeat. this rom doesn't like my phone.

Tazz's rom is more than enough for my needs and I need to stop wasting time chasing something thats going to give me a blue keyboard and dialer. Silly.

I appreciate everyone's help - Thank you! But I am convinced my phones hardware is to blame and any more finagling isn't going to help. My phone works with Tazz's rom and I just have to accept that this is more than good enough.

gonna go and have a medicinal smoke break and enjoy my tazz 2.0 phone.

erisuser1

Thanks for trying.

Pretty strange, really - I wonder if HTC did different builds with different hardware.


eu1

ppbb

that's what I'm thinking. You see so many different issues with each handset all pointing to hardware differences.

Thanks again you guys, you all really put some effort forth and I appreciate this forum so much.