Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[WARNING] v4.5.141 Causing Problems

OP kennethpenn

17th February 2012, 04:25 AM   |  #1  
kennethpenn's Avatar
OP Retired Forum Moderator / Retired Recognized Developer
Flag Washington, D.C.
Thanks Meter: 3,801
 
2,701 posts
Join Date:Joined: Nov 2006
Donate to Me
More
I've received a bunch of notifications saying that the latest update leads unlocked bootloader users to some sort of device brick. I know absolutely no details at this time. This post is a warning to those who may attempt the update.

If you have any details, please post below.

Notices:
- DO NOT USE SBF FILES EVER.
Last edited by kennethpenn; 17th February 2012 at 04:32 AM.
The Following 6 Users Say Thank You to kennethpenn For This Useful Post: [ View ]
17th February 2012, 04:59 AM   |  #2  
Alaq's Avatar
Recognized Contributor
U.S.
Thanks Meter: 397
 
1,098 posts
Join Date:Joined: Jan 2011
More
Exclamation 4.5.141 Update Warning!
So, hey yea you. What is this?
This is a warning that a developer has hard bricked his device by updating to the new 4.5.141 update and attempting to unlock his device. As well as some users hard bricking their phones by flashing the new 4.5.141 SBF via RSD Lite build on their already unlocked devices and updating via OTA on their already unlocked devices.
How can I avoid getting hard bricked oh knowledgeable person!
You can avoid bricking your device by not flashing any over-the-air updates to Android 2.3.6 (4.5.141). You can try flashing Nottach's new ROM based off the 4.5.141 update NottachTrix 4G or just don't upgrade at all.
Specifically, what should I avoid?
Specifically you should avoid updating over OTA on an unlocked device, although many users confirmed that it works there is still a very very high risk updating a device with an unlocked bootloader, and you should NOT FLASH THIS SBF!
That link is given so you know what not to flash, if you flash that and get bricked it's not our fault!
What if I already flashed the official 4.5.141?
If you flashed the official update you should seriously avoid flashing SBF files in RSD Lite. Using Fruit Cakes to downgrade have not been tested yet, it is suggested over RSD but your on your own until someone confirms that Fruit Cakes work to downgrade.
What happens when you get a hard brick?
The error shows:
SVF:105.1:2
Failed to boot 0X1000
Too late! I'm bricked, what can I do?
To tell you the truth, it has been impossible to recover from a hardbrick until yesterday. In his post, Nottach was able to fix his hardbrick. He wrote everything he did in that post. Read it and hope it works. Notice: This may not work for you, but you have nothing to lose if it doesn't work since you already bricked your phone...
Yea yea, I used Kenn's layout from the older warning thread, Sue me...
UPDATE FIX: UncleCemka made a guide for us to update to 4.5.11 with an unlocked bootloader and root. Give him thanks!

Quote:
Originally Posted by UncleCemka

I could not find any resource here, to provide a step-by-step guide for going from ATT 4.5.91 rooted, with Unlocked Bootloader to the latest 4.5.141 without bricking. I put this together myself and tested it on my own Atrix. Use at your own risk!

It's kind of a technical guide, but you really get to learn about your phone doing it this way. I did assume you know some basics about Android and Atrix that you could learn from Swiftks great guide: http://forum.xda-developers.com/show....php?t=1154600

Thanks to all of the resources here on XDA, that I used to pull this info together.

REQUIREMENTS:
- ATT Atrix 4.5.91 with Unlocked Bootloader
- Custom Recovery (Romracers or Rom Manager)

PRE STEPS:
- Take a full Nandroid Backup with CWM
- Backup your apps with TiBu
- Backup Call and SMS Logs with My Backup Root


Files Needed:
- 4.5.141 Full SBF - http://atrix.tk/4.5.141/ or http://forum.xda-developers.com/show...&postcount=393
- preinstall.img - for root - http://forum.xda-developers.com/show...22&postcount=2
- adb and moto-fdastboot - get anywhere
- Portable SBF Tool - http://forum.xda-developers.com/show....php?t=1059643
- .37P Radio zip (N_01.77.37P_usa_att_12dec2011.zip) - http://forum.xda-developers.com/show....php?t=1339047
- Nebtop for Webtop over HDMI - http://forum.xda-developers.com/show...p?%20t=1404625


