I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.
zax10 said:
I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.
Click to expand...
Click to collapse
a) make sure your sbf is good.
b) what version of RSD lite are you using on what OS?
I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App
zax10 said:
I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App
Click to expand...
Click to collapse
You might could try RSD 5.0
Although, I had problems with RSD on my WIN7 Vaio also that I could never get around so I just used an XP to do the job.
I gave up with win7 netbook. Used my XP desktop and it started and finished perfectly.
Sent from my X10i TripNMiUI using XDA Premium App
I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx
ctcost said:
I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx
Click to expand...
Click to collapse
re-download the sbf in the other thread and re-flash it. it probably flashed wrong in some minor way that is messing something up.
Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/
ctcost said:
Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/
Click to expand...
Click to collapse
There is no 2.1 .sbf so if the 2.2 .sbf isn't working then something is wrong. If you can, do a factory data reset and reboot and then try to flash the 2.2 .sbf. see if that works.
Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.
Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.
ctcost said:
Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.
Click to expand...
Click to collapse
Awesome! Good to hear. Glad I could help.
ctcost said:
Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.
Click to expand...
Click to collapse
HELP! I meet the same problem! How can you resolve it? Please help me!
OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.
dontbejeff said:
OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.
Click to expand...
Click to collapse
Did this end up working for you?
Yes it did. I am back using CM7 on my Bravo
Sent from my MB525 using XDA App
The posts relating to pushing the corner of the screen relate to Eclair, 2.1, recovery menu. Froyo, 2.2 ^ is pushing both Vol ^ and v.
Related
So I was told to install the deodexed [sp] of the GB leak, so I did on top of my rooted, non deodexed version, without wiping. After this I wiped my data a few times, as I heard it would be best to do. Well, after doing so... my phone won't stop bootlooping. I can't access the bootstrapped bootloader, only the stock Moterola one, and I cleared my data with it hoping it would work too...
Help please? How do I "sbf" back to stock or whatever?
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
I hope its ok to post this link here:
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
tried flashing it again, same thing happened. It failed at "switching phone to BP pass through" apparently. help me please
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Now just do the system only sbf.it will work
Sent from my DROIDX using XDA App
Do you have the latest drivers installed? Try using RSDlite 4.9!
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
z06mike said:
Do you have the latest drivers installed? Try using RSDlite 4.9!
Click to expand...
Click to collapse
i found rsdlite 4.9 didnt recognize my phone but 4.8 did
itzjen said:
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
Click to expand...
Click to collapse
Like what did you say to them?
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
this is totally being lazy AND the reason why everyone is raising their prices on insurance and why ppl like motorola are locking bootloaders. if it is too much or you're too lazy to do it. dont do it in the first place. sbf isnt hard there are a gazillion guides to sbf'ing. not trying to be rude but seriously?
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
thewanton said:
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
Click to expand...
Click to collapse
you have to sbf to .340 use z4 root to root then install DX bootstraper reboot to recovery flash gbrooted.zip if you get stuck in bootloop go into factory recovery and wipe data reboot download and install D2 bootstrapper yes D2, boot into recovery and flash gbrooteddeodexed.zip and let it try and boot it SHOULD bootup after a couple of minutes, if it doesnt get into stock recovery and wipe data, reboot
also it could bootloop because of corrupt downloads
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
itzjen said:
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
Click to expand...
Click to collapse
which is a problem that was caused by YOU because you take that and sbf
thewanton said:
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
Click to expand...
Click to collapse
most ppl overlook that as a typo
Funnyface19 said:
which is a problem that was caused by YOU because you take that and sbf
Click to expand...
Click to collapse
Yes it was a problem that I caused but at that momment I got scared and wasn't sure what I was suppose to do,and because I have no internet at home because i'm never home I use wireless tether when im there and my phone was messed up so wasn't able to look at guides to fix it.....So the easiest thing I thought of is calling them.I wouldn't have mind fixing it but again I wasn't able to at that momment.
I had the same thing happen. Put the letter p at the end of the file name and move it to c:\ this worked for me on rsd lite 4.8 I just kept pulling the battery and retrying until it went through
Sent from my Xoom using XDA Premium App
meshdub said:
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
Click to expand...
Click to collapse
I'd just like to point out that you don't actually need rsd lite 4.8 or higher. 4.7 has worked perfectly for me the several times I have SBF'ed
I've been through the forums all day trying to recover my Atrix. I'm now creating a post to see if I can get some fresh ideas. The LED just flashing red and the USB Enumeration says: Cold-booting Linux Reading ODM fuse: 1.
Any help would be great. The phone doesn't get past the Motorola Dual Core screen. Thanks!
Weese said:
I've been through the forums all day trying to recover my Atrix. I'm now creating a post to see if I can get some fresh ideas. The LED just flashing red and the USB Enumeration says: Cold-booting Linux Reading ODM fuse: 1.
Any help would be great. The phone doesn't get past the Motorola Dual Core screen. Thanks!
Click to expand...
Click to collapse
Try booting into RSD mode and flash back to 4.1.26.
Should find what you need here:
[Guide]Motorola Atrix Complete AT&T Rooting and Flashing Guide
CaelanT said:
Try booting into RSD mode and flash back to 4.1.26.
Should find what you need here:
[Guide]Motorola Atrix Complete AT&T Rooting and Flashing Guide
Click to expand...
Click to collapse
Thanks for the reply!! I will download the SBF and try that. I had one downloaded but it wouldn't work. I will try this one and report back.
RSD fails the flashing process. Are there any details I can post that will help?
Weese said:
RSD fails the flashing process. Are there any details I can post that will help?
Click to expand...
Click to collapse
Which version of RSD Lite?
Sent from WinBorg 4G using XDA Premium App
It's 5.0. I tried a different computer as per something I read. It finished however it's still just blinking the red light at me.
What were u doing when it hit the fan?
Sent from my MB860 using XDA App
If all fails...try and get your phone replaced under warranty (Don't tell them you did ANYTHING...just tell them you turned it off before you went to bed and when you turned it back on in the morning it did this) this kind of thing has worked for me before.. good luck
dubyajaysmith said:
What were u doing when it hit the fan?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Nothing strange at all. I was replying to texts from last night. Put it in my pocket and next time I pulled it out it had rebooted.
roharia said:
If all fails...try and get your phone replaced under warranty (Don't tell them you did ANYTHING...just tell them you turned it off before you went to bed and when you turned it back on in the morning it did this) this kind of thing has worked for me before.. good luck
Click to expand...
Click to collapse
They are sending me a replacement but it's going to be a few days. Plus I hate letting technology get the best of me.
Just be careful with the next one good luck man
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me
Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL
That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.
try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App
Hey guys so i mistakenly updated to 2.3.3 the other day and really didn't like it so I rooted my phone, and was about to flash Miui when I changed my mind and tried to Deodex my phone, because i had already rooted the phone I tried to do the manual deodex shown in the "noobs guide post" i did everything according the the instructions but it didn't work. So I grabbed the SHADO_X6_2.3.34_SYSTEM-ONLY.SBF file and loaded it in RSD lite to flash back and un-root my phone.. well half way into the process the phone rebooted to the Red M logo.. and everything I've done since has been to no avail.. i tried to download other SBF files that were supposed to be the "full" sbf but for some reason RSD lite wont even let me flash them... If i boot holdig the menu button the phone will bring up the recovery menu and from there i can still select the 4 different options but even after doing the factory data reset and formatting the catch nothing seems to change.. I have been looking for several hours now to get this working and I'm getting really frustrated. So i just want to apologist if this situation has already been dealt with but if you guys could help me out to get my phone working again i would be incredibly great full.
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
STAYFROSTY777 said:
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think I read something about the but havn't been able to find where to get the linux iso, am i correct in saying you can temporarily boot linux from the disk to do this? BTW Thank for the sugestion, my wife was about to make me sleep in the dog house for messing my phone up lol so when i get off work i'll try to find the Linux iso, maybe i can even find a thred that has a walk through to fix it.
In the event that I do get everything working again, is it easier to flash roms from gingerbread or from Froyo? or if you want a gingerbread rom i'm assuming you have to flash it from gingerbread correct?
Yes your correct about the roms from my understanding, and haha I know the feeling, yeah just burn the iso onto a disc (its not very big) on boot from disc on your computer, follow the instructions, and it will sbf you to froyo, probably be doing this for me tomorrow since in have some problems with tethering, good luck man, let me know how it goes
Sent from my DROIDX using XDA App
sweet I'll be happy to have my phone back.. lol i miss it, i feel lost without it to be honest. I never knew how attachedi was to my phone. but anyway I'll forsure let you know how it goes i'm praying that this will fix my phone, I have never really come accross a true definition of how to tell if your phone is "bricked" or not. it seems like everyone says their phone is bricked just because they cant get it to boot up but i always thought that the term "bricked" refered to the phone being so screwed up that you can no longer fix or salvage it.. does anyone know the actual definition?
I was recomended to look at this web page it was incredabley helpfull!! i'm running throught the process right now so i'll report my results when done but i'm pretty optimistic about this.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
Awesome man, i used that method, might be doing again after work today to change roms
Sent from my DROIDX using XDA App
yeah i was so happy that it worked although i was still worried at first because the phone still boots to the Red M logo but after a sec it goes the the droid eye and then load GB anyway now i just need to really understand how to deodex and flash a rom right way, but at least now i know how to fix the phone if i screw something up. One more question, would you guys say that my phone was considered bricked? if so than is it safe to say that there is nothing you can do to it that you can't fix using the Linux boot SBF method?
btw the actual page i used with all the downloads of Linux is right here in case anyone else needs it.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
It doesn't sound like it was bricked, and so for I haven't seen anything to bad where you can just use the Linux way, unless you mess up the hardware lol
well thats somewhat good to know lol thanks for all the advice
Anytime buddy, always glad to help
Sent from my DROIDX using XDA App
The reason why the first sbf didn't work is because you used a SYSTEM only Sbf and it was for froyo 2.3.340 instead of the FULL sbf which reverts everything back to froyo instead of just the system.
Sent from my DROIDX using XDA App
hmm so how is the system only sbf any different than doing a factory reset while running 2.3.340? i mean does doing the system only sbf undo rooting your phone?
So here is what happened. I made a backup of a stock atrix firmware and copied the backup to my atrix on deodexed 2.3.4. I tried to install the backup but it stops somewhere along the line and says error formatting data.
now the phone wont connect to the computer. when i opened rsdlite however it shows that the device is connected.the phone bootloops and I cant copy anything to the phone cause i cant connect to the phone except through rsd sorry if i posted in the wrong section cause this is the only one i can post in. and i searched for solutions but no one has this same problem. PLEASE HELP
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
ltdanno360 said:
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
Click to expand...
Click to collapse
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Did u do factory reset after the flash
Sent from my MB860 using xda premium
My atrix wont even boot to the RSD etc selection screen
So i had my phone rooted and wanted to unlock the bootloader so i followed the steps from pudding but it did not work. everyone has a NS version of the phone in RSD Lite but mine was SE not sure why. So i tried a few times to flash the new image and clear everything out to no avail. now i don't even get to the menu that gives me 5 seconds to select what method i want to use to fix it.
all i get is a flash of this on the screen before it goes black again
SVF:105:1:2
Failed to boot 0x1000
(stays for a second)
Entering NWFlash Recovery Mode
(Flashes under the other text but really fast before the screen goes blank)
windows wont even recognize that its plugged in. but what else is odd is that while plugged in it seems to be charging as the green notification light stays on.
any help would be great. thank you
voidlogik said:
Failed to boot 0x1000
Click to expand...
Click to collapse
isnt that a hard brick? it's over.
sanriver12 said:
isnt that a hard brick? it's over.
Click to expand...
Click to collapse
really?? no way to unbrick it?
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Bootloops means soft bricks which is not really a problem. When your phone Boots up, press the down key along worth the power button. Then keep pressing down button until you see Android Recovery. Do a factory reset or flash another room once in there.
Sent from my MB860 using XDA App
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1165154
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
Sounds like a hard brick indeed. At this moment in time hard bricks are incurable but some people said that taking their battery out and putting it back into their phones solved their problem. You might want to give it a shot.
A guy also claimed thay its possible to unhardbrick your phone using the jtag technique. You might want to read up on it.
Sent from my MB860 using XDA App
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
ltdanno360 said:
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
English plz.
Sent from my MB860 using Tapatalk
me too
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
I'd recommend starting a new thread w/ your issue. It's more likely to be seen and answered by someone who could help.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
If you're on AT&T - get RSD lite and find the proper sbf file and flash it. If you were using Gingerbread, make SURE you have a GINGERBREAD sbf file - or else you'll permanently brick your phone. If you're on Bell - you'll need the appropriate file for Bell to flash, same rules apply - If your on gingerbread, make SURE its a gingerbread file you're flashing.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
you need to have an unlocked bootloader to flash Any custom rom PM me ill show ya how its not too hard
a pc a atrix and a few files and you will
be up n running in no time at all
Sent from my MB860 using Tapatalk