FORUMS

OnePlus Addresses Reservation List Cheating

Jake Cooper figured out how to bump his place up on OnePlus’ reservation list and … more

OnePlus 2 Benchmark Scores Show Its Muscle

This video by FoneArena contains all the popular benchmarks being tested on the OnePlus 2, … more

Sony’s Emergence in The Middle: Is The Price Right?

Sony’s Electronics Division is not in its best days, and its smartphone … more

HTC Delivering Ads Straight to Sense Home

HTC’s 2015 has been a year marked by a desperate search for revenue.The HTC One M9 … more

[WARNING] Don't Hard Brick Your Atrix! Look Here.

2,701 posts
Thanks Meter: 3,806
 
By kennethpenn, Retired Forum Moderator / Retired Recognized Developer on 9th July 2011, 01:04 AM
Post Reply Subscribe to Thread Email Thread
What is this?
This is a warning that multiple users, including myself, have hard bricked their devices by SBF flashing to 1.8.3 after installing an official 4.5.91 update.
How can I avoid this brick?
You can avoid bricking your device by not flashing any over-the-air updates to Android 2.3.4. Instead, try flashing the 2.3.4 zip over here. Or, flash the pure stock images from here.
What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though.
What happens when you hard brick?
The error shows:
SVF:105.1:2
Failed to boot 0X1000

Quote:
Originally Posted by samcripp

the .91 update is the same as leak. Same binary 100% identical, not only do i confirm it, its confirm by every other dev. Dont listen to miss inform people. Once you update you will never be able to downgrade using sbf. You can sbf 4.5.91 because it has the same identical bl bp pass. Anything else will end up in a hard brick.

The only time this is an exception is for those who never unlocked. This folks after installing ota experience a semi hard brick when flashing pudding. This semi hard brick is similar in that it shows you 0x1000. But other than that it is just a semi hard brick.

What can you do to not hard brick your phone. Well easy, either you can use one of the widely available roms, any of the stock images, or a fruit cake. They are all base off .91

YOU COULD ALSO STOP USING SBF ALL TOGETHER. ITS NOT SAFE. RSD/SBF IS FOR INTERNAL CARRIER/MOTO USE. IT WAS NEVER MEANT FOR ANYONE TO EVER DOWNGRADE. PUT DOWN THE FLASE AND PRAISE THE SAFE METHODS.

safe methods:
fastboot
CWM
sbf with pudding already in it!

Last edited by _Alex_; 24th July 2011 at 04:05 AM.
The Following 37 Users Say Thank You to kennethpenn For This Useful Post: [ View ]
 
 
9th July 2011, 01:08 AM |#2  
Gutterball's Avatar
Senior Member
Flag New Jersey
Thanks Meter: 186
 
Donate to Me
More
Quote:
Originally Posted by kennethpenn

If you flash the official over-the-air update to get to 4.5.91 Gingerbread, you risk a hard brick.

The brick occurs when you flash the 1.8.3 SBF file in RSD mode over an officially updated 4.5.91 Gingerbread.

The stock ROM flashable I released is completely safe to use and should not brick your device if you choose to go back to 1.8.3.

I really think theres something wrong with 1.83 it's junk I'm using 1.26 only and manually updating from there from now on.
The Following 4 Users Say Thank You to Gutterball For This Useful Post: [ View ]
9th July 2011, 01:12 AM |#3  
Member
Thanks Meter: 16
 
More
Quote:
Originally Posted by Gutterball

I really think theres something wrong with 1.83 it's junk I'm using 1.26 only and manually updating from there from now on.

so is it safe to go from the ota to 1.26?
The Following User Says Thank You to geishroy For This Useful Post: [ View ]
9th July 2011, 01:13 AM |#4  
phobos512's Avatar
Senior Member
Flag Lexington Park, MD
Thanks Meter: 132
 
More
Could this be related to changes made to the bootloader in support of the discovered unlockability?
9th July 2011, 01:14 AM |#5  
kennethpenn's Avatar
OP Retired Forum Moderator / Retired Recognized Developer
Flag Washington, D.C.
Thanks Meter: 3,806
 
Donate to Me
More
Quote:
Originally Posted by geishroy

so is it safe to go from the ota to 1.26?

We're not sure at the moment.
9th July 2011, 01:16 AM |#6  
Member
Thanks Meter: 16
 
More
Quote:
Originally Posted by kennethpenn

We're not sure at the moment.

how about using a cwm backup from gingerblur instead? would that be safer. i know it's hard to say i just want your opinion if it comes to that. thanks.
The Following User Says Thank You to geishroy For This Useful Post: [ View ]
9th July 2011, 01:18 AM |#7  
Senior Member
Thanks Meter: 52
 
More
This should be stickied.

Sent from my MB860 using XDA App
The Following User Says Thank You to NoNameAtAll For This Useful Post: [ View ]
9th July 2011, 01:18 AM |#8  
AllTheWay's Avatar
Retired Senior Moderator
Flag Placerville, California
Thanks Meter: 80
 
More
Replacement Atrix
I have a replacement Atrix that was sent to me a couple of days ago. I havne't sent the old one back (vibration issues) I can update to the latest update and then try and flash back the 1.26 to see if that works.

I can try this out later tonight when I get home to make sure.
9th July 2011, 01:21 AM |#9  
AllTheWay's Avatar
Retired Senior Moderator
Flag Placerville, California
Thanks Meter: 80
 
More
Quote:
Originally Posted by NoNameAtAll

This should be stickied.

Sent from my MB860 using XDA App


Just took care of that ;)

I just flashed the OTA update from the other thread by renaming the file to update.zip.

It wouldn't surprise me if Moto did something to prevent you from flashing back to a earlier version sort of like what Apple does with the iPhone. Hopefully somebody will figure this out though. What about a NVFlash?
9th July 2011, 01:22 AM |#10  
Member
Thanks Meter: 1
 
More
so i had issues with 2.3.4 and flashed back to 1.8.3 before i read this and its bootlooping after the ATT splash. what can i do to fix this...im scared to flash anything else at the moment. somebody please help.
9th July 2011, 01:26 AM |#11  
Senior Member
Thanks Meter: 3
 
More
Has the official OTA started getting sent out yet? im still running gingerblur 4.5 with a locked bootloader and im not wanting to do anything until the offical one comes out. My plain is to flash 1.2.6 sbf and start all over and do all the OTA updates all the way to gingerbread then unlock the boot loader after that. Is that way the safest way
The Following User Says Thank You to mudd_cat23 For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread

Tags
tag2
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes