titanium and kitkat : sd card problem - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi everybody!
I can't use the external sdcard to backup my data with Titanium rooted. There is obviously a bug since it says I can't write on that directory/card. I already checked with scandisk. It was fine.
I heard about a bug in Android Kitkat. A story about wrong / new permissions. I am surprised that today, this problem is not fixed yet. I saw a solution where I have to modify some lines in the permissions.xml but ES Explorer refuses to save the file !! Moreover, people report a bug with the bluetooth ...
http://forum.xda-developers.com/showthread.php?t=2537793
Actually, I only want to flash a THL (Thailand) stock ROM although I am using a XTC stock ROM (Philippines). If I do it, I suppose it will reset my phone since these are different countries and CSC.
Boring. I am stuck now. Can't save my phone. Any ideas please?
Thank you!

Nemorensis32 said:
Hi everybody!
I can't use the external sdcard to backup my data with Titanium rooted. There is obviously a bug since it says I can't write on that directory/card. I already checked with scandisk. It was fine.
I heard about a bug in Android Kitkat. A story about wrong / new permissions. I am surprised that today, this problem is not fixed yet. I saw a solution where I have to modify some lines in the permissions.xml but ES Explorer refuses to save the file !! Moreover, people report a bug with the bluetooth ...
http://forum.xda-developers.com/showthread.php?t=2537793
Actually, I only want to flash a THL (Thailand) stock ROM although I am using a XTC stock ROM (Philippines). If I do it, I suppose it will reset my phone since these are different countries and CSC.
Boring. I am stuck now. Can't save my phone. Any ideas please?
Thank you!
Click to expand...
Click to collapse
If you're rooted , try this path /storage/extsdcard/Titanium Backup, or if you modified permission.xml already search for media_rw (grant permission rwxrwxrwx) then choose /mnt/media_rw/extsdcard/Titanium Backup.

Er,... Thank you but did you actually read my post? it doesn't work for me! I tried everything about that.
Thank you.
Edit : my bad, actually, adding some permissions, Here and there AND REBOOTING solved the problem. However, I'm surprised since the creator of the tuto I posted said we can't reboot or we loose the changes (^o^)
Sent from my SM-N9005 using xda app-developers app

Nemorensis32 said:
Er,... Thank you but did you actually read my post? it doesn't work for me! I tried everything about that.
Thank you.
Edit : my bad, actually, adding some permissions, Here and there AND REBOOTING solved the problem. However, I'm surprised since the creator of the tuto I posted said we can't reboot or we loose the changes (^o^)
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Glad you solved it , yes you need to reboot after you set the permission , except for media_rw , you need to set
the permission again after every reboot (for me).

Related

Cannot Unlock new Tab

