I can't copy any files to frameworks file - Atrix 4G Q&A, Help & Troubleshooting

Hello every one,
I upadated my Bell Atrix to 2.3.4 gingerbread and I rooted but when i try to copy some files to frameworks file but i can't because the file is read only
how i can solve this issue ?

Messi 10 said:
Hello every one,
I upadated my Bell Atrix to 2.3.4 gingerbread and I rooted but when i try to copy some files to frameworks file but i can't because the file is read only
how i can solve this issue ?
Click to expand...
Click to collapse
You need to remount the filesystem to be writable. Use "adb shell" to do the following:
Code:
$ su // Be sure to allow superuser if prompted on the handset
# /bin/mount -o rw,remount /system
At this point, you should be able to copy files to /system.
Hope this helps.

Thank you kwick60073
Now after I do your solution it is work but i tried to copy some files to lib folder but my atrix shutdown and i opened the battery when i return it my cellphone show just motorloa logo !
how i can solve this issue
regards

Messi 10 said:
Thank you kwick60073
Now after I do your solution it is work but i tried to copy some files to lib folder but my atrix shutdown and i opened the battery when i return it my cellphone show just motorloa logo !
how i can solve this issue
regards
Click to expand...
Click to collapse
Are you doing this on PC or terminal?

by using root explorer app

I think I soft bricked my phone
Hello Evryone, I was in the process of trying to root my phone and I think I soft bricked it. I had done this once before with another atrix that had to get replaced. This was before the Gingerbread update. I went to the same site and tried the same method and somewhere it messed up. I've scoured the internet for the past 2 days trying to find something similar but I haven't found something that matches my case to the point that I'm comfortable taking a risk trying to follow their steps to fix it. The reason I'm posting this is because most of the recovery fixes I've found on the internet are from March, before the gingerbread update.
So here is exactly what I'm looking at. I now have the following text on the screen:
SVF:105:1:2
Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop count down
Available modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 console-ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
---------------------------------------
Vol Up to select, Vol Down for next choice
Current choice is mode:
RSD
Starting Fastboot protocol support
I have downloaded RSDLite5.4.4 and SuperOneClick. I'm just not sure how to use them. I recognize I'm a noob and I am sorry if this is a redundant post, but if I could get any help at all, I would greatly appreciate it. Thank you so much in advance.

CantoErgoSum said:
Hello Evryone, I was in the process of trying to root my phone and I think I soft bricked it. I had done this once before with another atrix that had to get replaced. This was before the Gingerbread update. I went to the same site and tried the same method and somewhere it messed up. I've scoured the internet for the past 2 days trying to find something similar but I haven't found something that matches my case to the point that I'm comfortable taking a risk trying to follow their steps to fix it. The reason I'm posting this is because most of the recovery fixes I've found on the internet are from March, before the gingerbread update.
So here is exactly what I'm looking at. I now have the following text on the screen:
SVF:105:1:2
Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop count down
Available modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 console-ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
---------------------------------------
Vol Up to select, Vol Down for next choice
Current choice is mode:
RSD
Starting Fastboot protocol support
I have downloaded RSDLite5.4.4 and SuperOneClick. I'm just not sure how to use them. I recognize I'm a noob and I am sorry if this is a redundant post, but if I could get any help at all, I would greatly appreciate it. Thank you so much in advance.
Click to expand...
Click to collapse
Go into the dev forum and download the pudding file that corresponds with your phone. Flash it, then boot into fastboot and use the command fastboot OEM unlock
Sent from my MB860 using xda premium

Related

[Q] Hard brick.. 14 Options

