Database Develop

[GUIDE] Flash SBF to Motorola Atrix 4G

WARNING
DO NOT FLASH ON BELL ATRIX
​If you appreciate this guide, please visit my website (maybe check out my sponsors!), subscribe on Twitter, press the thanks button below, or donate to Fixter, DesignGears, Fenny and other great helpers/devs for the Atrix 4G.
Download
1.2.6
http://bandbinnovations.com/Atrix.7z
Password: atrixbl
1.5.2
HTTP (Rename from .rar to .gz)
HTTP (Rename from .rar to .gz)
MultiUpload
Hotfile.com
DepositFiles
UPDATE: Linux SBF guide here --> http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html --> Thank you "relaxed"
Flash Guide (Instructions)
Prerequisites
Download RSDLite 5.0 (MediaFire mirror)
Install the program
Download SBF file from above links
Bricked phone or test device
Fully charged device
Drivers installed (if you rooted your phone, your computer has the necessary drivers)
32-bit
64-bit
Problems
Some users experiencing WiFi connectivity weirdness
SIM-unlocked devices may still have WiFi problems
Market might not show all applications (easy fix on the way)
Do not flash this file unless absolutely necessary. It will help those who’ve bricked their device to recover, but this is not for flashing just for fun. BriefMobile cannot be held responsible for device damage due to this guide.
Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .gz file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Congratulations!

Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.

designgears said:
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
Click to expand...
Click to collapse
Good tip! Didn't know that!

Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?

tianqi said:
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
Click to expand...
Click to collapse
Yes. This isn't a confirmed issue, but others have experienced WiFi problems with this SBF flash over their SIM unlocked devices.

Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.

cellzealot said:
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
Click to expand...
Click to collapse
That's very odd. Mine most definitely shows as "NS Flash Olympus."

im a noob sorry, but what does this actually do?

fRenZy-_- said:
im a noob sorry, but what does this actually do?
Click to expand...
Click to collapse
If you mess around with your device and break it, this can save your life by unbreaking it!

I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.

kennethpenn said:
That's very odd. Mine most definitely shows as "NS Flash Olympus."
Click to expand...
Click to collapse
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.

cellzealot said:
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
Click to expand...
Click to collapse
Thanks for the info! Duly noted... editing the post.

jimmydafish said:
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
Click to expand...
Click to collapse
100% positive I purchased my device retail. I'll screenshot the RSD Lite for you in a moment when I recover from my soft brick (screwed up framework-res).

RSD Lite reports "NS Flash" for me too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
purchased through Amazon

kmiller8 said:
RSD Lite reports "NS Flash" for me too
purchased through Amazon
Click to expand...
Click to collapse
Perhaps "NS Flash" does not mean developer phone on the Atrix?

kennethpenn said:
Perhaps "NS Flash" does not mean developer phone on the Atrix?
Click to expand...
Click to collapse
Or maybe we both got incredibly lucky is there any way to further verify if RSD Lite is reporting incorrectly?
Also off topic, why is the "Start" grayed out for me?

mine also says NS, purchased directly from AT&T
start is greyed out if there is no file/an incorrect file to flash, notice that the file properties pane is blank, it has not actually loaded the file in the select box in that screenshot

Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
Mainly just recovers you from a soft-bricked or improperly hacked device. It flashes you back to stock (or as close to stock as we have right now.)
No new features. No bug fixes. Nothing different from stock except a few new possible issues.

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
It changes some stuff, but I can hardly see anything different at face value.

[Guide] How to revert to Stock Rom with S-On if USB port is broken (For Warranty)...