Just got a new Tab from a carrier shop here in Kuwait with some, let's just say, undesirable applications preinstalled which I would like to get rid off. Read all (well most of the posts) but getting nowhere.
Upgraded to new firmware through KIES.
downloaded Z4ROOT and rooted succesfully (or at least that,s what the app is telling).
Tried to copy the nv_data.bin file to my sd card - cannot be done
Tried to open nv_data.bin in HEXEDITOR - no can do
Tried to delete application - nope
So some help is obviously needed here if anyone is kind.
Best regards
You did install busybox, did you?
Which firmware? Post what you are doing on the adb shell. Be specific or we can't help you.
You're right should be more specific.
Well I did not install busybox (no idea what it is for) and
Firmware version is 2.2
Baseband version P1000JXJK2
Kernel version 2.6.32.9 [email protected]#1
Build No FROYO.JPJK2
Hope this clears it.
dsaric said:
Well I did not install busybox
Click to expand...
Click to collapse
Busybox gives you most shell commands (including, but not limited to, cp).
Thanks.
Installed BUSYBOX and copied nv_data.bin file to sd card for modification as per How to carrier/SIM unlock the Galaxy Tab topic from 17/11 but the address 0x181469 could not be found.
Also tried to uninstall the preinstalled apps - no success
need z4 unroot it
busybox
root explorer
Z4 unroot, DONE
BUSYBOX installed DONE
ROOT EXPLORER installed DONE
So
http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94
totaly worked for unlocking the SIM/carrier. Very easy and no problems encountered. Inserted a different SIM and made a call. Perfect. Thank you for all the work that made this possible.
However it still does not let me delete the APPs that came preinstalled with the Tab.
I am guessing this is something to do with the Kernel version 2.6.32.9 [email protected]#1. How can this be undone (another guess is flashing the ROM but i have no idea what it involves so back to the reading and learning)?
If somebody has a simple to follow guide and resolution to this please let me know the thread. Thanks
Have you mounted /system as r/w in Root Explorer?
Regards,
Dave
Dave, to advanced for me. How do i do that?
Just an update.
Managed to successfully flash the tab to the european version using guide from
[HOW-TO] Flash your at&t Tab to make calls + 1900+850 WCDMA - UPDATED
thank you it worked fine and i achieved what i was looking for: no more undesirable apps.
But, i lost the 3g and cannot get it back using the same guide as above.
With my limited knowledge of the whole thing I am guessing that this is to do with the modem.bin file. Will try to download an arabic version of firmware, extract it and try to use the modem file and see if it will work. will post an update just in case anybody is interested,
regards
I found it rather embarassing posting replys to my own thread all the time but I feel it might help somebody so what the hell!!
I finally got my 3G working on the Tab. A silly thing really: APN (Access Point Name) was deleted during flash and by adding and activating the APN i got my 3G restored.
Anyway, thank you guys for all the replies and help. Really good forum with a lot of useful stuff.
Regards

Arabic Support Update.

