i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore
odystyle said:
i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore
Click to expand...
Click to collapse
Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf
odystyle said:
what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf
Click to expand...
Click to collapse
I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).
Sent from my MB860 using xda app-developers app
palmbeach05 said:
I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1
odystyle said:
so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1
Click to expand...
Click to collapse
It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.
I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel
Sent from my MB860 using xda app-developers app
palmbeach05 said:
It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.
I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol
odystyle said:
coz people say it will brick your phone if you flash a full sbf
Click to expand...
Click to collapse
No they don't. Nobody said that. You will only brick the phone if you flash a wrong SBF. What you have (apparent relocking) is perfectly normal and expected and discussed before.
odystyle said:
ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol
Click to expand...
Click to collapse
Odd, might be a device issue.
Install steps should be like this
-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy
Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Odd, might be a device issue.
Install steps should be like this
-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy
Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom
odystyle said:
but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom
Click to expand...
Click to collapse
Ok, well thats good. Which rom are you trying to use right now? Are you trying to use it with the old kernel or the new kernel?
Sent from my MB860 using xda app-developers app
right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work
Sent from my MB860 using xda app-developers app
odystyle said:
right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Ok. I was able to get that to work for me. I wiped it down, flashed the rom, then rebooted and flashed gapps. Odd that its not working for you.
Sent from my MB860 using xda app-developers app
yeah....well its only me stay on GB forever
Sent from my MB860 using xda app-developers app
odystyle said:
yeah....well its only me stay on GB forever
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Did you try installing some other non GB rom but with old kernel?
Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?
Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:
delete
krystianp said:
Did you try installing some other non GB rom but with old kernel?
Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?
Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:
Click to expand...
Click to collapse
1.after i unlock my phone i only use MROM 7 AND MROM ICS with leaked kernel
2.when i try to get the new cm9 with 3.1 kernel. i put the rom,gapps and facelock on internel memory i didnt use memory card coz before flashing i always read instruction before flashing just to be clear what im doing.
3.phone info
memory type HYNIX
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR5: 0x0006 (0x0606)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR6: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR7: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR8: 0x0054 (0x5454)
Panel size
[ 0.000000] parse_tag_motorola: panel_size: 80000740
Sdcard present
16GB class 10
Atag revision
<4>[ 0.000000] mot_fixup: atag_revision=83f0
Tegrapart
tegrapart=mbr:d00:100:800,kpanic:2100:400:800
Related
So,just got my atrix and it is already on 1.8.3. Does that mean I should go ahead,unlock bootloader,root,flash cwm, then 2.3.4?
Sent from my MB860 using XDA Premium App
I definitely would recommend rooting it and installing Cupcake. I just got a MyTouch 4G a couple of weeks ago and I can't wait to root it (I just haven't had time yet). I'm so sick of all the crap that T-Mobile put on it. In addition, I think that's the key to getting better battery life out of it (though this is my first Android device so I'm not sure about that yet).
You can it all depends on what you want i wouldnt unlock it unless you are more
than just a normal user or it really wont mean much to you unless you like flashing.
Xenocyde said:
You can it all depends on what you want i wouldnt unlock it unless you are more
than just a normal user or it really wont mean much to you unless you like flashing.
Click to expand...
Click to collapse
Im way more than a normal user lol. And plus I want the newer moto launched. So,its safe to proceed with that proccess?
Sent from my MB860 using XDA Premium App
Yes , prior to doing ANY thing I would reflash 1.2.6 ota to 1.8.3
Then RSD pudding ( unlock for atrix )
Then install CWM ( Clock work mod )
then install Kenneth Beta #4 rom for gingerbread with is a stock rom with
root and a dedoxed system ( faster ).
Now I have seen some pple that had issues with using RSD , And Fastboot
its simple just read ,read and read.
post if you need helping installing anything i will see if i can type you though it
There are two fastboots use the right fastboot for the right files
one is for bigger files which is moto-fastboot and
the other is for smaller files which is fastboot.
ONLY use RSD for a RADIO AND OR The pudding file
once you have CWM please use it.
READ WARNINGS ON USING RSD.
Links
UNLOCK
http://forum.xda-developers.com/showthread.php?t=1136261
CWM
http://forum.xda-developers.com/showthread.php?t=1138541
Gingerbread by kenneth
http://forum.xda-developers.com/showthread.php?t=1159385
Xenocyde said:
Yes , prior to doing ANY thing I would reflash 1.2.6 ota to 1.8.3
Then RSD pudding ( unlock for atrix )
Then install CWM ( Clock work mod )
then install Kenneth Beta #4 rom for gingerbread with is a stock rom with
root and a dedoxed system ( faster ).
Now I have seen some pple that had issues with using RSD , And Fastboot
its simple just read ,read and read.
post if you need helping installing anything i will see if i can type you though it
Click to expand...
Click to collapse
Im already on 1.8.3 though
Sent from my MB860 using XDA Premium App
You can still flash the unlock now but I like to be safe and start out on a FRESH
start so you dont start having issues.
Sometimes NOT always you get small problems because of a past OS
that had stuff on it. FLashing back to the start and starting over insures you wont
have issues ( at lease you you can prevent )
Try flashing the unlock and then cwm then the new build it may work but
if you are having issues with something you may have to go though the whole
process again trying to save you a head ake.
you ask around or even look around alot safer starting from a fresh start
p.s. I am warning you because of my issues i had we live and learn sharing the smarts!
Xenocyde said:
You can still flash the unlock now but I like to be safe and start out on a FRESH
start so you dont start having issues.
Sometimes NOT always you get small problems because of a past OS
that had stuff on it. FLashing back to the start and starting over insures you wont
have issues ( at lease you you can prevent )
Try flashing the unlock and then cwm then the new build it may work but
if you are having issues with something you may have to go though the whole
process again trying to save you a head ake.
you ask around or even look around alot safer starting from a fresh start
p.s. I am warning you because of my issues i had we live and learn sharing the smarts!
Click to expand...
Click to collapse
Lol ok ill start fresh. But can you give me a link to unlock the bootloader? Ive seen too many threads on it
Sent from my MB860 using XDA Premium App
Just be safe and don't use sbf's after the unlock and stick with fruitcakes (posted in the dev section)
Sent from my MB860 using Tapatalk
BBock9 said:
Just be safe and don't use sbf's after the unlock and stick with fruitcakes (posted in the dev section)
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yes good advise dont use RSD after gingerbread unless installing a radio
And I did give you a link to all three
look in post above bud. but just for you!
Links
UNLOCK
http://forum.xda-developers.com/show....php?t=1136261
CWM
http://forum.xda-developers.com/show....php?t=1138541
Gingerbread by kenneth
http://forum.xda-developers.com/show....php?t=1159385
OK so I'm stuck on some messed up 2.3.4 build. How can I get back to, 1.8.3 safely?
Sent from my MB860 using XDA Premium App
Use cwm and flash a fruitcake to it check in dev section. They have a 1.8.3 flushable zip that is safe.
Again read read and reread before flashing anything
Sent from my MB860 using XDA Premium App
Hi guys;
I want to update my Atrix, but I don't know what path to take?
a) Through the OTA 4.5.91...
b) Unlocking the bootloader, and then upgrading to GingerBread via Custom Roms...
I really need your help, because I am a newby in this whole area...
Right now I am runnig:
4.1.57 ATT
Android Version: 2.2.1
Build Number: GingerBlur 2.5
Your still on 57?
Sent from my MB860 using XDA App
yeah I am on 4.1.57
Why don't you at least update to 1.83. We've ben on .83 for months now.
Sent from my MB860 using XDA App
And what then?
artemalek said:
And what then?
Click to expand...
Click to collapse
Depends what you want to do with your phone. If you like testing out custom roms and stuff then go the way of unlocking the bootloader and flashing one of the custom GB roms. If you want a stock phone with some minor root modifications then flash ota and root. Just beaware if you do the ota build you cannot flash back to froyo (not sure why anyone would but just to warn you)
Sent from my MB860
can you refeer me to the posts where I can unlock the BL and then install a custom Rom
Yeah I am on 4.1.83 and Android 2.2.2.
I want to upgrade as well. Everything is stock currently.
I want to be able to do Cynogen later so I think I need to unlock and flash a custom rom.
So I am like the op and need to know where to go. There is so much argument and misinformation on this forum my head hurts. Just read for an hour and am more confused.
All I know is i dont want to do the OTA update lol!
HOwever I downloaded it already and my phone keeps asking me to install it...
DOes anyone know how to remove that?
Well, first, I suggest you do NOT flash the OTA update.
I recommend that you use the Pudding file in the Development sub-forum to unlock your device. There are video and text guides floating around how to unlock.
If you're not wanting to try out any ROMs yet, I suggest Kenneth's ROM. It's the OTA update, except without the risk of hard bricking if you ever need to flash down.
If you are all feeling adventurous, you could flash an Overclock kernel (I recommend Faux's 1.1GHz OC). You can also flash Ninja ROM v0.4.5. It's super fast.
@mercilus if you freeze the FOTA app in Titanium Backup, I think that stops it.
Here's the guide: http://forum.xda-developers.com/show....php?t=1167373
@artemalek I see that you're on 1.5.7, that means you have an AT&T branded device. You'll need to flash the AT&T version of Pudding for your unlock.
Sinful Animosity said:
Well, first, I suggest you do NOT flash the OTA update.
I recommend that you use the Pudding file in the Development sub-forum to unlock your device. There are video and text guides floating around how to unlock.
If you're not wanting to try out any ROMs yet, I suggest Kenneth's ROM. It's the OTA update, except without the risk of hard bricking if you ever need to flash down.
If you are all feeling adventurous, you could flash an Overclock kernel (I recommend Faux's 1.1GHz OC). You can also flash Ninja ROM v0.4.5. It's super fast.
@mercilus if you freeze the FOTA app in Titanium Backup, I think that stops it.
Here's the guide: http://forum.xda-developers.com/show....php?t=1167373
@artemalek I see that you're on 1.5.7, that means you have an AT&T branded device. You'll need to flash the AT&T version of Pudding for your unlock.
Click to expand...
Click to collapse
Your link seems to be broken. Thanks for the recommendations on roms!
@Sinful
I have it rooted... Can you give me step by step guide! Do I need first to upgrade to 4.1.83 or I can do it from 4.1.57???
mercilus said:
Your link seems to be broken. Thanks for the recommendations on roms!
Click to expand...
Click to collapse
D'oh! Will fix that immediately! Thanks for that!
artemalek said:
@Sinful
I have it rooted... Can you give me step by step guide! Do I need first to upgrade to 4.1.83 or I can do it from 4.1.57???
Click to expand...
Click to collapse
Here's a video: http://www.youtube.com/watch?v=H02N4p9vEg0
Here's a text guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
It doesn't matter about the Firmware version. The guy in the video is on 1.5.7 and unlocks it.
Sinful Animosity said:
Here's a video: http://www.youtube.com/watch?v=H02N4p9vEg0
Here's a text guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
It doesn't matter about the Firmware version. The guy in the video is on 1.5.7 and unlocks it.
Click to expand...
Click to collapse
On the text version, the directions say "RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]"
Im on 2.2.2 so that means I should use sbf flash instead of rsd?
mercilus said:
On the text version, the directions say "RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]"
Im on 2.2.2 so that means I should use sbf flash instead of rsd?
Click to expand...
Click to collapse
RSD is fine. I think sbf flash is for Linux.
Sent from my MB860 using XDA Premium App
Sinful Animosity said:
RSD is fine. I think sbf flash is for Linux.
Click to expand...
Click to collapse
I just followed the directions and RSD said it failed and gave me an error. I accidently hit show phone and it erased the error message but it was something about error at restarting.
Now my phone wont turn on? When I hit the power button/hold it all I get is blank screen.
It doesnt try to turn on or anything?
Did i mess up the phone permanently? crap... just what i was trying to avoid..
any advice?
How full was your battery? And if your phone was hard bricked, you'd be seeing an error.
Sent from my MB860 using XDA Premium App
Sinful Animosity said:
How full was your battery? And if your phone was hard bricked, you'd be seeing an error.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Battery was at like 80% when I last looked. So it was more when I started, and I did not leave the phone watched the whole process up til the point where it wont turn on anymore. So I doubt it lost all that battery in that brief 5 minute time.
Its been plugged in since still and no response from power button.
Everything was completely stock when I started.
Update: I just noticed when I take out my battery and plug in the charger I do get a green light as long as battery is out. When I put it in and plug in I get no lights. Not sure if thats helpful or means anything... (Just noticed its only with the USB charger I get the green light and not AC charger. The battery must be out)
so I'm running 2.2 and want to upgrade to a rom running 2.3.4 but idk how to flash it. i know MIUI had a weird 2 odin method, but this is a normal rom and idk if i can jus flash over Froyo
lbroskee said:
so I'm running 2.2 and want to upgrade to a rom running 2.3.4 but idk how to flash it. i know MIUI had a weird 2 odin method, but this is a normal rom and idk if i can jus flash over Froyo
Click to expand...
Click to collapse
if you have the GB bootloaders just flash over like a normal rom
if you dont have the bootloaders use an odin version of the rom you want to flash then flash updates with rom manager
so to odin it, i dud need my exact rom and then the GB boot loaders as the PDA?
lbroskee said:
so to odin it, i dud need my exact rom and then the GB boot loaders as the PDA?
Click to expand...
Click to collapse
might not need the bootloaders to odin it but you cant see recovery without the bootloaders but with the odin files voodoo sometimes messes up and you need to go to recovery to disable it so you'll need the bootloaders
just flash the bootloades with odin and flash the rom over whatever you're on, probably the easiest way
the GB bootloaders sits at setup connection and never starts
lbroskee said:
the GB bootloaders sits at setup connection and never starts
Click to expand...
Click to collapse
If you haven't done this..... Right click on odin application and run as administrator.....
I got it, I just flashed stock bootloaders 1st and all went well. Just a little bummed it even wiped my pictures (15 flashes/Odin's and never happened) but its ok
Sent from my GT-I9000 using XDA App
lbroskee said:
I got it, I just flashed stock bootloaders 1st and all went well. Just a little bummed it even wiped my pictures (15 flashes/Odin's and never happened) but its ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
had repartition ckecked ??
i dont really like using odin so havent for ages and i've always had it checked but once i lost everything on internal sd
lbroskee said:
I got it, I just flashed stock bootloaders 1st and all went well. Just a little bummed it even wiped my pictures (15 flashes/Odin's and never happened) but its ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yeah there is an option that will clear your sd card in odin so you have to watch to make sure its not checked. It happens sometimes
What 2.3 ROM are you planning on flashing? You don't want GB bootloaders if you plan on flashing MIUI or CM7. Any other GB ROM and you will. Good luck!
I went with sensation by crysis. Love it and the battery, just hate how in 2.3.4 it auto stops charging wen full
Sent from my GT-I9000 using XDA App
lbroskee said:
I went with sensation by crysis. Love it and the battery, just hate how in 2.3.4 it auto stops charging wen full
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
settngs > apps > development > check screen on, that keeps it charging
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
"Always have an exit strategy"
You can flash a fruitcake but the "unlocked" text will remain so you can hope for the best.
Or you can try an SBF (Disclaimer: at your own risk).
How long have you had it? Usually if you have had it for more than 30 days AT&T won't help but if you are still under "warranty" with them I would try AT&T first.
If you can't find a way to return your phone back to stock you can try Motorola, they might just overlook the modifications you have done.... or they might charge you a service fee...... or they might just send the phone back to you. It really depends on who ever is processing your claim and the mood they're in.
Also, please don't start multiple threads on the same topic.
http://forum.xda-developers.com/showthread.php?t=1549599
scarbutt11 said:
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
Click to expand...
Click to collapse
OK thanks. I had read that if I use the Motorola Software Update tool it will erase the "unlocked" text. I don't know how true that is though.
And sorry about the multiple threads, its just annoying not being able to use half my keyboard in portrait. Just was hoping for some quick answers.
Thanks again for the quick response
Sent from my MB860 using XDA
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
scarbutt11 said:
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
Click to expand...
Click to collapse
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
LeroyVold said:
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Yeah, it depends on what "Official" build you were last on. Since you were on "4.5.91" then I would just use that SBF. Like someone else mentioned, it is possible to use RSD Lite, just use caution.
scarbutt11 said:
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Thanks so much for the help. I'll go ahead and give it a shot. I'll let y'all know the outcome.
Sent from my MB860 using XDA
Took a little pulling of my hair while I waited but fastboot wipe and then flashing the stock sbf worked like a charm. I am back on stock GB, the unlocked text is gone and now I can hopefully get my phone fixed or replaced.
Thank you so much @live4nyy and @LeroyVold!!! Without you guys I would have been still scratching my head. I owe you both big time
No problem man, i need to do the same.
my touchscreen is more and more often unresponsive, so i'm flashing my stock sbf as i write.
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
i need to do the same. im sending this phone in and already got my new atrix sitting here.
Freaking Motorola phones, they break without you even touching them. I gotta figure out how to send mine to att as well.
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
scarbutt11 said:
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Free or did you have to pay?
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
this isnt working for me. and i need to send my phone in within a day.
Atrix_Owner said:
Free or did you have to pay?
Click to expand...
Click to collapse
For free, I bought the phone through them less than a year ago. All I said was that the screen was unresponsive and they looked at it for less than 10 minutes and then said they would replace it for me.
jahizen said:
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
Click to expand...
Click to collapse
Thats not a bad idea. I have never done one before but now that I'm thinking about it I am sure there are others that need to do what I just did. I will try to write one up in the next few days. Thanks for the idea!
live4nyy said:
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
Click to expand...
Click to collapse
hello i guess you could help me with a doubt i have..i used to be on stock 4.5.141 Gb 2.3.6 atrix 4g..im new on this things..and i installed succesfully cm7.2 but its not stable as i expected..i wanna go back to stock rom but im not sure what to do...i tried to go back using CWM restore...¨yes i made my backup before everything¨ but the restore didnt work...its stuck on moto booting logo..then i had to install again cm7 but the ba2tf wich its a bit more stable but not enough comparing to stock i had.. then my question its...
should i flash my phone with sbf 4.5.141?? or what do you recommend me..i dont wanna make a downgrade just be at 4.5.141 again
thanks
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!