Im very dissapointed, my Streak has gone to silicone heaven and there is no reason for this either.
I got up this morning, got dresst and went to work as normal, I noticed my Streak vibrated in my pocket so when I got to work I had received a text so I proceed to unlock the device only to find it lagging to death and generally un-responsive.
This cleared and I started writing my responce to the text and the haptic feedback stopped and then the phone became fully un-responsive, so it was time for a bettery pull, I did this a further 3 times as it kept locking up (I though it was due to a media player I installed from the market last night so was going to uninstall it but it wasnt in the list of installed apps)
Then after the 3rd reboot I was then stuck at the boot screen and it would not go any further, I have gone into the recovery menu, cleared partitions etc etc and still its the same, I have also flashed back from DJ_steve 1.6.1 to 1.5.1 in the vein hope that it was something to do with 1.6.1, but no still the same.
Im going to try and put a stock rom on there and see what happens (as im able to flash etc etc it just seems to be when something is initializing during boot)
Im just wondering if anyone else has had this issue?
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Edrill said:
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Click to expand...
Click to collapse
Hi Edrill, thanks for the response, I have flashed 1.5.1 back on and factory reset, at 1st it didnt work but I tried again and was in the front room and I heard my alert tone back up and running on 1.5.1 think ill stick with that for now as its 2.2 anyways.
Thanks again bud.
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Edrill said:
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Click to expand...
Click to collapse
Ive opted for 1.5.3 for the time being, I had that for a few weeks without any issues so going to stick to that and see how the phone goes.
For now she's up and running without any issues *touches wood*
Related
So I've got a problem for you gurus out there. A little history...
It all started last week when I tried flashing to KaosFroyo v38 and it was eating my battery alive. People suggested flashing CFS kernel v6 (at the time) but every time I flashed I would never get past the skating androids. I factory wiped, davlik wiped, still no go. After messing with it for a couple days I just re-flashed back to KF v37 and figured I would wait for a new rev.
So this week CFS v8 is out and the new governor feature which I am really wanting to try so I figured I would give it a go again. Factory and dav wipe, flashed KFv38, flashed CFSv8 on top, same issue with the skating androids. Someone suggested to try a different rom. So, I tried CELBv3.6 since it had the same kernel and still no go. This morning I tried FloyoTazz v17 and the same issue.
It appears that it might be kernel related but I am really not sure. I PM'd conap and he suggested I get a logcat at boot to diagnose, but my device doesn't seem to boot enough to detect the device on my PC. When I enter adb logcat it just says "- waiting for device -" and if I enter adb devices nothing is listed. It's like all my phone does is turn on and thats it.
KaosFroyo is the only rom I've tried that I can get to flash and boot and v37 is the only one that doesn't drain my battery so thats where I am at.
Any help would be much appreciated.
Bump. Still looking for answers.
P.S. - Helped my friend root his eris this morning. Installed TazzFroyo v17 first time no problems. I'm really curious what in the world is causing my phone to not boot up...so weird.
Man I guess I really stumped you guys.
Just an update on some things I tried yesterday.
1. Reformated my SDCard to a single partition. No change.
2. Tried booting without SDCard. No change.
3. Unrooted back to factory 2.1. Re-rooted and flashed. No change.
I'm running out of google searches and ideas. Since I can't boot long enough for my PC to recognize my phone, is there a way I can run a boot log locally on my phone without adb? Unfortunately until I get a boot log of some sort, I'm stuck with the trial and error approach.
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
koamalu said:
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
Click to expand...
Click to collapse
I've run setcpu at 710 without issues, but definitely something to try. Thanks for the tip.
Just to follow up on this issue which is now resolved.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. After removing that from the kernel, everything flashes fine.
OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!
I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk
iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.
I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...
I had Vegan Ginger Edition running and it was working great. I decided to Factory Reset the tablet. I used Settings|Privacy|Factory Reset.
But it went into endless reboots, I think. What it was doing is that the screen that says Vegan Tab Ginger Edition comes and it does the animation (shocking and flashing), and it does this like 3 times and then the screen goes blank for a second or so and then the animation starts again, and so on, and it keeps on repeating forever and then it would turn off automatically.
I booted into recovery Clockwork Recovery, and tried to do wipe data/factory reset, wipe cache partition, etc, but nothing helped.
I eventually ended up in doing Wipe Dalvik Cache. Now it does not even get to that Vegan Tab animation. It now gets stuck at "Powered by G-TABDEVS" screen.
Any suggestions? Do I need to re-install? If so I guess I will have to copy the zip to SDCARD and then install it, since I can't boot at all. Is there any other option?
Ya, just reflash vegan ginger.
I reflashed it. It now moves on and does not stop at G-TABDEVS screen, but it is exhibiting the same problem. Repeated VEGAN-TAB GingerEdition screens.
What do I do?
I just flashed CyanogenMod, and even that exhibits the same issue. I even went in and did mounts and storage>format system as well as format data. And then flashed it. But still the same.
More bad news. I nvflashed bekit's original image. It now is showing the original big eliptical g-tablet logo as it boots up, but it continues to cycle between the birds and the gtablet logo.
CWM is also gone. When I try to go into recovery all it displays is the big triangle with exclamation sign for a second or so and then restarts the tablet going back into the endless cycle.
I am now totally stuck. Please help.
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
tcrews said:
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
Click to expand...
Click to collapse
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
shah123 said:
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
Click to expand...
Click to collapse
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
goodintentions said:
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
Click to expand...
Click to collapse
Hey goodintentions, I know you have good intentions , but I have been working with gtablet mods for quite some time now. Usually when you have a bricked gtablet, you are desperately looking for a solution. That's why I hopped from Vegan to Cyanogen to stock etc within an hour or so. And when you have been working on things for some time, you tend to not look at anything that says "start here". Honestly I had never seen your page before, which by the way is pretty good and would have been a life saver if I had known it.
I wonder... what should I name the page as?
I promise you, my instructions work for 99% of the problems people encounter.
goodintentions said:
I promise you, my instructions work for 99% of the problems people encounter.
Click to expand...
Click to collapse
I have no doubt.
i installed cm7 on my touchpad last week and everything went fine. so i tried to install it on my friends 32 gb touchpad and i get stuck in a bootloop. moboot seemed to install fine becuase i have the boot menu working, cwm works, but when i try to load cm7 i get the green pic that says cyanogenmod loading but after that it goes back to the hp logo and starts over. i can boot into webos just fine but cm7 gives me the run around. ive tried doing a factory reset, wiping the cache and dalvik cache from cwm but nothing. i even tried making a nandroid backup from my 32 gb touchpad and tried to copy that to my friends touchpad but i got an error in the restoring process. ive also tried reinstalling the zip through cwm and through the acmeinstaller. do i have to doctor it and try again? has anyone run into this problem?
thanks
I have the exact same problem on my touchpad. I've tried every single option I can think of (I've reset everything, re-installed WebOS 5 times, cleared all caches, attempted to install from zip, etc.), at one point I did have it boot into Android once, but when I came back the next morning it had rebooted and was sitting at the CM7 screen frozen and wouldn't boot back into CM7. I'm thinking it has something to do with corrupt memory on a certain sector of the flash, so I've been looking for a way to format the entire partition and then try a WebOS doctor, but there doesn't seem to be any information on it. So... I'd say we're stuck for now.
I installed alpha 1 and it was working well with the usual hiccups. Then I backed up alpha 1 and flashed alpha 2.1 and it installed.
The update was working great and then I decided to check the reboot to Web OS to check how things work. Web OS worked great then I booted to cm7 and got the dreaded boot loop.
Tried reflashing over and over but same result. Luckily I had backed up first alpha so I restored it and it did boot loop again, but only once this time,before booting into rom.
So I believe the issue has something to do with alpha 2.1.
Sent from my HP Touchpad using xda premium
Could be, my one successful boot in Android was in Alpha 1. I may be experiencing a somewhat different issue as mine only boot loops sometimes, others it just sits with the CM7 circle spinning until I force it to restart. I'll see if I can get Alpha 1 to work again.
Doin some Googling I found a thread on Google code with people that have the same problem, no fix as of last night when I checked but I subscribed to the thread to Ger notified when it is updated. Don't know if xda will allow a link to the thread so if you want the link pm me and ill send it to you
Sent from my PC36100 using xda premium
So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2