Hi to All.
I am new to Driod and this forum as well,
I bought Atrix From BELL.
So far I have flashed the ROM to the New OLYEM_U4_1.4.2 Telstra.
Rooted and Deoxed as well, I even got a Custom theme on it.
In short my story, I tried using the Arabic "Framework.jar" that is posted on one of the Dev-Forum on this site. My phone soft bricks.
Is there a better way to update the file. Or the file is just not compatible
What i have tried.
1 - Reflash > rooted > Deoxed > Arabic suport = Bricked ?
2 - Reflash > rooted > Arabic supprot = Bricked ?
Thank you
Anything
Yes, Please attache your original "Framework.jar" file for me.
azy8000 said:
Yes, Please attache your original "Framework.jar" file for me.
Click to expand...
Click to collapse
Thank you SIR
Here is the framework.jar
mediafire.com/?ozott7vlhpbojfs
Download the following file and replace it with the original one.
http://www.mediafire.com/?ube6tzbc8764oax
PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS, OTHERWISE IT WILL NOT WORK.
PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS, OTHERWISE IT WILL NOT WORK.[/QUOTE]
Should the permissions be:
rw-r-r ,,,
in CLI:
chmod 4644 /system/framework/framework.jar
and should i do it ADB or just file expert.
Thank you for your great work.
Regards,
Maas
azy8000 said:
Download the following file and replace it with the original one.
http://www.mediafire.com/?ube6tzbc8764oax
PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS, OTHERWISE IT WILL NOT WORK.
Click to expand...
Click to collapse
"PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS".
This!!
Even though I forgot to change permissions once and it wasn't not anything severe like a soft brick, the fix just did not work until I modded the permissions and restarted.
gold luck.
CyberPunk7t9 said:
"PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS".
This!!
Even though I forgot to change permissions once and it wasn't not anything severe like a soft brick, the fix just did not work until I modded the permissions and restarted.
gold luck.
Click to expand...
Click to collapse
I will try it when i get home and see if this would fix. I really cant afford a bricked phone while I am at work ,
good luck yes I need it.
CyberPunk7t9 said:
"PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS".
This!!
Even though I forgot to change permissions once and it wasn't not anything severe like a soft brick, the fix just did not work until I modded the permissions and restarted.
gold luck.
Click to expand...
Click to collapse
You know what I will it now, I WILL CROSS MY FINGERS and do it ....
I will let you guys know.
maas0999 said:
You know what I will it now, I WILL CROSS MY FINGERS and do it ....
I will let you guys know.
Click to expand...
Click to collapse
,
Red Light Blinking, Soft Brick
I made sure the extensions were set RW-R-R . but I guess this Firmware does not like it.
I guess this is a sign to stop using this Arabic support.
CyberPunk7t9 said:
"PLEASE MAKE SURE YOU CHANGE THE FILE PERMISSIONS".
This!!
Even though I forgot to change permissions once and it wasn't not anything severe like a soft brick, the fix just did not work until I modded the permissions and restarted.
gold luck.
Click to expand...
Click to collapse
Any Ideas how to recover without losing data ?
Thank you
sorry for that, its breaking mine too. you can fix the problem without lousing data by following this link
http://forum.xda-developers.com/showthread.php?t=966405
BTW i got the right file for you. if you need it tell me which rom you are using right now.
azy8000 said:
sorry for that, it is break mine too. you can fix the problem without lousing data by following this link
http://forum.xda-developers.com/showthread.php?t=966405
BTW i got the right file for you. if you need it tell me which rom you are using right now.
Click to expand...
Click to collapse
Please send it ..
Thank you for the Link
In which rom you are ?
azy8000 said:
sorry for that, its breaking mine too. you can fix the problem without lousing data by following this link
http://forum.xda-developers.com/showthread.php?t=966405
BTW i got the right file for you. if you need it tell me which rom you are using right now.
Click to expand...
Click to collapse
I Tried that Link I There is no Root access for ADB,
$ su
" does not work "
maas0999 said:
I Tried that Link I There is no Root access for ADB,
$ su
" does not work "
Click to expand...
Click to collapse
If you do not have root access will not work for you.
azy8000 said:
In which rom you are ?
Click to expand...
Click to collapse
OLYEM_U4_1.4.2 Telstra.
Rooted
Deoxed.
I know i have Root, I have Titanium Backup and Terminal. Everything is was fine.
Could Did your new framework.jar work ??
PS:
Under windows ADB connects but cant get root access for some reason ?
Can you wait for few days. I promise i will make it work for you and i am trying to get the browser too. So if not today wait till tomorrow and it will work. If you reflash your device do not install anything just keep it Deoxed and rooted. So if we have any problem you do not lose your files.
azy8000 said:
Can you wait for few days. I promise i will make it work for you and i am trying to get the browser too. So if not today wait till tomorrow and it will work. If you reflash your device do not install anything just keep it Deoxed and rooted. So if we have any problem you do not lose your files.
Click to expand...
Click to collapse
Hey
Thank for the good work, sell I use firefox its much better than the default I could wait all u want . As long as it does not brick my phone
Thank you again
Maas
Sent from my MB860 using XDA App
azy8000 said:
Can you wait for few days. I promise i will make it work for you and i am trying to get the browser too. So if not today wait till tomorrow and it will work. If you reflash your device do not install anything just keep it Deoxed and rooted. So if we have any problem you do not lose your files.
Click to expand...
Click to collapse
"i am trying to get the browser too."
Would be really awesome if you can!!
Gold luck and many thanks.

how to downgrade to android4.1.1 on nexus 7?

