Database Info

[Q] GingerBread Battery Fix v0.8 Problem

I wiped cache and dalvik cache, then installed the ZIP -- and after more than five minutes, the screen is still on "Installing update..." How long does this take?
Ten minutes later, I took the battery out to hard reboot the phone. It all came back OK (took a while because it had to build back the cache), but I'm not sure if the update took.
I did notice this error:
E:can't mount /dev/block/mmcblk1p2
(File exists)
But then it said it did delete the dalvik cache, so I thought it was all right, but maybe it didn't quite work. I'm using System Recovery to go into Recovery GFAN.COM V2.5.1.8. How do I successfully wipe the dalvik cache?

Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you

ch3mn3y said:
Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you
Click to expand...
Click to collapse
No, I'm not using FTR. I'm not even using ROM Manager -- I use System Recovery (an apk I found). It's the Moto A4 bootstrap that's based on Koush's CWM Recovery.

There is a problem with my signing on linux, I'll try and get a quick fix for the .zip tonight... until then:
1. Push files to correct folders.
2. Fix permissions to rw-r-r
3. Reboot
EDIT:
This is for the x2 right?? You should post in the Droid x2 Q&A section if so. It's not for other phones, only the Dx2.
Regardless, Problem fixed.

Are you saying I should unzip the files and then change their permission? What you describe, rw-r-r, is chmod 644. So I should extract, chmod, re-zip, then run the flash update? And yes, this is for the X2.

No l, just redownload, I fixd the problem.
Tapin' the Talk on my HTC Trophy

Just re-downloaded it, but nothing's different -- still having the same issue where it freezes at Installing update. I noticed there are two directories off of root now, Dx2_GB_BatteryFix and META-INF -- is that correct?

I am having the same issue with the zip file. Although I wouldn't say I am a noob, pushing these files is something new to me. If the zip cannot be properly signed or there is difficulty unforeseen in being able to do so, can someone explain in some detail how to push this?
Many thanks!
EDIT: So I figured it out using File Expert. Copied and overwrote battd to system/bin and libbattd.so to system/lib and corrected the permissions as you stated, rebooted and wiped cache and dalvik cache. All seems good now! Thanks for the fix.

[Q] bricked phone by editing build.prop please help!!!

I added some new strings to my build.prop and rebooted. afterwards it would get stuck on the tmobile screen. Theres no custom recovery for this phone.Its an alcatel one touch fierce. I factory reset and cleared cache. I still have my backup build.prop but i cant push it to the phone because i get error:closed. I only have adb sideload but i dont have the update.zip. Any way to save my phone......???:crying:

Bookg said:
I added some new strings to my build.prop and rebooted. afterwards it would get stuck on the tmobile screen. Theres no custom recovery for this phone.Its an alcatel one touch fierce. I factory reset and cleared cache. I still have my backup build.prop but i cant push it to the phone because i get error:closed. I only have adb sideload but i dont have the update.zip. Any way to save my phone......???:crying:
Click to expand...
Click to collapse
Try adb push of your backup after removing the build.prop.
You must have already enabled adb debugging, appropriate drivers in place & adb environment for this to work.
Hit thanks rather than typing it now Free

.
Well i have everything set up ,but when i try pushing it i get error:closed and ive tried alot to fix it. Maybe because its only adb sideload ?

Trying to set write permissions on /system ends in bootloop

hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987

Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk

d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987

So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.

es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987

k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.

Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.

...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root

.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks

k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img

^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095

[SOLVED] I Softbricked my phone, need some help!

-----SOLVED NOTE----
I did a reflash of the stock rom one more time with ODIN and it seems to have solved the problem. However I still have absolutely no idea about what was wrong with the phone, or why the first successful flash did not take care of the problem.
And a piece of advice, do not edit platform.xml. I swear I edited it correctly and then reverted to the correct settings, did using 3 spaces instead of a tab caused an error??? This will remain a mystery for me...
---------------------------
Hello All,
So I have the Verizon S3 i535, I edited the platform.xml file to give write permissions to external sd card and all hell broke loose after I reverted those changes. All of a sudden every app is getting that "unfortunately stopped" message. I cannot send any file to neither the internal nor the external sd card from my pc, file browsers cannot read any file on any of these cards, I tried pushing with adb but that does not work either. I tried factory reseting, and hard reseting to no avail.
I tried reflashing the stock rom with ODIN but after the flashing process nothing changes? (Does that have to do with me being on NE1).
I do not understand what is going on with the phone right now, flashing should have restored everything, I still get com.google.process.gapps stopped working then all sorts of apps stopping in the same manner, I still can't copy any file to any sort of storage on the phone.
Any idea what has happened and how I could fix it?
Thanks in advance.

That type of editing is not something I have done on Android.
Is there any chance it is a permissions issue and could be fixed with root permissions to a file manager or with adb?

dawgdoc said:
That type of editing is not something I have done on Android.
Is there any chance it is a permissions issue and could be fixed with root permissions to a file manager or with adb?
Click to expand...
Click to collapse
I would be willing to try that however I cannot connect to play store, neither the internet app connects to the internet so I cannot install apk's. I cannot "push" apks to the storage too I tried it via pc and via adb. So I cannot even install a root file manager.
Kingo root however accesses the system (through the pc) and manages to install itself. I have no idea how it can do it.

guguma said:
I would be willing to try that however I cannot connect to play store, neither the internet app connects to the internet so I cannot install apk's. I cannot "push" apks to the storage too I tried it via pc and via adb. So I cannot even install a root file manager.
Kingo root however accesses the system (through the pc) and manages to install itself. I have no idea how it can do it.
Click to expand...
Click to collapse
Glad to see you solved the problem.
I was speaking of using an adb shell to change the permissions of platform.xml to 0644 (-rw-r--r--) if they were set to something else. (I just checked my /system/etc/permissions/platform.xml to verify that was the settings on my device. I wasn't any more specific before because I hadn't checked the file locations nor its permissions.)

build.prop modification caused loss of root, now stuck with bad build.prop

Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery

memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop

-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.

memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache

-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help

memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site

Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.