HKTW 2.3.4 Major Touch Bug!! - Atrix 4G Q&A, Help & Troubleshooting

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.

Related

[Q] Help!!! ugrent!!!

I have Bricked my phone edditing system folder permissions...
REGREATED ROOTING EVER SINCE
Any way to fix it its simply the phone keeps rebooting with a red light blinking and the M sign dual core stuck
Ive tried 2 methods but they didnt work!! :'(
Rsd method
and the abd method i didnt fully understand because im still nubbish
sbf should fix this, after flash is complete if it still bootloops your probably using a service sbf so will need to enter android recovery and manually clear data etc. to do this hold volume down while turning on device, then keep pressing it till it says android recovery, press volume up, then you have to tap the bottom right corner to show the options when the android logo appears
Hi all I am in the same boat I followed the briefmobile instructions http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
Tried the Android recovery deleting cash and installing from SD but I keep getting failed authentication (or something like that)
Can anybody help or post a topic that can lead me in the right direction
ears1991 said:
sbf should fix this, after flash is complete if it still bootloops your probably using a service sbf so will need to enter android recovery and manually clear data etc. to do this hold volume down while turning on device, then keep pressing it till it says android recovery, press volume up, then you have to tap the bottom right corner to show the options when the android logo appears
Click to expand...
Click to collapse
Ive done this and it hasnt worked 0.0
heyhey24 said:
Ive done this and it hasnt worked 0.0
Click to expand...
Click to collapse
which sbf are you using?
ears1991 said:
which sbf are you using?
Click to expand...
Click to collapse
stock US att 1.8.3 with 2.2.2 froyo installed a couple of root apps
heyhey24 said:
stock US att 1.8.3 with 2.2.2 froyo installed a couple of root apps
Click to expand...
Click to collapse
download and try: http://www.megaupload.com/?d=IJC7SGJZ or http://www.megaupload.com/?d=0AH1MQDS
Id be suprised if neither worked
do i still get ota updates?
Also im longing to try the gingerbread atrix leak so do you think you could help me with that?
yes you will still get ota updates
i wouldnt recommend you trying the gingerbread stuff without doing A LOT of reading first, id just wait for it to arrive ota personally rather than risk messing your phone up again
What I don't get is that people edit random things and break their phones. Why did you change the permissions?
Sent from my Nexus S using XDA App
Question do you use Android Recovery or RSD or Fastboot? with the 1.8.3 file
I tried it cause I got the unlock and bootloader without any issue. so i was daring.....
you speak the truth lol
yea its comming this month anyway an the moth is have over
Not to sounds lik an idiot but can you tell me how to sbf because i think im doing it badly or something using rsq or something like that
http://briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
scroll down for guide
dario3040 said:
What I don't get is that people edit random things and break their phones. Why did you change the permissions?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
because i needed it for emoji but i guess i screwed up huh? lol
OmniMoAK said:
Question do you use Android Recovery or RSD or Fastboot? with the 1.8.3 file
I tried it cause I got the unlock and bootloader without any issue. so i was daring.....
Click to expand...
Click to collapse
...RSD and tried using android recovery to restore
RSD dosent recognize my phone ...
nevermind E-FAIL on my part
THANK YOU ALL YOU AMAZING AND TALENTED PEOPLE ON THE FORUMS IF ANYTHING GOES WRONG DURING THE PROCESS ILL CONTACT YOU LOVE YOU GUYS N THANKS FOR LETTING ME INTO MY NEW HACK HOME ... ANDROID AND XDA
OK new problem now I am out of battery, and I cant do anything to charge it. So the only thing I can do is in Android recovery but I cant find a update.zip file that will authenticate. Any ideas on how to get the battery charged? and where to get a update.zip that will work?
please help I know I may of hijacked this thread but it is a similar situation.

[Q] Going from gingerblur to 2.3.4

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

[Q] Tried going back to OTA 4.5.91 via RSDLite, stuck in boot-loop, can't get out.

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

