-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Need expert advice on flashing, boot loops etc
- Thread starter ppbb
- Start date
-
- Tags
- htc droid eris
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...
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.
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.
Frisco
=Luceat Lux Vestra=
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.
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
=Luceat Lux Vestra=
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?
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?
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.
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.
Code:
[FONT=Courier New]Step Start-Time End-Time[/FONT]
[FONT=Courier New]------------------- ---------- ---------[/FONT]
[FONT=Courier New]Nandroid backup 12:26 12:28[/FONT]
[FONT=Courier New]Wipe data/factory reset 12:28 12:28[/FONT]
[FONT=Courier New]Wipe Dalvik-cache 12:29 12:29[/FONT]
[FONT=Courier New]Flash .zip 12:29 12:31[/FONT]
[FONT=Courier New]Reboot (3 skateboarders) 12:31 12:32[/FONT]
[FONT=Courier New]CyanogenMod boot animation 12:32 12:35[/FONT]
[FONT=Courier New]Setup 12:35 12:36[/FONT]Total time: 10 minutes
Don't know how illustrative this is, but at least now ya know.
Podivin
Android Expert
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.
Alternately, if one is available to you try another SD card to see if it behaves.
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.
scary alien said:Okay, I installed the ROM with no problem (went pretty fast, actually):
Code:[FONT=Courier New]Step Start-Time End-Time[/FONT] [FONT=Courier New]------------------- ---------- ---------[/FONT] [FONT=Courier New]Nandroid backup 12:26 12:28[/FONT] [FONT=Courier New]Wipe data/factory reset 12:28 12:28[/FONT] [FONT=Courier New]Wipe Dalvik-cache 12:29 12:29[/FONT] [FONT=Courier New]Flash .zip 12:29 12:31[/FONT] [FONT=Courier New]Reboot (3 skateboarders) 12:31 12:32[/FONT] [FONT=Courier New]CyanogenMod boot animation 12:32 12:35[/FONT] [FONT=Courier New]Setup 12:35 12:36[/FONT]
Total time: 10 minutes
Don't know how illustrative this is, but at least now ya know.
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?
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)
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
=Luceat Lux Vestra=
I wonder if your sd card is corrupted.
Podivin
Android Expert
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.
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.
Frisco
=Luceat Lux Vestra=
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.
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.
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
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.
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.
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.