I have done a fair amount of searching to find a generalized thread on the different basebands and the corresponding numbers displayed in the About Phone menu in the setting with little luck. So I am starting this thread to show my findings.
After following the instructions here, on how to install CM7 Mini, I was left with a mismatching baseband and the flashing buttons. I did follow the instructions here to install a stock 407, downloaded from here. So I am not sure why this didn't work.
I flashed the amss.bsn and dsp1.mbn that TheManii kindly has provided on the streakdroid server. I did so using fastboot and the following commands. This seems to have fixed my issues.
DO AT YOUR OWN RISK, if anything this thread can be used to see if you have the right baseband.
TheManii said:
...shouldnt flash baseband/dsp by themself,
the stock roms have 7 different device firmwares that are flashed at a time, baseband and dsp are only 2 of them. Flashing them improperly can lead to a completely unfixable brick (granted this is hard to achieve, but speaking with DJ_Steve and fards they've seen it happen in very specific circumstances)
Mixing and matching firmware images will only give yourself headaches unless you know exactly why you need to make them mismatched. If you really need to update the firmwares what you should do is nandroid -> flash stock -> nandroid back (assuming you're on streakdroid) That'll flash the firmwares without losing your settings/install. (nandroid doesnt touch any of them)
If you REALLY need the files i didnt remove any of them from the mirror, only the links are removed. just check the dirs, they're all browsable.
Click to expand...
Click to collapse
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c reboot
407 - GAUSB1A1406214- amss.bin dsp1.mbn
406 - GAUSB1A140614 - amss.bin dsp1.mbn
405 - GAUSB1A140514 - amss.bin dsp1.mbn
366 - GAUSB1A136612 - amss.bin dsp1.mbn
364 - GAUSB1A136412 - amss.bin dsp1.mbn
360 - GAUSB1A136000 - amss.bin dsp1.mbn
354 - GAUSB1A135411 - amss.bin dsp1.mbn
353 - GAUSB1A135331 - amss.bin dsp1.mbn
352 - GAUSB1A135215 - amss.bin dsp1.mbn
351 - GAUSB1A135100 - amss.bin dsp1.mbn
345 - GAUSB1A134500 - amss.bin dsp1.mbn
344 - GAUSB1A134412 - amss.bin dsp1.mbn
340 - GAUSB1A134031 - amss.bin dsp1.mbn
339 - GAUSB1A133932 - amss.bin dsp1.mbn
324 - GAUSB1A132412 - amss.bin dsp1.mbn
322 - GAUSB1A132211 - amss.bin dsp1.mbn
319 - GAUSB1A131921 - amss.bin dsp1.mbn
318 - GAUSB1A131800 - amss.bin dsp1.mbn
315 - GAUSB1A131500 - amss.bin dsp1.mbn
309 - GAUSB1A130900 - amss.bin dsp1.mbn
305 - GAUSB1A130500 - amss.bin dsp1.mbn
206 - GAUSB1A120621 - amss.bin dsp1.mbn
205 - GAUSB1A120521 - amss.bin dsp1.mbn
204
203 - GAUSB1A120321 - amss.bin dsp1.mbn
112 - GAUSB1A111231 - amss.bin dsp1.mbn
111 - GAUSB1A111100 - amss.bin dsp1.mbn
106 - GAUSB1A110631 - amss.bin dsp1.mbn
104 - GAUSB1A110421 - amss.bin dsp1.mbn
Indeed a helpful one-stop solution for many.
Thanks a lot!
Sent from my Dell Streak using Tapatalk 2 Beta-4
It would appear that the recommended method for updating the baseband doesn't work because after flashing it preforms a recovery overwrite on the first boot... I can't manage to get it into fastboot before it recovers either.
Well I managed to get StreakMod installed without ever seeing a recovery overwrite.
I got into fastboot by holding down the camera button right at the end of the stock 407 update in the stock 407 recovery.
The phone booted into fastboot and I flashed StreakMod 3.2.8.
I did a nandroid full restore.
Booted the phone and I am back on my 349 baseband...
Anyone have an idea on what is going on?
Doing a Nandroid restore switches you back to the older firmware and also the older recovery! Don't Nandroid restore the backup taken before flashing streakmod recovery. Suggested step would be:
1. Your stock/407 firmware
2. Flash streakmod recovery
3. Flash ZIP version (not .pkg version) of your intended firmware as in this case 407 provided by TheManii.
4. Now backup and restore as per your wish, BUT always flash the ZIP version unless you intend to revert to stock!
Hope it helps.
Sent from my Dell Streak using Tapatalk 2 Beta-4
I've got a Stock 02 2.2, planning on installing a custom ROM so I had flashed the new amss and dsp1 files as directed by installation instructions of that custom ROM but flashing wasn't sucessful. So I was left with the blinking lights, seems to have been sorted by flashing the corresponding amss and dsp1 files for the ROM version as given by the OP.
ammujee said:
Doing a Nandroid restore switches you back to the older firmware and also the older recovery! Don't Nandroid restore the backup taken before flashing streakmod recovery.
Click to expand...
Click to collapse
Sure about that?
Updating baseband
I know I have seen multiple posts that say that the nandroid doesn't mess with the baseband, and when I created the full backup I was using the 407 baseband flashed with fastboot.
Blauvster said:
Sure about that?
Updating baseband
I know I have seen multiple posts that say that the nandroid doesn't mess with the baseband, and when I created the full backup I was using the 407 baseband flashed with fastboot.
Click to expand...
Click to collapse
You are right in saying that Nandroid doesn't mess up with baseband and amss, but IMHO your problem less in the sequence of doing restore. You were perhaps trying to restore a froyo nandroid over a gingerbread, which is not the correct way I think. I would suggest you to go for a fresh install of 407 zip after flashing streakmod recovery and then backup or restore to any further version of gingerbread. By doing so you'll never need to worry about flashing the baseband again.
Sent from my Dell Streak using Tapatalk 2 Beta-4
Well I have succesfully installed cm7 following the instruction in the first post and its unbelievably fast so happy with it. Thanks for the link didn't know it existed till I saw this post
Sent from my Dell Streak CM7 using XDA
Is the AMSS and DSP1 specific to region at all?
Hi, is the amss and dsp1 specific to region at all? I have an unlocked streak in South Africa, whenever I flash a new ROM, I get issues were I lose signal, or Sim not recognised. However if I flash to Android 2.2 "Simplestreak from Spidla" it works fine. http://forum.xda-developers.com/showthread.php?t=1113256
If I use the same dsp1 as I used in Android 2.2, with 2.3 it does not work. Reading the first post I understand why,
I recently installed the Official 407 from dell to install Cyanogenmod as per instructions here: http://forum.xda-developers.com/showthread.php?t=1528412
Now whenever I receive or make a call, using CM7 the person on the other end cannot hear me. Its not signal issue because when I install CleanGinger, Phone calls are fine:
However with CleanGB and GingerStreak 2.4.4 the phone reboots randomly.
Gingerstreak: http://forum.xda-developers.com/showthread.php?t=1333010
CleanGB: http://android.modaco.com/topic/347996-rom-cleangb/
I am going to flash to 407 Officia now, then Cyanogenmod then manually flash the asmm and dsp1 from the first post to test. Can anyone help me determine the issue.
How can I find out exactly what the dsp1 and amss files controll so I no were to start fixing the issues.
Updated Links
Any chance of getting the links updated? Now that I'm not using my S5 as a daily driver, I'm looking to play around with it. The old BB files would come in handy.
Manii did provide updated links recently. It's your job to search for them on the forum.
Whoops....ok, now that I know how to browse dirs on the dev-host site I'm good. To be fair, I did do a lot of searching before I posted, so it wasn't a complete noob moment....just quasi-noob.
Re upload mirror..plz thanx for the lovely collection :thumbup:
Sent from my Dell Streak using xda premium
please reupload again...i need baseband 407 :crying:
The links were pulled because Manii was using too much space on dev-host. If you want the baseband files you now need to download the entire update package and extract the baseband files from the zip. Or you could download MultiFlasher and get the baseband files that way. I know 407 is one of the included basebands.
ok i try Multiflasher
explanations
ehm... what is baseband ???
can you explaine it me , please
This is a gross oversimplification, but the baseband is the Android phone equivalent of a computer's BIOS. It provides low level control of the Streak's radios and other hardware so the device functions properly.
Ah... ok... is a Radio ROM
Related
Recovery
You should have fastboot installed properly on your system to be able to flash it.
Heres a quick guide for Mac (which is really similar to Linux, search for XP guides which are available all over)
FASTBOOT
Download Fastboot from http://developer.htc.com/adp.html
Unzip and move to whatever folder you want.
I put it in /Users/MyName/Android
OPTIONAL Rename from "fastboot-mac" to "fastboot" (makes following guides made for xp and linux easier)
Now you have to append it to your .bash_profile
Easy Way
Follow instructions on http://donovan.covblogs.com/archives/027838.html to edit the bash_profile visually with textwrangler.
Your .bash_profile should look like this:
Code:
export PATH=$PATH:/Users/MyName/Android
export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
remember to edit the path to wherever you put your fastboot file (some people like to put it in the tools folder in the android sdk so adb is added to the .bash_profile as well)
or
Terminal Way
Code:
export PATH="$Path:/Users/MyName/Android"
Hit enter
Now refresh your .bash_profile
Code:
~/.bash_profile
To see if you've done it right
Code:
fastboot --help
or
Code:
fastboot --h
If the help text shows in terminal in another directory other than where fastboot is then you've got it right
Code:
$fastboot --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
To use the fastboot command your device has to be in fastboot mode
Enter FASTBOOT_MODE
Hold power button with device off and when the Home/Menu/Back buttons light up, release power button then press and hold the camera button
Dell logo will appear shortly followed by a white screen.
Tap fastboot in the top right
Thank you mzsigler from modaco for pointing out this simple step i missed.
finally:
FLASH RECOVERY IMAGE
Download the attached file and unzip it.
Make sure terminal is in the directory where the recovery-US6601.img is.
Use
Code:
pwd
to see which directory ur in
Code:
$ fastboot -i 0x413c flash recovery recovery-US6601.img
sending 'recovery' (3280 KB)... OKAY
writing 'recovery'... OKAY
$
Now reboot your device and hold both volume keys to get into recovery mode.
To the 6 people who downloaded it first, i might of uploaded the wrong one because i forgot that before i did nandroid backup i had flashed a different recovery to get clockword mod to work. This should be the right one now which was pulled using adb shell before clockworkmod.
Dell Streak stock US 1.6 Build 6601
There are several ways to restore/flash this i'll mention 2 Fastboot and nandroid
Fastboot
Code:
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash system system.img
fastboot -i 0x413c flash cache cache.img
fastboot -i 0x413c flash userdata data.img
fastboot -i 0x413c flash recovery recovery.img
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
Now although this flashes 1.6 build 6601 it doesn't return the baseband to *****31
this is what mine now reads
Basband version
GAUSB1A110421-US
Kernel version
2.6.29-perf
OEM version
GAUSB1a111231
Build number
6601
Click to expand...
Click to collapse
Also be warned that after i returned to 1.6 i got the crazy home/menu/back lights as seen in this video I'm guessing it has something to do with the 21 baseband and 31 oem version
I think this is worthy of a sticky great work my friend keep it up
thanks for the files. wonder how to restore the 6601 baseband.
johnnobts said:
thanks for the files. wonder how to restore the 6601 baseband.
Click to expand...
Click to collapse
Yep, trying to figure that out now.. well back it up first from a device that hasn't been messed with.
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
when i flashed the recovery my screen got stuck at a black screen after the reboot
Worked great for me. Back to the out of the box experience.
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
uberamd said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
Click to expand...
Click to collapse
Are the other items flashing?
lbj23numb1 said:
when i flashed the recovery my screen got stuck at a black screen after the reboot
Click to expand...
Click to collapse
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Same here. Finally no O2 logo...
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
I had flashing lights. Flashing r2-4399-streak-superboot fixed the problem.
I am still at my original baseband. 21-EU
Stock 31 update is 4917. Why would you want to downgrade from 6601?
because we are in the US and are a little concerned we may not be able to apply the 2.2 upgrade with a modified baseband. fone, i don't think the baseband change will make a difference. i am concerned about the flashing lights as of right now.
fone_fanatic said:
Are the other items flashing?
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Click to expand...
Click to collapse
I can still get to the recovery using the buttons but when I select the second option that's when I get stuck at a black screen. I flashed the recovery through fastboot
No change in numbers and now no flashing lights. Still can not get to recovery, clockworkmod just reboots and button mode goes to standard recover and selectin option 2 goes black screen.
Model; Dell Streak
Firmware; 1.6
Baseband; GAUSB1A111231-US
Kernel; 2.6.29-perf
OEM; GAUSB1A111231
Build; 6601
I haven't been able to find any information about backing up baseband in order to do a restore.
get stuck on dell logo boot
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Hi fone-fanatic
Could you explain how backing up the recovery.img to be able to flash it ?
Thanks
gomesj said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Click to expand...
Click to collapse
I am having the exact same issue. Any advice?
I initially flashed this via fastboot and was stuck at the dell logo. i then flashed to the 02 1.6 rom and re flashed the att rom via clockwork mod nandroid. i am up and running but the lights flash like crazy and everything has "an unexpected error" and closes. cant open contacts, set up gmail, open "phone" so i cant get to the dialer. am i the only one getting all the force closes?
I would reflash mate
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
IronicUniqueUsername said:
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
Click to expand...
Click to collapse
Flash a stock 2.3.4 via moto-fastboot
http://bandbinnovations.com/xda/ging...ead-4.5.91.zip
extract boot.img, system.img from the archive and flash via moto-fastboot.
Download moto-fastboot for your OS here:
http://forum.xda-developers.com/showthread.php?t=1138092
Then do the following commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
This one should boot up without problems
You can upload files to flash i get error in the link to download the 2.3.4 stock
Tavo_an said:
You can upload files to flash i get error in the link to download the 2.3.4 stock
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
I followed these steps from streakdroid 1.9 to 2.3:
flashed AMSS with fastboot.
fastboot -i 0x413c flash amss amss.mbn
Flashed DSP1
Click to expand...
Click to collapse
fastboot -i 0x413c flash dsp1 dsp1.mbn
Click to expand...
Click to collapse
Both amss and DSP1 downloaded from the mainpage of XDA
Booted into recovery mode did a factory reset from dell menu. But when I try to install gingerstreak located at the root of the sdcard I get the dreaded assert failed error
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/GS2_3beta2.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I am though able to install streakdroid 2.0 without any problems. But I get too many random reboots with it. The base band shows to be
GAUSB1A140314-US
KERNEL 2.6.35.7-PERF
Is there a way to find out the AMSS version
Do I need to change the sequence DSP1 first then AMSS or something?
What am I doing wrong here. Please help
TIA
nutcr0cker said:
I followed these steps from streakdroid 1.9 to 2.3:
flashed AMSS with fastboot.
Both amss and DSP1 downloaded from the mainpage of XDA
Booted into recovery mode did a factory reset from dell menu. But when I try to install gingerstreak located at the root of the sdcard I get the dreaded assert failed error
I am though able to install streakdroid 2.0 without any problems. But I get too many random reboots with it. The base band shows to be
GAUSB1A140314-US
KERNEL 2.6.35.7-PERF
Is there a way to find out the AMSS version
Do I need to change the sequence DSP1 first then AMSS or something?
What am I doing wrong here. Please help
You may have something out of sync... first of all no need to root separately because the ROM comes rooted
I would flash stock ROM 360 recovery and then the ROM to get e erything back in sync
Once you have let the stock ROM maybe boot a couple times go into fastboot and flash the amss and the dsp1files and then let it boot a couple more times
Fastboot again and flash Streakmod and then boot into recovery and flash your custom ROM
This procedure is what has worked for me... hope it helps you out
Click to expand...
Click to collapse
Thanks for the reply cdzo72 but where do I find the 2.2 stock rom for the streak? The problem now I have is that the phone does not recognize my SIM card, probably the baseband mess up or the dsp1. The previous baseband file was GAUSB1A140314-US I was able to find the 315 baseband file but got the same error of simcard not found. Is there a 314 baseband file?
nutcr0cker said:
Thanks for the reply cdzo72 but where do I find the 2.2 stock rom for the streak? The problem now I have is that the phone does not recognize my SIM card, probably the baseband mess up or the dsp1. The previous baseband file was GAUSB1A140314-US I was able to find the 315 baseband file but got the same error of simcard not found. Is there a 314 baseband file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
That's the link for the Dell Streak Wiki where you will find all the info you need. I would update to the latest retail 360 ROM which will update all your phone's files.
i found a way around the dreaded
assert failed: write_raw_image("/tmp/boot.img". "boot")
E:Error in /sdcard/GS2_3beta2.zip
(Status 7)
Installation aborted.
i was running froyo 2.2 and had to downgrade to 2.1 to be able to root and install modding apps such as streakmod, i followed all of the proper steps to install streakdroid. and i got the same error, so i went back and i made a copy of the "boot.img" from the zip. copied it to my c:/streak folder and flashed the "boot.img" before i installed the rom. then installed the rom. you still get the install error. shutdown the device disconnect battery then reboot the device and the rom is installed. it unpacks everything except the boot.img but since its already been flashed it'll boot. i've been running the beta version for 3 weeks now and no hangups or random reboots. *do this at your own risk* i didnt think it would work and i havent seen anyone else try this. i wont be held responsible if you brick. i might have just gotten lucky. but it did work for me. and its very stable on my streak5
THESE STEPS PROBABLY DON'T WORK, SO DO NOT USE THEM!!
So, I've been thinking about how a number of people with Photons that accidentally flashed the 2.3.5 US Cellular SBF and lost 4G would like to get it back.
You will need to exact the CG*.smg files from 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Plus obtain a bootstrap flashable .zip of stock 198_6 or a stock nandroid system.img of 198_6.
You can use MotoAndroidDepacker.exe by Skrilax_CZ version 1.3 to unpack the SBF into the CG*.smg files.
You will also need 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US if you are not totally stock Electrify, and if you want to recover from messing this up.
Finally, you will need the leaked Blur_Version.45.3.6.MB855.Sprint.en.US.zip OTA.
Here's the general idea laid out...
1. Charge your battery to 100% full capacity
2. Make sure you are on the stock 2.3.5 USCC SBF (use RSD if necessary)
3. Enter stock recovery and select wipe data/factory reset
4. Boot back into Android, skip the setup wizard
5. Shutdown device and start up in Fastboot
6. Run: moto-fastboot flash webtop CG61.smg
7. Run: moto-fastboot reboot
8. Wait for device to boot back into Android
9. Shutdown device and start up in Fastboot
10. Run: moto-fastboot flash preinstall CG65.smg
11. Run: moto-fastboot reboot
12. Wait for device to boot back into Android
13. Enable USB mass storage mode and copy root + APK files to microSD card
14. Root, sideload Superuser APK
15. Sideload Bootstrap APK
16. Ensure battery is charged to 100% again (for RSD bailout)
17. Enter Bootstrap recovery mode
18. Select wipe data/factory reset
19. Restore Nandroid system.img of 198_6 or install a stock 198_6 .zip file
20. Reboot into stock recovery
21. Apply official 2.3.5 Sprint update.zip which will update the 2.3.4 files to 2.3.5 as well as flash the new AP20 and bp.img radio!
Note: Use http://sourceforge.net/projects/ext2read/ to open CG60.smg CG61.smg and CG65.smg
Note: Do not do moto-fastboot flash system CG60.smg or you will get Failed to boot 4 error
So, any thoughts if this would be a feasible process?
I think, this is possible.
Except that fastboot flash webtop.?
It's bad, that sbf depacker doesn't work with photon sbfs.
attaching good depacker
The reason I added the step to flash the webtop image is because the 2.3.5 update.zip performs an assertion check on a bunch of files in the webtop partition. So, they have to match or else the patching will fail and the radio update at the end will never happen.
I also noticed that the update script checks the boot and recovery's md5sum, so those will also have to be flashed in through a custom bootstrap .zip file.
olegfusion said:
attaching good depacker
Click to expand...
Click to collapse
If this is able to re-pack the SBF, then there is no need for the fastboot stage! One can just replace the codegroups within the SBF and then flash that. Not sure if there is anything preventing replacement there though.
brianez21 said:
If this is able to re-pack the SBF, then there is no need for the fastboot stage! One can just replace the codegroups within the SBF and then flash that. Not sure if there is anything preventing replacement there though.
Click to expand...
Click to collapse
I don't this can simply repack. It will allow the repack to happen, but it fails instantly upon trying to flash it through RSD. And I didn't make any modifications. Just unpacked the stock 2.3.5 SBF, and then compiled it again.
Might be some sort of signature check failing then...? Not sure.
Does anyone here have a good understanding of how RSD/the Photon's flashing process works?
brianez21 said:
Might be some sort of signature check failing then...? Not sure.
Does anyone here have a good understanding of how RSD/the Photon's flashing process works?
Click to expand...
Click to collapse
Would have to be. I don't think there is anything different about the recompiled SBF I created. Compared it to the original one and they are exactly the same size.
Hi
Link to particular files will be appreciated, have some files already, got some files by searching, but some file still missing. can anyone point me to right direction ?
Do not use anymore, there is a full SBF available. Flash using RSD Lite or via moto-fastboot.
This is the official ICS OTA update for the NonEFIGS region.
By means of spoofing firmware version as 651.167.21.XT910.NonEFIGSRetail.en.EU in build.prop user mbartosik managed to download 672.180.41.XT910.NonEFIGSRetail.en.EU OTA update from the QA environment.
If you want to thank user mbartosik, please go to this post and press "Thanks" button.
Download:
URL: Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU .zip
MD5: c57e495e901f58b0a070bd57c53eb397
Installation:
If you're on a GB build other than 651.167.21.XT910.NonEFIGSRetail.en.EU, flash this SBF prior to continuing with this OTA update. It is recommended to reset the phone to factory defaults in order to avoid FCs and battery drain.
If you're on a clean (no root, no modifications to the system partition, stock recovery) 651.167.21.XT910.NonEFIGSRetail.en.EU (GB 2.3.6), drop the update onto your external microSDHC card, go to recovery and proceed with update. It is recommended to reset the phone to factory defaults in order to avoid FCs and battery drain.
If you're on an ICS leak:
Put the update in your external microSDHC card.
Reboot to AP Fastboot.
Flash this kernel (also courtesy of user mbartosik): moto-fastboot flash boot boot_new_41.img
Flash system_signed from this SBF (unzip it): moto-fastboot flash system system_image
Reboot to recovery, wipe cache and proceed with update.
Note: Only use moto-fastboot in order to avoid preflash validation error when flashing the GB 2.3.6 system_signed.
Bugs:
Apps which use extended GPS commands (e.g. GPS Test and GPS Status & Toolbox) won't report visible satellites etc. This can be fixed by flashing newer U_04.12.00R radio image (again, courtesy of user mbartosik) using BootMenu Manager recovery. Beware, this may impact your 2G, 3G, WiFi and Bluetooth performance - in case of problems, you can revert to U_04.10.00R radio which is shipped with this update by flashing this image (as usual, courtesy of user mbartosik).
Original thread (contains screenshots): http://forum.android.com.pl/f472/wy...d-date-mon-jul-16-11-15-45-cst-2012-a-203392/
Can someone tell us the languages that are included? Much appreciated!
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
romdroid. said:
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
Click to expand...
Click to collapse
you must install service soft by rsd (ICS) and go to second point of OP
for autor
If we are to charge any leaks ICS fastboot package for 651.167.21.XT910.NonEFIGSRetail.en.EU, we also need EternityProject's FastBoot flashME
romdroid. said:
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
Click to expand...
Click to collapse
I only set up the thread - all kudos to mbartosik for pulling the OTA and sharing the patched kernel.
I'm not sure which partitions are being modified by custom firmwares, so flashing the ICS SBF prior to proceeding with the new kernel and GB system might be a safe bet. In theory, you should then flash the attached kernel and 2.3.6 system image, then apply OTA from the stock recovery. However, I stumbled upon preflash validation error when trying to flash system from NonEFIGS 2.3.6 over the leaked 676.226.3.
With regard to FlashME.bat - I don't use Windows. The FlashNIX.sh seems to be a clone of tools shipped within the ICS SBF. I will publish step-by-step tutorial once I get over the preflash validation error.
Sent from my XT910
The steps are really simple to do.
You just need an working ADB on your PC
Fastboot flash boot boot_new.img
Fastboot flash system system_signed
Boot in Recovery, wipe data & cache and apply the update.
All you guys need is the system signed of the based GB Fastboot and the linked boot.img :thumbup:
Sent from my CustomiZed XT910
Is it possible to update to this version from 651.73.30.XT910.NonEFIGSRetail.en.EU (2.3.5)? This is the latest officialy available (non-branded) version in my country (Czech Republic). Thx for the answer.
aaatoel said:
Can someone tell us the languages that are included? Much appreciated!
Click to expand...
Click to collapse
Dansk
Deutsch
English (U.K. & U.S)
Espanol (Espana & Espados Unidos)
Greek
Francais (Canada & France)
Italiano
Nederlands
Norsk bokmal
Polski
Portugues (Brasil & Portugal)
Suomi
Svenska
Turkce
HSD-Pilot said:
The steps are really simple to do.
You just need an working ADB on your PC
Fastboot flash boot boot_new.img
Fastboot flash system system_signed
Boot in Recovery, wipe data & cache and apply the update.
All you guys need is the system signed of the based GB Fastboot and the linked boot.img :thumbup:
Click to expand...
Click to collapse
Well, ADB in this context is only useful to enter AP fastboot mode... I followed this procedure using fastboot binary from the ICS SBF, but an attempt to fastboot flash system system_signed gave me preflash validation error (And yes, I was using the correct SBF.) - any suggestions?
Edit: It seems that the fastboot binary bundled within ICS SBF file is defective. I used moto-fastboot binary from this post and successfully flashed system image!
Besides that, how to update the recovery? Is partition dump the only way?
It should be the same procedure, like we used on EU Leaks. Only the Files have to be changed.
http://forum.xda-developers.com/showthread.php?p=28006523
Sent from my CustomiZed XT910
Can someone tell me what are the differences between 676.226.3.XT910.Retail.en.EU and 672.180.41.XT910.NonEFIGSRetail.en.EU (except numbers, date build, localization and preinstalled apps)? Your feelings in use, speed, smooth or that is something working or not.
I am on retail.en.eu ICS 4.0.4... Is there way to install non EU on my RAZR via fastboot? Or any other? Default ROM in my RAZR was nonEU 2.3.6, so I want to switch to nonEU again. With official ICS nonEU my warranty will back
do u think there will be a fastboot file availabe so we can flash it?
febanovsky said:
I am on retail.en.eu ICS 4.0.4... Is there way to install non EU on my RAZR via fastboot? Or any other? Default ROM in my RAZR was nonEU 2.3.6, so I want to switch to nonEU again. With official ICS nonEU my warranty will back
Click to expand...
Click to collapse
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developers.com/attachment.php?attachmentid=1080638&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip (Europeans NonEFGIS) from here: http://sbf.droid-developers.org/umts_spyder/list.php (you will need system_signed archive, copy to desktop )
3) https://hotfile.com/dl/167461766/1e24d34/Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Vatazhka said:
Well, ADB in this context is only useful to enter AP fastboot mode... I followed this procedure using fastboot binary from the ICS SBF, but an attempt to fastboot flash system system_signed gave me preflash validation error (And yes, I was using the correct SBF.) - any suggestions?
Besides that, how to update the recovery? Is partition dump the only way?
Click to expand...
Click to collapse
fastboot will not work to system_signed
use instead
Code:
moto-fastboot flash system system_signed
Cheers
Edit:
What do we have here?
Moto-fastboot
lol
achillesgk said:
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developer...8&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip από εδώ: http://sbf.droid-developer...pyder/list.php (you will need system_signed archive, copy to desktop )
3)https://hotfile.com/dl/167...en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Click to expand...
Click to collapse
I need file from step 3, please
achillesgk said:
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developer...8&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip από εδώ: http://sbf.droid-developer...pyder/list.php (you will need system_signed archive, copy to desktop )
3)https://hotfile.com/dl/167...en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Click to expand...
Click to collapse
links from step 1-4 is broken
romdroid. said:
links from step 1-4 is broken
Click to expand...
Click to collapse
found it
link from step 3 in 1 post my mistake - https://hotfile.com/dl/167461766/1e24d34/Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU.zip.html
link from 1 step: http://forum.xda-developers.com/attachment.php?attachmentid=1080638&d=1337846142
Thanks, do we still need to download -> " SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Servic e1FF_fastboot.xml.zip" and unpack it as this tutorial? http://forum.xda-developers.com/showthread.php?p=28006523
Because it's stated 2.3.6 I think we will brick, or?
I wonder if it will work because I am on custom rom..?
romdroid. said:
Thanks, do we still need to download -> " SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Servic e1FF_fastboot.xml.zip" and unpack it as this tutorial? http://forum.xda-developers.com/showthread.php?p=28006523
Because it's stated 2.3.6 I think we will brick, or?
I wonder if it will work because I am on custom rom..?
Click to expand...
Click to collapse
My battery is charging (60%), I will try soon.