(Solved) Stuck to Dual core logo....

Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Cooldevil1989 said:
Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Click to expand...
Click to collapse
sbf back to stock and do a factory/data reset (if it bootloops after sbf). then you should be good to go.
also it seems that that latest update is bricking lots of peoples phones!
na7q said:
sbf back to stock and do a factory/data reset (if it bootloops after sbf). then you should be good to go.
also it seems that that latest update is bricking lots of peoples phones!
Click to expand...
Click to collapse
as the OP states he is on the latest 2.3.5. update there is no sbf yet.
Cooldevil1989 said:
Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Click to expand...
Click to collapse
I had a similar issue. Through a long list of things that I tried, I was able to get back in. However, WIFI does not work at all, and none of the fixes posted here have worked.
Did you have bootstrap and a backup prior? That would be helpful for you. Try cold booting through linux. If that alone doesn't work, here is what I did. I cold booted though linux to get in after using the us cellular SBF, then I was able to restore my backup. Again, this got me back into the phone, but no WIFI.
Not sure if that helps at all.
chris.carstens said:
I had a similar issue. Through a long list of things that I tried, I was able to get back in. However, WIFI does not work at all, and none of the fixes posted here have worked.
Did you have bootstrap and a backup prior? That would be helpful for you. Try cold booting through linux. If that alone doesn't work, here is what I did. I cold booted though linux to get in after using the us cellular SBF, then I was able to restore my backup. Again, this got me back into the phone, but no WIFI.
Not sure if that helps at all.
Click to expand...
Click to collapse
Thanx for your reply.....
But can u please tell me how to try cold booting through linux. & then what to do???
Sorry as I am noob to photon ...
Cooldevil1989 said:
Thanx for your reply.....
But can u please tell me how to try cold booting through linux. & then what to do???
Sorry as I am noob to photon ...
Click to expand...
Click to collapse
Sorry, I can't remember for sure. (and my wife is not letting me touch her phone, who can blame her) But I think it was vol. up and power until you get some words on the screen. Then scroll thought the options and select the correct one.
sorry, I'm a noob also, and I can't check right now.
chris.carstens said:
Sorry, I can't remember for sure. (and my wife is not letting me touch her phone, who can blame her) But I think it was vol. up and power until you get some words on the screen. Then scroll thought the options and select the correct one.
sorry, I'm a noob also, and I can't check right now.
Click to expand...
Click to collapse
ok... buddy....thanx for your reply....
I am going to copy/paste this.
This will recover from brick, when you are permanently locked on Photon after 2.3.5 OTA update.
Take USC_19 full sbf from 2.3.5 sv2 custom sbf thread, flash that, wipe data in recovery, root it, install bootstrap recovery.
After that, you can flash mof 2.3.5ish rom or my rom (locked).
Then install bootstrap recovery again, if it's not preinstalled there. And flash 254_13 modules. After that flash 2.3.5sv2 unbrick sbf with 254_13 boot, recovery and cdrom. If you have no radio service, flash 254_12 libmoto_ril.so.
Here is the thread he copied that from. http://forum.xda-developers.com/showthread.php?t=1798145
Hopefully we both can solve our problems with that.
Thanx to u peetr_ sir..... great... help... nw my photon is perfectly workng....
Sent from my MB855 using xda app-developers app

[Q] Need Serious Help Troubleshooting a Problem

