i want to know if i can take the os build from my att streak with 6601 and move it to my other streak with build 4399 on it. mainly for warranty and return/exchange purposes... as in if i were to return the one with 4399 on it would need to have the original 6601 build on it right? its just that one of them turns off semi randomly but i already put the o2 rom on it but i have another streak that is still factory fresh can i copy the OS? and if so how?
They'd be able to tell the difference, i'm pretty sure they check the IMEI number, which is unique to each phone and can't be changed, not at the moment anyway.
I think you misunderstood the question meltus,unless i've got it wrong.
I think he wants to get the stock 6601 image as he's flashed the 2.1 o2 Rom on his att streak.
he's got two and wants to take the 6601 image from a stock one to flash a faulty one that he stupidly, despite all attempts to persuade people not to do it, flashed with the o2 firmware so he can warranty it.
To answer the OP, you can try a Nandroid backup using clockwork recovery, but I'm not sure there is a working version of it for the streak yet.
Its a pity dell don't supply the shipped roms. It would save a lot of heartache, for idiots who fail to read before jumping in with both feet..
well if i just send it back as is would dell not accept it? or could they maybe not even notice?
I'm sure they would take it back. All the do is inspect the box and contents. The OS doesn't matter. You think all the PC's that they get RMA's that they turn each and every one on and inspect the OS? Hell no they dont.
i've returned many winmo devices that have been hardSPL'd (similar to rooting on android for winmo) and running custom roms. Pretty sure when they recieve a returned electronic item the flash it to whatever its supposed to have.
you shoulda done a nandroid backup..
someone kind enough can give you a copy of their nandroid if they're on that build, otherwise, you're out of luck.
well i have another streak with the correct build... im not sure how to to a nandroid backup on one and send it to the other
imperial_patrick said:
well i have another streak with the correct build... im not sure how to to a nandroid backup on one and send it to the other
Click to expand...
Click to collapse
Go to the cloclwork recovery thread (which is a sticky) and read through it. There's pretty good instructions in there. I don't have my streak yet but that is gonna be the first thing i do so i have something to flash back to if i mess it up.
It can be done!!
imperial_patrick said:
i want to know if i can take the os build from my att streak with 6601 and move it to my other streak with build 4399 on it. mainly for warranty and return/exchange purposes... as in if i were to return the one with 4399 on it would need to have the original 6601 build on it right? its just that one of them turns off semi randomly but i already put the o2 rom on it but i have another streak that is still factory fresh can i copy the OS? and if so how?
Click to expand...
Click to collapse
@imperial:
If you install the AdamG's modified clockworkmod recovery (see AdamG's thread: http://forum.xda-developers.com/showthread.php?t=754563), you should be able to perform a backup by running the nandroid command using adb.
It's not too hard and if you are interested, see my post post for instructions: http://forum.xda-developers.com/showpost.php?p=7686197&postcount=21. Make sure you have installed the clockworkmod recovery first before attempting to do the backup.
If you do decide to take the plunge, please make sure provide link to a copy the 6601 ROM backup (system.img and boot.img only)! I could sure use a copy. :-D In my haste to dump 1.6, I didn't perform a backup. I was kinda hoping someone would have provided a link to the 6601 build by now, but I guess I was wrong. Luckily, my 2.1 build has been running without any major issues.
was never able to get nanrdoid backup working with my 6601, am currently running o2 2.1 rom, would also love a copy of someone's 6601 backup if possible.
If I were able to get a nandroid backup of a US 6601 (baseband 31) 1.6 OS, theoretically would it restore my UK android 2.1 (baseband 21) back to 31?
I'm still learning this stuff so any help or advice is appreciated.
well, fone has been able to get a restore/recovery for the 6601 firmware, except it does not restore the baseband back to 31, and you are left with the flashing led light glitch. last post i think he typed he was trying to find some way to backup the 6601 baseband from an untouched US Streak. That should restore the radio and hopefully get rid of the led flashing.
johnnobts said:
well, fone has been able to get a restore/recovery for the 6601 firmware, except it does not restore the baseband back to 31, and you are left with the flashing led light glitch.
Click to expand...
Click to collapse
IIRC baseband depends on a configuration file in initrd.
Flashing leds is an effect of running incorrect kernel.
So... both issues will be solved by flashing boot.img correct for your Streak model.
Ie. I'm currently running US 6601 build on UK 21 model - it required flashing 4399 boot.img and works just fine.
I did restore the boot image from my nandroid backup and device still gave me 21 baseband but oem version was reverted to 31.
When I get to my computer later I'll give you easier instructions to backup your rom via fast boot
Sent from my Dell Streak using XDA App
have you by any chance been able to downgrade from the 8023 version?
johnnobts said:
have you by any chance been able to downgrade from the 8023 version?
Click to expand...
Click to collapse
I was able to downgrade from the 2.1 build 6941 to the US 1.6 build 6601. See the sticky with the backup posted there.
johnnobts said:
was never able to get nanrdoid backup working with my 6601, am currently running o2 2.1 rom, would also love a copy of someone's 6601 backup if possible.
Click to expand...
Click to collapse
Heres how to bakup via adb
Your device has to be rooted
Code:
$ adb shell
# cat /dev/mtd/mtd1 > /sdcard/recovery.img
# cat /dev/mtd/mtd2 > /sdcard/boot.img
# cat /dev/mtd/mtd1 > /sdcard/system.img
# cat /dev/mtd/mtd2 > /sdcard/cache.img
# cat /dev/mtd/mtd1 > /sdcard/userdata.img
Now you have them backed up on your memory card.
And i think to restore you just do the opposite
Code:
$ adb shell
# cat /sdcard/*.img > /dev/mtd/mtd#
where * is whatever img your trying to put back and make sure it corresponds to the proper mtd # as above
Related
I have to return my European GSM Hero to HTC because of a problem with the backlight and usb connection so I should restore it to the original ROM.
It's currently running one of the 2.1 ROMs and has the RA-hero-1.6.2 recovery image also.
I have all the nandroid backups I made along the way including the first one which includes boot, cache, data, misc, recovery and system. Although the recovery image in this backup would be the custom one I put on there when I first rooted it.
I also have the original recovery image that was saved when I first rooted the phone using the flashrec app.
So I guess the procedure to restore it would be:
1. First restore the earliest nandroid backup and then,
2a. Boot into the old custom recovery and flash the original recovery image.
2b. Or I could use flashrec again to restore the original recovery image.
Any thoughts? Suggestions? Gotchyas I should know about?
Also is there anything special I have to do with the Radio? Do I need to restore to the original radio too?
Solved:
So I followed this procedure and it worked perfectly to restore my phone to the original ROMs:
1. Boot into recovery and restore earliest nandroid backup (which contained the original ROM but an old version of a custom recovery)
2. Reboot phone
3. Boot into the old recovery and flash an update.zip for the original radio
4. Reboot phone twice
5. Boot up phone and run flashrec, but flash the phone with the backup recovery image I made when I ran flashrec originally.
6. Restore the phone to factory settings before sending it back to HTC.
I didn't need to use the HTC Sync software or the RUUs at all and it all seems to have worked fine.
Thanks everyone for your help.
Orginal rom?
Download and install a orginal RUU rom update, and i belive Radio, rom etc. will be flashed to the stock rom?
Wow, useful first post!
I know you can flash the original HTC rom in update.zip format, but that will keep the custom recovery intact. After this you should restore the original recovery with flashrec.
in contrast to your 26th post chool's first post contains the correct answer to the question...
But it was still more informative than your 1,217th.
Chool is spot-on, though. You can download the HTC Sync software and run the original rom's RUU once it's connected to your phone, and it will set it back to the default original.
rayjt9 said:
But it was still more informative than your 1,217th.
Click to expand...
Click to collapse
are you drunk, dumb or both?
edit: since THIS POST is #1217 for me you are actually right. yet my questions remains...
I should have mentioned that I'm on Linux. I'm pretty sure the HTC Sync software is only for Windows. I can get Windows if I need to, so that's not too much of a problem.
I have heard that running the RUUs once you have changed your Radio can be harmful? Is there any truth to that?
kendong2 said:
are you drunk, dumb or both?
edit: since THIS POST is #1217 for me you are actually right. yet my questions remains...
Click to expand...
Click to collapse
In answer to your question, neither. I was going by the numbers at the top right of your posts, which, this morning, was 1217. Did you perhaps delete something sending it back to 1216?
bonneHero said:
I should have mentioned that I'm on Linux. I'm pretty sure the HTC Sync software is only for Windows. I can get Windows if I need to, so that's not too much of a problem.
I have heard that running the RUUs once you have changed your Radio can be harmful? Is there any truth to that?
Click to expand...
Click to collapse
Hmm, it doesn't look like there's an alternative to HTC Sync which would work for Linux, as far as I'm aware. I haven't heard of any problems with RUUing after a radio change, but if you're concerned, I believe there should be no harm in reflashing your radios with the original versions first.
Hello,
I am getting ready to venture into 2.2 on my vibrant which is currently unlocked on ATT. Before I do so, I would like to make sure that my phone will still be functional on ATT after going to Froyo. I already have the unlock code, will that change once I go to 2.2 or can I just enter the same one.
In addition, I was reading that there is some directory I should back up prior to flashing a 2.2 ROM? Can someone please elaborate on that?
Your help is greatly appreciated.
torpy said:
Hello,
I am getting ready to venture into 2.2 on my vibrant which is currently unlocked on ATT. Before I do so, I would like to make sure that my phone will still be functional on ATT after going to Froyo. I already have the unlock code, will that change once I go to 2.2 or can I just enter the same one.
In addition, I was reading that there is some directory I should back up prior to flashing a 2.2 ROM? Can someone please elaborate on that?
Your help is greatly appreciated.
Click to expand...
Click to collapse
Unlock codes are bound to imei number. You should be fine.
Use titanium backup to backup your apps and with data. Custom roms do not touch your external card and /sdcard partition on your phone.
Sent from my Nero powered Vibrant
actually if its the first time flashing a 2.2 rom, doesn't it have a chance to wipe the internal sd? i would back up both to your PC just to be safe...
actually i would backup DCIM and any folders you wanna keep.. just to be safe...
Hiya,
So I bought a Dell Streak off Craigslist that happened to support T-Mobile AWS 3G. I didn't do enough research to realize that the Android 2.2 update was only out for unlocked and AT&T Streaks, and since the AWS Streak isn't supported by Dell, there's little to no chance of an official 2.2 upgrade.
This morning I decided to try flashing DjSteve's ROM, and after trying several Clockwork recoveries, I found an older version, 1.8.1, I believe, that wouldn't just sit at a blackscreen. It wouldn't flash either Steve's 1.5.1, 1.6.1 or 1.7 ROMs, so I decided to use FASTBOOT to flash over the baseband Steve recommends for 1.5.1 and higher of his ROM.
The ROMs still would not flash, and when the Streak boots back into the Stock 1.6, I have no cellular connection whatsoever, get strange warnings about my battery and charger not being supported (even though it wasn't plugged in) and in Settings > About, the baseband shows up as unknown.
I thought about trying to flash an AT&T baseband, and then flash the ROM, but I don't think this would give me my 3G back. I did not make any nandroid backups and I can't seem to locate the original AWS stock baseband to flash back to.
I also tried flashing StreakModRecovery using FASTBOOT, but neither 0.3.2 or 0.3.2.6beta work, they just sit at a black screen similar to what ClockworkMod 2.5.0.1 does.
I just want to get 2.2 on my Streak and have my cellular and 3G working again.
Can someone please help me?
Thanks much.
there are a few recent posts on aws streaks and their stock 2.2. I just read a few yesterday...
Sent from my Dell Streak using XDA Premium App
Can you tell us your current build number/baseband number before you update?
so far the recent aws streaks reporting in have builds not currently released to the public and are worth backing up before updating.
kable said:
there are a few recent posts on aws streaks and their stock 2.2. I just read a few yesterday...
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
I was only able to find information about rooting the AWS Streak 2.2. It's possible I missed it, and if so, could you please point me in the right direction? I have been looking for a few hours, both on here and Google.
My Streak is:
Firmware version: 1.6
Baseband version: unknown
Kernel version: 2.6.29-perf
OEM version: GAUSB1A111933
Build number 9158
After attempting to flash the baseband, 4.AMSS for v1.5.1+, from the downloads section on streakdroid.com, I lost my cellular connectivity, Baseband shows up as unknown, my button LEDs flash randomly and the device tells me my battery or charger is broken even though it's not plugged in.
Also, I am not able to update. I can't get either a recent version of ClockworkMod or StreakMod to flash correctly - they just show a blackscreen after selecting Update package from SD Card from the Dell recovery (vol up + vol down & power), option 2. I was only able to get an older version of ClockworkMod to work, and that still would not flash DjSteve's ROM. I got an error code, Status 7.
!! 119 is yet another new version
could you please provide a nandroid of it? it's yet another version that's completely unique to the AWS streaks
The baseband you flashed only works with froyo builds, since you're currently on a 1.6 build it shouldnt work. You need to update your streak to an official 2.2 build to get back connectivity and as a prereq to flashing streakdroid
TheManii said:
!! 119 is yet another new version
could you please provide a nandroid of it? it's yet another version that's completely unique to the AWS streaks
The baseband you flashed only works with froyo builds, since you're currently on a 1.6 build it shouldnt work. You need to update your streak to an official 2.2 build to get back connectivity and as a prereq to flashing streakdroid
Click to expand...
Click to collapse
I suppose that makes sense that a 2.2 baseband doesn't work with 1.6.
I would be happy to provide a nandroid of it, if I can get some type of recovery installed again. I always end up with the black screen after doing option 2 from Dell recovery with both Clockwork and StreakMod.
Have you tried multiple versions and not just the most recent one? I think other AWS users have had trouble with the most recent ones. (Also keep in mind your streak is rather old compared to theirs, I really dont know the tiny differences that make some streaks not work with some recoveries/firmwares)
TheManii said:
Have you tried multiple versions and not just the most recent one? I think other AWS users have had trouble with the most recent ones. (Also keep in mind your streak is rather old compared to theirs, I really dont know the tiny differences that make some streaks not work with some recoveries/firmwares)
Click to expand...
Click to collapse
I've tried 0.3.2 and 0.3.2.6beta and neither work. I'm looking for older versions as we speak, but I'm not sure there any.
The only recovery I can get to load is ClockworkMod REcovery v1.8.1.7
It opens with the following errors:
E:Can't find MISC:
E:Can't find MISC:
ClockworkMod Recovery v1.8.1.7
E:Can't find MISC:
Attempting to perform a nandroid backup with this recovery fails, and says the following:
SD Card space free: 14737MB
Backing up boot...
Error while dumping boot image!
E:Can't find MISC:
I don't really know what else to do, other than to try and poke around and figure out how to go from 1.6 to 2.2 on my goofy version of the Streak.
Do you have any ideas?
If you cant nandroid, trying adb pulling the entire system folder.
Weither or not you can you might need to use qdl tool to update, I think the bootloaders on your streak might be too old to like the recoveries you tried (but I dont have any hard knowledge) I'm not really an expert on updating
I have been searching all night and can not find what i am looking for.
Can some one explain why the dell streak 5 I have is at version #347 15274 but i see that latest retail version as # 351 15609.
My question is what are the differences between the two? I also see a new build from hong kong version #354 15881.
I already have a rooted phone but i have never upgraded the version before. Is it even worth it?
I guess i am just confused.
Actually there is a lot of info at the XDA Streak Wiki.
It appears that 347 is one of the ROMs that TheManii does not have files for. You should contact him about sharing your ROM with him, so it can be posted to the Wiki.
AFAIK 351 is just bug fixes. I am running 351 and have found it to be very stable.
marvin02 said:
Actually there is a lot of info at the XDA Streak Wiki.
It appears that 347 is one of the ROMs that TheManii does not have files for. You should contact him about sharing your ROM with him, so it can be posted to the Wiki.
AFAIK 351 is just bug fixes. I am running 351 and have found it to be very stable.
Click to expand...
Click to collapse
Thanks for your quick reply, Would you recommend the upgrade? Also which method would you recommend for doing this.
NotoriousHaze said:
Thanks for your quick reply, Would you recommend the upgrade? Also which method would you recommend for doing this.
Click to expand...
Click to collapse
I have never used 347 so I can not make any comparison. I do know that 351 runs very well for me. The reports that I see for 351 are better bluetooth and wifi connectivity.
I would try downloading the 351 .pkg file directly to your phone. When the DL is complete open your notification bar and tap on the completed download and it should install. Using this method preserves your apps and settings. You should be connected to WiFi.
Please note that on some phones (probably depends on what apps you are using) you may see issues and have to do a factory reset after the upgrade which will mean setting up your phone again, so back everything up.
You must have the stock recovery for 347 on your phone for this to work. If you still have install-recovery.sh on your phone (never renamed or deleted it) your phone will still have the stock recovery on it. See this info about the recovery image.
If the upgrade does not install rename the file to upgrade.zip and make sure it is in the root of your SD card and install it from recovery.
Read this flashing guide.
Please contact TheManii before upgrading to see if you can get the 347 files to him.
I already have a nandroid of 347, what i dont have is a pkg which i would not expect him to have.
TheManii said:
I already have a nandroid of 347, what i dont have is a pkg which i would not expect him to have.
Click to expand...
Click to collapse
OK - did not know that.
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