Tried Flashing the pudding unlock through rsd. Didnt go so well. I have the same failed to boot 0x1000 error along with:
no os detected going to rsd mode in 5 seconds press a key to stop count down:
1 Rsd
2 Flash boot
3 NvFlash
4 BP HW Bypass Rsd
5 BP Hw Bypass Qc DLOAD
6 BP HW diag & Boot Ap
7 BP HW Bypass BP only
8 BP Sw Bypass RSD
9 Android recovery
10 Boot Android (no BP)
11 Device UID
12 Console=****,***
13 Early Usb Enumeration
14 BP tools
Is there anything I can Do?
Sthony said:
Tried Flashing the pudding unlock through rsd. Didnt go so well. I have the same failed to boot 0x1000 error along with:
no os detected going to rsd mode in 5 seconds press a key to stop count down:
1 Rsd
2 Flash boot
3 NvFlash
4 BP HW Bypass Rsd
5 BP Hw Bypass Qc DLOAD
6 BP HW diag & Boot Ap
7 BP HW Bypass BP only
8 BP Sw Bypass RSD
9 Android recovery
10 Boot Android (no BP)
11 Device UID
12 Console=****,***
13 Early Usb Enumeration
14 BP tools
Is there anything I can Do?
Click to expand...
Click to collapse
I'm not entirely sure if this is what you need to do, but...I had 1.83 stock locked, then used the the OTA 2.3.4 zip, then I flashed the Pudding through RSD 5.3.1, and finally I had to use the "moto-fastboot oem unlock" command to unlock my device. I believe I got the same error before doing the unlock command. Confirm with someone else besides me. I don't want to be responsible for anything you do.
Sthony said:
Tried Flashing the pudding unlock through rsd. Didnt go so well. I have the same failed to boot 0x1000 error along with:
no os detected going to rsd mode in 5 seconds press a key to stop count down:
1 Rsd
2 Flash boot
3 NvFlash
4 BP HW Bypass Rsd
5 BP Hw Bypass Qc DLOAD
6 BP HW diag & Boot Ap
7 BP HW Bypass BP only
8 BP Sw Bypass RSD
9 Android recovery
10 Boot Android (no BP)
11 Device UID
12 Console=****,***
13 Early Usb Enumeration
14 BP tools
Is there anything I can Do?
Click to expand...
Click to collapse
If you can get into RSD protocol, flash 4.1.57 full sbf, update to 4.1.83, try again.
OSNPA said:
If you can get into RSD protocol, flash 4.1.57 full sbf, update to 4.1.83, try again.
Click to expand...
Click to collapse
I can get into RSD. But i updated through the OTA 2.3.4 zip. Im not to sure if its safe to flash older SBF files.
Its safe as long as u used kenneth version
Sent from my MB860 using XDA Premium App
unknownerr said:
I'm not entirely sure if this is what you need to do, but...I had 1.83 stock locked, then used the the OTA 2.3.4 zip, then I flashed the Pudding through RSD 5.3.1, and finally I had to use the "moto-fastboot oem unlock" command to unlock my device. I believe I got the same error before doing the unlock command. Confirm with someone else besides me. I don't want to be responsible for anything you do.
Click to expand...
Click to collapse
Thanks.. Had really nothing to lose, so i took the gamble. Finished with the fastboot unlock by navigating through the options. Unlocked the BL.Then the phone rebooted back to gingerbread.
Xenocyde said:
Its safe as long as u used kenneth version
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
No I updated through System recovery.
kenneth version worked for me!
Your lucky you didn't flash any sbfs because you would have hard bricked. Good call on finishing unlock that's exactly how I had to do it. For anyone else if you flashed the ota don't flash any sbfs.
Sent from my MB860 using Tapatalk
I really throws the same error, what should I do? what is the easiest method
fix? thanks
Jnewell05 said:
Your lucky you didn't flash any sbfs because you would have hard bricked. Good call on finishing unlock that's exactly how I had to do it. For anyone else if you flashed the ota don't flash any sbfs.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Just so we're all on the same page, it IS alright to flash fruit cakes. Just a side note...
in this thread talking about flash version 4.1.57 of Kenneth (correct?), someone could help me a bit because they do not find it.

Need help really badly!!!!!!!! *ANYONE?!*

