Related
Good morning everyone. I have a major technical issue with my phone after flashing to HKTW 2.3.4 and I am in dire need of assistance. I hope someone here can help me asap since I really need to use this phone.
So here is my issue. After flashing to 2.3.4 via Flash Recovery, I was greeted with an unusable touchscreen. Everything looked fine, however when I try to "touch" anything on the screen (keyboard, icons, menus, etc) I am forced to touch the opposite side of it, which means to click on an icon on the left side of the screen, i have to touch the right side of the screen. Similarly with the keyboard, to click a letter that's on the right side of the screen, I have to touch on the left side. I think the touchscreen is mirrored, probably for the Chinese characters?
But not only that, apparently, the 4 primary touch buttons (menu, home, return, search) are also reversed, thus having me to touch search in order to access menu.
I practically can't set up the phone due to this, and I didn't make a backup of /data prior to unlocking the phone (didnt know how to do so earlier). I have backups from TiBu but it's at home right now.
Is there anything I can do? Maybe change a setting via root explorer, or maybe through Flash recovery? Please someone help me.
Thanks,
Aqua
p.s. Moderators/Admins, I know I've posted this in several threads and I apologize for "spamming" but this is very urgent, so please don't delete this thread. Thank you.
Try to SBF flash 1.83 via RSDLite
Sent from my MB860 using XDA App
neer2005 said:
Try to SBF flash 1.83 via RSDLite
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hi Neer, I will try that right now. If it fixes the issue, then something's wrong my flash to 2.3.4. I was hoping that I can resolve this without going backwards but I guess have no choice.
aquariuz23 said:
Hi Neer, I will try that right now. If it fixes the issue, then something's wrong my flash to 2.3.4. I was hoping that I can resolve this without going backwards but I guess have no choice.
Click to expand...
Click to collapse
That's the only hope you've got buddy.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
ceo.mtcl said:
That's the only hope you've got buddy.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
Click to expand...
Click to collapse
Crap!! now it's stuck in a boot loop. After flashing 1.8.3, it attempts to boot, and after passing the att screen, the screen goes black and the red led continuously blinks. Afterwards it just reboots again. What should I do?
the cwm flash method seems to present this bug to several people. Now that you have flashed to 1.8.3, try going into recovery and doing a factory reset. If that does not do it, i would then try flashing either 1.8.3 or 2.3.4 via fastboot, by manually flashing the system and boot partitions. if neither suggestion works, then this problem is beyond my realm of expertise and youll have to wait on someone who knows what they are talking about to chime in.
Well, I now can't proceed nowhere. Apparently, I bricked my phone flashing back to 1.8.3. Now another ordeal to tackle. Gonna try Designgear's guide to recovering from a brick. Wish me luck
aquariuz23 said:
Well, I now can't proceed nowhere. Apparently, I bricked my phone flashing back to 1.8.3. Now another ordeal to tackle. Gonna try Designgear's guide to recovering from a brick. Wish me luck
Click to expand...
Click to collapse
the same thing happened to me.. charge up your phone all the way and flash the 1.2.6 SBF. it took 2 seperate flashed for me, but it worked. and then i was able to proceed flashing 2.3.4 again
Successfully unbricked the phone via this guide: (just posting it in case some people encountered the same issue)
http://forum.xda-developers.com/showthread.php?t=966648
Now i'm in stock 1.83 froyo. Gonna do the unlock again, and proceed from there on. Not gonna do the 2.3.4 flash via CWM, will try a different method, hopefully it wont fail on me this time
what does bricking mean?
for the record a bricked device cannot be unbricked.
SuperUserMovado said:
for the record a bricked device cannot be unbricked.
Click to expand...
Click to collapse
I guess i did a soft-brick? Not to argue with you, but based on several threads here on the forum, if the atrix is stuck boot-looping with the red led flashing rapidly, then it's considered bricked, but hey what do i know. All I care is I managed to get out of the predicament and proceed with trying to flash 2.3.4.
use the fastboot flash method, very clean and works great.
Success!!
I managed to get 2.3.4 without any issues (excluding whatever bugs there might be on this release). The touchscreen works perfectly fine without the crazy reversed touch or super sensitive responses.
After unlocking the phone using the pudding guide, I went and flashed the following through fastboot:
http://forum.xda-developers.com/showthread.php?t=1139715
And it works like a charm. I am guessing either Tenfar's CWM or his flashable 2.3.4 release is buggy and did not want to work with mine. Or maybe I simply had to start from scratch (1.83 sbf) instead of continuing from my deodexed 1.83 *shrugs*. But yeah, things are looking much better now thank god.
Now, I will try to install Tenfar's CWM and this as well:
http://forum.xda-developers.com/showthread.php?t=1142674
Hopefully all will stay well
Thanks for all your help and suggestions guys/gals.
pyro254750 said:
use the fastboot flash method, very clean and works great.
Click to expand...
Click to collapse
Did so, n it works much better than through flash recovery. Thanks.
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).
Build#: 4.5.2A-51_OLL-17
System: 45.2.17.MB860.BellMobility.en.CA
Version: 2.3.4 (on rooted stock Gingerbread)
I rooted my 2.3.4 Bell Atrix using the instructions on Atrixforums website, and it worked like a charm. Then i went into the market and downloaded ROM Manager, through which i flashed the latest Clockwork Mod Recovery. Since this was going to be my first time flashing a Custom ROM, I followed online advice of performing a Nandroid backup. I pressed "Backup Current ROM" in ROM Manager, and my phone turned off. When it turned back on, I was at the Motorola Dual Core screen, and at the top there was a message: "Failed to boot 2 Starting RSD Mode". After reading some more on the forums, I noticed that I never unlocked my phone and that I couldn't flash a custom Recovery meaning Nandroid backups won't work.
But now I'm stuck with a broken Recovery mode and I don't know what to do to fix this. Can I still flash the original recovery image back to fix the Failed to boot error?
Can someone please help point me to the right direction?
Thanks
Try pulling the battery. Hope that works, then unlock your phone, re root it and install rom racers recovery and you should be good to go. Thoroughly read the beginners thread, it will answer a lot of your questions and help walk you through everything you ned to do. Saved me a lot of hassle and headaches
JRW 28 said:
Try pulling the battery. Hope that works, then unlock your phone, re root it and install rom racers recovery and you should be good to go. Thoroughly read the beginners thread, it will answer a lot of your questions and help walk you through everything you ned to do. Saved me a lot of hassle and headaches
Click to expand...
Click to collapse
to unlock my phone, don't i need to get into the recovery mode first? I can still boot into the homescreen and do stuff, but it's just the recovery mode is screwed up. RSD lite and stuff still works though. Would you be kind enough to provide a link to the right direction to unlock the phone? Will this fix my recovery mode problem? I've been going on a wild goose chase to find a way to install a custom ROM and alot of the posts were for the AT&T Atrix (or at least i believe it's only compatible with the ATT Atrix).
no, you have to use RDS to flash a unlockable bootloader, use fastboot, and then install the custom recovery
Sent from my MB860 using XDA App
i am having this same exact problem as the original poster. i am still new to the "rooting" world, and the motorola atrix is quite a bit more difficult then the other devices i have rooted, if someone could link a guide to follow it would be very much appreciated, i have been browsing the forum for quite awhile now searching for a guide. again, thank you very much for your time and please excuse my ignorance.
guidoido004 said:
no, you have to use RDS to flash a unlockable bootloader, use fastboot, and then install the custom recovery
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+1
Sent from my MB860 using XDA App
How to unlock:
http://forum.xda-developers.com/showthread.php?t=1136261
Ok so here's the thing I obviously have a Motorola Atrix 4g and I am from the United States. I have rooted my device via Pete's Motorola root tools, I have accessed my webtop hack and tether. I've been research for about a week straight on how to install CM7, but the CM7 that I really want is EVOGP's whch has facial recognition capabilities (http://forum.xda-developers.com/showthread.php?t=1382934&highlight=facial+recognition). I am currently running stock Gingerbread. I have previously tried t0dbld's way of installing for the latest version of CM7 (Ba2TF) based on his installation instructions (http://forum.xda-developers.com/showthread.php?t=1257574&highlight=facial+recognition). Unfortunately I failed and ended up wiping all my contacts and starting brand new. The portion that I do not see is the second step :
1.)Reboot phone into CWM recovery (Power Button + Vol Down), press Vol Down until you see "Android Recovery" then press Vol Up to enter.
2.) Go to Backup & Restore and create a backup (this may take some time)
I dont see where to go for Backup and restore to create a back. It too me a while to figure out that had to press the both volume buttons just to toggle. But this was the first area, that was blurry. If someone could explain step by step how to get to "Backup &Restore and create a backup" would be great.
Next while apparently not backing up my rom, I decided since I already had a rom and I wanted CM7 that wouldnt be important. So I try to install the Ba2tf.zip via the bootloader screen which located on my sd card. So I go "apply blah blah to Sd card" I see the Ba2tf.zip and I press the power button to unzip the file or install. The process I see starts unloading the zip file then starts to installing the file, everything is great. Then it says "installation failed".
If someone can tell me what I did wrong and give me a step by step process of what I should and be seeing, I would greatly appreciate this help. As you cant tell I really want CM7 especially EVOGP's. Please help!!! Step by step please!!!!
Have you unlocked your phone using fruitcake? Which CWM are you running?
It's Pudding, not fruitcake.
http://forum.xda-developers.com/showthread.php?t=1136261
Fruitcakes are stock system files that can flashed through CWM.
jiggytom said:
Have you unlocked your phone using fruitcake? Which CWM are you running?
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, then unlock it. Search for pudding in the Dev Forum.
After that, you need the right recovery (CWM)
Which recovery are you using? You should flash romracer's latest CWM. Most of all the ROMs are using the latest Romracer's recovery so you won't go wrong with using that.
Then from there --- you should be good to go.......
I had no idea you had to unlock, I thought unlocking and rooting was the same thing. And I a bit new with lingo does CWM refer to Clockwork Mod? If so I downloaded the standard free Rom Manager on the market. I assume judging by your message I should probably unlock my phone using fruitcake? If I do can you post simplified link on how to install fruit cake?
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1302423
The instructions provide links for Pudding and romracer's recovery, which are both needed to flash any custom Rom.
Here's the link for CM7:
http://forum.xda-developers.com/showthread.php?t=1257574
baller24hr said:
I had no idea you had to unlock, I thought unlocking and rooting was the same thing. And I a bit new with lingo does CWM refer to Clockwork Mod? If so I downloaded the standard free Rom Manager on the market. I assume judging by your message I should probably unlock my phone using fruitcake? If I do can you post simplified link on how to install fruit cake?
Click to expand...
Click to collapse
I guess I have to use pudding right? I see the link i'll flash it. I'll go searching for Romracer's latest recovery... please point me towards it if possible.
Re-read what I wrote.
live4nyy said:
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1302423
The instructions provide links for Pudding and romracer's recovery, which are both needed to flash any custom Rom.
Here's the link for CM7:
http://forum.xda-developers.com/showthread.php?t=1257574
Click to expand...
Click to collapse
baller24hr said:
I guess I have to use pudding right? I see the link i'll flash it. I'll go searching for Romracer's latest recovery... please point me towards it if possible.
Click to expand...
Click to collapse
@live4nyy Thank you so much you are a huge help.... I greatly appreciate it
No problem, just make sure to read the instructions thoroughly and make sure you have the appropriate "pudding" file.
baller24hr said:
@live4nyy Thank you so much you are a huge help.... I greatly appreciate it
Click to expand...
Click to collapse
I have installed rsdlite. Where can I find the drivers that I'm supposed to install? Or does it come bundled already?
Here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Also, after you install the drivers it helps to plug it in and then go through all the USB options in the drop down and allow each one to install as well. (eg. Windows Sync, USB Mass Storage, Portal)
baller24hr said:
I have installed rsdlite. Where can I find the drivers that I'm supposed to install? Or does it come bundled already?
Click to expand...
Click to collapse
Yeah i remember downloading this a while back.... I'm currently at Proper Recovery 5B and my command prompt says <waiting for device> and it wont allow me to type 5C.... Do I choose either A,B or C then pick D? And I'm currently on my bootload screen and it says Unlocked in the top left corner
Does anybody know anything of this nature?
Someone help I'm getting worried now
Now my phone shut off and the charging light is on....
I typed in 5c and it says it's not found... i tried 5d and that didnt work <waiting for devices> .... my phone was unresponsive even to the power button so i pulled the battery and turned it on it brought me back to the bootload screen that said unlock in the top left. my phone is now charging on the normal house charger and i turned it back on it's responsive I dont have any of my cards in so it's showing motoblur
Does this mean my phones unlocked and I should just go ahead and install the CM7?
baller24hr said:
Does this mean my phones unlocked and I should just go ahead and install the CM7?
Click to expand...
Click to collapse
Yup.
Sent from my Xoom using xda premium
thanks I appreciate it