i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my GT-I9300 using xda app-developers app
rooted or not?
not rooted
Sent from my GT-I9300 using xda app-developers app
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
ace9988 said:
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
Click to expand...
Click to collapse
thank you for answing
But the problem is that i do not know how to downgrade to 4.1.2
Sent from my GT-I9300 using xda app-developers app
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Yea that tool kit really saved my butt a couple of times when I needed to back to stock android. I made sure to give a donation for the work he did.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Hi,
tell me if i understood correctly..... now that i have still 4.1.1 is better i do root, backup and nandbackup and after upgrade to 4.2, so in case of proobs i can come back.. is it right?
PS: actually my Nexus is completely empty
Which software u suggest, consider im no expert
Many thanks and sorry for my english
Ale
Take a look here
http://forum.xda-developers.com/showthread.php?p=34389960#post34389960
How to downgrade to 4.1.2 - very simple!
charlie135246 said:
i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my Samsung GT-I9300 Galaxy SIIIusing xda app-developers app
Click to expand...
Click to collapse
I am a 11 Year old Girl and now i'll give you an instructions how to downgrade very easily.
I do already know the scams and battery problems with 4.2!
Question:Which OS do you have got on your Galaxy S3?
If you've got Android 4.0.4 IceCreamSandwich, then it sucks.
Ok, here is it=:
You need to have your device connected to the PC with a cable to follow this GUIDE.
For this you'll need a Cable which is still working without loose connection or so...
One end is a USB-Input like on USB-Stickers and the other end is MicroUSB and schould fit in your device.
Such a so-called „Micro-USB-Cable"
It is recommended to use an USB 2.0 input in order to avoid compatibility problems such as compatibillity problems with USB-3·0 or so. .... .
1.Download the best and most easy to use Nexus Toolkit (-- )made by a symphatic programmer- WugFresh.
WugFreshs Tooklit is even better than SkipSofts and has more features and even better!
Download it here [ „ http://www.WugFresh.Com/Nrt "], new version 1.8.7 released today. 9'o clock (09:22:51) in GMT+1
I had 1.8.4 and yesterday the 5th September, i did upgrade at 15:56:59 GMT+1 to 1.8.6..
Click to expand...
Click to collapse
2. Install this Program.
3.Download the Factory-Image of the Nexus 7 2012.
You cannot actually have the 2013-Version because the 2013-Version came out with 4.3 [Only-WiFi] and 4.3.1 on the Mobile 4G LTE-Version
IF you have got the only-WiFi-Version then take this link:https://developers.google.com/android/nexus/images?hl=de#nakasijzo54k (Choose JZO54K 4.1.2, too bad, Google did exclude 4.1.0;4.1.1;4.20;4.2.1;4.4.1Kot49e E)
IF you've got the Cellular Nexus 7, then it is not possible because unfortionally the cellular version was launched with 4.2.0!
Information:
FileName=nakasi-jzo54k-factory-973f190e.tgz"
Version: 4.1.2
Build:„JZO54K"
MD5·Checksum:„d906b505ccae0d439839d3c5fafb137a"
SHA·1-Chécksum:973F190e25cbafc29d9739fbe0ffb64ed8946946
[.]9b.Chéérs! Cheers?
http://forum.xda-developers.com/showthread.php?t=176647
http://forum.xda-developers.com/showthread.php?t=1766475
See my posts and WugFresh's answers on the last few pages by pressing the [>>] button on the page selection for more information.
4. You need to launch this program and press Auto·Detect Device+Build OS or so...
If this does not detect your device, then try choosing Device (Nexus 7 2012 WLAN or WiFi so-called...) and your Android-Version Manually.
5.[Backup]
To do a Backup with a device with not unlocked bootloader, then choose „Android Backup"
Do not select the both tickable options (Shared data and SysApps+Data backup) or it won't work.
Choose a location to save the ADB-File and wait until the device is unlocked, then unlock the screen and optionally you can type a password to crypt your backup.
Then start and wait.
Here it's recommended to use newer versions of this program. 1.8.4 was stuck at 92.495 MB or so. 1.8.6 worked fine for me so 1.8.7 will work fine too!
If the progress has finished, then the program will show you a Window with detailled Information. I did even upload a screenshot of this and it is on the official Wug thread on Page 440. Link is ^^^^ûp!^^^^^wards.
If your device has got an Unlocked Bootloader then just choose „[Full NºAndroid°Backup /W/]" and done. Just root in the main menu and... done!
Click to expand...
Click to collapse
6.Go to the devices settings menu and tap on „Storage", then tap on ⁞ and choose the USB-Option. Enable MTP and go to the Devices storage with your Computer on Windows Explorer.
Choose all files and if it says that the time lenght is being „Calculated" then it'sa just counting files, stay patient and wait!
7.
When even this finished then... well, you're ready, now you can Unlock the Bootloader!
I and my heart hate the factory data reset!
The only things that you can't actually be able of backing up are the Systen Settings, the Home Screen LayOut and the internal data of the System Apps.
Example:
Chrome History
Download History
YouTube Search History (if you've got an account, then online on your YouTube Account NOTHING will be changd!)
G·PlayStor Search History
(Google Drive Files will not be deleted from online!)
GMail Offline Sync (don't worry, anything still available online!
and etc.
Except of this, you'll actually loose Nothing!
Click to expand...
Click to collapse
After unlocking the bootloader you can finally root your device but this is not required for downgrading.
Now go to the Programs Home Screen and Load your Costum-ROM.
Use your about 256 MB big downloaded file for this.
The Original Name:„nakasi-jzo54k-factory-973f190e.tgz"
Size:268.416.146 Bytes
Size on Disk Drive(r):268.419.072b.
Windows Explorer shows the file as 255MB; FireFox as 256 MB.
And now you're..... Done!!!!!!!! ( )C o n g r a t u l a t i o n s ! ! ! ! ! [/FONT]
If you want to Relock your bootloader:
A.OEM Stock
B.Follow stéps
C.Done.
If the Backup is smaller than the App Data would be, then i don't know if the file contents are compressed or not... WugFresh won't answer (anymore) because he's probably tired of my (loooooooooooooooooooooooooooooooooooooooooong ( )) questions. I asked too much, my mistake. I asked if compressed or not... but still no answer there!
In this case read the official Nexus WugThrèad for more Important information.
I am doing the same steps but i downgrade from 4.4.2! This Colour for the Status-Bar Icon loox better than this!!!!!
:=Helpabilitty
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Hannah Stern said:
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Click to expand...
Click to collapse
The method is clear but.. the post is from 2012.. i think the OP has solved the problem or maybe he don't even has the n7...

[Q]How can i fix my touchkeys?

sir,
I have a rooted i9300,and when i used the Root Explorer to open/change this file:
/sys/devices/virtual/sec/sec_touchkey/touchkey_firm_update
or other files in:
/sys/devices/virtual/sec/sec_touchkey
THEN,MY TOUCHKEY GONE BAD,won't react to my touch
and flash(light) about a second when the system start, and fall black.
pls help...........
(from China)
please help.............
thanks.....................
breakshadow0504 said:
thanks.....................
Click to expand...
Click to collapse
Two post and two breaking the rules .
One this is not for questions two no bumping .
breakshadow0504 said:
sir,
I have a rooted i9300,and when i used the Root Explorer to open/change this file:
/sys/devices/virtual/sec/sec_touchkey/touchkey_firm_update
or other files in:
/sys/devices/virtual/sec/sec_touchkey
THEN,MY TOUCHKEY GONE BAD,won't react to my touch
and flash(light) about a second when the system start, and fall black.
pls help...........
(from China)
Click to expand...
Click to collapse
Maybe a wipe+flash your rom will solve the problem.. Have you tried that?
Why you changed that file? You should never do something like that unless you know what you are doing.. always keep a nandroid backup just in case..
Never edit system files unless you know what you are doing.... Wipe system clean and install rom over...alternatively download app called softkeys/ button savior root to enable on screen softkeys
Sent from my XT912 using xda app-developers app
Roymik said:
Maybe a wipe+flash your rom will solve the problem.. Have you tried that?
Why you changed that file? You should never do something like that unless you know what you are doing.. always keep a nandroid backup just in case..
Click to expand...
Click to collapse
Thanks,fixed。

[Q] Nexus 4 not bootin afer modifying build.prop :(

Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909

Resources