Related
hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt
You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App
You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk
google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition
Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App
mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk
well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.
if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App
Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App
If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App
thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.
i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?
It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App
oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol
Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!
yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.
Welcome to my thread on bootloop fixes for flashing new ROM's through CWM.
I have seen many cases where people will get stuck in a bootloop from flashing a newer 2.3.4 ROM with CWM, and this has also happened to me. Please be aware I made this guide for AT&T Atrix 4G's. I am unaware if this works for international devices.
Click to expand...
Click to collapse
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY GO WRONG WHILE FOLLOWING MY INSTRUCTIONS. YOU SHOULD ALREADY KNOW THERE IS ALWAYS A RISK OF BRICKING YOUR DEVICE WHILE FLASHING.
DO NOT DO THIS IF YOU ARE COMING FROM A 2.3.4 STOCK AT&T OTA UPDATE ROM.
THIS WILL WIPE ALL DATA EXCEPT INTERNAL MEMORY AND THE SD CARD, AND MAKE YOUR PHONE LIKE NEW.
ALSO, BE AWARE THIS IS FOR AT&T, NOT INTERNATIONAL.
Click to expand...
Click to collapse
WHY?:
In almost every bootloop case, it is because the CWM version installed on your atrix is older then what the ROM maker made it for. For example, if you were like me and flashed the HKTW ROM right when it came out with Tenfar's first unlocked CWM recovery, then tried to flash a new ROM such as Kenneth's 2.3.4 AT&T, then you would be stuck in a bootloop. So again, you always need the latest CWM.
Click to expand...
Click to collapse
SOLUTION?:
WINDOWS ONLY:
Prerequisites:
1.2.6 SBF file (the password to extract the file is "atrixbl")
RSD Lite 5.0
Drivers: 32 bit OR 64 bit
INSTUCTIONS:
1. Make sure your phone is turned off
2. Take out your microSD card and SIM card for the flashing process
3. While turning the phone on, hold the Volume Up button until it acknowledges RSD
4. Your device will say “Starting RSD protocol support”
5. Run “RSD Lite” on your computer
6. Press the “. . .” button next to the box labeled “Filename”
7. 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)
8. Plug your device into your computer
9. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
10. Press the “Start” button
11. Be patient while the phone reboots. It will take a long time.
12. OTA update from 1.2.6, all the way to 1.8.3
Download "Rom Manager" from the android market.
13. Click the first option "Flash ClockworkMod Recovery"
14. Select Motorola Atrix 4G.
15. Now you're all set and back in the game. You are safe to flash any new ROMs with this OFFICIAL CWM. And Rom Manager will let you know when a new CWM version is available.
Click to expand...
Click to collapse
IF ANYTHING IS INCORRECT, PLEASE LET ME KNOW. ALSO, IF THESE METHODS DO NOT WORK, LET ME KNOW AND I WILL UPDATE THE GUIDE. WHAT I HAVE POSTED HERE IS BASED ON WHAT WORKED FOR ME, AND EVERYONE I HAVE HELPED.
Click to expand...
Click to collapse
If you would like to donate to me, I will put a link below. What I do with donations is find ROM developers, and see their current work progress, and donate to them. So anything you donate to me, gets donated to future ROM making.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8Q3MSD9KW2GD6
Click to expand...
Click to collapse
Thank you for everyone who has given us ROMs, hacks, mods, you name it. This device is nothing without you guys!
Click to expand...
Click to collapse
Reserved
Sent from my MB860 using XDA Premium App
jbrussee said:
Does this not effect anyone?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
People who are on the ota DO NOT flash back to 1.83 or prior op make this clear please although most will know some noobs wont lol
edit my fault you did, maybe a little bigger? if not its ok at least you have it
Yeah, I made sure I said that.
Sent from my MB860 using XDA Premium App
hi im posting this so I can post in the development section.
LMAO Techno. You got punked on two consecutive threads. Why do you have to be so rude and arrogant? Oh and please follow your own advice.....read before posting any comment.
Sent from my MB860 using XDA App
logantyler said:
hi im posting this so I can post in the development section.
Click to expand...
Click to collapse
+1 This place is way to aggressive with new users.
bootloop
Hi All,
I wanted to add my solution for having my phone stuck in a bootloop and then soft bricking it. My phone did not unlock successfully
1. Download a working version of 1.83
2. Download RSD Lite for your computer
3. When starting phone enter recovery by holding the volume down and pressing the power button, when the recovery option at the top shows up, use the volume down to get to RSD Mode. Volume Up selects.
4. Launch RSD Lite
5. Plug phone into computer using USB and RSD Lite should recognize phone.
6. Select the 1.83 file. Then run it
7. This may take some time, but it will boot your phone back to stock settings.
8. Read directions more carefully next time when you install a custom rom.
Hope this helps someone!
Thanks for more input!
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
Hello, I installed GingerBlur and Now want to upgrade to Gingerbread. I am having some issues with doing an OTA upgrade. I aslo no longer have a PC which I used to root and flash before. Any help would be greatly appreciated.
I believe your instructions are only for AT&T users (judging by the files and OTA numbers).
If so, you should state that so some new International user doesn't try this and hard brick.
Zero-k, thank you for informing me of this.
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
As the title says, After I unlocked the bootloader, and flashed a 2.3.4 rom, My Atrix sometimes will go up to the blur phase of the boot and then it will restart, but most of the time will just do a boot loop on the Red Moto Logo at boot, I can go into fastboot and recovery no problem...
Thanks on any help...
same thing
i get the same thing every now and then but i can get fastboot and recovery so im good i guess.
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
also do a factory reset and make sure your on the newest recovery
quicklyspent said:
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
Click to expand...
Click to collapse
Did the fastboot -w and reinstalled the ROM and it is doing the bootloop the same, first boot goes up to the blur phase and reboots, and afterwards just does the boot loop up to the motorola dual core red logo.
TechnoNeto said:
also do a factory reset and make sure your on the newest recovery
Click to expand...
Click to collapse
I have the latest recovery, thanks...
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
TechnoNeto said:
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Where can I find your guide, and should I SBF 1.83 or what..
It's in general under video how to go... Sorry I'm on my phone
Sent from my MB860 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1179506
Sent from my MB860 using XDA Premium App
Did you make sure to use tenfar's CWM instead of ROM Manager's? My 2.3.4 install also bootlooped, and that ended up being the issue.
Sent from my ATRIX running CherryBlur 1.3.
I'm still having issues, I have the latest Recovery, and I have tried to flash through Recovery and still get the boot loops...
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
poorg said:
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
Click to expand...
Click to collapse
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
mramirezusa said:
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Starting RSD protocol support....
poorg said:
Starting RSD protocol support....
Click to expand...
Click to collapse
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
mramirezusa said:
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for the help, really appreciate this...
poorg said:
Thanks for the help, really appreciate this...
Click to expand...
Click to collapse
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
mramirezusa said:
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
Click to expand...
Click to collapse
Ok, but mine does not say unlocked right now, I did Unlock the bootloader but after I flashed the 1.2.6 SBF it does not say it!!!!
I noticed you posted that you actually have unlocked bootloader just make sure that when you turn on the phone it said in the left top corner "unlocked", if it is not that case just follow intructions on this post:
http://forum.xda-developers.com/showpost.php?p=15930466&postcount=1
download the script and select option 1 from the main menu and then option 3 and complete all the steps
so you can re unlocked the bootloader
then follow the instrucionts that I posted before here
mramirezusa Thank You.... As you stated, everything went smoothly and my phone it's perfect again, something I noticed, when it boots, it's does not say unlocked anymore shoul'd I do the procedure with the the script that you sent posted above...
[MegaUpload][Not signed] http://www.megaupload.com/?d=KZMXFFKN
Be still unsigned, you can`t flash it to a productions phone. only engineering phones are allowed.
[MegaUpload][Signed] http://forum.xda-developers.com/showpost.php?p=15954239&postcount=174
This one can still not be flashed to productions phone.
without signature...so still could not flash it right now?
WongJames said:
without signature...so still could not flash it right now?
Click to expand...
Click to collapse
yes, can only be flashed to engineering devices.
Thank you for your contribution to Milestone2.
I don't see any "[2.3 Leak] complete .sbf of Official GB ROM"
ARE YOU KIDDING OR WHAT?!!!!
not kidding,please be reading my post carefully.
Thank you for bringing it here,uploading it to international file host service is too troubling for me. What I want to point out is that even it's unsigned, we can depack anyway,maybe we can repack a system.img and boot.img.
Or you can try to force flashing or fake your phone as a prototype,neither way is in my reach.
Sent from my ME722 using XDA App
I am sorry, but although I am happy that 2.3 is finally leaking I only see China Retail instead of UK something in the filename. Additionally, what can be achieved with this sbf? Can it be signed afterwards, will it be flashable somehow? Thanks.
In China GB is just short for GuoBiao,mean's national standard for character not the Great Britain.
Sent from my ME722 using XDA App
JunHou said:
In China GB is just short for GuoBiao,mean's national standard for character not the Great Britain.
Sent from my ME722 using XDA App
Click to expand...
Click to collapse
I mean GingerBread here......
can it flash by sbf_flash in Linux? I see the sbf_flash can flash boot.img by "sbf_flash -r -d --boot boot.img"... Is it true?
PS. sorry for my English.
It's time about time MS2 got GB!! Can't wait for the official version.
Will my phone be functional once I flash it since the leak is based in China (I think?) and I'm from US? Functional meaning phone data and calls/texts (phone service). I want to know before I flash!
Thanks.
SedaG said:
Will my phone be functional once I flash it since the leak is based in China (I think?) and I'm from US? Functional meaning phone data and calls/texts (phone service). I want to know before I flash!
Thanks.
Click to expand...
Click to collapse
This ROM is unsigned. And because of that fact, RSD Lite won't let you flash it onto the phone.
frenetico said:
This ROM is unsigned. And because of that fact, RSD Lite won't let you flash it onto the phone.
Click to expand...
Click to collapse
so how do I get it on my phone?
EDIT: It says "cannot be flashed to production phones." If mine is not a production phone can I then flash it? (Is my understanding)
SedaG said:
EDIT: It says "cannot be flashed to production phones." If mine is not a production phone can I then flash it? (Is my understanding)
Click to expand...
Click to collapse
Well, if you got a developer phone you can flash it.
Some others managed to flash another .sbf of the 2.3 leak onto their phones which refused to boot properly.
I have a developers phone, except I think my phone is in a boot loop anyways I just flashed it and I'm not sure if it's just supposed to take this long the first time booting up, bc it took a while in the past. My boot-up image is the same as before and it keeps repeating. I'm gonna wait a little more, pull the battery ( ) if no results and do a hard factory reset with the new .sbf
Did you erase the cache through android recovery?
frenetico said:
Did you erase the cache through android recovery?
Click to expand...
Click to collapse
dammit no. I forgot! ughhh. What can I do? The hard factory reset isn't working. Should I flash my old sbf?
EDIT:
Took forever, pressing the search key doesn't open the android recovery menu anymore.. i basically hit all the keys like an idiot until it popped up. I think it was both volume keys at the same time that did it. I wiped cache and then did a factory reset and it works beautifully.
ONE PROBLEM.
Forgot China had issues with Facebook and Google, so you can't hook up those two accounts.. which is very important to me.. so no Gmail unless you use a 3rd party app from market which I'm looking up now. Don't know if I really like that.
Oh, long story short. I got it
How come you have a developer phone? Yes, try to flash last or working sbf and then wipe cache before updating
Sent from my MotoA953 using XDA App
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Haphim said:
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Click to expand...
Click to collapse
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
msd24200 said:
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Haphim said:
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Click to expand...
Click to collapse
Sbf flashing is dangerous and not recommended
Sent from my MB860 using XDA Premium App
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Sent from my MB860 using XDA App
Dirtburgler said:
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Click to expand...
Click to collapse
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Haphim said:
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Click to expand...
Click to collapse
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
dLo GSR said:
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
Click to expand...
Click to collapse
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Haphim said:
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Click to expand...
Click to collapse
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Sent from my MB860 using XDA App
Nevermind 10char
I could see flashing back to an older build beneficial to a developer but not your everyday user and rom flasher. Both methods will get you to the same place, fruitcake or ota. I know there are benefita doing the ota like partition size and some other tweaks but I'm not 100% what those benefits are.
I jumped in early and got the leaked ota before we knew of the hard brick issue and like I said I'm still rocking the same atrix I bought back in march.
Sent from my MB860 using XDA App
Dirtburgler said:
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Click to expand...
Click to collapse
Thanks! If that's an okay route to take, then that's what I'll do.