So i wanted to edit the android version. I succesfully edited it but after a restart i was shocked by all apps force closing so i couldnt even fix it. Instead i did a factory reset so the root is lost, and now i tried to pull build.prop via adb but i always get this error: "remote object '/system/build.prop' not a file or directory" and i cannot seem to get it working.
Related
So, I wanted to delete my google account in the first place. I found this tutorial with video. It says:
Basically this was done on a rooted phone. We used the program called Root Explorer and navigated to /system/framework. Make sure that is mounted r/w and not r/o (read write vs read only). Rename framework-res.apk > framework-res.apk.bak. You might get an error after this (force close). Just go ahead and force close it. Immediately rename it back to framework-res.apk. Reboot and you're done. Enter your new main Google account.
Click to expand...
Click to collapse
I rooted the phone using the Galaxy S II Root Guide on this forum. I put the XWKDD_insecure.tar on my phone, succesfully. After reboot i rooted the the phone using SuperOneClick. Everything went fine, it asked me if i wanted BusyBox > clicked 'Yes'.
I rebooted my phone, left it in USB Debugging (you never know what happens). I launched the application Root Explorer (v2.14.2) > some message asked me if i allowed the app acces to my root > clicked yes.
So, Root Explorer launched, i navigated to /system/framework and clicked "mount R/W" (read/write). I renamed framework-res.apk to framework-res.apk.bak. TROUBLE STARTS HERE
All kind of processes started to crash and asked me to do forced close the tutorial says this can happen, so i force closed. But the errors kept popping up, and i kept clicking force close. In the end there were 3(i guess) processes which continiously kept crashing one-after-another.
The proces system crashed also, so the creen was black. I was able to slide the top bar (system tray?), the icon of my advanced task killer was there so I tried to launch that but it crashed too. So I gave up, and long pressed the powerbutton.
Big trouble
I tried to reboot, the samsung galaxy s II launch image appeared. That's it.. nothing left. After a lovely cursing-session i put on the KE2 original kernel. (again, just like the root guide says) Rebooted but it's still stuck at the launch image.
Kernel version:
2.6.35.7-I910XWKE2-CL187606
[email protected] #2
I've got this phone handed by the mailman 24hours ago, and i really really want to get this fixed. Whoever helps me to get my phone working again will get a reward, I'm really desperate.
Anymore information needed? Leave a reply plz
Just go into download mode and flash again with whatever rom you want (FULL ROM not just kernel). Should be fine I would think as /system is not essential (well, for to use it as a phone/pda yes) but not for flashing again. Should be fine then.
Although i'm new to the flashing stuff, i understand what you mean. I'm going to find a full rom and download it to my phone, and be back asap
Thanks already!
Phone works again
deanwray, if you have an paypal accoun you may PM your details to me. As i've said:
Whoever helps me to get my phone working again will get a reward, I'm really desperate.
Click to expand...
Click to collapse
I guess answering my question was almost easier then picking your nose still i want to thank you
I do have a paypal account, but to anyone who would want paying for simple advice, I would have little respect for and even less so for myself, just press the thanks button in xda, im more glad that your sorted than nething else
Sent from my GT-I9100 using XDA Premium App
Understood, i already pressed the thanks button.
@Admins: If needed, this topic may be closed now.
I too did rename framework-res.apk and bricked my Kindle fire; need help
I too did the same dumb thing.
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
How can we??!?! Ive done this with every phone I couldnt load an international rom, even the Optimus G Pro. I`d change ro.build.target_operator= in the build prop to either TMO or OPEN depending on what Data Icons I wanted it and just work with no errors or causing anything to force close..
Well on the G2 Changing it to anything other than ATT I can NOT access the Mobile Network settings it force closes and says "Unfortunately, the Process com.android.phone has stopped" How do I fix this????? Its the ONLY problem I have when changing that, The Data Icons change and work perfectly!, But I get the stupid error when trying to go to mobile networks which NEEDS to work.
Any Ideas??
hyelton said:
How can we??!?! Ive done this with every phone I couldnt load an international rom, even the Optimus G Pro. I`d change ro.build.target_operator= in the build prop to either TMO or OPEN depending on what Data Icons I wanted it and just work with no errors or causing anything to force close..
Well on the G2 Changing it to anything other than ATT I can NOT access the Mobile Network settings it force closes and says "Unfortunately, the Process com.android.phone has stopped" How do I fix this????? Its the ONLY problem I have when changing that, The Data Icons change and work perfectly!, But I get the stupid error when trying to go to mobile networks which NEEDS to work.
Any Ideas??
Click to expand...
Click to collapse
i changed SPRINT 'SPR' same to OPEN...
and bricked the phone...
Please help. to push the original build.prop to system... via sideload...
cananyone help...
[email protected] said:
i changed SPRINT 'SPR' same to OPEN...
and bricked the phone...
Please help. to push the original build.prop to system... via sideload...
cananyone help...
Click to expand...
Click to collapse
have you tried
adb pull /system/build.prop c:\ (this copy build.prop to your pc at the root of your primary c:/ drive )
and replacing the original values, and copy the build.prop back to g2 with adb push ? i'm not sure this will work
coc014 said:
have you tried
adb pull /system/build.prop c:\ (this copy build.prop to your pc at the root of your primary c:/ drive )
and replacing the original values, and copy the build.prop back to g2 with adb push ? i'm not sure this will work
Click to expand...
Click to collapse
When used adb pu;; or push .. it says : Device Not found.
but in sideload mode.. it works for only sideload
..
YEs sir tried the adb push initially .. but it didn't work..
the thing only Work is ADB SIDELOAD ...
SO need a Flashable ZIP either to overwrite the build.prop or to install the recovery via Sideload...
Can you help to get flashable ZIP for either or.
I have a Sprint GN3. I've rooted with CF Auto Root, flashed TWRP, flashed Jellybomb, and then restored back to stock from a nandroid backup. I've come across a few different errors, and I'm not sure if they're related or not.
For one thing, when I try to download a file in Chrome, I get a "No SD Card" error, even though both the SD card and the internal storage have plenty of space.
And then for the Audible.com app, even after clearing all the data, and uninstalling and reinstalling, I get the following error:
Failed to save your library to your device. /storage/emulated/0/Audible/<snip>: open failed: ENOENT (no such file or directory)
And it's right, I don't have an Audible directory in there, or anywhere else that I can find.
So my question is: Is that likely the correct path for the Audible app to save my data, and if so, why could it not create the Audible directory there?
And could that have anything to do with Chrome not being able to see or write to storage?
Thanks.
Edit: So I tried to manually create the Audible directory in /storage/emulated/0/ with Astro, and it wouldn't let me do it. Then I tried with Total Commander, and it worked, but I also go the "Total Commander has been granted superuser permissions" popup.
Then when I run Audible, I now get a EACCESS (permission denied) error.
So did I somehow set my internal storage to read only other than for root?
Possible solution.
Hi, it has been over a year since you asked this question, but I figured I'd respond anyway. I was experiencing a similar problem (exact same error that you describe) with my galaxy s4 provided by FreedomPop - I think it stemmed from their special version of android that they pre-installed on the phone. Anyway, their support staff suggested installing and running a program called "folder mount (root)" - it ran and found 2 errors, I had to re-boot my phone, and it completely fixed my problem.. Hope this helps
Glad you posted. Not much info out there on this issue, and your fix worked. Thanks.
SGH-i337m
Rooted and still on stock MK6
SuperSU and TWRP
Everything seemed ok after root and was running fine, phone restored up from google without issue.
First noticed the issue a few days later when swiftkey keyboard suddenly was unable to load language packs. Of course suspected it was a swift key problem and troubleshot from there. No solution found so gave up and switched back to default keyboard.
Tried to run Titanium, received unable to access "/storage/emulated/legacy/TitaniumBackup" error.
Used X-plore (with SU privilege) to try to access and create dir or write to directory, no success. Able to create and write in /(root) without issue.
/sdcard 777 and all subs are 775
Seems that some apps can write into /sdcard and others fail.
Assume that the Swiftkey failure was due to unable to write to the default directory (/sdcard/Android/data/com.touchtype.swiftkey/files/).
Tried factory reset and restore to backup when keyboard worked and no change.
Unless there are any ideas my next option is to roll back to factory unroot and start over or look for good custom rom and hope it fixes the problem.
I know I shouldn't have done this. But somehow I managed to "cut" the system fonts instead of copying them. And when I realized it, I tried to put the fonts back. but everything messed up and fonts started disappearing from every app. So I restarted the phone and boom. Stuck at Samsung boot animation.
Now, I've searched for this issue and now know that I've to replace system fonts with a genuine one for my device. So do I need to replace just the Roboto-regular.ttf or every font that was present in /system/fonts?
Secondly, I'm rooted and have Philz recovery installed. But I'm not able to use adb when phone is booting in normal mode. It says device unauthorized (I believe we need to authorize a pc for the first time).
Again, I can't push files using adb in recovery to /system/fonts because su right is not available. It says access denied.
And the data is important. So any method except RESET would be welcome.
Ok, I got it working partially. I'm able to push files to system partition. I pushed roboto regular ttf file. The phone boots now but systemui keeps on crashing. So can someone just provide me the stock fonts folder dump? I will try to push every font to see if the crashes still occur or not.
Edit: Finally solved it. What I was missing was the permissions. I was just pushing the font file but never bothered to think about permissions. So it could help someone in future. Push the font file to /system/fonts and change the permission to rw-r--r-- . I used aroma file manager for this purpose in philz recovery. I think you can also change the permission using adb.