406 BB for DSC fix - Streak 5 Q&A, Help & Troubleshooting

upgraded from gs2.4.4 yesterday, like the few others i had the problem with bb not converting to 406. solved by letting system boot all the way through after flashing 406 recovery and 406 ROM, check that bb is now 406, then reboot and continue to streakmod flash dsc. (not sure if 406bb really makes difference, phone still operational while temporarily stuck on lower bb)
is anyone on gxkernels on dsc? how's your wifi hanging?
thanks.

Related

[Q] Streakdroid disables wifi, cannot get it to work

I've never been able to install streakdroid on my dell streak due to this issue, and as this is the third time I've spent practically a whole day trying to do it and it still won't work, I figured it's time to ask for some help.
I'm running the stock 02 2.1 build 8105, and the streak is locked to o2. I tried to flash streakdroid using the guide which tells you how to upgrade from the 8105 build, although obviously I used the 1.9.0 zip to upgrade rather than the old one it links to. Everything else I followed to the letter.
Upgrading to stock o2 2.2 via the system update works fine, and the wifi is fine, but when I flash streakdroid, I can't turn on the wifi - it just says error. Wifi mac address is also unavailable, and even after factory resets, cache wipes, and practically everything you can think of it still won't work.
This is extremely frustrating as I'm sure I'm doing it right, and whenever I install streakdroid it's clear how much better it is. Sadly, I need wifi so have to keep flashing back to o2 2.2/2.1.
So, can anyone help me? Has anyone used the same route as me and can upload the exact files they used along with the steps?
thanks.

[Q] using update.pkg vs just flashing the baseband

Hi all,
I've had a search but can't seem to find the answer to this query:
I've seen a few posts now that say you need to do an update via a .pkg to put a new baseband on, rather than just pushing the amss via fastboot.
What I'd like to find out is what's missing if you just flash the baseband?
I went from O2 2.1 to various Streakdroids (1.4 to 1.5.3 to 1.7, 1.8.1 and now 1.9.1). I flashed baseband 318 at some point and recently flashed 354 to the 1.8.1 build before upgrading on Monday to 1.9.1
Im not happy with battery life currently and also feel the performance should be better, compared to other people's posted figures.
Also a lot of folk are claiming over double the battery life I'm seeing.
What do I gain, if anything, by installing say the official 2.2.2 or 2.2.3 update.pkg and then re-installing Streakdroid 1.9.1? Can anyone give me a few pointers?
cheers.....
Read the last few posts in gingerstreak thread where they have very good explanation on this debate.
Sent from the Dell Streak
thanks!
Ideally I'd like to discover a bit more about what there is and what does what but that certainly tells me i need to go do the .pkg update and re-install!
much appreciated
Yes I had a issue with just flashing the baseband. Market and any other app would not update or install on my phone. Once I did a update pkg then install 1.9.1 all is good now.
Sent from the Dell Streak
quick answer would be, is that an official update.pkg will flash all the images built specifically to be compatible with eachother, including some core code.
afaik, flashing baseband on its own shouldn't really make a huge impact on stability..
I use 318 BB just cause its the last official 00 regional update in australia.. I could use 351 BB, which is the last 00 BB, which I've tried, but 318 works best.
cheers!
Stability is very very good, in fact it doesn't hang or reboot at all (as long as the CPU is kept at 1152 or under)
I was really thinking about battery life (there are rumours of the batterystats from 2.2.2 showing longer life and mine is currently awful), signal strength, wifi, graphics performance (my quadrant score seems low at 1571) etc.
i'll probably give it a bash anyway - all good for experience!
I am having the same issue with my streak. Battery performance does not seem as good as others report on 1.9.1, and I am unable to overclock past 1152 without freeze/eventual reboot.
Phone originally had ATT 1.6 on it, then upgraded to OS2 2.1, then to various versions of StreakDroid and currently 1.9.1.
Today I tried using the 351 recovery.img and flashed the 351 update.pkg for the stock ROM. After successfully booting and using the stock rom for a bit, I did a factory reset then I flashed back to streakmod recovery and then re-loaded streakdroid 1.9.1. Then I did another factory reset.
This made no difference on the overclocking issue for me. Any ideas what I could/should i try next?
I think thats purely a hardware factor. The CPUs have varations in clock speed limit and it looks like yours is the same as mine
Gonna play with .pkg updates over the weekend and see what if anything happens to battery life. Maybe I just use it too much

How to find/fix kernel issue?

