/proc/ is totally locked down. Help? - Motorola Droid 4

I'm having a really messed up problem on my rooted D4. /proc/ is totally locked--completely, 100% locked. Even in the terminal in root, and even in adb. No matter what, /proc/ just cannot be modified in any way, shape, or form.
What is going on?!

/proc is never writable. Nothing to do with android, it goes way back to unix days
Sent from my DROID4 using Tapatalk

Related

[Q] Bootloop after copying apps back to system/app

boots upto droid sound and then keeps repeating. I feel an idiot. What can I do?
Did you ever get this resolved? I am in the same place :-(
I guess it is true that "a little knowledge is a dangerous thing"
Try using psouzas tools to help you redo this
Sent from my DROID3 using Tapatalk
unfortunately I have no ADB access. I was too hasty, let this be a lesson. Especially damning as im in england and cant return it!
slvrarrow said:
unfortunately I have no ADB access. I was too hasty, let this be a lesson. Especially damning as im in england and cant return it!
Click to expand...
Click to collapse
Did you try doing the bp tools method? That gives u temp adb access and can help you restore your system/app
Sent from my DROID3 using Tapatalk
slvrarrow said:
unfortunately I have no ADB access. I was too hasty, let this be a lesson. Especially damning as im in england and cant return it!
Click to expand...
Click to collapse
If your /system/app is pure, you could install the pulled OTA update.
its unfortunately not, I tried to copy some APK's back that id deleted through root explorer
yeh tried BP Tools as well. factory reset so USB debugging would be disabled... is there any other way to use adb? any way to enable debugging?
if u use bp tools I heard it enables adb. I test drived this today and I was able to get adb using the bp tools method even though im not bootlooping or anything
Sent from my DROID3 using Tapatalk
i would tell u to remote install or voice shortcut into the market & install USBDebug but you cant even get to the android/setup screen...
just wondering, is it looping bc u forget to set permissions?
no idea about permissions. possibly. the replacement apps were straight from a

[Q] Bricked?

I was attempting to work through applying the .218 update to my droid 4. It was giving me a system validation error while when it was running in recovery. I found a thread that stated I needed to replace the apks and odex's as well as the build.prop. I didn't read it carefully enough as it said to replace *THE* problem ones. My validation error was on the build.prop file, I think.
In any case, I was using root explorer to copy *ALL* the files from a base zip file's app folder into the /system/app folder. Things were going along fine, until the phone app forced closed, then the phone rebooted.
Now I'm boot looping.
What can I do? I don't have any safe straps.
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
thanks for the reply...
I don't have safestrap installed on the device, and I've never used it. I don't think that's an option, unless you have something up your sleeve there
As for Stock recovery, I'd love to give it a try, but I don't know how that would work. I can't get to ADB because I can't boot the phone.
I *CAN* get into the bootloader. From there, I can get into recovery, AP Fastboot, BP SBF Flash BP boot... and others.
So, I'm hoping there's some kind of way to push to the device from one of the boot loader options. I've had a Droid 1, and a number of other android devices, but I've never gotten this far into a hole before.
again... thanks for whatever you got
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
jbeazell said:
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
Click to expand...
Click to collapse
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
kwyrt said:
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
Click to expand...
Click to collapse
I'm heading down there in a few minutes. Thanks for the help all ! I think I'm getting the razr maxx. My wife has one and the screen on that thing is incredible. I think it's worth losing the keyboard to get that screen... and the battery life. That part is also incredible.
again.. thanks.
BTW, you guys absolutely rock. You've helped me out of some serious holes with my OG Droid and other devices more often than I can count.
Sent from my DROID4 using Tapatalk 2
You can use bp tools to push over a clean system. I believe theres a tutorial somewhere that written for bionic. Just replace that with the droid 4 system. I would extract it from one of the stock roms available and push it thru bp tools.
Sent from my DROID4 using Tapatalk 2
Can you link that tutorial? I'm also trying to figure out how to use adb via stock recovery. Thanks!
Sent from my DROID4 using Carrier Pigeons
http://forum.xda-developers.com/showthread.php?t=1236465
Sent from my Galaxy Nexus using Tapatalk 2
Thanks!
Sent from my DROID4 using Carrier Pigeons
Let me know
Sent from my Galaxy Nexus using Tapatalk 2
It sounds like OP is going to exchange their phone, but could you really just replace the entire /system folder and have it work? (Nothing special with permissions, etc?)
If so, that is definitely something worth knowing...
Yes i believe so.
Sent from my DROID4 using Tapatalk 2

Cannot get past Android Upgrading on 2233

No matter what I try I cannot get past this screen.
//merickk.smugmug.com/Other/Misc/Miscellaneous-Stuff-1/i-P8ZBVg4/0/L/0626120050-L.jpg
I've even tried to moto-flash the mbm and cdt files from a downloaded leak file and no luck there either.
Formatting the internal memory after FXZing back to 902 and installing the leak on a fresh formatted SD card with only the leak file on it after OTAing to 905 doesn't work either. I've tried 6 or 7 2233 files, and a couple 2231 files as well as a couple different 902 FXZ files.
ICS is there somewhere otherwise I don't think it'd get that far into the boot process and charge the battery.
When I do a battery pull and try to reboot, it just sits at the Droid screen.
Pulling the battery while plugged in takes me to the Dual Core screen where it sits.
When sitting at the starting applications screen I am able to get tactile feedback when pressing and holding the home key but after sitting for an hour or so there is no feedback from the home key. No response from any of the other keys. The keys are also lit up.
This has happened every time with every leak file I've flashed the exact same way.
Does anyone have any suggestions?
Quite a conundrum... Maybe you should wait for the OTA to come out, let it brick your phone, then take it to Verizon and demand to trade it in for a phone with good battery life and no data drops? lol. If I were in your shoes and it looked like the ICS update was gonna make my phone eligible for a warranty replacement, I'd use that as an opportunity to let Verizon spring for a new device. Just sayin'.
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
XperianceIT said:
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i have the same problem , did this work for the OP?

Safestrap & stock ROM issues?

While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
cpnbnanamn said:
While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
Click to expand...
Click to collapse
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Endoroid said:
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
cpnbnanamn said:
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
Click to expand...
Click to collapse
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Endoroid said:
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
cpnbnanamn said:
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
Click to expand...
Click to collapse
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Endoroid said:
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The kexec ICS from 8/6 is surprising stable for me. I've been running it for nearly a week and while I've had some reboots and a couple of freezes that required a battery pull, it's run better than I expected.
I have had the problem with leaving bluetooth on and answering a call without a headset - no audio until BT turned off.
Also, as advertised, no camera. Another note, the car dock USB audio doesn't work.
I've even scripted a mount to keep the Play Music directory on the external SD card and mass storage mount on the computer works better than stock with the mount in place. Internal sd doesn't mount though.
Sent from my XT862 using Tapatalk 2

[Q] Missing /preinstall files for ota update

I am trying to update to ics from 2.3.6 I have uninstalled safestrap and frozen root with otarootkeeper. I get hung up during install, so I checked my error log. It seems I am missing files from /preinstall specifically from /knowyourdevice which no longer exists. Is there a way of getting a copy so I don't need to go through fast boot? There was a link up elsewhere, but it's dead. Any help is greatly appreciated.
I recommend to flash fastboot 4.0.4 files.
I know, but this has turned into a pet project for me. I was really hoping to do it the hard way. There was a link up in the dev forum, but it's dead now...
I had the same issue when upgrading. Turns out, the update scans your system for ANY modifications that would signify you were, or had been rooted. You either need to completely remove anything that signifies you are rooted and any apps that require root, or sbf to either gb or ics. Doing a simple factory format still leaves files behind. Honestly, just doing an sbf would easier, as it ensures your system is 100% clean. If you need new links to the one click sbf, I can pm you a link later.
Sent from my DROID4 using xda premium
I had this problem and just downloaded the fastboot files, extracted the /preinstall archive from there, and copied it to my phone using adb. Simple.
Sent from my DROID4 using Tapatalk

Categories

Resources