[Motorola Atrix 2] black_panther10:
Hi,

http://xdaforums.com/showthread.php?t=1865582

I earlier posted this thread, but at that time I was not sure of so many things and what exactly was wrong with my phone.

But now after trying for about a week or so I have got most of the things figured out

So here it goes....

I was not able to install the OTA 2.3.6 update by any means possible.(I was on 2.3.5 all the time and I am still on 2.3.5 only)

So, I tried to unlock my phone using the 2.3.6 one click method(I am not sure why I thought it will help with installing the update)....I dont exactly remember it worked or not.

I was still not able to install the update. So, I thought lets get to stock and then try it again.

So, I followed this post to get back to stock 2.3.5

http://xdaforums.com/showthread.php?t=1396650

I tried to create the back up first using this guide

http://xdaforums.com/showthread.php?t=1511616

I installed ATRIX2 BOOTSTRAP but I rebooted it never rebooted in Clockworkmod Recovery mode.

So , I was not able to create any backup.

But, when I tried to use the RSD lite to install the 2.3.5 firmware back to the phone it failed with this error

Failed flashing process: Failed flashing process 3/20 flash mbmloader "mbmloader.bin" -> Phone returned FAIL ;phone connected"

After this I was rebooting all the time in AP fast boot mode only and had to select normal reboot to use my phone....but everything kept on crashing after this...many processes were force closing....but I was still able to make calls and playing music.

Then I came across the http://xdaforums.com/showthread.php?t=1539167 return to stock script... it was able to write everything except this < waiting for device >

sending 'mbmloader' (39 KB)... OKAY [ 0.005s]

writing 'mbmloader'... INFOCommand restricted

FAILED (remote: ) (you can see the complete output in my previous post link above)

The script fixed the always booting in fastboot mode. But still rest of the things were the same all processes force closing

But, it was so irritating I had to restart my phone every few hours because some critical android process was force closed. sometimes the contacts were not loaded etc.....

So, I posted the previous thread on this forum asking help, but since I was not very precise about the problem I think people were not able to help me.

So, what actually I have figured out is my complete phone memory is in read only mode...I don't know which of the above things would have did this. Well, if you ask me how I know this... I used the es file explorer to go into the system dir deleted some files rebooted and they were back there. I tried the adb shell and tried to set the permission but it failed saying the file system is read only.

Also, when I try the root.bat file its saying this...

2100 KB/s (501292 bytes in 0.233s)

[*] Motofail: Universal Motorola Android Root Exploit

[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)

[*] Exploit complete.

[*] Done. Rebooting device...

[*] Done. Pushing su and Superuser to device...

failed to copy 'su' to '/system/xbin/su': Read-only file system

Unable to chmod /system/xbin/su: Read-only file system

link failed File exists

failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy

stem

[*] Done. Cleaning up exploit...

/data/local/motofail: not found

rm failed for /data/local/motofail, No such file or directory

and when I try the unroot file it says that it is not able to find Superuser.apk and it finds xbin/su but it cannot remove it saying file system is readonly

Please help me get out of this problem...I have looked around the internet but I have not found any solution.

Also, here is the system info of my phone

System Version: 55.11.16.MB865.ATT.en.US

Android Version:2.3.5

Kernel Version: 2011-09-21 09:42 off.Bld LUD_EDISON_RLD7_PATCH_27_110921_0913

Build number:5.5.1-175 EDEFW1-16

All I want is to somehow get the file system out of the read only mode so that I get unroot the phone and get it repaired form the motorola people only....I cannot give them this rooted phone since they ill just return it saying the warranty is void since its rooted.

OR it would be much much better if someone can figure out what the problem is and I can just get back to stock....:)

Thanks in advance guys....I hope someone will be able to figure out what I did wrong.