I have an odd problem. My Dell Streak will boot but once it gets into the OS none of the buttons are responsive. It is not frozen however. I've recalibrated the touchscreen but that does nothing.
However, the controls work when I am booted into recovery and the screen before fastboot.
The person I bought it from had tried to install StreakDroid but I'm not sure how he went about it. I followed the guides, flashing the correct amss and dsp. But I have the same issue.
I'm wondering what the problem could be. Should I try and flash the original Dell rom back on first and see if that works? It is just odd that everything works except when it has booted into Android.
I'm going to assume you have a custom recovery on there. If so, make a nandroid backup, flash a stock recovery, update via the matching pkg file, flash StreakMod recovery, then restore your nandroid backup. That will ensure all the firmwares "match", which could be causing your problem. It sounds like you aren't sure of the history of the roms and such on this phone. This will start you out at square one without losing your custom rom and settings. Certainly couldn't hurt.
I've tried to install the stock pkgs (I tried 360 and 319) but both stop working at the end of the install. How long is the install meant to take? Because I've left them for half an hour at the end but it hasn't completed
Related
Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
kero4 said:
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
Click to expand...
Click to collapse
delete whatever update.zip you
http://forum.xda-developers.com/showthread.php?t=849028
get the 1 from there, reinstall packages twice and it should go to clockwork recovery
Okay, obviously option b would be better, however, will I have to reroot after if I use option B?
Nadda, same results, it's okay though, I'll live with it for now since I'll keep 2.2 with all the crud removed for now.
Please read that guide. You've missed some key points. I'd explain more, but I'm hanging with my kid.. Read the guide.
had the same problem i used this method and it worked for me
http://forum.xda-developers.com/showthread.php?t=833423&highlight=recovery
I've made a few mistakes when trying to install the latest cyanogen Nightly to my SGS2.
I initially tried the ROM Manager method of flashing to Cyanogen but only managed to get myself stuck in only being able to boot into ClockWork Mod Recovery mode so I ended up having to use Odin to re-flash with Stock Mod (had to guess which stock rom I needed as I hadn't looked it up before heh) and when that completed my phone booted up ok and all my apps were there but the screen was strangely washed out in appearance. Not sure if the o2 UK rom that came with the phone had some tweaks to make the colours richer or something - I checked the display settings and it was at the setting I'd chosen previously.
Anyway, I re-tried using the Recovery mode instructions and now my phone is stuck at the boot screen and has been for 20 minutes. I'm aware the first boot after cyanogen is installed is meant to be longer (while it dexopts or something like that) but 20 minutes seems a trifle tardy so I suspect it's gone tits up again.
Oh well.
Onto my question:
I want to flash with the correct o2 UK version of the SGS2 rom whilst completely wiping everything from my phone including system internal sd and external sd.
Is this possible and how?
try this procedure provided by ithehappy.
Wipe Cache+ Factory Reset should work.
Anyway, try this in keypad,
*2767*3855#
Thanks for the help
Hello,
I installed GingerStreak2.4.4, and it worked just fine for about 2months, one day I was playing some kind of soccer game where you have to swipe to give a direction to the ball, I stopped playing it and just let my streak on a table until it got discharged, I turned it on until the next day after charging it for a while, and my surprise was that the touchscreen became unresponsive.
I tried to re-install it with different densities, different launchers, I think I tried all the possible configurations in the intstall.txt (I cleaned dalvik machine and all that stuff prior to every new installation), I tried the Screen Calibration, wich it says that is correctly calibrated, but when I enter to the white fastboot screen, and run the tests, the touchpad test only work in a "small rectangle" rather than the whole screen, so I'm afraid that this is a configuration issue.
So, in order to discard any possible damage to the touchpad, I would like to be able to install .pkg files again, since that's the format the Stock ROM have (right now is only accepting .zip files). So I need to revert the recovery tool that I had to install before installing the custom ROM. Do you guys know how to revert the recovery, or to run .pkg files again at least?
Thanks in advance!
To change recoveries, follow the procedure you used to install StreakMod Recovery on the Streak in the first place. Just make sure it's a stock recovery you install.
From there, assuming that this is not a hardware issue, you should be able to install the stock ROM. After that, install DSC 0.7 instead of GingerStreak. GingerStreak's code is based off a beta version of the 407 ROM, whereas DSC is based off 407 itself.
Hi,
Issue: After system loads (I get to see launcher/sim unlock screen), couple of seconds later streak reboots. At the same time, leds swich off, than flash and reboot starts.
What I tried (almost all combinations of below points):
restore to factory settings
different roms: DSC v2.3, PCM7-Streak, Mokee OS, Longhorn 2.9.3, some ICS rom
custom recovery images: ClockworkMod 6.0.1.2, StreakMod 0.3.2.8
stock roms with corresponding recovery 366, 360, 369, 406, 407
user QDL tool from streakflash.zip/repairtool.zip do recover to Baseband GAUSB1A130500
booting without sim/SD cards
Things to note:
For flashing I have followed the procedure to wipe data, cache, dalvik, fix permissions, dell factory reset.
In the past I had not issues flashing DSC, PCM7-Streak and other roms.
When booting into service mode? (camera+power button, *#301# code) phone passed all tests (including Internal SD card).
Tests performed with two original dell batteries (one bought 8 months ago, barely used).
Batteries fully charged.
Same issue experienced with custom and stock roms.
The issue started after flashing one of the roms (DSC v2.0 probably).
To be honest I run out of ideas. Please tell me if I missed something?
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Strephon Alkhalikoi said:
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Click to expand...
Click to collapse
Thanks for advise.
I have tried starting with with 305 from repairtool.zip working my way up through 360, softbank and Olleh. Stopping at each step and flashing ClockworkMod + DSC. Same applies to any updates to each of mentioned custom roms.
The only thing that I know I could have checked better is the internal SD, just a moment ago found a neat way to get to the Internal SD - http://youtu.be/6w4AbtIGp8A. I might give it a try.