Ok so before I take my phone to the shooting range tomorrow. Can someone help me please?
I got this when I tried to flash the [HOWTO] Root any Atrix after .sbf flash. I got the following message when the SBF failed:
SVF: 105:1:2
Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 console=ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
--------------------------------------
Vol Up to select, Vol Down
for next choice
Current choice is:
RSD
Starting Fastboot protocol support
If I'm screwed then. I'm done buying phones with f**king locked bootloaders.....
And now the phone restarted and it got this message:
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot protocol support
Chubby_Skunk said:
Ok so before I take my phone to the shooting range tomorrow. Can someone help me please?
I got this when I tried to flash the [HOWTO] Root any Atrix after .sbf flash. I got the following message when the SBF failed:
SVF: 105:1:2
Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 console=ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
--------------------------------------
Vol Up to select, Vol Down
for next choice
Current choice is:
RSD
Starting Fastboot protocol support
If I'm screwed then. I'm done buying phones with f**king locked bootloaders.....
Click to expand...
Click to collapse
Choose option 2 and follow the instructions to unlock your bootloader. fastboot oem unlock then fastboot oem unlock xxxxxxxxxxxxx(your specific code goes there) it will then bootup.
Sent from my MB860 using XDA Premium App
jruweaver said:
Choose option 2 and follow the instructions to unlock your bootloader. fastboot oem unlock then fastboot oem unlock xxxxxxxxxxxxx(your specific code goes there) it will then bootup.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
God im a dumba**.......
thanks a bunch
Chubby_Skunk said:
God im a dumba**.......
thanks a bunch
Click to expand...
Click to collapse
how were you in "Failed to boot 0x1000" and then had fastboot ????
In my case I get "Failed to boot 0x1000" and some other message pops up at the end and then the phone shuts down
I had this same issue however when i try to unlock it i hear the usb disconnect noise and then it says "FAILED (remote00180001)). I did the exact same things as op up to this point,
maybe this would be the place to look - DEBUG] Calling all (AT&T) 0x1000 'hard' bricks
http://forum.xda-developers.com/showpost.php?p=15573674&postcount=1
I believe this issue has been resolved.
hakemcpu said:
In my case I get "Failed to boot 0x1000" and some other message pops up at the end and then the phone shuts down
Click to expand...
Click to collapse
BUMP... same here. trying to find a resolution before paying 125 for the insurance to replace it with a refurb.
itsauniquesn said:
BUMP... same here. trying to find a resolution before paying 125 for the insurance to replace it with a refurb.
Click to expand...
Click to collapse
Do you have the menu screen?
Sent from my MB860 using XDA App

No OS Detected -- simple fix?