Last week i came across a couple of guys who had their phone's USB port broken and cant revert back to their stock Rom with S-On as they couldn't flash an RUU using their PC.
These steps helped them revert back to their stock Rom with S-On which is required for warranty claim. I thought it would be useful for others as well if I compile a simple guide here.
Remember I didn't invent this method rather its a result of research in the past when I was rooting my DHD and Incredible S and found these instructions on different forums. I have just compiled it in an easy guide.
I have tested this method myself and if this guide is correctly followed step by step its very safe but still I am not responsible if your GF/BF dump you, your phone becomes a paper weight or heavens fall as a result of following this guide.
DO IT AT YOUR OWN RISK.
Follow these steps:
1. Download your device specific RUU from this sticky thread or Google for it.
2. Run the RUU and when its de-compressed and asks you to press next, just stop there (Don't close this window).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Go to the "temp" folder on your PC. If you are on Windows 7 its located in "C:\Users\{Your_User_Name}\AppData\Local\Temp" and on Windows XP its in "C:\Documents and Settings\{Your_User_Name}\Applications Data\Local Settings\Temp"
4. Use the windows search function in "Temp" folder or dig deep into sub folders to find "rom.zip" file. It'll be around ~250MB in size.
5. Copy this file and paste it somewhere else on your PC e.g. desktop.
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Delete the "PG32IMG.zip" from SD Card now.
To verify S-On reboot into bootloader again (Step 11) and on the very first line it will say S-On or S-Off.
Need any further help??
Leave a reply here
Ehsan

Great guide. Thanks .

thank u.. ^_^v

You all are welcome
It's all about the community
Sent from my HTC Incredible S using XDA App

That may just come in handy some day. Thanks!

ehsan76 said:
Last week i came across a couple of guys who had their phone's USB port broken and cant revert back to their stock Rom with S-On as they couldn't flash an RUU using their PC.
These steps helped them revert back to their stock Rom with S-On which is required for warranty claim. I thought it would be useful for others as well if I compile a simple guide here.
Remember I didn't invent this method rather its a result of research in the past when I was rooting my DHD and Incredible S and found these instructions on different forums. I have just compiled it in an easy guide.
I have tested this method myself and if this guide is correctly followed step by step its very safe but still I am not responsible if your GF/BF dump you, your phone becomes a paper weight or heavens fall as a result of following this guide.
DO IT AT YOUR OWN RISK.
Follow these steps:
1. Download your device specific RUU from this sticky thread or Google for it.
2. Run the RUU and when its de-compressed and asks you to press next, just stop there (Don't close this window).
3. Go to the "temp" folder on your PC. If you are on Windows 7 its located in "C:\Users\{Your_User_Name}\AppData\Local\Temp" and on Windows XP its in "C:\Documents and Settings\{Your_User_Name}\Applications Data\Local Settings\Temp"
4. Use the windows search function in "Temp" folder or dig deep into sub folders to find "rom.zip" file. It'll be around ~250MB in size.
5. Copy this file and paste it somewhere else on your PC e.g. desktop.
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Delete the "PG32IMG.zip" from SD Card now.
To verify S-On reboot into bootloader again (Step 11) and on the very first line it will say S-On or S-Off.
Need any further help??
Leave a reply here
Ehsan
Click to expand...
Click to collapse
didnt work
Plz help dude
---------- Post added at 03:27 PM ---------- Previous post was at 03:13 PM ----------
suaji said:
thank u.. ^_^v
Click to expand...
Click to collapse
Hey suaji
Did it really work for u?
Coz my radio is also same as u
plz help me im really pissed off!!

santhoshpirate said:
didnt work
Plz help dude
---------- Post added at 03:27 PM ---------- Previous post was at 03:13 PM ----------
Hey suaji
Did it really work for u?
Coz my radio is also same as u
plz help me im really pissed off!!
Click to expand...
Click to collapse
are you downgrading your radio>?
if you are its impossible can only go up with the IS

jul644 said:
are you downgrading your radio>?
if you are its impossible can only go up with the IS
Click to expand...
Click to collapse
no im doin nothin i just want my incredible s back to s-0n

humm
santhoshpirate said:
no im doin nothin i just want my incredible s back to s-0n
Click to expand...
Click to collapse
what software version are you on right now/.?
is your usb port broken?
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2...5AU_3805.06.03.03_M_release_199308_signed.exe

jul644 said:
what software version are you on right now/.?
is your usb port broken?
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2...5AU_3805.06.03.03_M_release_199308_signed.exe
Click to expand...
Click to collapse
but my baseband radio version is 20.2805.30.085AU_3805.04.03.27_M

santhoshpirate said:
but my baseband radio version is 20.2805.30.085AU_3805.04.03.27_M
Click to expand...
Click to collapse
Then try extracting the ROM.zip file from this RUU:
RUU_Vivo_Gingerbread_S_KT_KR_2.21.1010.4_Radio_20. 2805.30.085AU_3805.04.03.27_M_release_194748_signed

tpbklake said:
Then try extracting the ROM.zip file from this RUU:
RUU_Vivo_Gingerbread_S_KT_KR_2.21.1010.4_Radio_20. 2805.30.085AU_3805.04.03.27_M_release_194748_signed
Click to expand...
Click to collapse
i tried and it was success but my phone is still s-off and also shows revolutionary and the hboot version 6.13.1002

santhoshpirate said:
i tried and it was success but my phone is still s-off and also shows revolutionary and the hboot version 6.13.1002
Click to expand...
Click to collapse
OK, that is a start. The Revolutionary HBOOT prevents a RUU/ROM.zip from overwriting it.
I answered your post in the General section about the procedure steps to remove the Revolutionary HBOOT. Hopefully that will get you going as long as your USB port cooperates.

Guide updating soon!!!
This guide was actually targeted for those users who have their USB Ports broken and have nothing else to do.
Anyways due to so many PMs asking me how to get S-Off when their HBOOT is not being overwritten by this method so no S-On for them... I am updating this guide very soon to help all those.
Please keep in mind I will just post the guide but can't test it myself as I don't own an Incredible S anymore.
I been extremely busy lately with my newborn so couldn't update it or reply you guys. Just wait for a day or so and you'll have this guide updated with instructions for those who can't get S-On with the current instructions.
I'll try to make it valid for those who have their USB ports broken as well
Thanks.
Ehsan

ehsan76 said:
This guide was actually targeted for those users who have their USB Ports broken and have nothing else to do.
Anyways due to so many PMs asking me how to get S-Off when their HBOOT is not being overwritten by this method so no S-On for them... I am updating this guide very soon to help all those.
Please keep in mind I will just post the guide but can't test it myself as I don't own an Incredible S anymore.
I been extremely busy lately with my newborn so couldn't update it or reply you guys. Just wait for a day or so and you'll have this guide updated with instructions for those who can't get S-On with the current instructions.
I'll try to make it valid for those who have their USB ports broken as well
Thanks.
Ehsan
Click to expand...
Click to collapse
Waiting for fresh posts....
Pls update soon on how to get back to stock ROM... i.e how to unroot the phone(my usb is not broken though)
Which is the best method to root?...
I am confused seeing each and every thread here...superoneclick,alpharev..etc....
Pls give a basic complete guide...thanks.

can anyone else verify that they got S-ON back with this method? and also whether Hboot and recovery reverts back to stock? GF's phone needs to go for warranty due to a faulty earpiece and i'm in a different country as she is so will need to guide her over skype. any help is welcome. Thanks in advance.

jul644 said:
what software version are you on right now/.?
is your usb port broken?
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2...5AU_3805.06.03.03_M_release_199308_signed.exe
Click to expand...
Click to collapse
i used this RUU to turn my phone back to s-on now i do not receive any OTA?! what should I do?!

k7azadeh said:
i used this RUU to turn my phone back to s-on now i do not receive any OTA?! what should I do?!
Click to expand...
Click to collapse
Be patience and keep checking.

Hey,
your guide worked for me without any problem. Now I´m S-On
and on the Stock - Rom and my phone is ready for warranty!
Tank's allot!!!!!!!!
ehsan76 said:
Last week i came across a couple of guys who had their phone's USB port broken and cant revert back to their stock Rom with S-On as they couldn't flash an RUU using their PC.
These steps helped them revert back to their stock Rom with S-On which is required for warranty claim. I thought it would be useful for others as well if I compile a simple guide here.
Remember I didn't invent this method rather its a result of research in the past when I was rooting my DHD and Incredible S and found these instructions on different forums. I have just compiled it in an easy guide.
I have tested this method myself and if this guide is correctly followed step by step its very safe but still I am not responsible if your GF/BF dump you, your phone becomes a paper weight or heavens fall as a result of following this guide.
DO IT AT YOUR OWN RISK.
Follow these steps:
1. Download your device specific RUU from this sticky thread or Google for it.
2. Run the RUU and when its de-compressed and asks you to press next, just stop there (Don't close this window).
3. Go to the "temp" folder on your PC. If you are on Windows 7 its located in "C:\Users\{Your_User_Name}\AppData\Local\Temp" and on Windows XP its in "C:\Documents and Settings\{Your_User_Name}\Applications Data\Local Settings\Temp"
4. Use the windows search function in "Temp" folder or dig deep into sub folders to find "rom.zip" file. It'll be around ~250MB in size.
5. Copy this file and paste it somewhere else on your PC e.g. desktop.
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Delete the "PG32IMG.zip" from SD Card now.
To verify S-On reboot into bootloader again (Step 11) and on the very first line it will say S-On or S-Off.
Need any further help??
Leave a reply here
Ehsan
Click to expand...
Click to collapse

Hi, which Rom do I use for the UK?
Thanks
Sent from my HTC Incredible S using xda premium

[Q] how do i relock the bootloader?

can someone help? i want to update tot he 4.0 but i need to relock my bootloader to have it work. i dont know how since im pretty noob at this

Provided u still have the folder u used to unlock, boot ur phone into fastboot (vol dn + power) connect it to ur pc with a USB cable, then from the command prompt in the folder where fastboot.exe is, type: "fastboot oem lock" without the quotations. Good luck!
Sent from my HTC Raider X710e using xda premium

ah damn i dont think istill have it
is there another way?

oh nvm i think i do i have it i just need to look for it
thank u so much haha im so happy right now

i have one more question when i did it it said this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so idk if it worked
i tired to update and it still didnt work

anyone have a copy of this fastboot.exe file..
i dont seem to have it anymore.. need to relock also so i can install the file.
---------- Post added at 01:55 AM ---------- Previous post was at 01:27 AM ----------
an4564 said:
i have one more question when i did it it said this
so idk if it worked
i tired to update and it still didnt work
Click to expand...
Click to collapse
Mine just did the same thing...
---------- Post added at 02:01 AM ---------- Previous post was at 01:55 AM ----------
OK, so i went back in to try again, came up saying its locked..
lets see how it go's.

i tired it a few times idk if its gonna work

mine comes up saying locked now, but when i go to install it powers down and then go's into the bootloader.. hmmm

i still havent seen the update yet
i tired it a bunch of times and nothing ever comes up

you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
an4564, what device do you have, what network are you on, and what exactly are you attempting to achieve, what does "nothing ever comes up" mean to the rest of us who are not mind readers

If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card

i have the htc vivid for AT&T and am trying to get the ics update. i relocked my bootloader and typed in the *#*#682#*#* code and waited for the notification to come up but it never does. i have tired it multiple times

woodsytattooman said:
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
Click to expand...
Click to collapse
oh is this the update that was put out today?

an4564 said:
oh is this the update that was put out today?
Click to expand...
Click to collapse
No it is not. I don't know if there is a RUU for the newest ics.

davidcampbell said:
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
Click to expand...
Click to collapse
i am trying to update my Velocity with the OTA ICS update, i relocked the bootloader, restarted the phone, initiated the install, it gets to the point of restarting and instead of starting the install Fastboot comes up..

I think I bricked it - CWM unable to mount Ext SD & Data

First few things: I've searched already, can't find any similar threads that actually help. I have the international version. I was running the CM10.2 Rom prior to 'the accident'. I will put a bounty on this if I have to.
There's a bit of a story to this so I'll go over it all - not sure what's relevant.
I've been running out of storage for days, a 64GB SD card is in the mail. I currently have an 8GB one as well as the internal 16GB, both of which were near full, but the external one had relatively more than the internal one, so I decided to use foldermount and link2SD to move some space over. That all went fairly well.
This morning I got invited to the Aviate Beta launcher, which looked interesting. Tried to install, didn't have enough space. So I decided to make a backup of Nova, go into the play store, uninstall nova to free up space and then install Aviate without leaving the playstore. It worked, turns out I don't like Aviate much, so I worked backwards. Uninstalled Aviate, went to install Nova. Not enough space (idk how). Uh oh.
So I deleted some less-necessary apps that I could reinstall later. Not enough storage. Notification comes up in the bar along the lines of "storage critically low, device may malfunction". Now whenever I attempted to enter settings, the process crashed. Great. Simple fix, flash a NANDroid back-up in CWM. I can't remember what the message was, but there was something wrong with the back-up.
Wiped everything and tried to flash CM10.2 from the external SD Card but it wouldn't mount. Data also wouldn't mount. I tried several SD Cards ( ie about 10, different brands, sizes, classes, etc out of hope). So I decided I'll open up and Odin and just re-do everything per /showthread.php?t=2387980.
Turn the phone back on, stock Jelly Bean lockscreen was there, and once unlocked only the notification bar was there (no launcher). So I used different versions of Odin, different cables, downloaded the image several times, etc etc. Nothing fixed it. In fact, it's worse now. after booting past the Samsung logo, the screen just goes black now. smh
Can anyone help? It would be extremely appreciated. It's also a time sensitive issue as I need the device for work on Monday.
Sorry if I've missed anything. Yes I'm a noob, but you great people at XDA have helped a lot of people out before so I'm hoping you can help me.
Thanks!

Sorry to bump...
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.

tiskael said:
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
Click to expand...
Click to collapse
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.

Devo7v said:
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Click to expand...
Click to collapse
Yes, the i9295 - the international version. The Odin md5 can be found on this thread: /showthread.php?t=2387980.
Sorry if this sounds rude (it's not, I just don't know how to use kies) but what's that supposed to do? I can't find a way for Kies to fix anything... I tried this thread: /showthread.php?t=1984717 but when I have to enter my phone model (GT-i9295) it says "Please check the model name and enter it" and closes the pop-up window within kies. Any more help?
Thanks for trying so far.

Sorry for bumping but i need this fix. $100 to the first person who can fix this by Monday.

I can't possibly believe that no-one knows how to fix this, or at least whether it's fixable or not. Is anyone willing to answer my question?

Check this threads or ask the guys who helped me there, they are Awesome
So after boot you get an totally black screen? Only theorigial Samsung boot logo before it turns dark?
I had this problem twice, but can you tell me if you start the phone after the dark screen do you have sound (like the phone still works, but only no screen) or nothing?
The first time i had sound, need to say that i never solved this problem, re-installed stock firmware, (recovery still works, you only need to know wat to puch) Unrooted my phone, and send it in for waranty, They send me a new phone, never know what was the problem, it can be o broken screen, but i never believed it totally... check this thread for that: http://forum.xda-developers.com/showthread.php?t=2363185&page=9
The other time i had this i installed a other CWM Recovery Version, i had one installed, but some problems with it, installed an other version, after Reboot the Same Samsung Logo...Dark screen, installed this CWM: http://forum.xda-developers.com/attachment.php?attachmentid=2464887&d=1387533161
Good Luck with it M8

Here is something that could/couldn't help you...
I am not sure/not tested this so i am not responsible for anything that happenes to your phone
1.DOWNLOAD A STOCK FRESH SAMMY ROM FROM SAMMOBILE
2.Use odin3.7
3.Open ODIN AND CHOOSE PDA THEN CHOOSE THE FIRMWARE YOU EXTRACTED /DOWNLOADED
4.Now flash the firmware
5.When reached at the state you previsouly in reboot to download mode again and do step 3 again
6.Now download the pit file from HERE
7.In odin screen make sure 3 buttons are checked F.rest time , auto reboot , REPARTITION
8.Now choose frimware in pda
9.CHOOSE THE FILE YOU HAVE ALREADY DOWNLOADED FROM ATTACHMENT IN SIDE THE PIT BOX LIKE THE PICTURE UNDER
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
10.hit start and let the device flash like normal
11.it will auto reboot ...hope this fixes your issue
THE PIT FILE IS CALLED i9295.pit and is from here
HERE IS SOME INFO ABOUT PIT FILES
What are pit files ?
A pit file is a kind of file often used in samsung phones / tablets , these files contain partition tables of the device and the spaces of them with the arragment of each partition with there corresponding mount points ; these files can difenitly dangerous and can kill your tab/phone with a breeze if not used with care
Click to expand...
Click to collapse
What do pit files really do ?
Pit files can help in fixing a broken mmc for ex:
Click to expand...
Click to collapse
NOTE: I AM NOT RESPONSIBLE IF THIS WILL MAKE THINGS EVEN WORSE
make a try and let me know

try this too..
When my DATA is not mounting, i feel bad as well for in my case, i can't do what mythi's solution by flashing PIT file and stock rom using odin, coz my usb port isn't functioning anymore.. in short, my phone is just charging and not syncing to PC anymore... what i did is go to cwm, tried to mount /data there but gives me an error... what i did next is format /data and /data/media (/sdcard) then flash the new cm11 KITKAT they just finished building... reboot, waited for 2 min or so, boom my phone is back to life..

Bricked phone.

Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.

Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224

Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV

Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.

Real appreciated, will keep you updated, if anything works ill post it here.

Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL

Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536

Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?

mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??

TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu

mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\

mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)

TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.

mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig

TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?

mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo

TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\

Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards

ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?