So as the title says I want to downgrade back to 2.2 and install simple streak 1.2
Don't think that I can downgrade directly.So how could I go abou3t it?
I wanted sonething nice and not so buggy.how is lobghorn compared to the simplestreak?
Are you aware that version 2.4 of GingerStreak is available and is far more stable than 2.3?
If you want to downgrade, restore a stock ROM first. Doing so replaces the broadband and amss files, as well as ensures that you have a consistent base to work from before putting on SimpleStreak. After that, replace the stock recovery with StreakMod then flash SimpleStreak.
You did search the forums before you asked this I hope?
I was.First thought was to do that.But i didn't quite know if that would replace the amss and the other files i had flashed.Figured i'd double check before attempting anything.
I somehow missed the stability of simplestreak so figured i'd jump to that since streakdroid is pretty much still in beta and some annoying issue or the other always pops up.
With the new StreakDroid comes new baseband and amss files, so you'd have to flash anyway. A stock ROM would put its baseband and amss files on the Streak in place of the ones you used for StreakDroid. But I completely understand the prospect of annoying issues cropping up.
I used the ROM for about a week without a single crash. But then I lost my battery cover and so had to go back to SimpleStreak which has the sensor disabled.
Flashed SS1.2 over 2.4, and did a factory reset. Simple!
Related
Hey everyone, I recently obtained an unlocked Streak from Dell running the 347 baseband, There is sadly no update.zip on my SD as other with this build have said in other threads. So far I have successfully rooted my streak and want to move to Streakdroid 1.9 but have seen multiple threads with people coming from my build getting stuck in bootloops and such trying to move to Streakdroid.
Has anyone had success flashing from 347 to Streakdroid 1.9 or any other versions? If so, what extra steps, if any, were required to flash these ROMs without issues?
Thanks for all the help!
Mine was on 347 and i flashed to Streakdroid without issue.
Only problem i had was making a backup with Nandroid prior to flashing which i outlined in another thread in this section.
Other then that it has been smooth sailing and i have went back and forth testing stuff between both the Stock OS and Streakdroid and have had 0 issues to speak of .
quazimojo said:
Mine was on 347 and i flashed to Streakdroid without issue.
Only problem i had was making a backup with Nandroid prior to flashing which i outlined in another thread in this section.
Other then that it has been smooth sailing and i have went back and forth testing stuff between both the Stock OS and Streakdroid and have had 0 issues to speak of .
Click to expand...
Click to collapse
did u do a factory reset or anything before flashing Streakdroid or did u just flash the update.zip and everything worked?
The first time i flashed the ROM i litterally just flashed right over the Original factory one.
After going back and forth messing with stuff i have done a factory reset on both the Original and DJ's .. Not sure i really had to or not but since DJ recommends to do a factory reset after the install i did it the second time i flashed his ROM .
I went back and forth a few times as of today and everything is peachy and am currently on his ROM with the Perfmod Volppt Tabmail in the install.txt file..
Another thing i believe people are making a mistake on possibly is when making the install file from notepad naming it install.txt when infact you just name it install because the txt suffix is on the end already you just dont see it in Windows unless you have file extensions enabled .
im still on the old 305 bb/rom...i have thought about putting a newer rom/bb like the 351.....but my phone is working good now....even with 1.9.0 on it,and the ro.ril hack.
what reason should i update....what better if any would i see.....please let me know....i really just want to mess with it....but it is running good now,so i really need some improvement to justify it.
Answer is pretty simple...
If you update to the latest BB, and theoretically use your phone in the exact same manner as you do now, then you will see improved battery life AND have a quicker phone when you do use it for apps... it's pretty much a no brainer
Does BB and ROM have to be identical? i.e. Can we flash the 354 BB on the 351 ROM? Would there be any potential benefit or drawback to doing so?
Well that used to be more of a commom practice, but a couple months ago TheManii suggested it wasn't such a good idea to flash parts of ROMs such as dsp and amss, etc... so what I suggest to you is for the best performance is:
Choose your ROM, 351 or 353
Flash stock recovery for the ROM you want to use
Download and place update.pkg of that ROM on your SD card
Flash the ROM, do a factory reset and let it boot
Download and have your custom ROM if you're gonna use one on your SD
Flash StreakMod and immediately boot into StreakMod
Flash your custom ROM (recommend StreakDroid or SimpleStreak (I use StreakDroid personally)
Let it boot and you should be trouble free, and all internal SD files and internal flash memory should now be in sync.
You should do all this with your phone at 100% battery.
You should see much better performance, no force closes and much better battery life, at least this was my experience
From all of the discussion I have seen 354 is very little different than 351. The biggest difference is that 354 is customized for the Hong Kong region and has limited language support.
cdzo72 said:
Well that used to be more of a commom practice, but a couple months ago TheManii suggested it wasn't such a good idea to flash parts of ROMs such as dsp and amss, etc... so what I suggest to you is for the best performance is:
Choose your ROM, 351 or 353
Flash stock recovery for the ROM you want to use
Download and place update.pkg of that ROM on your SD card
Flash the ROM, do a factory reset and let it boot
Download and have your custom ROM if you're gonna use one on your SD
Flash StreakMod and immediately boot into StreakMod
Flash your custom ROM (recommend StreakDroid or SimpleStreak (I use StreakDroid personally)
Let it boot and you should be trouble free, and all internal SD files and internal flash memory should now be in sync.
You should do all this with your phone at 100% battery.
You should see much better performance, no force closes and much better battery life, at least this was my experience
Click to expand...
Click to collapse
Thanks for the info.......im going to do this,and put the 351 on her.....and maybe go with 1.9.0 or simple streak......and wait till a complete and stable gingerbread custom rom is put out....if ever
Sent from my Pimped Out Dell Streak using XDA Premium App
also FYI: if you use a stock rom and your baseband doesnt match (ie bb354 with stock 351) you'll get the blinking leds issue.
This is by design in the rom as it complains that they dont match.
Custom roms have it disabled, they dont care what bb you have (though they should as old bbs are generally a bad thing)
TheManii said:
also FYI: if you use a stock rom and your baseband doesnt match (ie bb354 with stock 351) you'll get the blinking leds issue.
This is by design in the rom as it complains that they dont match.
Custom roms have it disabled, they dont care what bb you have (though they should as old bbs are generally a bad thing)
Click to expand...
Click to collapse
Manii i have a question, i got my phone from dell new rma'ed a week ago, it had 339 bb installed and android 2.2.1, i rooted it, put streakdroid on it and everything then flashed to the 351 amss.bin, now am i still suffering from depleted battery life doing this, or should i flash over the 351 rom itself, then nandroid back to my old save? or how would that work?
first you shouldnt just flash the bb, you should use the entire update pkg,
and secondly that shouldnt directly be involved, did you factory reset before installing sd? it might be a config issue, it's likely more of a SD issue then a bb issue
Need advise, guys,
I installed 354 Rom (of course with 354's baseband) and Nadroid backup.
Flashed 406 baseband and install GB Rom.
Now,
I restore Nandroid backuped 354 Rom and seems everything ok..
My question is ;
Do I have to re-flash baseband of 354 Rom or automatically restored through Nandroid so not unnecessary to re-flash for baseband ??
Thanks.
Nandroid doesn't restore the baseband. That's low-level stuff that you need fastboot to change.
Strephon Alkhalikoi said:
Nandroid doesn't restore the baseband. That's low-level stuff that you need fastboot to change.
Click to expand...
Click to collapse
Doesnt it? I didnt know that..because I've been jumping from Froyo(simple streak) to GB (DSCv06b) everytime with just the nandroid backup..and everything seems to be doing fine on both.
I am sure nandroid does not touch those files. If you did a search on the forums you would find posts mentioning the recommended method of restoring the amss and dsp files is to install a stock ROM because doing so guarantees that all the files have the same version number.
In your case, you have a Gingerbread baseband and I presume you're running a custom Froyo ROM. As you note, you've had no problems, but I bet if you look at the baseband, you'll be quite surprised at what version is present.
Thanks soooo much...
Strephon Alkhalikoi said:
I am sure nandroid does not touch those files. If you did a search on the forums you would find posts mentioning the recommended method of restoring the amss and dsp files is to install a stock ROM because doing so guarantees that all the files have the same version number.
In your case, you have a Gingerbread baseband and I presume you're running a custom Froyo ROM. As you note, you've had no problems, but I bet if you look at the baseband, you'll be quite surprised at what version is present.
Click to expand...
Click to collapse
Now, I can understand why sometime my GB5 acting weird....
Thanks a lot !!
Strephon Alkhalikoi said:
I am sure nandroid does not touch those files. If you did a search on the forums you would find posts mentioning the recommended method of restoring the amss and dsp files is to install a stock ROM because doing so guarantees that all the files have the same version number.
In your case, you have a Gingerbread baseband and I presume you're running a custom Froyo ROM. As you note, you've had no problems, but I bet if you look at the baseband, you'll be quite surprised at what version is present.
Click to expand...
Click to collapse
hmmm...thats weird..because my baseband for GB shows 406 coming from Froyo Nandroid backup. So for me, it did change the baseband.Anyways, I might actually did good doing that restoring the GB from Froyo , because since the last time I did that,I never had an FC or SOD.Unlike when I first installed GB (streakdroid and dsc) by the recommended flashing of BB and DSP1 first and factory restore,heaps of issues.But since that my Streak have been stable as SimpleStreak was.
Okay in the last three days I have softbricked my vibrant several times. Each time after tyring to update to a newer ROM. Now however I can not even return to what I had, only the Eclair ROM. I was running Tigers Breath Kernel with Bionix ROM
I should point out that my efs has hone corrupt mysteriously on this phone twice before in the past , and luckily I made a back up that was easily restored.
I now have a vibrant that was restored to a stock image however I believe the stock image is incomplete. It lacks the ability to reset.Says Something like reset service unavailable. I would be happy for now at the stock eclair image however I run into the same issue I had on Eclair before. Android Market will not download any apk, it starts pauses and fails.. When I look at the corresponding device in google play on the web I see it says PHONE and there is another SAMSUNG GALAXY VIBRANT T 969 . However the corresponding device is PHONE . So Google has no idea what my phone is. This could be the market issue however I want to point out that when I first set up the google account I can go to the market and download but once the market app is updated, it no longer works!
So a few days ago my goal was to attempt to install Gingerbread or higher to take a look at xbmc for android betas. The result has literally given me a 3 day headache.
before three days ago I was running Bionix and Tigers breath kernel. I tried to follow instructions to downgrade to stock and then to Gingerbread or higher. I have now made more the several attempts. All I can do is O|DIN to the stock image I have which complains that oit lacks the reset service.
Even trying to restore either of My CWM back ujps of Bionix fails.
I also have another interesting thing that when I attempt to install CWM from an update.zip I get screen goes black for a second then i see CWM running . It is as if it is running it instead of installing it.
The one image that I have that I can restore does have ROM manager that55 always reports a download error with installing CWM from there
Is there an image that I can install from ODIN that will get me Gingerbread or higher? ODIN seems to be my only hope.
And what of the market errors , do ya think my EFS is hammered again? before the issue was the electronic serial number (dont remember what its called) but the carrier stopped honoring the generic number it was producing. I do however recall last year that I could not get the market working and now I seem to have returned to that. I think it has much to do with the market version on Eclair.
would the vibrant be adequate to run XBMC beta at lest to test it?
Should I repartition from ODIN?
Is there a stock froyo image around at least that I can install from ODIN?
Thanks,
Mark
Yes you should check repartition when you use Odin to flash ROMs. There are froyo Odin images out there but I don't think there is a "true" stock 2.2 froyo image, only custom ones. I know there is a ROM uploaded by moped ryder that is as close as you will get to stock 2.2, fishman made an odin image of it. You can check it out here http://forum.xda-developers.com/showthread.php?t=1674519. I know for sure fishman uploads odin images with his 2.2 ROMS, they are far from stock but I love them. I've been running Axura resurrected 2.2 for months, its solid. You can check it out with this link http://forum.xda-developers.com/showthread.php?t=1787267, it has odin images. Just be sure to read first and follow directions.
Sent from my SGH-T959 using Tapatalk
If it was me, I would Odin back to stock JFD. There is a guide on YouTube by Eddie1west that I recommend.
Then just I would follow the guide to install Gingerbread boot loaders.
Then I would download and wipe/wipe cache/dalvik and flash a fresh Froyo ROM download. I use Bionix V fishmans with the Bali kernel. Then if your satisfied then stop. If not, download latest CM9 Nightly (ICS). Wipe/wipe cache/dalvik and flash the ROM and common files.
Since you've gone this far download latest Helly Bean all in one, wipe/wipe cache/dalvik and flash HB and the add on file.
Might as well right? I had lots of trouble flashing up to HB yesterday, and I had never had any issues before.. but if your looking to get to GB or beyond... I would follow the steps above. Could be overkill. But I tried about every other combination of flashes I could think of before Odining back and doing it that way.
Hello , everyone... i recently purchased a Dell Streak 5 and like the phone ..but do not know how to update its Android software.my goal is to get a more up to date android firmare onto the device.i have initially tried the volume up/down /power on ..to acess the ..factory reset..the update from sd card ..and the screen calibration ..menu. and have pressed (camera button ) to highlight from SD card ..but it then goes to a page which outlines android recovery software..and has my baseband number next to it .
1. does that mean a recovery image for the dell streak 5 must be actually on the sdcard at that time eg. recovery.img or must it be installed /mounted ..i am unsure.
i apologise for a myriad of questions....
2. the update.pkg i understand these are region specific.
mine is baseband GAUSB1A110421-EU build 3883.
3. will other basebands work ?
the idea is i make small steps to slowly upgrade from 1.6 to improve the lifespan of the handset.
any basic help would be appreciated.
breaktx
Unfortunately, the fact you're still on Donut (Android 1.6) means that basic help is going to be impossible. The reason being that, if I recall correctly, to do the upgrade from Donut to a later version will require you to manually flash both a new baseband and a new recovery before you can even install a Froyo (Android 2.2.2) ROM. Since you have to flash a new baseband and new recovery anyway, you might as well skip the baby steps and go straight to a custom ROM.
I know that's not the answer you were expecting and I apologize, but it's the simple truth of the matter. In answer to your questions...
1. The recovery image is loaded into the Streak the same way the baseband files are, through the Streak's fastboot mode. While you should look in the Dell Streak wiki on XDA for instructions on how to manually flash the baseband and recovery, I have a tool that can automate the process so all you really have to worry about is installing the drivers, which should be possible using Dell's sync software.
What is stored on the MicroSD card are the actual ROM files. Dell provides them in a .pkg format compatible with the stock recovery. Custom ROMs are provided as .zip files which will not work in a stock recovery but will work in a custom one.
2. Dell ROM packages are region specific. The baseband files and the recovery are all region specific. These regions must match to be able to flash a stock ROM. In your case, going from Donut to Froyo is such a huge jump that the only way I recall to accomplish it is to manually flash the baseband files and stock recovery. It's not as dramatic going from Froyo to Gingerbread (Android 2.3.3), but manually flashing the baseband files and recovery is why I recommended in my opening paragraph to skip the baby steps. Since you're going to have to flash both baseband and recovery anyway you might as well go with a custom ROM rather than stock.
3. This question was partly answered in 2 above. It is possible to install a baseband from a different region than the recovery. As long as the region of the recovery matches the region of the ROM the ROM will install. However, when you boot the device, the OS kernel checks the firmware version of the baseband files to see if it matches what the kernel expects. If the versions do not match, your Home, Menu, and Back buttons will all flash every few seconds. This is an indicator of a baseband mismatch.
To resolve a baseband mismatch you would need to flash the correct baseband. The custom Gingerbread ROM I offer, its predecessor, and all the Cyanogenmod 7-based ROMs all have the baseband check disabled in the kernel, allowing any baseband to be flashed. For an easy example, take a look at my ROM or its predecessor and their "Flash Me Before Installing" packs. That pack will install the 366 baseband, while the ROM itself is 407. Ordinarily there would be an issue of flashing lights but the check was disabled in the kernel, so the flashing lights will not trigger.
Ref: Donut (android 1.6) help.
First and foremost thanks Strephon for the swift response as regards my dilema and an insight into the tasks i may have to do ,to achieve a more useable gui for my device. I sadly do not fully understand this "flashing " process as it is all totally new to me. All i can do is take onboard the points raised ,and take some time to read through the streak wiki.I must admit what you have outlined does actually sound promising with the baseband flashing and the custom rom . I have recently read of such tools as Fastboot ...Android -adb...clockworkmod recovery ..but it is tricky ..for eg .i get into fastboot mode ..connect to my pc ..open cmd ....and it all falls apart from there..as i try to navigate to where fastboot is situated but i fai as the command in the windows shell i cant do as of yet. I appreciate the last thing people need is a fellow user whingeing/whineing as i know it is possible to get a Custom rom onto said device ,but nevertheless must face up to its ...quite hard to get to grips with. As said prior Many thanks for a quite indepth response detailing what i may have to do ..to get a custom Rom to work on my Dell streak 5.in the future i may try the advice given ..with regards the baseband ..and rom ..aswell as the dell sync software.
sadly i am very limited on my knowledge of this subject ...for me the end goal is getting a nice os running on the device ..which has a pleasant interface.I am realistic ..yes the device is years old but it still has capability to be of use to me ..
once again thankyou for the reply/feedback
breaktx
Strephon Alkhalikoi said:
Unfortunately, the fact you're still on Donut (Android 1.6) means that basic help is going to be impossible. The reason being that, if I recall correctly, to do the upgrade from Donut to a later version will require you to manually flash both a new baseband and a new recovery before you can even install a Froyo (Android 2.2.2) ROM. Since you have to flash a new baseband and new recovery anyway, you might as well skip the baby steps and go straight to a custom ROM.
I know that's not the answer you were expecting and I apologize, but it's the simple truth of the matter. In answer to your questions...
1. The recovery image is loaded into the Streak the same way the baseband files are, through the Streak's fastboot mode. While you should look in the Dell Streak wiki on XDA for instructions on how to manually flash the baseband and recovery, I have a tool that can automate the process so all you really have to worry about is installing the drivers, which should be possible using Dell's sync software.
What is stored on the MicroSD card are the actual ROM files. Dell provides them in a .pkg format compatible with the stock recovery. Custom ROMs are provided as .zip files which will not work in a stock recovery but will work in a custom one.
2. Dell ROM packages are region specific. The baseband files and the recovery are all region specific. These regions must match to be able to flash a stock ROM. In your case, going from Donut to Froyo is such a huge jump that the only way I recall to accomplish it is to manually flash
the baseband files and stock recovery. It's not as dramatic going from Froyo to Gingerbread (Android 2.3.3), but manually flashing the baseband files and recovery is why I recommended in my opening paragraph to skip the baby steps. Since you're going to have to flash both baseband and recovery anyway you might as well go with a custom ROM rather than stock.
3. This question was partly answered in 2 above. It is possible to install a baseband from a different region than the recovery. As long as the region of the recovery matches the region of the ROM the ROM will install. However, when you boot the device, the OS kernel checks the firmware version of the baseband files to see if it matches what the kernel expects. If the versions do not match, your Home, Menu, and Back buttons will all flash every few seconds. This is an indicator of a baseband mismatch.
To resolve a baseband mismatch you would need to flash the correct baseband. The custom Gingerbread ROM I offer, its predecessor, and all the Cyanogenmod 7-based ROMs all have the baseband check disabled in the kernel, allowing any baseband to be flashed. For an easy example, take a look at my ROM or its predecessor and their "Flash Me Before Installing" packs. That pack will install the 366 baseband, while the ROM itself is 407. Ordinarily there would be an issue of flashing lights but the check was disabled in the kernel, so the flashing lights will not trigger.
Click to expand...
Click to collapse