Ok so I got this AT&T USA Atrix lastnight from craigslist, it was working fine and I tried to unlock it for T-Mobile. It's a model MB860
I looked for tutorials and see alot of outdated and confusing information, so I found one that instructed me to download RSD Lite and flash the phone with Pudding 4547-fix-try2.sbf. Well now the phone says
SVF:105:1:2
Failed to boot 0x0001
No OS Detected, going to RSD Mode in 5 seconds
Press a Key to stop count down
Available modes are:
1 RSD
2 Fastboot
3NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 Console=tty50,115200n8
13 Early USB Enumeration
14 BP Tools
and when I tried to Boot Android No BP it says (Magic Value Mismatch) Reading ODM Fuse 1
So what do I do now? I hope I didnt brick this thing, I just spent $160 on it and now I have no phone. Can someone tell me how to restore this please? Thank You very much.
Phonebricker said:
Ok so I got this AT&T USA Atrix lastnight from craigslist, it was working fine and I tried to unlock it for T-Mobile. It's a model MB860
I looked for tutorials and see alot of outdated and confusing information, so I found one that instructed me to download RSD Lite and flash the phone with Pudding 4547-fix-try2.sbf. Well now the phone says
SVF:105:1:2
Failed to boot 0x0001
No OS Detected, going to RSD Mode in 5 seconds
Press a Key to stop count down
Available modes are:
1 RSD
2 Fastboot
3NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery
10 Boot Android (No BP)
11 Device UID
12 Console=tty50,115200n8
13 Early USB Enumeration
14 BP Tools
and when I tried to Boot Android No BP it says (Magic Value Mismatch) Reading ODM Fuse 1
So what do I do now? I hope I didnt brick this thing, I just spent $160 on it and now I have no phone. Can someone tell me how to restore this please? Thank You very much.
Click to expand...
Click to collapse
The unlock process you started is for the bootloader. Sounds like you wanted a carrier unlock.
Right now you just need to finish unlocking the bootloader. If you don't have drivers, fastboot, etc already set up then I would recommend just using the Automatic Unlock tool. There is an option (#3) that deals with your exact situation. Also, there are dozens of posts dealing with this issue. Searching for 'unlock bootloader', 'SVF:105:1:2', or 'No OS Detected, going to RSD Mode in 5 seconds' should get you plenty of good info.
Here is a quick rundown of what to do manually:
1. Boot into fastboot
2a. Issue command: fastboot oem unlock
2b. Take note of the OEM number it displays for your phone.
3. Issue same command, but this time add the # from step 2b: fastboot oem unlock #######
This should finish the unlock process. See the pudding thread for pictures of what to expect.
Thank You very much Ghost_OG, that worked! Now my problem is that the phone booted up, I inserted my tmobile sim and it asked for a code, so I booted into recovery mode to attempt to flash a rom and the recovery mode showed a Chinese symbol instead of the CM symbol, but I accidentally erased the data partition and now when I try to flash the gingerbread rom from a .zip file on my sd card, it says its unable to mount external sd. So now Im stuck. It mounts internal memory fine, but I cant access the internal memory with my pc to put the image on it to flash. Damn. This is all new to me, the last phone I flashed regularly was the Google G1, so that show you how long ago that was. What can I do?
Phonebricker said:
Thank You very much Ghost_OG, that worked! Now my problem is that the phone booted up, I inserted my tmobile sim and it asked for a code, so I booted into recovery mode to attempt to flash a rom and the recovery mode showed a Chinese symbol instead of the CM symbol, but I accidentally erased the data partition and now when I try to flash the gingerbread rom from a .zip file on my sd card, it says its unable to mount external sd. So now Im stuck. It mounts internal memory fine, but I cant access the internal memory with my pc to put the image on it to flash. Damn. This is all new to me, the last phone I flashed regularly was the Google G1, so that show you how long ago that was. What can I do?
Click to expand...
Click to collapse
Easy fix (now that you're unlocked).
First thing first, your recovery. I'm assuming you installed the recovery that came with the Auto Unlock tool? That is a very outdated recovery. I recommend using romracer's. You want to d/l the .img file, not the zip. Put the recovery-atrix5.img file in your Auto Unlock folder and open a command prompt from that same directory. Follow the instructions from that thread to install.
At this point you can see if both internal/external are available while in recovery. You may need to mount them from within the recovery program. If you're able to access either, put the your zip back on the card and try to re-flash the ROM. Make sure to follow all install instructions from the ROM thread as well.
DAMN DUDE! That worked! I wasnt sure what you meant about putting that romracer img file in the folder an opening a command prompt from within there and updating it that way, so instead I renamed romracer's img file to that old one that was already in there and the batch file flashed it for me. From there, I mounted internal usb storage, dropped my rom in there, and viola! Good lookin Out Brother! I'll drink a beer for you! Sending some good karma your way. I really appreciate it.
Would this fix my Boot Loop
So I'm guessing this would fix my Boot Loop Thanks Guys.... (I'm unlocked and have an old recovery image file....) but the $#!T I'm in now is that I can't flash the romRacer recovery img for the simple reason that My battery is to low so I can't go into fastboot lolol...... I'm going to order and external charger to charge this damn Battery...
Or is there another way for me to charge my battery... because from what I'm seeing my battery does not charge during this bootloop...... in a way I don't mind buying it... but I just don't want to wait....
Phonebricker said:
Thank You very much Ghost_OG, that worked!
Click to expand...
Click to collapse
I have the same problem..... but I cannot read Ghost_OG's answer .... how could I read it?