Steps:
- Open full 4.5.141 SBF with Portable SBF Tool, to extract the smg files. Move the SMG folder, before closing the tool.

- Power off phone
- Power on while holding down the vol button
- Scroll to Fastboot with the vol down, vol up to select fastboot
- Connect to PC
- Cleanup:
moto-fastboot erase system
moto-fastboot erase boot
moto-fastboot erase webtop
- Flash new boot, system, webtop, preinstall
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
moto-fastboot flash preinstall preinstall.img
- Wipe and reboot
moto-fastboot -w
moto-fastboot reboot

- Turn on USB Debugging
- Root
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH
pm install /preinstall/Superuser.apk
*Make sure to accept the Superuser prompt on the phone when using it the first time.

- sqlite
cp /preinstall/sqlite3 /system/bin/sqlite3
chmod 6755 /system/bin/sqlite3

- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit

- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"

sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db

select * from settings WHERE name='entitlement_check';

*118|entitlement_check|disabled
.exit


- Radio
adb push N_01.77.37P_usa_att_12dec2011.zip /mnt/sdcard/
reboot into recovery and apply from sdcard
wipe cache
wipe dalvik cache
reboot

- Recover apps with TiBu

- Restore Call log and SMS data with My Backup Root

- Remove Annoying SDCARD Mount sounds
adb shell
su
setprop persist.service.mount.playsnd 0

- Install the Nebtop Apk for Webtop over HDMI

Last edited by Alaq; 24th February 2012 at 10:52 PM.
The Following 12 Users Say Thank You to Alaq For This Useful Post: [ View ]
17th February 2012, 07:37 AM   |  #3  
Account currently disabled
Flag New York
Thanks Meter: 3,950
 
1,587 posts
Join Date:Joined: Mar 2008
More
I went through this update fiasco with two different Atrixs, One unlocked, one locked.

Unlocked device:
I could not get the OTA update to work no matter how "back to stock" I was.
I kept receiving Failed to Boot 2 errors and could only solve them using RSDlite.
I also received a Failed to Boot 1 when using the auto-update tool and RSDlite again was the only solution.
Each time I used the pre-unlocked 4.5.91 sbf to fix.

After returning that device, for unrelated issues, I got a brand new, locked, device.
I applied the OTA update before unlocking.
Then I flashed pudding.sbf and got:
SVF message: 105:1:2
Failed to Boot 0x1000
I thought I was done for.
But after trying many different button combos I was somehow able to get to fastboot.
I think it was holding vol up and power while inserting the battery that got me into fastboot.
From there I tried to flash different 4.5.91 partitions starting with boot but it kept failing.
So, I proceeded to finish the unlock by, fastboot oem unlock.
That got me into a bootloop and I was able to reboot into fastboot the normal way where I then installed the stock 4.5.91 system and boot images.
I was then able to boot into 4.5.91.

If you get to this point I recommend waiting for a fruitcake or trying out NottachTrix.
It was a real pain to get the update flashed and booting, more trouble than it's worth unless you plan on ripping it apart. I believe it's because there were apk patches opposed to full apks. Also boot patches that I think checked for an unlocked bootloader. But I'm not sure about that.

I hope this helps anybody who may find themselves in a similar situation.
Last edited by Nottach; 17th February 2012 at 07:51 AM.
The Following 12 Users Say Thank You to Nottach For This Useful Post: [ View ]
17th February 2012, 08:09 AM   |  #4  
Junior Member
Flag Elk Grove
Thanks Meter: 3
 
21 posts
Join Date:Joined: Jan 2012
More
For what it is worth, I was able to download the OTA and successfully install it running the 2.3.4 SBF using Motorola's Software Update thing. A data factory reset and clean deletion of my sdcard worked on 2.3.4 . I cannot speak for anyone else nor do I endorse this idea, but it IS possible.
The Following 2 Users Say Thank You to nickvisel For This Useful Post: [ View ]
17th February 2012, 10:47 AM   |  #5  
Pzyduck's Avatar
Senior Member
Flag La Rioja
Thanks Meter: 803
 
