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 fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
NickS_ said:
OK fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
Click to expand...
Click to collapse
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
SielickiN said:
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
Click to expand...
Click to collapse
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
Trying to flash CWM, it's giving me an error..
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Ruh roh
Alcapone263 said:
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Click to expand...
Click to collapse
Do they actually check that? Or is just theoretically they can...?
SielickiN said:
Do they actually check that? Or is just theoretically they can...?
Click to expand...
Click to collapse
it's a theoretically they can sort of deal.
NickS_ said:
Trying to flash CWM, it's giving me an error..
Ruh roh
Click to expand...
Click to collapse
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Alcapone263 said:
it's a theoretically they can sort of deal.
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Click to expand...
Click to collapse
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't.. regardless I'm currently flashing pudding with the version of RSDLite in his thread which is slightly different than the one I was using. (red logo vs blue)
Alcapone263 said:
it's a theoretically they can sort of deal.
Click to expand...
Click to collapse
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
NickS_ said:
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't..
Click to expand...
Click to collapse
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
SielickiN said:
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
Click to expand...
Click to collapse
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks SO much. Really appreciate your help.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks so much man. I have a replacement phone on the way due to the random shut offs considering people have been reporting it with the stock GB rom too, and it's believed to be a hardware malfunction, I just wanted it to appear more "stock" when they received it to avoid any question asking. Would really suck if I bricked it before hand haha.
I actually like the stock ROM on this phone anyway, probably won't be going back to CM7 once the new one comes in. It's rebooting now with the pudding SBF, we'll see if she still loops or not. If it still loops, I'll flash the modified CWM and the fruitcake ROM and report back. You guys are super helpful, thanks again!
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Alcapone263 said:
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Click to expand...
Click to collapse
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
I hard bricked my first one it was also rooted and unlocked and att sent me a new on on,the warrenty for free
Sent from my MB860 using xda premium
NickS_ said:
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
Click to expand...
Click to collapse
well i'm glad you got your problem sorted out! before you flash any ROMs though, be sure to do a complete backup of your phone as it is right now. it'll help you in case of PDS corruption later on.
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
NickS_ said:
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
Click to expand...
Click to collapse
i'm sure you have CWM installed by now, use Romracer's and do a full backup of your device. just keep it on your phone, with a copy of it backed up on your computer.
the PDS partition is a place on our phone that holds a lot of information about our device, if it gets corrupted you can experience a lot of touchscreen issues. just better to be safe. i flash my phone every 2-3 days and haven't experienced anything, but other people have, so like i already said; better safe than sorry
Hey guys, I think I'm in trouble. Two weeks ago I got an X2, and soon after discovered the Modding and Root world. Needless to say I ended bricking with Rom Manager. Obviously a user error... Anyway, I was wondering if there might be somehow I could use the memory on the phone as an external hard drive or something. Could I install the zipped .sbf file to SanDisk, and if I find a way to get back in to recovery....you see where I'm going with this.
Thanks again
Have you tried SBF'ing it back to stock using RSDLite?
Triscuit said:
Have you tried SBF'ing it back to stock using RSDLite?
Click to expand...
Click to collapse
Yes I have. I rooted it initially and everything was fine until I lagged the system somehow with certain settings. The learning curve is not a big one, but its still existent. Anyway, I wiped and flashed .sbf perfectly. It was only when I rooted the second time and opted for a Mod where things went badly...I guess. No warning, the device just shuts off and comes back to the boot screen(Motorola emblem). No fastboot option or anything.
MathiasKnight said:
Yes I have. I rooted it initially and everything was fine until I lagged the system somehow with certain settings. The learning curve is not a big one, but its still existent. Anyway, I wiped and flashed .sbf perfectly. It was only when I rooted the second time and opted for a Mod where things went badly...I guess. No warning, the device just shuts off and comes back to the boot screen(Motorola emblem). No fastboot option or anything.
Click to expand...
Click to collapse
You'd be surprised by how many people on ebay and other sites want bricked devices. Some use them for parts and others just want to screw around with them.
Sent from my DROID X2 using xda premium
MathiasKnight said:
Yes I have. I rooted it initially and everything was fine until I lagged the system somehow with certain settings. The learning curve is not a big one, but its still existent. Anyway, I wiped and flashed .sbf perfectly. It was only when I rooted the second time and opted for a Mod where things went badly...I guess. No warning, the device just shuts off and comes back to the boot screen(Motorola emblem). No fastboot option or anything.
Click to expand...
Click to collapse
I'd be very surprised if this was truly bricked. When you rooted the second time, did you get bootstrap recovery installed? If so you can pull the battery, leave it turned off and plug it into a wall charger. It should power itself on and take you right to ClockWorkMod recovery and from there you could Use ADB to push a working rom and start off on a clean slate (or restore a nandroid if you made one before flashing mods.)
Otherwise, I would suggest continuing trying to get in the device in RSD mode. Sometimes these phones can be finicky, I know when I first started messing with Androids it would often take several times to get to the Bootloader options rather than just powering on the device.
What was the questionable mod you used?
MathiasKnight said:
Hey guys, I think I'm in trouble. Two weeks ago I got an X2, and soon after discovered the Modding and Root world. Needless to say I ended bricking with Rom Manager. Obviously a user error... Anyway, I was wondering if there might be somehow I could use the memory on the phone as an external hard drive or something. Could I install the zipped .sbf file to SanDisk, and if I find a way to get back in to recovery....you see where I'm going with this.
Thanks again
Click to expand...
Click to collapse
Have you tried following my tutorial on SBF? Try holding the Volume Up button and see if you get to the "Starting RSD" (or something like that). You should be able to SBF from there.
The link is in my signature or here: HowTo: Perform a SBF ("factory restore") of your Motorola Droid X2
Ciao!
As long as the phone turns on you can fix it. SBF will fix your issue.
sent from my TF Prime using XDA premium
Baseball
If it truly is bricked, you could use it for batting practice. I've wanted to do that to a working X2 many times, so I know I would if it were bricked
Sbf sbf S B F
make sure u charge ur battery full up before flashing sbf file
Like moon said power button and volume up starts rsd protocol
If that doesn't work there is also a thing called ezSBF someone can tell ya bout
Sent from my Galaxy Nexus using Tapatalk 2 Beta-6
I've tried the fastboot(volume button) method and there is nothing. No response what so ever. I've never even heard of EZsbf, but I'm gonna try it out. Oh, whoever asked about the MOD a while ago....it was gingerbread I think. The only thing I wanted was to overclock my cpu's just a bit, but ended up getting in way over my head very quickly. The light comes on when the phone is plugged in with no battery and stays on. Other than that no change. Hey thanks guys, alot!
No not fast boot
That shows when u press power and volume down together(u need to hold both buttons down)
Instead
PRESS POWER BUTTON AND VOLUME UP AT SAME TIME and hold them BOTH for about 10seconds. U should see "starting RSD protocol..." at the top of ur screen
If u don't then u probly need to charge ur battery
Also
We have NO WAY to over clock due to our locked bootloader. You need to be able to install a custom kernel to be able to over clock and we can't do that.
I recommend not to try any mods or anything outside of this DROIDX2 development forum(don't even use stuff made for original X it will mess ur phone up. And definitely stay away from atrix, photon, etc...even if something says "universal mod/tweak/hack" its most likely gonna break ur x2 cuz the x2 is just a finnicky ass phone lol)
Good luck!
Sent from my Galaxy Nexus using Tapatalk 2 Beta-6
You need to reinsert the battery, keep the phone off, then plug it in to the wall charger. If you had BSR installed it'll boot into recovery.
Thank you so much guys, all of you. I'm back in to my X2!!!
MathiasKnight said:
Thank you so much guys, all of you. I'm back in to my X2!!!
Click to expand...
Click to collapse
So what exactly did you need to do?
Were u just missing a step?
Or did u try something new?
This way someone else who hits the same snag can know a solution
Congrats! Bringing the x2 back from the dead is always fun lol
signature: 404 error
ashclepdia said:
So what exactly did you need to do?
Were u just missing a step?
Or did u try something new?
This way someone else who hits the same snag can know a solution
Congrats! Bringing the x2 back from the dead is always fun lol
signature: 404 error
Click to expand...
Click to collapse
Yeah, you're right! Still new to threading! I was able to initialize DSP Restore, but I didn't have bootstrap prior to the crash, but beca use the X2 was now recognized I could push the .sbf using DSPlite. Then, once the nano was open I just factory defaulted, because my service wasn't recognized by my carrier.... And they all modded happily ever after. I do have a question though: what do you think about trying the root again and instead of manually removing the fluff programming I get a manger to take care of it? This thing is factory pure right now. Btw, I'd like to call attention to where this is being posted from. That is called success...thanks again.
MathiasKnight said:
Yeah, you're right! Still new to threading! I was able to initialize DSP Restore, but I didn't have bootstrap prior to the crash, but beca use the X2 was now recognized I could push the .sbf using DSPlite. Then, once the nano was open I just factory defaulted, because my service wasn't recognized by my carrier.... And they all modded happily ever after. I do have a question though: what do you think about trying the root again and instead of manually removing the fluff programming I get a manger to take care of it? This thing is factory pure right now. Btw, I'd like to call attention to where this is being posted from. That is called success...thanks again.
Click to expand...
Click to collapse
There is a list in this forum from a long while ago that has what's safe to remove and what isn't.
But the easiest thing u could do is to flash either eclipse, molten, liberty , or cm7
They will pretty much get rid of ALL the bloat that is safe to remove and cm7 will even remove ALL the blur skin along with bloat and give you an AOSP experience with your device
signature: 404 error
I'm going to try it....now!
Its pretty hard to brick these devices with the SBF file Motorola supplies. And just a suggestion for future reference, DO NOT use ROM manager with this phone. ROM manager is more for phones with an unlocked bootloader which this phone doesnt have. Some things will work but some things will mess up your phone.
MathiasKnight said:
I'm going to try it....now!
Click to expand...
Click to collapse
Enjoy
But make a nandroid first!
That way if u wanna go back u don't need to flash sbf u can just restore ur nandroid and be on ur way lol
signature: 404 error
Ok, just to check my rationale: I'm going to create a Nandroid, to the SD, but I should download CM7 to my PC and install it that way so as not to lag or cause any complications with the X2. Correct?
Hi,
For now I am stuck on stock GB rom.
My amaze 4G is rooted, and bootloader unlocked (S-on).
I was not able to get the OTA ICS mobilicity to install.
I need my phone to be more energy efficient. Is there a way to do this with a kernel on stock GB rom?
Or some other way?
Also with S-on, can I flash any GB rom whether it be wind, mobilicity, telus or tmobile?
Thanks in advance.
skugpezz said:
Hi,
For now I am stuck on stock GB rom.
My amaze 4G is rooted, and bootloader unlocked (S-on).
I was not able to get the OTA ICS mobilicity to install.
I need my phone to be more energy efficient. Is there a way to do this with a kernel on stock GB rom?
Or some other way?
Also with S-on, can I flash any GB rom whether it be wind, mobilicity, telus or tmobile?
Thanks in advance.
Click to expand...
Click to collapse
Ask Dark Nightmare he's a BEAST at these thing also there's like 2 thread about this already update to ICS from GB JUST READ READ RAED n yaaa RAED SOME MORE i always thought Canadians like tyo read my 2ex loved to read maybe cause there girls lol but
use apps from the market like this one https://play.google.com/store/apps/details?id=com.latedroid.juicedefender&hl=en juice defender
skugpezz said:
Hi,
For now I am stuck on stock GB rom.
My amaze 4G is rooted, and bootloader unlocked (S-on).
I was not able to get the OTA ICS mobilicity to install.
I need my phone to be more energy efficient. Is there a way to do this with a kernel on stock GB rom?
Or some other way?
Also with S-on, can I flash any GB rom whether it be wind, mobilicity, telus or tmobile?
Thanks in advance.
Click to expand...
Click to collapse
Energy Rom seemed pretty efficient on gb, others on your company have used it, so I don't think it should be a problem.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
Energy Rom seemed pretty efficient on gb, others on your company have used it, so I don't think it should be a problem.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
i was gonna say use energy for GB but i didn't wanna be wrong again thanks for helping him bro
Jay_Rulen said:
i was gonna say use energy for GB but i didn't wanna be wrong again thanks for helping him bro
Click to expand...
Click to collapse
We tried upgrading him to ICS jay, remember the thread with over a 100 post? Lol Unless we get a mobilicity GB stock ruu magically somehow or my theory actually works, there's no way he can upgrade unless he s-off's the device.
By the way, there's never a wrong answer, if you have an opinion say it, that's why we're all here, to help each other.
Jay_Rulen said:
Ask Dark Nightmare he's a BEAST at these thing also there's like 2 thread about this already update to ICS from GB JUST READ READ RAED n yaaa RAED SOME MORE i always thought Canadians like tyo read my 2ex loved to read maybe cause there girls lol but
use apps from the market like this one https://play.google.com/store/apps/details?id=com.latedroid.juicedefender&hl=en juice defender
Click to expand...
Click to collapse
I dont like apps like that.
Remember my other thread where I could upgrade to ICS?
Dark Nightmare said:
Energy Rom seemed pretty efficient on gb, others on your company have used it, so I don't think it should be a problem.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Thank you I will check out the thread on Energy Rom.
Dark Nightmare said:
We tried upgrading him to ICS jay, remember the thread with over a 100 post? Lol Unless we get a mobilicity GB stock ruu magically somehow or my theory actually works, there's no way he can upgrade unless he s-off's the device.
By the way, there's never a wrong answer, if you have an opinion say it, that's why we're all here, to help each other.
Click to expand...
Click to collapse
THIS is WHY i RESPECT YOU s-off is so easy now i let my 6yr daughter do it for my friends amaze even a child can do it hahahahaha but ya i know but i still didn't wanna give him a wrong answer then brick his phone it happened to me when i was on nexus one ahole semi bricked my phone but it was people like you who made me LOVE the xda members so THANKS LIGHT Nightmare lol you don'r scare me anymore hahaha i'm stupid hahaha
Jay_Rulen said:
THIS is WHY i RESPECT YOU s-off is so easy now i let my 6yr daughter do it for my friends amaze even a child can do it hahahahaha but ya i know but i still didn't wanna give him a wrong answer then brick his phone it happened to me when i was on nexus one ahole semi bricked my phone but it was people like you who made me LOVE the xda members so THANKS LIGHT Nightmare lol you don'r scare me anymore hahaha i'm stupid hahaha
Click to expand...
Click to collapse
Yea he is definitely a great dude. Makes me feel more welcomed here.
Found the rom here http://forum.xda-developers.com/showthread.php?t=1362759&highlight=energy
It is dloadng at 1kB/s though 13 days to complete
Jay_Rulen said:
THIS is WHY i RESPECT YOU s-off is so easy now i let my 6yr daughter do it for my friends amaze even a child can do it hahahahaha but ya i know but i still didn't wanna give him a wrong answer then brick his phone it happened to me when i was on nexus one ahole semi bricked my phone but it was people like you who made me LOVE the xda members so THANKS LIGHT Nightmare lol you don'r scare me anymore hahaha i'm stupid hahaha
Click to expand...
Click to collapse
Lol at being scared of me, I'm still a kid dude, well kinda, I can legally drink but I don't look like it . Glad to see you guys love it here like I do, Been here a few weeks, probably a month now, I'm no beast, I'm just crazy enough to try things and pass my experience on.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
skugpezz said:
Yea he is definitely a great dude. Makes me feel more welcomed here.
Found the rom here http://forum.xda-developers.com/showthread.php?t=1362759&highlight=energy
It is dloadng at 1kB/s though 13 days to complete
Click to expand...
Click to collapse
It's hosted on a dev site, loads of people downloading, sorry I can't find you a faster link, give it some time or retry downloading, speed should pick up a bit as the load no the server eases.
Dark Nightmare said:
Lol at being scared of me, I'm still a kid dude, well kinda, I can legally drink but I don't look like it . Glad to see you guys love it here like I do, Been here a few weeks, probably a month now, I'm no beast, I'm just crazy enough to try things and pass my experience on.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
It's hosted on a dev site, loads of people downloading, sorry I can't find you a faster link, give it some time or retry downloading, speed should pick up a bit as the load no the server eases.
Click to expand...
Click to collapse
Retried and it is going a little faster now.
I also found this rom http://forum.xda-developers.com/showthread.php?t=1433078
I think I like it more than the energy rom. It seems a little more complicated to install with faux kernel etc. Also there are no instructions there.
Could you give me some guidance on how to install this?
Also do I need to unlock my bootloader?
skugpezz said:
Retried and it is going a little faster now.
I also found this rom http://forum.xda-developers.com/showthread.php?t=1433078
I think I like it more than the energy rom. It seems a little more complicated to install with faux kernel etc. Also there are no instructions there.
Could you give me some guidance on how to install this?
Also do I need to unlock my bootloader?
Click to expand...
Click to collapse
You'll need your bootloader unlocked for any rom installation or the recovery won't be able to write certain files. I'll be checking out the other rom in a minute.
Edit: The flashing of that rom is the same as any other, you wipe all partitions then flash the rom, faux kernel is OPTIONAL, you don't have to flash it, but it seems it's a part of the rom, once you're using 4EXT recovery, it's gonna flash the kernel for you, just make sure you make a nandroid backup of your current set up so if the flashing fails, you can always wipe and restore your old system so that you don't end up with an expensive paper weight, always remember to have a backup.
Dark Nightmare said:
You'll need your bootloader unlocked for any rom installation or the recovery won't be able to write certain files. I'll be checking out the other rom in a minute.
Edit: The flashing of that rom is the same as any other, you wipe all partitions then flash the rom, faux kernel is OPTIONAL, you don't have to flash it, but it seems it's a part of the rom, once you're using 4EXT recovery, it's gonna flash the kernel for you, just make sure you make a nandroid backup of your current set up so if the flashing fails, you can always wipe and restore your old system so that you don't end up with an expensive paper weight, always remember to have a backup.
Click to expand...
Click to collapse
I can do a nandroid back with rom manager?
Does full wipe actually wipes everything including the OS from the phone?
Should I use Hasoons tool to flash the EXT recovery?
skugpezz said:
I can do a nandroid back with rom manager?
Does full wipe actually wipes everything including the OS from the phone?
Should I use Hasoons tool to flash the EXT recovery?
Click to expand...
Click to collapse
Yes, use hasoon's tool and get 4EXT, do the nandroid backup on 4EXT using the backup/restore option, don't use rom manager and yes a full wipe formats all the partitions leaving nothing on the device system partition, you can find that in the format options. Just be sure to flash the new rom before rebooting.
Dark Nightmare said:
Yes, use hasoon's tool and get 4EXT, do the nandroid backup on 4EXT using the backup/restore option, don't use rom manager and yes a full wipe formats all the partitions leaving nothing on the device system partition, you can find that in the format options. Just be sure to flash the new rom before rebooting.
Click to expand...
Click to collapse
Thanks, I am going to flash the energy rom right now first. It finished downloading before the others.
skugpezz said:
Thanks, I am going to flash the energy rom right now first. It finished downloading before the others.
Click to expand...
Click to collapse
Kewl, happy testing, good idea to test, let's you find something you like easier, :thumbsup:.
Dark Nightmare said:
Kewl, happy testing, good idea to test, let's you find something you like easier, :thumbsup:.
Click to expand...
Click to collapse
Flashed the 4EXt and doing nandroid backup now.
Will wipe erase my external sd?
skugpezz said:
Flashed the 4EXt and doing nandroid backup now.
Will wipe erase my external sd?
Click to expand...
Click to collapse
Nope.
Dark Nightmare said:
Nope.
Click to expand...
Click to collapse
Sorry I am confused again . Dont want to brick the phone.
I see allot of wipe options do I select "format all partitions except sdcard"?
Or do I select "wipe/factory reset"?
EDIT: I think I should do factory reset wipe... fingers crossed.
skugpezz said:
Sorry I am confused again . Dont want to brick the phone.
I see allot of wipe options do I select "format all partitions except sdcard"?
Or do I select "wipe/factory reset"?
EDIT: I think I should do factory reset wipe... fingers crossed.
Click to expand...
Click to collapse
Nope, wipe all except sd, you did have the rom on your sd card right?
Once wiping, select install from sd card, choose the rom file and let it do it's magic.
Dark Nightmare said:
Nope, wipe all except sd, you did have the rom on your sd card right?
Once wiping, select install from sd card, choose the rom file and let it do it's magic.
Click to expand...
Click to collapse
There is no option for "wipe all except sd".
I see "wipe data/factory reset" . Clicking that it asks "wipe data, cache and sd-ext partition?". I have two options yes or no.
Seems it is goign to wipe my sd card.
The rom is on my sd card.