Alright, so I have a problem where my bluetooth and wifi don't work at all. Wifi status shows up as error and when I try to enable it, it just puts the phone in a reboot cycle where it starts up for a bit then restarts unless I can catch it fast enough to put it into airplane mode. From what I've been reading after doing some looking around on the net, it's most likely a kernel issue.
How can I figure out exactly what is causing this issue so I can flash over the corrupt kernel and try to get it to work? I've tried flashing 3 different roms but none of them fix the problem so I'd like to try to find a way to figure out which individual kernel is causing it.
Post what you've installed and what you're running. Usually using a ROM that does a full wipe will usually solve any issues. Are you using ROM manager to do your installs or CWM?
Originally I was having this issue on 1.83. When I used rsdlite to flash the stock 2.3.4 sbf, it fixed the issue for me. I later tried to install the new androidmarket apk and the issue came back.
Since then, I've used Tenfar's CWM to flash Ninja SF, Alien, the CWM stock 2.3.4 and am now running piCrust but I haven't been able to fix it again.

[Q] Original battery life.

Hey quick question, Running my streak with Streakdroid 1.9, only background apps are widgetlocker, twitter/facebook sync updates (even though they only seem to update properly when i tell them to.
Average use, few texts throughout the day, screen brightness on about 30%, no phone calls and minimal wifi or 3G data use as i'm around computers all day. I never use it for music/movies either.
Took off charge at 9.12AM, 86% at 12.28, after no use other use than sending 2 texts and receiving one. I got this phone in November last year, is the battery literally just this shocking or should i email DELL about getting a replacement?
TLR = Original battery dies faster than the person that says they'll brb in horror films, what do? (Also what's the correct email address to ask for?)
-Sean
Maybe you should try a new baseband?
Sent from my Dell Streak using XDA App
valest said:
Maybe you should try a new baseband?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
See i've asked this many times, what is a baseband and what does it do? I've never upgraded it due to the fact no one has answered this question
Also how would a baseband affect battery life? My phone says: GAUSB1A131921-EU
Seanyftw said:
See i've asked this many times, what is a baseband and what does it do? I've never upgraded it due to the fact no one has answered this question
Also how would a baseband affect battery life? My phone says: GAUSB1A131921-EU
Click to expand...
Click to collapse
IIRC, baseband is a separate ARM CPU running a real time operating system that handles the actual business of communicating with the mobile phone network. When flashing the phone, 'baseband' = operating system image for this CPU. You need a baseband version compatible with the version of Android you're running (what exactly is compatible in this context depends on the phone + version of Android)
Different baseband could affect battery due to different mobile radio use pattern or maybe by keeping Android awake for longer or by different power saving behavior on baseband CPU etc.
Not Relevant said:
IIRC, baseband is a separate ARM CPU running a real time operating system that handles the actual business of communicating with the mobile phone network. When flashing the phone, 'baseband' = operating system image for this CPU. You need a baseband version compatible with the version of Android you're running (what exactly is compatible in this context depends on the phone + version of Android)
Different baseband could affect battery due to different mobile radio use pattern or maybe by keeping Android awake for longer or by different power saving behavior on baseband CPU etc.
Click to expand...
Click to collapse
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
351 AMSS.mbn
Retail 00
353 AMSS.mbn
USA AT&T Region 31
354 AMSS.mbn
Hong Kong Region 11
Code:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c reboot
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
Be advised,SD2.0 is still a working progress,not stable release!
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
I'm afraid I don't know. I'm on the same baseband as you and I want to know if it's safe to install retail 351 on it. I know that the wrong baseband could stop your phone booting, might make Android unstable, prevent you making phone calls or accessing internet over 3G so I'm not keen on risking it...
nickshertzer said:
351 AMSS.mbn
Retail 00
353 AMSS.mbn
USA AT&T Region 31
354 AMSS.mbn
Hong Kong Region 11
Code:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c reboot
Click to expand...
Click to collapse
Thanks for this but which one should i use? I'm using Streakdroid 1.9
-Sean
Seanyftw said:
Hey quick question, Running my streak with Streakdroid 1.9, only background apps are widgetlocker, twitter/facebook sync updates (even though they only seem to update properly when i tell them to.
Average use, few texts throughout the day, screen brightness on about 30%, no phone calls and minimal wifi or 3G data use as i'm around computers all day. I never use it for music/movies either.
Took off charge at 9.12AM, 86% at 12.28, after no use other use than sending 2 texts and receiving one. I got this phone in November last year, is the battery literally just this shocking or should i email DELL about getting a replacement?
TLR = Original battery dies faster than the person that says they'll brb in horror films, what do? (Also what's the correct email address to ask for?)
-Sean
Click to expand...
Click to collapse
I run 1.9.1 and finally, my battery will last me over 24 hours. And thats with moderate use, trip to three hours of phone use on a bluetooth headset, and even some video from youtube or crackle. What I did this time was to install the stock 354, then 1.9.1 over that. I had bounced around between different roms so much that I'm sure my firmware files were all mismatched. Installing a stock rom from an update.pkg, not update.zip, installs several firmwares. The bandana off only one of these, albeit the most popular.
After the install I started using apps such as spare parts and cpu spy to help me figure put what was using up my battery the most. I turned my notifications to every two hours for Tweetcaster Pro and turned off notifications for Facebook. The facebook app seemed to be one of the biggest culprits.
It takes a little bit of work and patience to figure it out, but it makes a huge difference in the end. I no longer worry about my battery not making it through my day anymore.
Sent from my Dell Streak using Tapatalk
The hong kong and retail one you can try! for your question,I think the kernel is,more affect the efficiency of you phone related to battrry life.
lordmorphous said:
What I did this time was to install the stock 354, then 1.9.1 over that. I had bounced around between different roms so much that I'm sure my firmware files were all mismatched. Installing a stock rom from an update.pkg, not update.zip, installs several firmwares. The bandana off only one of these, albeit the most popular.
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
So what method did you use to accomplish that. I am interested in trying flashing stock (probably either 351, or 353) and then putting SimpleStreak 1.2 back over top. When I got some free time today and tried to do it I realized that Clockworkmod recovery replaces the option that would let me flash an *.pkg file. Did you flash the stock recovery, flash the stock rom, then reflash clockworkmod?
Thanks for the help.
cwegga said:
Did you flash the stock recovery, flash the stock rom, then reflash clockworkmod?
Thanks for the help.
Click to expand...
Click to collapse
Correct. Except use StreakMod and not Clockwork.
That's what I did this time. Though in the past I was using Clockwork because the previous versions of Streakmod I had tried didn't agree with my phone. I used Multirecovery flasher and it worked great. The only snag I went into is none of my nandroid backups would restore.* It made the whole thing more of a headache than it needed to be. From now on I guess I'll have to try restoring right after I back up to make sure everything is working.
*I tried to restore them through the same version of Clockworkmod that I had before and they all failed with the checksum error.
cwegga said:
. . . . .
*I tried to restore them through the same version of Clockworkmod that I had before and they all failed with the checksum error.
Click to expand...
Click to collapse
Did you rename the folder the backup was in? Spaces and some otjher characters can cause issues, search and you will find posts relating to this (see the clockwork and streakmod threads).
You can also manually check the md5 sums of the backup to see if the values in the file agree. There is a file named nandroid.md5 that is just a text file with the checksums, compare these values with the checksums for the files in the backup. I use hashcheck in WinXP to add the checksums to the properties dialog in the file explorer.
marvin02 said:
Did you rename the folder the backup was in? Spaces and some otjher characters can cause issues, search and you will find posts relating to this (see the clockwork and streakmod threads).
Click to expand...
Click to collapse
Nope, I didn't change a thing. At first I flashed the wrong recovery(Streakmod) and it said it couldn't find them. But I dug through my computer and flashed what I believe is the same version of Clockworkmod (should be the same, It's the only non-stock recovery I had saved) that gave me the md5 errors. No biggy though, after some hours of work and playing most of Cut the Rope again I'm pretty much back where I was.

P500h - root+upgrade process.

I've got a Telecom NZ P500h phone here which Superboot would refuse to root as surprisingly it came with a late October release of 2.3.3 OOTB.
I had to use LGMDP to flash the old (December) 2.2.1 release of the same P500h firmware (from the thread in the dev forum), and I was then able to root it with Superboot.
I then had to use LGMDP again to flash the v20g baseband - this is the slightly dodgy bit as there doesn't seem to be a v20g baseband anywhere that is specifically for the P500h. I bit the bullet and flashed it anyway, and the phone now identifies as a standard P500. (Uh oh I thought).
Once I'd done that, I used the manual method to flash the current v3.06 ThunderG recovery, then rebooted into recovery and flashed the GingerLOL ROM.
Rebooted, and everything seems to work fine. WiFi works, 3G data works, calls work.
So, I'm not sure what difference the "h" designation implies, but unless I've yet to find something nasty, crossflashing it to a standard P500 seems to work just fine.
Now I'm about to flash it to the current AGA ROM instead as GingerLOL hasn't been updated in a long time. Not keen on CM7 as it seems to have too many issues.
So, if anyone else has a 500h phone, then you might be lucky and this process will work for you. If someone has gone through the same process and knows of issues I'm likely to come across as a result, please let me know!

Categories

Resources