396 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by daywalker04

Original Gingerbread SBF 2.3.6 for ATRIX 4G AT&T USA



For AT&T DEVICES ONLY

DO NOT FLASH TO A DEVICE WITH AN UNLOCKED BOOTLOADER. ATTEMPTING TO DO SO MAY RESULT IN A BRICK !!!!

Upgrading to 2.3.6 will more than likely prevent you from downgrading to any previous version of Gingerbread.



Blur_Version.4.5.141.MB860.ATT.en.US


1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz
http://www.fileserve.com/file/vgWHxg...PE_P012.sbf.gz





Compression MD5 - 78CBE2314D76016A12118B30655A3451

SBF MD5 - 0BC556A7FD949317F061E29D88632242

To install this version must have installed the Firmware 2.3.4 Original, if they have unlocked the bootloader, flash back to version 2.3.4 you can install the new update
The Following 2 Users Say Thank You to Pzyduck For This Useful Post: [ View ]
17th February 2012, 11:11 AM   |  #6  
G-Man.'s Avatar
Senior Member
Flag Laramie, WY
Thanks Meter: 268
 
771 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by Pzyduck

To install this version must have installed the Firmware 2.3.4 Original, if they have unlocked the bootloader, flash back to version 2.3.4 you can install the new update

Wrong! I went back to stock and had "failed to boot 4, starting RSD mode" EVERY TIME!!!! Its this update period - its ****... something is effed up in it....
17th February 2012, 12:57 PM   |  #7  
Junior Member
Thanks Meter: 3
 
19 posts
Join Date:Joined: Dec 2006
I tried fruitcake downgrade but not sure it will really help seeing that I removed the ap20bl.img and didn't install the update within the OS. I would think if I posted my venture here it would be double posting so here's the link

http://forum.xda-developers.com/show...8#post22633758

Sorry if I'm not supposed to do that either
17th February 2012, 12:58 PM   |  #8  
Junior Member
Thanks Meter: 2
 
10 posts
Join Date:Joined: Jul 2008
I flashed my MOTOROLA ATRIX 4G AT&T 2.3.4(4.5.91) with unlocked boot with
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.

And not bricked

my SYS/Firmware/fuse/ReservedODM before flashing 10000000000010001000300004000
my SYS/Firmware/fuse/ReservedODM after flashing 10000000000030001000300004000

Do not downgrade 4.5.141 with RSDlite & sbf/
17th February 2012, 01:33 PM   |  #9  
Junior Member
Thanks Meter: 2
 
10 posts
Join Date:Joined: Jul 2008
I flashed my MOTOROLA ATRIX 4G AT&T 2.3.4(4.5.91) with unlocked boot with
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.

And not bricked

my SYS/Firmware/fuse/ReservedODM before flashing 10000000000010001000300004000
my SYS/Firmware/fuse/ReservedODM after flashing 10000000000030001000300004000

Do not downgrade 4.5.141 with RSDlite & sbf/
17th February 2012, 02:36 PM   |  #10  
Junior Member
Thanks Meter: 7
 
28 posts
Join Date:Joined: Feb 2011
I got a different situation. I post it here hopefully it is helpful to some ppl:

My atrix 4g:
Unlocked bl, custom CWM recovery and everything else is stock (4.5.91).

The situation:
Proceed with normal OTA procedure, it will shutdown and flash the update and give a big failure symbol(exclamation mark) after 3 seconds. You should feel lucky, because nothing important is really flashed. Possibly just some initial checks were performed. But if you reboot normally at this time, it will automatically shutdown and try to install the update again.

If you have a situation similar to this, don't panic, here's the quick fix: boot into CWM and format the /cache partition, then reboot normally. Basically this will purge all the downloaded OTA from your phone, and atrix is therefore prevented from automatically installing anything except giving warnings.

The Following 2 Users Say Thank You to DeXtmL For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
4.5.141 ota, 4.5.141 sbf, hardbrick, possible fix, warning
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes