Related
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
jojojohnson7410 said:
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
Click to expand...
Click to collapse
The link in your post points to the official OTA.
It contains the new bootloader as a part of the payload.
This bootloader will make it impossible to go back to 1.8.3 SBF (or any other SBF) without the risk of hard brick.
For your safety, use Fruit Cakes or any of the ROMs floating around.
Stay away from official OTA or anything that does not have the new bootloader disarmed (or removed).
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
lol sorry forgot to mention the fruitcake part X_X made so many posts in the past hour or so, I tend to leave out information I've repeated over a lot of times. I honestly don't have a problem with the OTA (minus the fingerprint, but i think that's with everyone), so that is another viable method. So long as he stays away from SBF (which we technically should anyways) and sticks with eating his Fruitcake, I don't see what's the big deal =]
That's just my two cents on that matter. However, feisty_noodles is probably right about flashing ROMs, as they are usually well tested and don't blow the Odmfuse like the new bootloader does when you unlock with it. It's really your choice, but I preferred having an OTA (until my ROM-itis kicks back in >.>), so I just gave you the method I used.
Good luck!
~jojojohnson7410~
feisty_noodle said:
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
Click to expand...
Click to collapse
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
jojojohnson7410 said:
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
Click to expand...
Click to collapse
There is nothing wrong with fastboot images. I am running a stock from system.img (from Ken's archive) at the moment.
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
thanks you all....
i will decide today what to do.
mramirezusa said:
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Continuing on with the list--options that do not mess with the bootloader:
4) Flash the .img files from Ken found here plus the CWM-flashable radio
5) Fruit cakes!!!
With the recent explosion of information, I'm getting a little confused on what steps I need to take (areas to read about) in regards to getting a custom ROM.
I sit on the last version of gingerblur.
Can anyone point me to what I need to do next/Where I should read? I'm getting things confused as there seem to be different ways to go about this, with different results. Many thanks in advance.
Ditto.
I stayed stock 1.83 and downloaded latest update, from what I read ... I can no longer unlock bootloader. Would be nice to see Ken P post another n00b guide like he did with gingerblur.
Sent from my MB860 using XDA App
No it IS possible to unlock using 2.3 OTA as a base.
However you will soft-brick it, then have to recover. It is a bit heartstopping.
I agree the info is a bit of a mess however its basically this method with a DIFFERENT PUDDING FILE (make sure you grab the one marked for AT&T 2.3 OTA).
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
As for the softbrick, more details in this thread
http://forum.xda-developers.com/showthread.php?t=1182871
I'm not an expert but hope above helps. FWIW yeah I used the script
These are useful posts bro. Thanks
Sent from my MB860 using XDA App
no worries. Just DON'T PANIC when it softbricks, and immediately (before the 5 second timeout) put it into fastboot mode, then keep going with fastboot oem unlock process seems to do the trick.
At least thats what the script seemed to do. Perhaps start a new topic to clarify with someone who did 2.3OTA unlock manually to confirm.
If I flash back to stock from Gingerblur, is it preferable to go to a certain version? Should I just use 1.8.3?
And does it matter if you use Service or Full? The only thing I can find is that "Full erases all your data and service does not." I assumed that flashing back to stock would erase everything regardless.
i will admit it def. is heart stopping to softbrick, but like he said just proceed with the fastboot unlock
I unlocked 2 days ago from OTA 2.3.4 using the full 4.5.91 sbf that includes pudding and preinstall root. I flashed the sbf using rsd 5.3.1 and then got a soft brick 0x1000 no os installed. I freaked out for a moment but after running the fastboot unlock commands the phone booted up and everything was smooth sailing from there out. Good luck!
Sent from my MB860 using XDA App
Hey
If you are still on the 1.83 version, then I recommend this way:
1) Unlock your bootloader.
2) Install CWM.
3) Flash any 2.3.4 custom rom you desire.
Thats what I did 4 days ago, and everything went smooth, without any soft bricks, of heart failure.
I used this great tool:
http://forum.xda-developers.com/showthread.php?t=1182871
But, you can do it however you desire.
Hope it helped
scarpachi said:
If I flash back to stock from Gingerblur, is it preferable to go to a certain version? Should I just use 1.8.3?
And does it matter if you use Service or Full? The only thing I can find is that "Full erases all your data and service does not." I assumed that flashing back to stock would erase everything regardless.
Click to expand...
Click to collapse
Can anyone provide advice on these questions? The first commenter seems to be getting all the comments/advice.
I am on latest Gingerblur, and its my understanding that I need to get back to stock first.
scar I believe thats the case. In either event it couldn't possibly hurt. All the guides and testing has been done using one of the stock variants as base. I wouldn't even attempt it using gingerblur myself
Was able to flash back to full1.83, unlock bootloader, root and add rom. Aside from my mistake of picking wrong recovery the first time (and bootlooping) everything went smooth.
Sent from my MB860 using XDA App
ROM newbie here, but I wanted to know how the pros figure out which ROMs they can safely install.
Over on the development board, I see all sorts of references to hard bricking phones as a result of installing the wrong ROM.
I'd really like to update my rooted/gingerblur'd (I believe, how can I check?) phone to Gingerbread.
Thanks for any tips y'all can give me!
Start here : http://forum.xda-developers.com/showthread.php?t=1154600
For the rom safety installs ... just read the all information about the rom and understand what you need to have and if it fits to your phone.
Its rare a rom bricks a phone. Hard brick that is. Its the pre rom stuff required that's gets people into trouble. Soft bricks usually have an easy escape route. Its the panic and the omg I bricked my phone because I didn't read the instructions threads that confuses people.
Sent from the coolest voided warranty phone ever.
the only way you'll hard brick a phone is if you use RSDlite to flash an SBF file.
Specifically, if you did the OTA gingerbread upgrade, then flash a pre-gingerbread SBF.
If you do everything through clockwork recovery, then you'll be able to recover in one way or another.
Have you unlocked your bootloader? If not I recommend doing so, check the pudding thread, unfortunately this does involve using an SBF file (no other way I believe?). But thats just once, after you unlock, flash recovery via moto-fastboot, then do everything through moto-fastboot or recovery, 0% chance of bricking. After you unlock your bootloader its pretty straightforwards.
Roms don't usually brick phones. Most ppl tend to brick by messing up on rooting/unlocking.
I used the Automatic Root/Unlocker/CWM installer (http://forum.xda-developers.com/showthread.php?t=1182871) to do the setup and it all went fine.
Ok so i don't know what happen but my phone now says Failed to Boot 4 Starting RSD Mode
What i want to know if i use the SBF for 1.2.6 will it brick my phone ? I see people saying just use that one and then upgrade after that, but i do not want to take the chance of bricking my phone.
So i hope somebody can help
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
pukemon said:
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
Click to expand...
Click to collapse
Well the problem is i did try fastboot and when i did that it still did not work and it also REMOVED fastboot..... so now i dont have that as a option
I found this http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I
and it says im safe to do that one beings it was the same as what i had on my phone before this happended, but im just not sure
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
pukemon said:
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
Click to expand...
Click to collapse
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Well, read, reread and try to find a couple of threads or better yet experienced members that can help. I try to avoid situations that can possibly get you in a predicament like this.
I voided my warranty.
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have EVER flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Tao_Man said:
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have ever flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Click to expand...
Click to collapse
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
RivKristopher said:
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
Click to expand...
Click to collapse
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Phalanx7621 said:
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
How are fruitcakes loaded through RSD Lite as well ?
Fruitcakes are not .sbf files because they do not need to be. They don't contain the amount of data a .SBF would, usually just system and necessary files. They are flashed with CWM *clockwork recovery mod*, as a .zip file. This makes it a ton easier and the chances of hard bricking your phone are almost zilch. CWM for unlocked bootloaders can be found here http://forum.xda-developers.com/showthread.php?t=1204500
fruitcake is cwm, so if you can not get cwm/recovery to work your only option it seems is to flash the offical 2.3.4 sbf and ONLY the 2.3.4 one, do not use an older version.
once you flash 2.3.4 then you should then be able to get your phone opened up again and get cwm working again, and be ok going forward, but never go back older then 2.3.4.
There are hacked sbf files for safe versions of 1.8.3 but I see no reason to go back to 1.8.3 if you are not going to follow the normal upgrade path anyway.
RivKristopher said:
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Click to expand...
Click to collapse
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Sent from my MB860 using XDA App
Sass86 said:
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Click to expand...
Click to collapse
^ this. Always the possibility. Kinda the risk we all take when joining and being a part of this community. I actually got mine soft bricked at one point, and thank God I was able to recover. Good luck in all you do, keep the gravy train rollin'
I bricked one Atrix already a few weeks ago, and have since gotten another...(don't wanna think about it)..
I had toyed with unlocking it, and 'rooted' using the gingerbreak method. I was then, bored, one day and installed CWM paid version(Since I had it on my Nexus One, and it popped up under 'my apps'). Out of curiosity I installed the bootloader via CWM, thinking it would fail before it broke anything..wrong.. It froze after a reboot, but after taking the battery out and back in came back up. Didn't think any more about it, and figured i'd finish the unlocking/flashing part some other time..
Meanwhile the annoying pending system update kept going off, and I inadvertently clicked download... it downloaded, so I figured might as well install and not worry about roms since with root I was able to use the google adhoc wifi apk, which is what I care about most. The install was stuck in an infinite loop. It would 'fail to load RSD', if you took the battery out it boot to android then reboot automatically for system update over and over. I tried using the RSD lite program at this point to flash back to stock rom, and ended up hard bricked...
So, forgive me for being a complete noob as I never had an issue with my nexus one. I am at 4.1.83, android 2.2.2. and baseband 1.7.15.. Which of the many tutorials and post should I follow? How safe are they? Did I brick because I had a partial 2.3.x install, and flashed back to a pre 2.3 base? I've read many post, but definitely a bit gun shy of bricking another Atrix. The phone keeps bugging me to update, and I keep hitting 'cancel'.
I'd like to unlock the boot loader for custom roms.
I'm also a heavy linux user, majority of tutorials seem to only imply windows with RSD lite? can this not be done with adb, and fastboot via linux?
http://forum.xda-developers.com/showthread.php?t=1154600
I would personally go HERE Read through the entire post, then read it again. And go with the ATT 2.3.4 pudding+root
That of course is after reading and re-reading THIS post! (also linked in the post above mine.
Just my opinion.. and make sure you read and nkow what to expect!
xploited said:
http://forum.xda-developers.com/showthread.php?t=1154600
Click to expand...
Click to collapse
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
jmorgan6 said:
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
Click to expand...
Click to collapse
Nope, don't update. It's safer to unlock BL while you are still at 4.1.83, you just need to download the correct unlock file from the pudding thread.
Otherwise the unlocking steps are exactly the same.
The easiest steps to unlocking are here:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
From there you can flash CWM in one minute.
From there you can flash any rom via CWM in two minutes.
Good luck and don't do anything stupid.