Related
My Atrix came with Android 2.2.2 --- Blur_Version.4.4.35.MB860.Retail.en.GB.
The complete name of the SBF is OLYEM_U4_4.3.5_SIGNED_USAOLYPRTGB_P026_A004_M001_H Wolympus_1g_1FF.sbf.gz.
It never received a Gingerbread OTA (we are still waiting for it in Europe)
I rooted it and unlocked the bootloader. Now it has CM7 installed and another radio.
Is it possible to flash to go back to the original SBF with Froyo, or will it brick my phone? I know that the bootloader would remain unlocked.
Another question: does the SBF also include the original Radio version? (I don't remember which one it was)
Update:
My question is generating interesting interventions, so I am going to update the most interesting facts in this post.
Yes, it is possible to go back to stock SBF with Froyo after root, unlock and installation of other ROMs, even those based on Motorola Gingerbread ROMs. You just must never install an official OTA update from Motorola that brings Gingerbread to you.
@GolfCranKinstallation flow has been:
New Telstra Atrix 2.2.2 > CM7 > Telstra 2.2.2 sbf > OTA Gingerbread and no more sbf flash from now on
My installation flow has been:
Android 2.2.2 --- Blur_Version.4.4.35.MB860.Retail.en.GB. > bootloader unlock and root > Cyanogenmod 7.1.0 > Alien Rom #4 (based on AT&T official Gingerbread for Motorola Atrix 4G) > Android 2.2.2 --- Blur_Version.4.4.35.MB860.Retail.en.GB. back again. I just had to unlock and root again the device, but everything went fine.
In this post @NYG-SBXLII explains how to extract an official SBF in order to generate moto-fastboot images. This is for creating sort of fruit cakes. Additionally, he explains how to just extract the Radio firmware from a SBF.
While trying some Radios out, I noticed that by flashing a CMW Radio zip instead of a SBF file, the new radio would flash but won't be overwritten again by any other SBF file. This is probably a bug of sbf_lite. If you flash again using RSD-LITE, it will work again.
Thank you all, XDA users!
Don't quote me on this but I'm fairly certain that if you unlocked the boot loader you should stay away from .sbf'ng anything but gingerbread. Check the fruitcake thread.
Sent from Hyperspace using Tapatalk
There's too much confusion on this topic
Once you unlock your bootloader its not recommended to flash back using spf's. If you want to go back to froyo, use fruitcake. Its the same as the .sbf but it doesn't rollback your bootloader...which its what can lead to a hard brick.
As much as I know, it will work just fine, as long as you done flash a 2.3.4 bootloader and than revert to a 2.2.2 one.
quicklyspent said:
Once you unlock your bootloader its not recommended to flash back using spf's. If you want to go back to froyo, use fruitcake. Its the same as the .sbf but it doesn't rollback your bootloader...which its what can lead to a hard brick.
Click to expand...
Click to collapse
From what I understand, a fruitcake that corresponds to my SBF does not exist. Am I right?
crnkoj said:
As much as I know, it will work just fine, as long as you done flash a 2.3.4 bootloader and than revert to a 2.2.2 one.
Click to expand...
Click to collapse
I never installed official OTAs. I just went from stock 2.2.2 to custom ROMS.
I installed Alien ROM one time, but I don't think that it contains the malicious 2.3.x bootloader from Motorola. Does it?
How do I now which bootloader version is installed on my phone?
bodom_lx said:
There's too much confusion on this topic
Click to expand...
Click to collapse
Yes I found it confusing and was wary before I did it. But what you are wanting to do is in fact safe. When you flash back to Froyo using sbf the bootloader will not be unlocked anymore but it will only take a minute to reflash the small unlock pudding sbf. You will not even need to run the unlock with fastboot afterwards.
I have just done this successfully. I went New Telstra Atrix 2.2.2 > CM7 > Telstra 2.2.2 sbf > OTA Gingerbread. I understand that if I flash an sbf now I will brick the phone so it's only zips from now on
Have you got the correct sbf from Firmwares Superthread?
Hit thanks if I've helped you.
bodom_lx said:
My Atrix came with Android 2.2.2 --- Blur_Version.4.4.35.MB860.Retail.en.GB.
The complete name of the SBF is OLYEM_U4_4.3.5_SIGNED_USAOLYPRTGB_P026_A004_M001_H Wolympus_1g_1FF.sbf.gz.
It never received a Gingerbread OTA (we are still waiting for it in Europe)
I rooted it and unlocked the bootloader. Now it has CM7 installed and another radio.
Is it possible to flash to go back to the original SBF with Froyo, or will it brick my phone? I know that the bootloader would remain unlocked.
Another question: does the SBF also include the original Radio version? (I don't remember which one it was)
Click to expand...
Click to collapse
As long as you have never installed a gingerbread bootloader (other then pudding) you should be fine. However if you give me some time id be willing to make a moto-fastboot flashable alternative for you just to be safe.
Also do you have a mirror for that sbf file im trying to download it but its really slow (over 12 hours)?
NYG-SBXLII said:
As long as you have never installed a gingerbread bootloader (other then pudding) you should be fine. However if you give me some time id be willing to make a moto-fastboot flashable alternative for you just to be safe.
Also do you have a mirror for that sbf file im trying to download it but its really slow (over 12 hours)?
Click to expand...
Click to collapse
The only GB bootloaders I could have installed come from Alien ROM and Cyanogenmod, if any.
Thank you very much if you build it for me!
Are you downloading this one?
http://forum.xda-developers.com/showpost.php?p=16273531&postcount=111
Unfortunately I don't know any mirror. Is it difficult to create the moto-fastboot? If you help me I may try to do that.
GolfCranK said:
Yes I found it confusing and was wary before I did it. But what you are wanting to do is in fact safe. When you flash back to Froyo using sbf the bootloader will not be unlocked anymore but it will only take a minute to reflash the small unlock pudding sbf. You will not even need to run the unlock with fastboot afterwards.
I have just done this successfully. I went New Telstra Atrix 2.2.2 > CM7 > Telstra 2.2.2 sbf > OTA Gingerbread. I understand that if I flash an sbf now I will brick the phone so it's only zips from now on
Have you got the correct sbf from Firmwares Superthread?
Hit thanks if I've helped you.
Click to expand...
Click to collapse
It seems that you made about the same operations I would do (except the last one, we are still waiting for GB in Europe..) Thank you for the information, I will try this if @NYG-SBXLII does not manage to create the safe file
bodom_lx said:
The only GB bootloaders I could have installed come from Alien ROM and Cyanogenmod, if any.
Thank you very much if you build it for me!
Are you downloading this one?
http://forum.xda-developers.com/showpost.php?p=16273531&postcount=111
Unfortunately I don't know any mirror. Is it difficult to create the moto-fastboot? If you help me I may try to do that.
Click to expand...
Click to collapse
yes that is the file im trying to download but for whatever reason i cant download it it keeps stopping. do you already have the sbf? if so you can use dropbox or something like that to upload it somewhere for me.
also if you already have the file you can use Portable Sbf Tool to extract the contents of the sbf you can then get system webtop and boot from the file and use moto-fastboot to flash them. you can not flash a radio with moto-fastboot though. you would need to make a custom sbf that has just the radio.
once you extract the sbf you will need CG 56(boot), CG 57(system), CG 58(webtop). after you remove those files rename them accordingly boot, system and webtop. Move them to your fastboot folder and flash.
for the radio you will need to remove the rest of the files in the smg folder execpt for CG 5, RDL 1 and RDL 3 recompile the sbf. now you can flash it with rsd lite.
NYG-SBXLII said:
yes that is the file im trying to download but for whatever reason i cant download it it keeps stopping. do you already have the sbf? if so you can use dropbox or something like that to upload it somewhere for me.
also if you already have the file you can use Portable Sbf Tool to extract the contents of the sbf you can then get system webtop and boot from the file and use moto-fastboot to flash them. you can not flash a radio with moto-fastboot though. you would need to make a custom sbf that has just the radio.
once you extract the sbf you will need CG 56(boot), CG 57(system), CG 58(webtop). after you remove those files rename them accordingly boot, system and webtop. Move them to your fastboot folder and flash.
for the radio you will need to remove the rest of the files in the smg folder execpt for CG 5, RDL 1 and RDL 3 recompile the sbf. now you can flash it with rsd lite.
Click to expand...
Click to collapse
I would hit the "Thanks" button 100 times if I could. Thank you very much for the mapping of the smg files and for the radio trick!
The last question (I hope):
I once flashed the CWM radio N_01.100.00R from here http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1.
This worked fine. But, why can I no more flash other sbf radios? If I pick any sbf radio and sbf_flash it, the program will just tell me that everything went fine but after the reboot I always see N_01.100.00R as radio version.
This also happened with the new radio I compiled with your instructions. I know this is not related to the process you told me, because it happens with other sbf radios, too.
bodom_lx said:
I would hit the "Thanks" button 100 times if I could. Thank you very much for the mapping of the smg files and for the radio trick!
The last question (I hope):
I once flashed the CWM radio N_01.100.00R from here http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1.
This worked fine. But, why can I no more flash other sbf radios? If I pick any sbf radio and sbf_flash it, the program will just tell me that everything went fine but after the reboot I always see N_01.100.00R as radio version.
This also happened with the new radio I compiled with your instructions. I know this is not related to the process you told me, because it happens with other sbf radios, too.
Click to expand...
Click to collapse
not really sure why ive never had that problem. let me test a few things and see if i can find a different work around.
---------- Post added at 07:12 PM ---------- Previous post was at 07:06 PM ----------
bodom_lx said:
I would hit the "Thanks" button 100 times if I could. Thank you very much for the mapping of the smg files and for the radio trick!
The last question (I hope):
I once flashed the CWM radio N_01.100.00R from here http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1.
This worked fine. But, why can I no more flash other sbf radios? If I pick any sbf radio and sbf_flash it, the program will just tell me that everything went fine but after the reboot I always see N_01.100.00R as radio version.
This also happened with the new radio I compiled with your instructions. I know this is not related to the process you told me, because it happens with other sbf radios, too.
Click to expand...
Click to collapse
do you have a copy of that cwm radio you can upload for me? the download link no longer works
also can you upload just the CG 5 that you got from the sbf you made?
NYG-SBXLII said:
not really sure why ive never had that problem. let me test a few things and see if i can find a different work around.
---------- Post added at 07:12 PM ---------- Previous post was at 07:06 PM ----------
do you have a copy of that cwm radio you can upload for me? the download link no longer works
also can you upload just the CG 5 that you got from the sbf you made?
Click to expand...
Click to collapse
Of course:
The un-overwritable CWM Radio
My CG 5 smg
Please note that you could try any sbf radio after the CWM flash, even this one. It is the International sbf referenced in this post. sbf_flash will not be able to overwrite the installed CWM radio.
bodom_lx said:
Of course:
The un-overwritable CWM Radio
My CG 5 smg
Please note that you could try any sbf radio after the CWM flash, even this one. It is the International sbf referenced in this post. sbf_flash will not be able to overwrite the installed CWM radio.
Click to expand...
Click to collapse
I notice you are referencing sbf_flash are you talking about sbf_flash for linux? If so that may be your problem. Do you have access to a windows OS? Try rsd lite for windows because I just flashed the file you gave me and then used rsd lite to flash back to my normal radio with no issues.
Finally!
NYG-SBXLII said:
I notice you are referencing sbf_flash are you talking about sbf_flash for linux? If so that may be your problem. Do you have access to a windows OS? Try rsd lite for windows because I just flashed the file you gave me and then used rsd lite to flash back to my normal radio with no issues.
Click to expand...
Click to collapse
It worked with RSD Lite. Maybe there is a bug with sbf_flash, it is probably not able to flash a SBF Radio over a CWM Radio.
Thank you again NYG-SBXLII. Thank you, thank you, thank you.
Hi,
I have a Motorola atrix 4g. The phone will not boot up. It turns on and the Motorola logo come then the red light stars blinking. after a minute or so the phone restarts and repeats the process. I tryed factory hard reset but no luck.
i fount this on the web http://forum.xda-developers.com/showthread.php?t=966405 but has no idea how to do this.
Pleas help me
thank you
Pgeorge
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Jack Krauser said:
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Click to expand...
Click to collapse
hi,
thank you for the fast replay. I have rsd installed, but where can i find this rom
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
stevendeb25 said:
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
It is not unlocked. There is nothing on the logo. Only the m
help
kinggeorge3287 said:
It is not unlocked. There is nothing on the logo. Only the m
Click to expand...
Click to collapse
help please
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
android-DEP said:
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
Click to expand...
Click to collapse
Hi,
I tryed doing this, but i get a error " Failed to process command flash: recovery error (0x180002)
I think when i tried to flash rom with RSD LIght may have done something to the files. and it was no help. I dont get a flashing red light now. only the phone stops booting at M logo.
Now How do i flash new rome ? Do i use RSD Light or something else. I know that RSB Requires .sbf file but all the files i see in the site you gave me are .zip.
i also tryed the fastboot flash boot boot.img and no luck, it gvies me the error "Failed to process command flash: recovery error (0x180002)"
thank you for the replay
Pgeorge
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
android-DEP said:
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
Click to expand...
Click to collapse
Well i tryed everything you provided, but no luck. I tryed the RSD but it dont go past the M logo after flash. any other way you know?
thnak you
pgeorge
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
android-DEP said:
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Click to expand...
Click to collapse
kinggeorge3287 said:
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
Click to expand...
Click to collapse
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
lucamibel said:
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
Click to expand...
Click to collapse
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
kinggeorge3287 said:
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Click to expand...
Click to collapse
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
sikkijazz said:
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
Click to expand...
Click to collapse
Hi,
doing this gave me SVF:108:1:2
fail to boot 3
starting rsd mode
lucamibel said:
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
Click to expand...
Click to collapse
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
kinggeorge3287 said:
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
Click to expand...
Click to collapse
help please
kinggeorge3287 said:
help please
Click to expand...
Click to collapse
I am able to get into android recovery. It has a option to update from sdcard. Can i do something with this?
Pleas help
Pgeorge
I've always had trouble finding a definitive answer for this question.
In general, are bootloaders backwards compatible? For example, if I flash a JB 4.2 bootloader, will flashing a JB 4.1 or ICS ROM work as expected, or does the bootloader need to be downgraded too? I know that some newer phones (like the S4) have an efuse that prevents going backwards (at least for stock), but does that concept hold true for all phones?
I have an S2 that I just replaced with an S4, so I'm going to play around with it some now (currently on stock 2.3.4 KH7 with rooted kernel). It's been a while since I've flashed an entire ROM (usually I just work on getting root), but since this won't me my primary phone anymore, I can play around with it a bit.
I can't give you a definitive answer. We have established that even though the file size for the boot loaders remains consistent from Gingerbread through jelly bean, there are differences between the files when examined as hex code. So the engineers do perform modifications with each version. I have never seen any discussion of the boot loaders not being backward compatible. So, since we have lots of stock and custom firmware on the forum that does not contain boot loaders, I would assume that you could flash a Gingerbread or ICS over JB or KitKat boot loaders without problems. And even if there were issues, it would be no problem to flash a full stock distribution to get the correct boot loaders. But again, this is only my surmise, and not based on direct knowledge.
There have been some statements by at least one developer that you must upgrade the boot loaders for the latest versions of Jelly Bean or KitKat. I would think it advisable to have matching boot loaders on your daily driver.
(apologies ahead of time that my initial post was probably in the wrong forum).
Well, at least I'm not the only one who hasn't been able to find a definitive answer.
Speaking specifically about the S2 (since that seems to be one of your specialties), if I need to update the bootloader to ICS or JB (since I'm on gingerbread) and something goes wrong, will it hard brick the phone or can I still get into the ODIN download mode to recover/reflash? Is the download mode on this phone considered part of the bootloader? I get a little confused sometimes in regards to what is included in the "module".
For example, it seems like (at least for this phone), the recovery image is built into the kernel as opposed to a separate image like my ASUS Transformer TF300T. Is that correct? On my TF300T, I can flash the recovery image separately through fastboot without touching the kernel, bootloader, or anything else, but it seems like the recovery image for the S2 always comes with a kernel.
Basically, I want to do anything I can ahead of time to reduce the risk of a brick (and know what I should avoid to reduce bricking the phone). Based upon what you said, it sounds like the best way to upgrade my bootloader is to flash a stock ROM that includes the bootloader. If that is the case, since JB 4.1 was the last version release by AT&T, should I just go to that bootloader and hope it works if I install a JB 4.2/4.3 or KitKat based ROM? I assume if I reflashed the stock KH7 ROM, it would just replace everything (including bootloader) and get me back to where I am now?
I have a lot of experience in the Linux world, so I'm trying to map over the Android concepts to the Linux concepts, but I still get tripped up sometimes (recovery, bootloader, kernel, ROM, etc). Sometimes people don't seem to use the terms the same way.
From a technical standpoint, it doesn't surprise me too much that the bootloaders are the same size. It's probably similar to the MBR code for hard drives that just does a minimalistic job of getting the hardware in an accessible state so it can later boot the kernel (like GRUB).
jpasher said:
(apologies ahead of time that my initial post was probably in the wrong forum).
Click to expand...
Click to collapse
Yes, questions are usually supposed to go in the Q&A forum, but there is not so much activity in this phone's forum any more, so it really doesn't matter much. And this information is more of a general nature anyway.
Well, at least I'm not the only one who hasn't been able to find a definitive answer.
Speaking specifically about the S2 (since that seems to be one of your specialties), if I need to update the bootloader to ICS or JB (since I'm on gingerbread) and something goes wrong, will it hard brick the phone or can I still get into the ODIN download mode to recover/reflash? Is the download mode on this phone considered part of the bootloader?
Click to expand...
Click to collapse
1. Hard brick on an android phone generally means that one of the boot loaders is corrupt, or it might mean that the memory module section that contains the boot loaders or other low level code is damaged. In general, the main thing you have to be careful about is when flashing a boot loader to make sure that the flash is not interrupted. For instance, say the power goes out, or the dog pulls out the usb cord, right in the middle of the flash, and after the boot loader partition is wiped, only part of the code is copied back to the partition. The good news is that the individual bootloaders are fairly small, so the time of vulnerability is a matter of seconds.
If you need to update to ICS or JB boot loaders, you would have to flash the full stock distribution that has the boot loaders included. No one has made Odin flashable tars of either of those. The UCKH7 Gingerbread secondary boot loader is available in tar, and that is the only separate tar I know of.
2. I don't know software engineering, only a little programming. I don't know where the code that puts the phone into download mode is located. It seems likely that it is in the secondary boot loader, but that is only speculation. I do know that you can enter download mode, and then flash both boot.bin and/or sbl.bin.
I get a little confused sometimes in regards to what is included in the "module". For example, it seems like (at least for this phone), the recovery image is built into the kernel as opposed to a separate image like my ASUS Transformer TF300T. Is that correct? On my TF300T, I can flash the recovery image separately through fastboot without touching the kernel, bootloader, or anything else, but it seems like the recovery image for the S2 always comes with a kernel.
Click to expand...
Click to collapse
1. The memory is partitioned. Each chunck of code is loaded into its specific partition. I don't have a partition table handy for the S2, but essentially you have: primitive boot loader (boot.bin), secondary boot loader (sbl.bin), parameters (param.lfs), kernel (zImage or boot.img), cache (cache.img), system (factoryfs.img), hidden (hidden.img), modem (modem.img) and several others like PIT, EFS, CSC and I don't remember what. But the ones I named are what is included in a full firmware distribution, and the AT&T model does not allow for the changing of the CSC like on the international S2 so that is not used. I'm not a Linux person, but if my understanding is correct, the img files install like a block device, but the boot loaders and param at a lower level.
2. There may be a recovery partition, but I'm not sure of that. If there is, it isn't used. Anyway, you are correct that the recovery is compiled into the kernel and is installed as a unit on the S2. You can not install a separate recovery on the S2. Many Android phones, maybe most as far as I know, do have a separate partition for the recovery. The S3 and S4 do also.
3. If you are interested, I have attached a partition table for the S4, which you might want to look at just for interest and learning. If memory serves me, it is quite a bit different from the S2.
Basically, I want to do anything I can ahead of time to reduce the risk of a brick (and know what I should avoid to reduce bricking the phone). Based upon what you said, it sounds like the best way to upgrade my bootloader is to flash a stock ROM that includes the bootloader. If that is the case, since JB 4.1 was the last version release by AT&T, should I just go to that bootloader and hope it works if I install a JB 4.2/4.3 or KitKat based ROM? I assume if I reflashed the stock KH7 ROM, it would just replace everything (including bootloader) and get me back to where I am now?
Click to expand...
Click to collapse
I would assume that the above is correct. The boot loaders in the 4.1.2 UCMD8 firmware would be the latest official ones for this phone. As far as flashing back to earlier stock, you would only get the boot loaders if you use a full distribution. Many of the stock distributions and almost all of the custom firmware posted on this site for the AT&T S2 do not contain boot loaders or param.lfs.
I have a lot of experience in the Linux world, so I'm trying to map over the Android concepts to the Linux concepts, but I still get tripped up sometimes (recovery, bootloader, kernel, ROM, etc). Sometimes people don't seem to use the terms the same way.
From a technical standpoint, it doesn't surprise me too much that the bootloaders are the same size. It's probably similar to the MBR code for hard drives that just does a minimalistic job of getting the hardware in an accessible state so it can later boot the kernel (like GRUB).
Click to expand...
Click to collapse
A lot of people around here (myself included) speak from anecdotal information gathered from the forums.
Wow. A LOT of useful information in that response. Thanks! A few of the things finally made some light bulbs go on in my head and clear some things up.
creepyncrawly said:
If you need to update to ICS or JB boot loaders, you would have to flash the full stock distribution that has the boot loaders included. No one has made Odin flashable tars of either of those. The UCKH7 Gingerbread secondary boot loader is available in tar, and that is the only separate tar I know of.
Click to expand...
Click to collapse
So to get to an ICS or JB bootloader, does it mean I have to perform an update through Kies? I'm looking at the different custom ROMs running KitKat and at least some of them say to be on a JB bootloader. I've read that at least some some devices (such as my TF300T), the different bootloader versions can actually have different partition layouts
If I tried flashing your OCD package for UCLL6 4.0.4 on my current system (with gingerbread BL), would it boot (or worst case, just not boot but still allow me to enter ODIN download mode to flash back to stock UCKH7)? If I'm understanding things correctly, it seems like as long as I'm not touching the bootloader, the worst thing that could happen is that I get an unbootable phone that I can still recover using ODIN download mode.
creepyncrawly said:
2. I don't know software engineering, only a little programming. I don't know where the code that puts the phone into download mode is located. It seems likely that it is in the secondary boot loader, but that is only speculation. I do know that you can enter download mode, and then flash both boot.bin and/or sbl.bin.
Click to expand...
Click to collapse
I guess I'll have to start poking around the different partitions to see if I can find any signs that point to what is what (unless I can't do a simple dd of the partition to a file using adb shell).
creepyncrawly said:
1. The memory is partitioned. Each chunck of code is loaded into its specific partition. I don't have a partition table handy for the S2, but essentially you have: primitive boot loader (boot.bin), secondary boot loader (sbl.bin), parameters (param.lfs), kernel (zImage or boot.img), cache (cache.img), system (factoryfs.img), hidden (hidden.img), modem (modem.img) and several others like PIT, EFS, CSC and I don't remember what. But the ones I named are what is included in a full firmware distribution, and the AT&T model does not allow for the changing of the CSC like on the international S2 so that is not used. I'm not a Linux person, but if my understanding is correct, the img files install like a block device, but the boot loaders and param at a lower level.
Click to expand...
Click to collapse
Very useful stuff. I'll have to read around a bit more to understand the different functions associated with each image. And yes, it would make sense that the img files are simply a direct bit-for-bit copy of that partition (which I would assume could be obtained with a simple dd copy). That would also explain why the bootloaders are the same size (if you dd a block device/partition, the resulting raw file is the size of the block device/partition). My guess is that the flashing process essentially just takes each img and does the same thing as a dd of the file to the partition.
This makes me wonder... If the bootloader partition for a phone has a JB BL, I can't see why someone couldn't do a dd of that partition into an image file and then restore that to the bootloader partition of another phone (maybe there's built in security that prevents stuff like that).
creepyncrawly said:
3. If you are interested, I have attached a partition table for the S4, which you might want to look at just for interest and learning. If memory serves me, it is quite a bit different from the S2.
Click to expand...
Click to collapse
Very nice. Thanks. I just got my S4 last month, so I don't plan on doing anything to it besides already acquiring root. I'm also on the MF3 release which doesn't have any known way of installing custom ROMs anyway.
I wouldn't use Kies. Flash the full distribution of the stock firmware that you want the boot loader. For JB boot loaders, flash UCMD8 full. You can find that in the Download Repository at the bottom of the page.
The OCD for UCKK6 does not have boot loaders. To get the Gingerbread boot loaders, flash UCKH7 full. To get the ICS boot loaders, flash UCLE5 or UCLL6 full. Again, you can get those in the Download Repository.
You can use dd to pull or restore the contents of a partition. You can use adb shell, or you can use terminal emulator right on the phone. In fact, it's a good idea to back up your efs partition using the dd command. I've posted how to do that several times in the forums. Advanced search for "back up efs" and "creepyncrawly" should find that for you.
I personally would never try to flash a bootloader using the dd command, although it is definitely possible. There is too much margin for error. Remember, the dd command is lovingly called the destroy disk command.
wait. I've never flashed any bootloader. My phone came with GB but the last official firmware that my phone had was the ICS OTA. From there, I flashed up to JB and now I'm happily running KK.
I have flashed the latest modem, however.
Unless I am missing something, my phone works just fine with old bootloaders and new kernel/recovery/roms.
Sent from my SGH-I777 using XDA Premium 4 mobile app
Once again, thanks for the useful info.
I would definitely only use dd to replace the contents of a partition as a last resort. Since I don't know enough about how android would handle a partition being changed underneath its feet, it would be risky.
I grabbed the file for UCMD8 (4.1.2) and I'll play around with that. I tried to grab UCLL6 (4.0.4) too, but the links point to the defunct hotfile site. Do you have updated links for that file (or is it exactly the same as what I can download at sammobile.com)? The full stock binaries (.tar.md5) go in the ODIN PDA slot, right?
Also, for those that may be interested, I made a copy of the bootloader from my stock UCKH7 (partition /dev/block/mmcblk0p2) and looked for strings related to the ODIN download mode, and I was able to find all of the strings that appear when in download (e.g. "ODIN MODE", "PRODUCT NAME", "ERASING DOWNLOAD INFORMATION", etc), so it's safe to say that ODIN download mode is part of the bootloader. All the more reason to just leave the bootloader alone if possible.
I also noticed that the two bootloader partitions (mmcblk0p2 and mmcblk0p3) are almost identical except for the text string SNBL in the mmcblk0p2 partition. I wonder why the two partitions...
bleggy said:
wait. I've never flashed any bootloader. My phone came with GB but the last official firmware that my phone had was the ICS OTA. From there, I flashed up to JB and now I'm happily running KK.
Click to expand...
Click to collapse
Which JB version are you running? One possible reason I can think of where a newer bootloader would be needed is if the partition layout changes. I've heard of some devices where that occurred with JB 4.2. Maybe that's why TWRP recovery has two different versions for 4.1 and 4.2 on my TF300T.
At any rate, it's good to hear that someone hasn't broken their phone by running an older bootloader with a newer ROM.
I'm on KitKat 4.2.2 now.
Previously, 4.3 & 4.2-something Jellybean. And a ICS rom before that.
I dont think flashing new bootloaders is necessary. I mean, I dont think its common.
Sent from my SGH-I777 using XDA Premium 4 mobile app
jpasher said:
I grabbed the file for UCMD8 (4.1.2) and I'll play around with that. I tried to grab UCLL6 (4.0.4) too, but the links point to the defunct hotfile site. Do you have updated links for that file (or is it exactly the same as what I can download at sammobile.com)? The full stock binaries (.tar.md5) go in the ODIN PDA slot, right?
Click to expand...
Click to collapse
I haven't finished uploading files to dev-host yet. But I'll be sure to upload that one today. I don't think you can get the file from sammobile either. They also used hotfile, and have not re-uploaded their complete library yet.
Yes, put the tar.md5 in the pda slot.
Also, for those that may be interested, I made a copy of the bootloader from my stock UCKH7 (partition /dev/block/mmcblk0p2) and looked for strings related to the ODIN download mode, and I was able to find all of the strings that appear when in download (e.g. "ODIN MODE", "PRODUCT NAME", "ERASING DOWNLOAD INFORMATION", etc), so it's safe to say that ODIN download mode is part of the bootloader. All the more reason to just leave the bootloader alone if possible.
Click to expand...
Click to collapse
So you dd'd the contents of 0p2 and looked at that? What tool did you use to look for strings? And do you know if that is boot.bin or sbl.bin? I think it must be boot.bin.
I also noticed that the two bootloader partitions (mmcblk0p2 and mmcblk0p3) are almost identical except for the text string SNBL in the mmcblk0p2 partition. I wonder why the two partitions...
Click to expand...
Click to collapse
Is it possible that there is built in redundancy? If one partition is bad, the second one can be used?
I have uploaded UCLL6 Odin Flashable tar.md5 to dev-host and posted it in the Download Repository.
By the way, I forgot so didn't mention it earlier in the discussion, but both UCLE5 and UCLL6 contain boot bin, but do not contain either sbl.bin or param.lfs. Evidently, the secondary boot loader and param files were not updated in the upgrade from Gingerbread to ICS.
Thanks for the files. One more question about them. If I simply remove the boot.bin and sbl.bin from the tar file and flash, that's the same as the "no bootloader" flash images, right? Maybe param.lfs too? I'm just thinking of ways to make things safer while I'm doing my initial testing (and bleggy seems to be running newer ROMs off the original GB bootloader).
creepyncrawly said:
So you dd'd the contents of 0p2 and looked at that? What tool did you use to look for strings? And do you know if that is boot.bin or sbl.bin? I think it must be boot.bin.
Click to expand...
Click to collapse
It was definitely the SBL, because it's a 1.25MB image instead of the 128K first stage bootloader. I found this thread about the Captivate (another extra phone I have) that says it works the same way (and does a good job explaining the boot process). I haven't figured out where the first stage bootloader (boot.bin) is stored, since it's not in a partition. I'll have to do some research on that.
In Linux, there's actually a command called strings that you can run on a file and it will extract all of the text strings it can find. A grep of that can find specific text. You could of course do the same thing by opening the file in a hex editor.
Is it possible that there is built in redundancy? If one partition is bad, the second one can be used?
Click to expand...
Click to collapse
That was my thought, but I'm not brave enough to experiment to see if that's true.
whats the point, anyway? having consistent bootloader and rom doesnt seem to matter and plenty of i777 owners are running kitkat which there is no available bootloader to download and flash.
Is this an OCD thing? I get flashing the various modems for signal improvement, but I've never had a problem booting any rom with my old GB or ICS bootloader.
Sent from my SGH-I777 using XDA Premium 4 mobile app
jpasher said:
One more question... If I simply remove the boot.bin and sbl.bin from the tar file and flash, that's the same as the "no bootloader" flash images, right? Maybe param.lfs too?
Click to expand...
Click to collapse
Yes, that would be true. As long as you are using Linux to tar the remaining files, they should flash fine. I guess you can add the md5 if you want also.
The UCLE5 and UCLL6 one-click downloaders that I posted have the boot.bin removed. The UCLE5 and UCLL6 stock plus root also have the boot.bin removed. No one has ever said anything about any problems resulting.
My assumption is that it's ok to keep gingerbread boot loaders, or to flash the ICS boot loader, or to flash the JB boot loaders, and you would never be able to tell the difference. On the other hand, there must be a reason that Samsung puts them into the kies download. I just have no knowledge and no speculation on how they differ, or whether it is important to have matching boot loaders.
Edit: Oh, and boot.bin probably goes into 0p0 partition, just a guess. But it gets flashed in the pda slot just like sbl and param, so it must go into a partition.
Edit: A forum friend found this thread for us.
Edit: I just found Adam Outler's online pit file analyzer and ran the pit file from the Download Repository through it. Partition information for the AT&T SGS2 attached.
bleggy said:
whats the point, anyway? having consistent bootloader and rom doesnt seem to matter and plenty of i777 owners are running kitkat which there is no available bootloader to download and flash.
Click to expand...
Click to collapse
I have no reason to make the bootloader match the ROM. I'm just making sure I understand how everything works together to avoid doing something that may potentially brick my phone. I flashed the no bootloader version of stock UCMD8 today and everything seems to be working fine. As long as things work, I don't really care which bootloader I have.
creepyncrawly said:
Edit: Oh, and boot.bin probably goes into 0p0 partition, just a guess. But it gets flashed in the pda slot just like sbl and param, so it must go into a partition.
Click to expand...
Click to collapse
There's not a "zero" partition. My only guess is that it's embedded somewhere else. Not sure at this point.
I found that post the other day with the S2 partition layout (that's what I was using for my tests). The PIT file analysis gives a little more info, although it says boot.bin partition is 0 bytes. That's what confuses me a bit. But in the end, not really a big deal. More of a curiosity than anything else.
When this forum was active "Don't mess with bootloaders" was common knowledge. Unless you absolutely have to. You can hard brick this thing if there's a problem while flashing it.
Don't mess with any of the files you mentioned. As far as I know it's unnecessary. I'm running Renders CM11 build with no problems with the original GB bootloader. Never had a problem with ICS or JB roms either.
Yea, my main purpose for starting the thread was to make sure I wouldn't break anything beyond repair by having mismatched bootloaders. It makes perfect sense why corrupting the bootloader would hose things (just like if you corrupted the MBR of your hard drive and had to boot off of alternative media to repair it, except for the fact that the phone does not have the ability to boot alternative media). My ASUS Transformer TF300T is nice in that aspect as the Nvidia chipset allows booting into APX mode which is an extremely low level boot mode that allows repair of almost anything. It should would be nice if the additional bootloader slot on the S2 could be used as a fallback with a way to choose which bootloader to run.
I'm the kind of person that likes to know more about the innards of how something works instead of looking at it as a black box. When I'm "flashing the kernel", I like to know exactly what it is I'm changing so I can understand the repercussions, especially if something goes wrong.
So the net result after this conversation is that I'm a lot more confident about flashing android devices (as long as I stay clear of messing with the bootloader whenever possible). I have CM11 running now too (stock CM kernel) while still on the GB bootloader.
Good afternoon, XDA community, I've been searching the heck out of Google for an answer to what I'm trying to do, and haven't gotten anywhere.
I have a Motorola Backflip running the latest AT&T firmware, and I'd like to downgrade it back to Android 1.5.
Now, I learned early on the Radio/Bootloader cannot be downgraded. After some digging I've found a thread on ModMyMobile that instructs you on loading the Radio image from the newer firmware into an SBF containing the older Android version. This can then be flashed from RSD Lite, and it'll keep the new radio and bootloader while loading the system partition of old.
However, an update released after that was post was made put the kibosh on that approach. It now refuses anything that isn't an official, signed SBF.
Here's three ideas I think might work, and I'd like your feedback on them:
1.) I have the MBN files extracted from the Android 1.5 SBF sitting on my hard drive. Is it possible to extract the contents of the systemsec.mbn file, load it into a flash-able ZIP; and then flash it via the custom recovery I have on the phone?
2.) If someone out there were to provide me with a backup of the old firmware, created with jr00ds recovery, could it then be modified to remove everything but the system partition, and then simply restore the modified backup to my device?
3.) This is one I know will do the trick: if someone on these forums has an old, battered Backflip that still has Android 1.5 sitting on its ROM, I could just transplant the motherboard to my pristine unit. If any of you have one you're willing to sell cheaply, please let me know!
Before anyone asks the obvious "Why so much effort for an outdated device/version of Android?", it's purely for nostalgia. This was my first Android device, and part of me would like to relive it. Because, frankly, the 2.1 update was just plain terrible.
I just got by brand new M8 (AT&T, Android 4.4.4). I plan to flash custom roms but in reading about some of the roms it seems I'm better off upgrading to the newest OTA update first. Since I don't have my at&t nano sim yet I figured I'd update manually. I downloaded the ruu from the HTC site along with the HTC sync app. In installed the sync app and connected my phone to it no problem. I then tried to run the ruu. It gives me an error 170. After researching the error and trying a few things still no luck.
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Any suggestions on getting on the latest update before I begin rooting and trying custom roms?
axeman71 said:
I downloaded the ruu from the HTC site I then tried to run the ruu.
Click to expand...
Click to collapse
What version number RUU?
axeman71 said:
It gives me an error 170. After researching the error and trying a few things still no luck.
Click to expand...
Click to collapse
If you don't specifically tell us what you tried, that second sentence isn't particularly useful.
Error 170 is USB connection error. RUU is very finicky, so just because other USB functions work, doesn't mean the RUU will. Try with the phone in bootloader-fastboot mode, try a different USB port, and different cable. USB 2.0 and Win7 have best compatibility with RUU.
axeman71 said:
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Click to expand...
Click to collapse
I'm not familiar with the instance of 2 different ROM.zip files being generated in the temp folder, so its impossible for me to say which to flash, and/or if they are safe.
Large zip file error when flashing zip is usually because there is a new requirement with the MM ROM, where you need to flash the MM firmware.zip before you can RUU. But I can give more guidance once you specify which RUU you are trying.
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
I thought the 2 roms was strange too. I didn't find reference to it anywhere in my searches.
I have been trying the bootloader-fastboot method but the process hangs at either "Updating...(1/2)Sending" or "Updating...(2/2)Sending". After an hour or and hour and a half I finally just disconnect the phone and reboot it.
axeman71 said:
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
Click to expand...
Click to collapse
You can't update by RUU to MM, unless you flash the MM firmware.zip first. Its some new requirement HTC added with all the MM RUUs. See the red text under RUU section of my Index thread, for instructions on flashing the firmware: http://forum.xda-developers.com/showthread.php?t=2751432
Although, failure to flash the firmware usually results in Error 155 Unknown Error. I suspect you still have some PC incompatibility with the RUU. Some folks have mentioned you can temporarily "turn off" USB 3.0 (if you have it) and make the port use USB 2.0. I'm not too familiar how to do that, but at least one guy had success with the RUU that way. So may be worth looking into. Otherwise, you may need to try to find a Win7 PC you can use.
The other option is to flash the firmware, then try the ROM zip again by SD card method. But I'm still a bit uneasy why there are 2 ROM zips, so do so at your own risk.
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
axeman71 said:
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
Click to expand...
Click to collapse
Happy to see it worked for you.
Yeah, I agree its strange. Folks fairly frequently need to resort to RUU to update, due to OTA not working or not available (such as you). So its odd to introduce the requirement to flash the firmware (which the huge majority of users won't have the skills or resources to even figure out is a requirement, must less perform), which AFAIK is present in every MM RUU for the M8 (not just AT&T).