[Q] Motorola atrix 4g giving SVF:105:1:2 error while trying to unlock bootloader

Hello ..
I was following the method given on the cyanogenmod website to unlock the bootloader and then install cm7 ... After i downloaded the files suggested i opened the RSD lite and selected the sbf file and pressed start when my phone rebooted it gave the following error ..
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop countdown
Available modes are:
1. RSD
2. Fastboot
3. NVFlash
4. BP HW Bypass RSD
5. BP HW Bypass QC Dload
6. BP Diag & boot AP
7. BP HW bypass BP only
8. BP SW bypass RSD
9. Andriod Recovery
10 .Boot andriod (No BP)
11. Device UID
12. console=ttyS0,115200n8
13. Early USB Enumeration
14..BP tools
i followed all the instructions clearly but dont know why it happened ... what should i do now .. ?
i am really scared i think i might have bricked my phone :crying: .. please help me out .. Please .. ...
Also i am a big noob .. this was my first time for unlocking a bootloader .. Also i rooted the phone successfully first ..
I found a thread on xda http://forum.xda-developers.com/showthread.php?p=25708728
It says that its a soft brick trying to follow the instructions but it isnt opening this file
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
And i cant find the atrix oem unlock anywhere on the internet ....
Kindly please help me out ...
I don't see a problem here. This is perfectly normal. Select fastboot and install custom recovery, then proceed to install ROM of choice. Also next time use search and read existing threads as this has been covered already.
ravilov said:
I don't see a problem here. This is perfectly normal. Select fastboot and install custom recovery, then proceed to install ROM of choice. Also next time use search and read existing threads as this has been covered already.
Click to expand...
Click to collapse
Really sorry for asking but how do i install the custom recovery .. ? .. will go into fast boot while pressing the power on button and the up volume key .. thanks for the reply
zealot92 said:
Really sorry for asking but how do i install the custom recovery .. ? .. will go into fast boot while pressing the power on button and the up volume key .. thanks for the reply
Click to expand...
Click to collapse
You could have found the sticky thread in Atrix General forum:
http://forum.xda-developers.com/showthread.php?t=1302423
And, "oem unlock" is not a file, it's a command of fastboot application.
Thank you
i was able to solve the problem by completing the fast boot procedure ... thanks

Expert help requested...Stock ATT 2.3.6/4.5.145 failed on 2nd reboot

Very upset and would appreciate any help. Cant afford another phone now.
I have been a Atrix user for sometime now (MB860, ATT)
Was very happy with my phone, running on stock, no root, no unlocked bootloader.
My friend was playing with my phone and decided to download and install the OTA update to
2.3.6, 4.5.145
First run went fine. Today, I opened the back cover to clean some accumulated dust near the
mouthpiece. When I re started the phone, I got this
SVF:105:1:2
Failed to boot 0x1000
No OS detected going to RSD mode in 5 seconds
Press key to stop countdown
Available modes are
1. RSD
2. FastBoot
3. NV Flash
4. BP HW Bypass RSD
5. BP HW Bypass QC DLOAD
6. BP HW Diag & Boot AP
7. BP HW Bypass BP Only
8. BP SW Bypass RSD
9. Android Recovery
10. Boot Android (No BP)
11 Device UID
12. Console=ttys0 115200n8
13. Early USB enumeration
14. BP Tools
---------------------------------------------------------------------------------
Vol Up to select, Vol Down for next choice
Unable to understand what happened exactly....How do I get my phone back???
Would appreciate any help and advice. Not exactly a noob on software dev, though not
related to android.
Thanks in advance.
Thread Closed as a duplicate...

Categories

Resources