Related
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
Ok, so right now I have:
System Info:
Version.4.1.83.MB860.ATT.en.US
Android Version:
2.2.2
It is rooted I have sideloading enabled. I don't know what program I used to do this with, it's been a long time. I remember there being a "beforeroot.bat" and "afterroot.bat" or something like that.
Anyway, I want to get the Alien ROM.
So, how do I do this? Do I need to update to the newest OTA? What method is the best for unlocking the bootloader? I have heard not to use PUDDING cause it uses RSD and I'm not supposed to use RSD?? Confused.
First of all DO NOT OTA. It may cause hard brick if you do not know what u are doing.
1. Unlock bootloader with pudding
2. Fastboot flash tenfars CWM
3. Backup everything with titanium backup
4. Download and install alien with CWM
Search is your friend on this one.
Sent from my MB860 using XDA Premium App
You do use pudding and RSD lite ONLY to unlock your bootloader then you uninstall it and start flashing with fasboot or tenfar's CWM. Hope that clears things up a bit.
The OTA is not a bad thing to get. I got it when it was leaked. There really is no need to flash back to older build unless you are a dev and even they dont really have the need to flash back to an older build.
The only way the OTA will brick your device is if you try to use rsd to go back to an older build.
The easiest process for getting to alien is:
1- Go here and use pudding--->http://forum.xda-developers.com/showthread.php?t=1136261
2- Go here to get Tenfars CWM installed(need this to flash ROM's)-http://forum.xda-developers.com/showthread.php?t=1138541
3- Go here to get your Alien on- http://forum.xda-developers.com/showthread.php?t=1186537
armonwilson888 said:
First of all DO NOT OTA. It may cause hard brick if you do not know what u are doing.
Click to expand...
Click to collapse
Why? The person I am about to quote says otherwise.
armonwilson888 said:
Search is your friend on this one.
Click to expand...
Click to collapse
I've been researching for a few days now, but there is SO MUCH information, most conflicting, that its extremely difficult to follow if you are not well versed in this stuff, or haven't done it before.
Dirtburgler said:
The OTA is not a bad thing to get. I got it when it was leaked. There really is no need to flash back to older build unless you are a dev and even they dont really have the need to flash back to an older build.
The only way the OTA will brick your device is if you try to use rsd to go back to an older build.
Click to expand...
Click to collapse
This what I have read. I don't think you can brick your phone UNLESS you go back to 1.83 or whatever after you unlocked the bootloader, because those are not compatible (something about a fuse or something.....yada yada)
Dirtburgler said:
The easiest process for getting to alien is:
1- Go here and use pudding--->http://forum.xda-developers.com/showthread.php?t=1136261
2- Go here to get Tenfars CWM installed(need this to flash ROM's)-http://forum.xda-developers.com/showthread.php?t=1138541
3- Go here to get your Alien on- http://forum.xda-developers.com/showthread.php?t=1186537
Click to expand...
Click to collapse
Perfect information. The only thing I don't get is this:
What is RSD? Here's what my assessment on the topic is, please correct me if (when) I'm wrong.
RSD is a tool given by motorola to flash ROMs to phones. CWM is a 3rd party tool similar to RSD made by a member named Tenfar.
Is this correct?
Also, the pudding thread in general is obscenely cluttered and has no instruction. I'm concerned with this. They mention 1.83, so should I stay with what I have? What I don't get is that if I'm flashing a ROM, what does it matter what version I have now, if it's going away? I don't get it.
Ooh, one last thing: If I install a ROM, does that mean I will not receive any more OTA update notifications? I would hope so, because if I tried to install an OTA over a ROM wouldn't that completely FUBAR everything?
RSD is motorolas tool for getting builds onto their devices and shouldnt be used at all for themost part. RSD will brick your phone if you try to go back to an older build. ie: 1.26,1.57, or 1.83. Your already on 1.83 so use RSD to flash the Pudding,(only takes a few seconds) then you have to use fastboot to actually unlock the device. This is explained in the pudding thread. CWM is how we get ROMS on our device by only flashing what is needed. CWM leaves the bootloader alone so you dont have to worry about Hard bricking your device. It is however possible to soft brick your device with CWM but a softbrick can be easily recovered. I have the leaked OTA and cant RSD back to an older build, but i have been flashing roms on a daily basis with no problems at all. Just read the directions twice and then read them again and im sure you can figure out how to unlock your device and get rolling with these hot roms.
Explaination on how to use fastboot is in the pudding thread as well as the UNlocked only CWM thread.
Here is the link to Pudding sbf.http://www.multiupload.com/FLZR9I9CNX
be sure to unzip the pudding zip first. should just be a .sbf inside
The pudding part- download the pudding sbf- put phone in rsd mode by powering in while holding the volume button up. launch rsd and load the pudding sbf and hit start. Only takes a second and the phone will reboot. Once it has rebooted, turn phone off and turn back on while holding down on the volume. fastboot should pop up first them press up on the volume and it will say entering fastboot. This is where you open a command prompt in windows(after you have put the fastboot files on the root of your c:\ drive. The fast boot files are here- http://diamantephoto.com/fastboot.rar
Put all the files that are in the fastboot zip on your c: drive and not in folders. (my computer-> C:\ drive put all the fastboot files here and not in a folder.) open command prompt and type cd\. this gets you to the root of your c: drive. should just see c:\ not cd\windows. type fastboot and you should activity then back to a c:\ prompt. once that is done you type (fastboot oem unlock) follow directions on Pudding thread from there.
Its easiest to flash pudding if your still on 1.83.
You can still do it if your on GB already
Ok, great. I'll step out of my comfort level (aka leap many thousands of yards out of my comfort zone) and try this when I get my SD card in from Amazon.
Just to clarify/simplify:
Since I have 1.83, I use RSD to flash Pudding.
Using Fastboot, I unlock the device.
Using CWM, I install Alien.
From that point on, if I want another ROM, I fire up CWM and install it there, and I shouldn't have any issues.
Is this all correct?
Also, what if I had updated my phone with the gingerbread OTA? What would the steps be then?
One more thing, do I have to have an SD card for any of these steps?
it's great for you to do it by yourself, as you're going to learn a lot more that way, if you're a little wary about using RSD and all that sort of thing, here's a cool script that'll do it for you
http://forum.xda-developers.com/showthread.php?t=1182871
Alcapone263 said:
it's great for you to do it by yourself, as you're going to learn a lot more that way, if you're a little wary about using RSD and all that sort of thing, here's a cool script that'll do it for you
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
Do I need an SD card for this?
k4zyn said:
Do I need an SD card for this?
Click to expand...
Click to collapse
no, you download that script on your computer and run it (following the instructions on the script, of course)
k4zyn said:
Do I need an SD card for this?
Click to expand...
Click to collapse
I updated the previous post a little, An sd card is the safest bet for flashing around. the sd is used for CWM flashing. put file on sd flash with cwm etc. SD not needed for pudding or unlocking bootloader
You may or may not be notified if there is an OTA update. IF you have rom installed and an update becomes available come back to forums to see if its safe to do it before you allow it, bt in most cases I dont think it will notify you if your on a Modded Rom.
If your already on GB then process is similar for unlocking. You have to unlock to use the Good CWM. The locked bootloader CWM can be troublesome.
If you want the OTA GB then unlock your bootloader then OTA up to GB. Then fastboot flash recovery Tenfars CWM, then your free ROM it up
Alcapone263 said:
no, you download that script on your computer and run it (following the instructions on the script, of course)
Click to expand...
Click to collapse
Right, I understand how the script works, I was just concerned because I'd read somewhere in this great nether that an SD card was required for one of the ROMS.......maybe I misread it though.
Dirtburgler said:
I updated the previous post a little, An sd card is the safest bet for flashing around. the sd is used for CWM flashing. put file on sd flash with cwm etc. SD not needed for pudding or unlocking bootloader
Click to expand...
Click to collapse
Makes sense! Thanks everyone.
k4zyn said:
Right, I understand how the script works, I was just concerned because I'd read somewhere in this great nether that an SD card was required for one of the ROMS.......maybe I misread it though.
Click to expand...
Click to collapse
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Alcapone263 said:
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Click to expand...
Click to collapse
Understood, thanks very much
Alcapone263 said:
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Click to expand...
Click to collapse
new tenfar's rom has an option of internal and external sd...so I am not sure if you have to have an external sd card...
orly?
the plot thickens.......
While I'm here, does TiBu back up everything? like, contacts, texts, email setups, etc?
k4zyn said:
orly?
the plot thickens.......
While I'm here, does TiBu back up everything? like, contacts, texts, email setups, etc?
Click to expand...
Click to collapse
TiBu backs up user apps and app data (settings). Do not backup system apps with it as you might have problems upon restoring.
For everything else you can use Mybackup Root ( Sms/MMS/Bookmarks/settings).
ok first off im on 4.5.91 rooted, unlocked and was running CM7. So i decided was going to try to get rid of the word unlocked at the boot screen so flashed 234-sb-released.zip and that didnt get rid of the word unlocked so i used RSD and flashed and that worked so I rooted my phone again and installed Rom Manager Premium installed CMW it said its installed so when i try to flash a rom or zip I get failed 2 boot. I have looked for the file install-recovery.sh" @ /system/etc as some ppl have suggested and dont see that file so now im stuck the phone boots normal and works fine just cant flash anything I also tried installing
MOTOA4_Bootstrap_0408_1720-signed which lets me enter recovery but gives me all kinds of errors when I try to flash something. Some good advice is needed beside google search as I tried that too!!!
Always_Jonezen said:
ok first off im on 4.5.91 rooted, unlocked and was running CM7. So i decided was going to try to get rid of the word unlocked at the boot screen so flashed 234-sb-released.zip and that didnt get rid of the word unlocked so i used RSD and flashed and that worked so I rooted my phone again and installed Rom Manager Premium installed CMW it said its installed so when i try to flash a rom or zip I get failed 2 boot. I have looked for the file install-recovery.sh" @ /system/etc as some ppl have suggested and dont see that file so now im stuck the phone boots normal and works fine just cant flash anything I also tried installing
MOTOA4_Bootstrap_0408_1720-signed which lets me enter recovery but gives me all kinds of errors when I try to flash something. Some good advice is needed beside google search as I tried that too!!!
Click to expand...
Click to collapse
Try re-installing pudding and running the unlock procedure again. Romracer was helping someone out with this yesterday. See here around post 451 on. Not your exact situation, but sounds veeeerrrry similar.
Yeah you can't relock your bootloader but flashing a .sbf will make it look like you did and you'll have to go through the procedure of unlocking it again. But its not actually locked. Its complicated.
Sent from Hyperspace using Tapatalk
so im still unlocked as I thought but the recovery software doesnt believe or see my phone as unlocked so I will have to unlock my phone again in order to be able to flash things again is that even safe
Always_Jonezen said:
so im still unlocked as I thought but the recovery software doesnt believe or see my phone as unlocked so I will have to unlock my phone again in order to be able to flash things again is that even safe
Click to expand...
Click to collapse
Yes, the link I provided has some follow up from the person who was having this problem. But I believe you will need the pudding file since the original bootloader doesn't have the fasboot oem unlock built into it.
*Edit* You'll also need to install your custom recovery too, since the sbf replaced it.
Ok so I messed around too much with my first Android.
What I did..
I have an AT&T 4.1.2.6 device.
I didn't succeed in upgrading the version through RSD, but I did manage to unlock the bootloader (using this tool http://forum.xda-developers.com/showthread.php?t=1182871), and installed Tenfar's CWM recovery.
Then I put this CM7: http://forum.xda-developers.com/showthread.php?t=1257574
I loaded it from zip and rebooted and the device was just stuck on the Motorola logo. I didn't wipe or did anything else before rebooting.
SO I tried to RSD to version 4.1.57, it started ok, but then FAILED, and that's where I am at now. My device is recognized by the RSD software.
What do I do? Should I RSD back to 4.1.2.6? This one http://gititbit.ch/asbf1
Can this be fixed or did I kill it already?
biodome11 said:
Ok so I messed around too much with my first Android.
What I did..
I have an AT&T 4.1.2.6 device.
I didn't succeed in upgrading the version through RSD, but I did manage to unlock the bootloader (using this tool http://forum.xda-developers.com/showthread.php?t=1182871), and installed Tenfar's CWM recovery.
Then I put this CM7: http://forum.xda-developers.com/showthread.php?t=1257574
I loaded it from zip and rebooted and the device was just stuck on the Motorola logo. I didn't wipe or did anything else before rebooting.
SO I tried to RSD to version 4.1.57, it started ok, but then FAILED, and that's where I am at now. My device is recognized by the RSD software.
What do I do? Should I RSD back to 4.1.2.6? This one http://gititbit.ch/asbf1
Can this be fixed or did I kill it already?
Click to expand...
Click to collapse
Use RomRacer's CWM; tenfar's is too old and is obsolete.
Try "wipe user data", "wipe cache" and "wipe dalvik cache" before flashing CM. Most likely your problem is that you didn't wipe.
You shouldn't use RSD/SBF after you unlocked your phone, it's not quite safe - it could hard brick your phone if you upgrade then downgrade. See the stickies like this one: http://forum.xda-developers.com/showthread.php?t=1160408
Instead, you can use "Fruit Cakes" if you really want to go back to MotoBlur: http://forum.xda-developers.com/showthread.php?t=1163009
Do you have a backup before flashing CM? If yes, try to use the recovery you have right now to revert (restore) your phone to its previous good working state.
As long as you're able to access fastboot and recovery, your phone isn't dead. Check http://forum.xda-developers.com/showthread.php?t=1154600 and http://forum.xda-developers.com/showthread.php?t=1302423 etc if you don't know what to do. Make sure you understand what you're going to do before you do anything to your phone.
See this also: http://forum.xda-developers.com/showthread.php?t=1233346, especially this one:
http://forum.xda-developers.com/showpost.php?p=18208784&postcount=20
Also Google for possible solutions.
Good luck!
Thanks for trying to help..
So if I did the CM7 and then I tried to RSD/SBF the 1.83 so it's possible I hard bricked it..
I didn't backup anything, because I didn't make any changes to my phone yet, never really used it..
So now I need to download FruitCakes 1.83? or higher?
How do I load it? with the RSD? I don't have access to CWM so I don't think I can use them.
I think that's the only way I have to communicate with my phone right now is RSD.
Keep in mind I'm a noob in this.
I don't think I have access to the flashboot and recovery.. that by pressing volume down, right? It doesn't get there.
Only thing I can access now is RSD... :/
biodome11 said:
Thanks for trying to help..
So if I did the CM7 and then I tried to RSD/SBF the 1.83 so it's possible I hard bricked it..
I didn't backup anything, because I didn't make any changes to my phone yet, never really used it..
So now I need to download FruitCakes 1.83? or higher?
How do I load it? with the RSD? I don't have access to CWM so I don't think I can use them.
I think that's the only way I have to communicate with my phone right now is RSD.
Keep in mind I'm a noob in this.
I don't think I have access to the flashboot and recovery.. that by pressing volume down, right? It doesn't get there.
Only thing I can access now is RSD... :/
Click to expand...
Click to collapse
When you power up the phone, hold "Volume Down" key, see if you can see "fastboot" on the screen... if you see it, try click the volume down key again a few more time, see if you can find "Android Recovery"...
if you can see it, hit "Volume Up" key to enter recovery, from there you'll be able to flash anything you like... this way you can recover your phone.
The other way is to use "moto-fastboot" when the phone is in "fastboot" mode.
Holding volume down doesn't help, it won't go to fastboot.
Can anything be done?
Not sure what else can be done. Search the forum see if you can find any hint. I heard success stories by returning phones in warranty to at&t customer help center (not warranty center).
I'm not in the US and can't return it for warranty :/
Any ideas anyone?? Will trying RSD to 1.2.6 **** it more or no harm in trying??
biodome11 said:
I'm not in the US and can't return it for warranty :/
Any ideas anyone?? Will trying RSD to 1.2.6 **** it more or no harm in trying??
Click to expand...
Click to collapse
Flash an sbf of gingerbread with pudding. DON"T TRY TO FLASH ANY sbf without pudding our you will HARD BRICK.
After that you should be back on track. You will then be able to flash Romracer's latest CWM recovery and use that for flashing roms.
In order to not get stuck on Moto logo after flashign roms, do a full wipe before and after flashign a rom.
Good luck.
Can you give me a link to the correct SBF with pudding? I'm pretty much a noob at this.
I'm not sure that I didn't hard brick it already by trying to flash the 1.8.3 before..
biodome11 said:
Can you give me a link to the correct SBF with pudding? I'm pretty much a noob at this.
I'm not sure that I didn't hard brick it already by trying to flash the 1.8.3 before..
Click to expand...
Click to collapse
4.5.91 sbf with pudding
If it lets you enter RSD mode, means you haven't hard bricked yet. Be careful.
This is yet another reason why people should research things thoroughly before jumping into something they don't know much about just because it looks fun.
Sent from my MB860 using Tapatalk
xploited - THANK YOU!!!
It's ALIVE again! My god I'm so happy
So I'm now 4.5.91 with pudding and root Android 2.3.4 - Which guide do I follow to installs Roms the right way? which recovery do I install?
ANYTHING else I should know before I do something stupid?
Congrats!
Try to install RomRacer CWM first before install any ROM. It's a line of defense in case anything bad happens to your phone. Read http://forum.xda-developers.com/showthread.php?t=1154600 first if you don't know much about your phone. Don't hurry, take your time and make sense of what you've read.
Let's make sure I understand correctly.
The SBF I installed with pudding and root means my device is already unlocked right?
It says unlocked on top left corner when I start the device.
So all I need now is to install RomRacer's CWM and go by the instructions - true?
biodome11 said:
Let's make sure I understand correctly.
The SBF I installed with pudding and root means my device is already unlocked right?
It says unlocked on top left corner when I start the device.
So all I need now is to install RomRacer's CWM and go by the instructions - true?
Click to expand...
Click to collapse
Yes, you only need to unlock your phone once. Unlock won't go away unless you RSD flash a rom without pudding. Which you shouldn't cause that will most likely hard brick your phone.
And yes, now you can install RomRacer's Recovery or koush's Rom Manager (Clockworkmod Recovery) from the market, that can be flashed without even entering fastboot. So easiest option right there.
With CWM (especially koush's Rom Manager ) flashing roms is super easy.
When I try to run koush's Rom Manager it says "superuser was not found at /system/bin/su or /system/xbin/su" and that I must root my device.
How can it be not rooted with the SBF I used? as I said when I open the device the bootloader says"unlocked"
biodome11 said:
When I try to run koush's Rom Manager it says "superuser was not found at /system/bin/su or /system/xbin/su" and that I must root my device.
How can it be not rooted with the SBF I used? as I said when I open the device the bootloader says"unlocked"
Click to expand...
Click to collapse
Try installing Superuser from the Market.
biodome11 said:
How can it be not rooted with the SBF I used? as I said when I open the device the bootloader says"unlocked"
Click to expand...
Click to collapse
"unlocked" doesn't mean "rooted".
Unlocked means the bootloader is unlocked.
Rooted means you have the capability to gain "root" privilege (a Unix-like concept)
A phone can be rooted while locked. Vice versa.
Ya but I figured the pudding SBF was with root, or so it said.
Anyway all is well now.. I'm on CM7 at last
Thanks to all that helped..
By the way I don't see an option to sync my google and facebook contacts like I saw in the previous version.. I need to install something for that?
I'm missing gmail and maps as well, guess I need google tools of some sort..
biodome11 said:
By the way I don't see an option to sync my google and facebook contacts like I saw in the previous version.. I need to install something for that?
I'm missing gmail and maps as well, guess I need google tools of some sort..
Click to expand...
Click to collapse
The CM7 thread should have the google apps link, you can install from there. After Market is installed, you'll be able to install gmail and maps.
For sync: Menu->Settings->Accounts & sync->Add account, your contacts will be sync once you turn it on
I installed an app to change the boot animation on my Atrix 4g and when I rebooted to see it, all i get is the m logo with dual core technology under it. It is rooted and i didn't flash any new roms or anything. i wiped the cache partition from the recovery menu and also " wipe data/factory reset" but it still doesn't boot up.
its on android 2.3.6 build 4.5.141
please help me :crying:
Do you have recovery software?
Fervi
Just restore the system partition from the backup you SHOULD do before any modification and you will be good to go.
Otherwise, delete the faulty bootanimation and restore the original via adb on recovery and reboot.
There is also a no bootanimation option on build.prop, althrough I'm not sure if it's avaiable on 2.3
Enviado desde mi MB860 usando Tapatalk 2
i don't have any recovery software or backups made.
If you have fastboot option, you can install TWRP (or CWM) and then install other rom (like Motorola Atrix ICS [4.0])
Fervi
ferviverus said:
If you have fastboot option, you can install TWRP (or CWM) and then install other rom (like Motorola Atrix ICS [4.0])
Fervi
Click to expand...
Click to collapse
and how would I accomplish this?
http://wiki.cyanogenmod.org/w/Template:Recovery_install_fastboot
Remember - There is no guarantee that everything will go fine. You do it at your own risk
Fervi
ferviverus;54222742
Remember - There is no guarantee that everything will go fine. You do it at your own risk
Fervi[/QUOTE said:
whenever i type fastboot devices into command prompt even when it is connected and in fastboot it doesn't work.
Click to expand...
Click to collapse
So I got fastboot and everything working. I think flashing the sbf with rsd lite might work, only problem is that whenever I try to download the sbf files it takes me to some ilivid download manager. Soo anyone know where I can download the actual sbf?
specter187 said:
So I got fastboot and everything working. I think flashing the sbf with rsd lite might work, only problem is that whenever I try to download the sbf files it takes me to some ilivid download manager. Soo anyone know where I can download the actual sbf?
Click to expand...
Click to collapse
http://sbf.droid-developers.org/
Sent from my MB886 CM10.2/4.3.1
i think things just got worse
palmbeach05 said:
[ul]htt://sbfdroid-developers. org/[/url]
Sent from my MB886 CM10.2/4.3.1
Click to expand...
Click to collapse
I tried flashing and now when I put my phone into rsd mode its says: failed to boot 1
PwrReason: PWR_KEY_PRESS
starting fastboot protocol support
and when I try to put it into fastboot my phone comes on says something and it turns off to quickly for me to see what the text says.
and when I just power on without pressing anything it says failed to boot 1 and that same confounded dooming m logo
I feel as though my atrix is unflashable or something.
specter187 said:
I tried flashing and now when I put my phone into rsd mode its says: failed to boot 1
PwrReason: PWR_KEY_PRESS
starting fastboot protocol support
and when I try to put it into fastboot my phone comes on says something and it turns off to quickly for me to see what the text says.
and when I just power on without pressing anything it says failed to boot 1 and that same confounded dooming m logo
I feel as though my atrix is unflashable or something.
Click to expand...
Click to collapse
its actually in a state of i need to be unlocked and searching failed to boot 1 would have brought you to this - http://forum.xda-developers.com/showthread.php?t=1528729
the sbf download link from the forum link you posted doesn't work
A DEAD PAGE 404 ERROR
HIDE THE PIE!!!!
specter187 said:
the sbf download link from the forum link you posted doesn't work
A DEAD PAGE 404 ERROR
HIDE THE PIE!!!!
Click to expand...
Click to collapse
Really? the mini sbf that I'm referring to is not a full sbf. it is a 1 MB file that you should get and do to obtain root.
Where in what you have said in this entire thread did you unlock the bootloader?
palmbeach05 said:
Really? the mini sbf that I'm referring to is not a full sbf. it is a 1 MB file that you should get and do to obtain root.
Where in what you have said in this entire thread did you unlock the bootloader?
Click to expand...
Click to collapse
my bootloader isn't unlocked
specter187 said:
my bootloader isn't unlocked
Click to expand...
Click to collapse
Then I would highly advise that you unlock your bootloader before any more help is given to you. I don't say that in a mean way, I say that in a strong recommendation way. Without that bootloader being unlocked, there is little help we can do to get you back up and running.
palmbeach05 said:
Then I would highly advise that you unlock your bootloader before any more help is given to you. I don't say that in a mean way, I say that in a strong recommendation way. Without that bootloader being unlocked, there is little help we can do to get you back up and running.
Click to expand...
Click to collapse
my bootloader is now unlocked
AVAAAAST YEE!
I HAVE SALVATION! MY PHONE IS ON! I HAVE SEEN THE MOTOBLUR SCREEN.
i am almost afraid now to root it
here goes nothing
specter187 said:
my bootloader is now unlocked
Click to expand...
Click to collapse
delete, wifi on my end didn't post this when I originally did. congrats btw!
Update?
there is an update to upgrade it to 4.5.145 i tried and i got a failed to boot 4 starting rsd protocol support
but i fixed that. So can i not update a phone with unlocked bootloader? or is there some kind of run around?