Hi,
there is a problem with my rooted 6.0 soak. Wanted to change system ui sounds and I can't.
I tried to copy some files do media/audio/ui in R/O and R/W mode using Root explorer and it says that copy failed. I also tried to rename those files (like old_sound) that fails too. Then I tried to flash zip file via recovery - nothing changes.
Any solutions?
grzesiek_pl said:
Hi,
there is a problem with my rooted 6.0 soak. Wanted to change system ui sounds and I can't.
I tried to copy some files do media/audio/ui in R/O and R/W mode using Root explorer and it says that copy failed. I also tried to rename those files (like old_sound) that fails too. Then I tried to flash zip file via recovery - nothing changes.
Any solutions?
Click to expand...
Click to collapse
Sure. Switch to cm13.
damn, thanks captain obvious. How about gps problem in latest version of cm13, does it still exist?
Related
hello
my dialer deleted somehow and i want to get it back.
i didnt like other dialer and want the original back or very similar to it.
can someone help me download it.
thanks
download stock firmware, unzip and copy to phone via Root Explorer
"Application not intalled"
marrrek said:
download stock firmware, unzip and copy to phone via Root Explorer
Click to expand...
Click to collapse
I did this. Copied file to system app folder via root explorer. Then tried to install and got "application not installed".
Rebooted and tried again, same result. Any thoughts?
i have been tried to edit build.prop,
got stuck at bootloop,
did that twice,
had to reflash JB Twice,
anyway to make build.prop flashable,
can i just move it to sdcard,
compress it to .zip
and apply update from external storage?
i dont want to flash firmware again and again,
help please.
mj111996 said:
i have been tried to edit build.prop,
got stuck at bootloop,
did that twice,
had to reflash JB Twice,
anyway to make build.prop flashable,
can i just move it to sdcard,
compress it to .zip
and apply update from external storage?
i dont want to flash firmware again and again,
help please.
Click to expand...
Click to collapse
For that we need custom recovery, like we had TWRP in GB. Developers are working on it, and soon we will have that. Meanwhile you can reflash whole firmware.
You can try to use zip file from Shaan's root. Just delete system/app, and system/bin, and put build.prop in system folder. But I am not sure if it will work this way.
I attached how I think it should work. If you got any more bootloops editing it, try it.
i cant,i dont have a pc,
i went to my frnd twice and flashed twice today,it feels bad to go to others house
all the time,
another guy sucessfully edit by solid explorer,
mine got bootloop when i tried by es explorer,
is that got smthng do with es explorer?
mj111996 said:
i cant,i dont have a pc,
i went to my frnd twice and flashed twice today,it feels bad to go to others house
all the time,
another guy sucessfully edit by solid explorer,
mine got bootloop when i tried by es explorer,
is that got smthng do with es explorer?
Click to expand...
Click to collapse
Maybe you better wait for custom recovery. With it would be lot easyer. You will have backup to restore.
I just tried it, it is not working because of signature.
Reboot phone In recovery mode, connect usb, run adb shell In PC:
su
mount -o remount system /system
cat /sdcard/build.prop > /system/build.prop
reboot
(Assuming u have a backup build.prop In /sdcard)
Sent from my GT-I9070 using xda app-developers app
i want to avoid
PC part
mj111996 said:
i want to avoid
PC part
Click to expand...
Click to collapse
Then you have to wait custom recovery.
@shut down,
now we have temp cwn,
can i flash build.zip of build.prop
which i compress by zarchiver?
mj111996 said:
@shut down,
now we have temp cwn,
can i flash build.zip of build.prop
which i compress by zarchiver?
Click to expand...
Click to collapse
I did not try, but I think you can. Just make it CWM compatibile. I have empty zip that is compatibile with TWRP, but I do not know if it is compatibile with CWM. I will try it later.
will wait for you to test
build.zip
mj111996 said:
will wait for you to test
build.zip
Click to expand...
Click to collapse
This CWM is buggy. When I press option install from SD - it refresh. I needed 3 times to push restart to get phone restarted. I am waiting for fully working CWM, and I will try then. I am not pushing my luck after problems with TWRP last time.
YES solid explorer works,
changed to S2,
RESOLVED
Use another .zip that extract things to system, if u replace files In the cwm zip it wont work because of the update-script inside
Sent from my GT-I9070 using xda app-developers app
what you mean exactly?
shut_down said:
For that we need custom recovery, like we had TWRP in GB. Developers are working on it, and soon we will have that. Meanwhile you can reflash whole firmware.
You can try to use zip file from Shaan's root. Just delete system/app, and system/bin, and put build.prop in system folder. But I am not sure if it will work this way.
I attached how I think it should work. If you got any more bootloops editing it, try it.
Click to expand...
Click to collapse
Man, you just saved my phone by this zip. Thank you
Hi, I know this is an old h thread but I'm pretty sure this will be handy to someone
Try this app for an easy way to make an update.zip It's still in beta but seems to be working fine on my N7100 so give it a go...
Zip.me can be found here (playstore)
Cheers
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?
hi;
i was trin to change my boot animation and sound.then i was realize i cant rename delete or overwrite files under system\customize\resource\
but strange thing is if i install boot animations from zip files over TWRP it can be installed.
i was tried also on twrp recovery mode with file manager but more strange thing is i cant see any file under system folder. there is only bin folder nothing more. also tried on est file manager file preferences but there no any permission option. ah also i was tried fix permissions option on twrp options. nothings changed..,
any suggests?
thnx
You need to mount system as r/w. Use ES File explorer
thnx .
when i was tried first it wasnt ask to me what to do..i was uncheck and recheck so i got the mount option.
regards
hi all
i have known green tint pictures problem. my phone has root and also s-off. i tried the method that changes awb.cal file but es file explorer cannot overwrite the file and it gives not enough space failure message. i guess i need to flash a custom kernel but i dont want to do it. so my question is if there is any other way to fix this annoying problem.
ayasun said:
hi all
i have known green tint pictures problem. my phone has root and also s-off. i tried the method that changes awb.cal file but es file explorer cannot overwrite the file and it gives not enough space failure message. i guess i need to flash a custom kernel but i dont want to do it. so my question is if there is any other way to fix this annoying problem.
Click to expand...
Click to collapse
You need an unsecured kernel to write files to this partition or you can try to push the file to the right location using adb from custom recovery or using twrp's file manager.
alray said:
You need an unsecured kernel to write files to this partition or you can try to push the file to the right location using adb from custom recovery or using twrp's file manager.
Click to expand...
Click to collapse
thx for answer . now when i try to change file with twrp file manager it says "file operation complete and under this its written failed" with red. and below its written full selinux support is present and mtp enabled. the second question is if i success this method will the file turn stock when i restart my phone.