Anybody that thinks they are one of the best if not the TOP troubleshooting helper around, Please let me know if you are available after 5 today. I dont have a lock screen anymore and when I hold the power button down, the device shuts off instead of having the options to reboot, power down, screen shot, whatever else available. I am rooted, but I did try going back to stock and had no luck with the lock screen. Also, I cound a backup on a different MicroSD card and tried to restore that. It worked fine, but never gave me the lock screen or power down options again. Weather you want to talk on the phone, chat, or email. Please reply here or email me at [email protected] Thank You!
Sorry but we don't have a ranking system here. You get what you get . . .
The power off menu is in the framework of the OS. Have you flashed anything with CWM/TWRP that could have changed the framework? Almost any mod could be a possible cause.
Did you use a theme-setting app? These apps change the framework and that includes the lock screen too.
Have you restored a backup recently?
Post your rom version and apps you installed recently.
rangercaptain said:
Sorry but we don't have a ranking system here. You get what you get . . .
The power off menu is in the framework of the OS. Have you flashed anything with CWM/TWRP that could have changed the framework? Almost any mod could be a possible cause.
Did you use a theme-setting app? These apps change the framework and that includes the lock screen too.
Have you restored a backup recently?
Post your rom version and apps you installed recently.
Click to expand...
Click to collapse
I'm sorry you felt the need to take what i said the way you did. I was simply stating what i said the way i did because nobody could ever help me with this. I am currently rooted on stock ics. I didn't even have a lock screen after i flashed back to stock on Odin, then used kies to get the latest ics. It doesn't make sense. Do Tippy have any idea how i could put this back to normal? It's a pain having to rely on go locker and go launcher. Also, when i hold the power button down, the phone just shuts down, with no options like normal. It's crazy. I appreciate your help either way. It won't let me flash a different ROM right now. Gives some error. I just want to be fully stock with a lock screen and power menu options them go from there.
brandon440 said:
I'm sorry you felt the need to take what i said the way you did. I was simply stating what i said the way i did because nobody could ever help me with this. I am currently rooted on stock ics. I didn't even have a lock screen after i flashed back to stock on Odin, then used kies to get the latest ics. It doesn't make sense. Do Tippy have any idea how i could put this back to normal? It's a pain having to rely on go locker and go launcher. Also, when i hold the power button down, the phone just shuts down, with no options like normal. It's crazy. I appreciate your help either way. It won't let me flash a different ROM right now. Gives some error. I just want to be fully stock with a lock screen and power menu options them go from there.
Click to expand...
Click to collapse
If you push the power button in and it reboots, can't you just hold the middle of the volume rocker in at the same time to get into recovery?
Sent from my SAMSUNG-SGH-I717 using xda premium
dafoxs said:
If you push the power button in and it reboots, can't you just hold the middle of the volume rocker in at the same time to get into recovery?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Well yeah but what does that have to do with anything? It doesn't help at all. That doesn't fix any of my problems. This problem is much more complex. The issue is that my phone is not as it normally should be..with options after holding down the power button, and with no lock screen...even after successfully going back to stock, these things were missing...
brandon440 said:
Well yeah but what does that have to do with anything? It doesn't help at all. That doesn't fix any of my problems. This problem is much more complex. The issue is that my phone is not as it normally should be..with options after holding down the power button, and with no lock screen...even after successfully going back to stock, these things were missing...
Click to expand...
Click to collapse
Since you can't go back to stock,
Flash a rom, it should install those missing things.
Or mess it up worse and take it back for a new one.
Sent from my SAMSUNG-SGH-I717 using xda premium
dafoxs said:
Since you can't go back to stock,
Flash a rom, it should install those missing things.
Or mess it up worse and take it back for a new one.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
It won't let me flash another ROM. Gives me Assn error and doesn't go through. If i try returning the device with the flash counter where it's at, won't that be an issue? I can't go without the device. I use it for too much. Maybe i could figure out how to reset flash counter? Idk..i just need this fixed bad
This maybe a dumb thought but can you use kies and install the original ICS again? I know you mentioned backups didn't work so reinstalling original ICS probably won't worj either. Just a thought.
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
This maybe a dumb thought but can you use kies and install the original ICS again? I know you mentioned backups didn't work so reinstalling original ICS probably won't worj either. Just a thought.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I thought I already mentioned this but I already tried that. It does not work. It sucks man. Nothing seems to work. I wonder if there is somebody who could walk me through the troubleshooting of the whole system or soemthing. I know if I try to contact AT&T about it they will laugh at me and not be able to help me. If anybody knows the ins and outs of the framework or anybody could even show me where to look and what needs to be there that isnt..even terminal emulator...anything...I appreciate everybody trying to help me so far but nothing has helped yet Thank you though and thank you to anybody who from here on out tries to help me. I know I will tell you again too.
brandon440 said:
I thought I already mentioned this but I already tried that. It does not work. It sucks man. Nothing seems to work. I wonder if there is somebody who could walk me through the troubleshooting of the whole system or soemthing. I know if I try to contact AT&T about it they will laugh at me and not be able to help me. If anybody knows the ins and outs of the framework or anybody could even show me where to look and what needs to be there that isnt..even terminal emulator...anything...I appreciate everybody trying to help me so far but nothing has helped yet Thank you though and thank you to anybody who from here on out tries to help me. I know I will tell you again too.
Click to expand...
Click to collapse
Are you going back to stock ICS or gingerbread? I would Odin back to gingerbread and start brand new. This will solve any major issue for sure. But only do it if you have the things you need to get back to where you are, like the GB root, cwm or twrp, and your roms. Let me know if that helps
truth77 said:
Are you going back to stock ICS or gingerbread? I would Odin back to gingerbread and start brand new. This will solve any major issue for sure. But only do it if you have the things you need to get back to where you are, like the GB root, cwm or twrp, and your roms. Let me know if that helps
Click to expand...
Click to collapse
I can let you know up front this did not work. I did this in the beginning. Went back to stock GB then had to use Kies to get to ICS. This did not help my issue/problem at all. Still no lock screen. It sucks. I am almost lost for help here it seems. Is there any way to completely reset the device from the beginning? Or again, any way to get help with everything in the actual framework of the whole device? Anything anybody could do to help me with would be amazing. Thank you for everything again!
Try this, not sureb if it fits your issue 100%.
http://forum.xda-developers.com/showthread.php?t=1870561
Sent from my SAMSUNG-SGH-I717 using xda premium
brandon440 said:
I can let you know up front this did not work. I did this in the beginning. Went back to stock GB then had to use Kies to get to ICS. This did not help my issue/problem at all. Still no lock screen. It sucks. I am almost lost for help here it seems. Is there any way to completely reset the device from the beginning? Or again, any way to get help with everything in the actual framework of the whole device? Anything anybody could do to help me with would be amazing. Thank you for everything again!
Click to expand...
Click to collapse
Idk but I did warranty claim with one of my notes and Samsung didn't say anything about the flash counter after. But they also sent me the new phone first then I sent mine back, but like I said they didn't say anything after.
but now that I think about it, the lock screen is not a device issue. it comes different in every ROM in the framework res.apk! I don't see how that's even possible? The entire frameworks flash and the device can't on its own decide not to install that especially not on stock GB. For you to Odin back to GB and not have a lock screen on GB is just crazy. Nothing out there I'm aware of can do that and not brick the device. You have to bring that device back foreal. That's screwed and if you do fix that pm me and tell me how!
truth77 said:
Idk but I did warranty claim with one of my notes and Samsung didn't say anything about the flash counter after. But they also sent me the new phone first then I sent mine back, but like I said they didn't say anything after.
but now that I think about it, the lock screen is not a device issue. it comes different in every ROM in the framework res.apk! I don't see how that's even possible? The entire frameworks flash and the device can't on its own decide not to install that especially not on stock GB. For you to Odin back to GB and not have a lock screen on GB is just crazy. Nothing out there I'm aware of can do that and not brick the device. You have to bring that device back foreal. That's screwed and if you do fix that pm me and tell me how!
Click to expand...
Click to collapse
Will do. You see why it's crazy now!? It's ridiculous! Never heard of or seen this problem ever..I'm not new to Android or Android troubleshooting atall. Just this blows my mind!
There is no warranty issue here.
I asked several questions about what you have done, but you didn't inform us.
You never said what recovery you have. The simplest solution is to reboot into recovery, wipe all caches, factory reset, then flash a stock rom.
If you can't do that I would use Odin to flash a stock rom.
Those are your options.
rangercaptain said:
There is no warranty issue here.
I asked several questions about what you have done, but you didn't inform us.
You never said what recovery you have. The simplest solution is to reboot into recovery, wipe all caches, factory reset, then flash a stock rom.
If you can't do that I would use Odin to flash a stock rom.
Those are your options.
Click to expand...
Click to collapse
I have tried to answer every single question to the best of my ability. Sorry I did not answer your question properly. I was on CWM recovery but Just now again I flashed back to STOCK using Odin. Meaning I have stock recovery. I still DO NOT HAVE a lock screen or any options when shutting the phone down. Those "options" you gave me are no longer available. I did all that. I am about to try to go to a friends house to flash to ICS using Kies...which still will give me no lock screen or options when holding down the power button. There is obviously a deeper problem here. I hope somebody could help me solve this issue. Please I am begging here It is horrible!
http://forum.xda-developers.com/showthread.php?t=1506330
This is what I just did. Also, I have been looking at this http://forum.xda-developers.com/showthread.php?t=1504218 wondering if I should try this next. Either way, I am not getting a lock screen or options when I hold down the power button. Please help Anybody!
Why isn't flashing a stock rom using Odin not an option? Odin is the pc software Samsung created and uses for their work.
Kies didn't work -- try Odin3 1.85
rangercaptain said:
Why isn't flashing a stock rom using Odin not an option? Odin is the pc software Samsung created and uses for their work.
Kies didn't work -- try Odin3 1.85
Click to expand...
Click to collapse
Again, I feel like a broken record by repeating this SEVERAL times but Flashing Back To Stock Using ODIN Does Not Work! I just said that I did this in my post before last. I finally have managed to get cm10 nightly to flash on my device. When I flashed this, it gave me the lock screen back along with options when I hold down the power button. Thank you all for your help anyways. I guess this is as good as it will get.
When you flash a rom with Odin, it reformats your phone, like a clean slate, then installs the new system.
When you say you flashed back to stock, did you use a .pit file, a .tar file, and a .bin file? If not, you are not flashing back to stock -- you're just adding up a mess in your phone.
If you use Kies, then use the emergency firmware recovery, it will supposedly do the same thing as a correct Odin flash -- reformat then install a clean stock rom.

Categories

Resources