Hey guys. I was editing my build.prop to allow google now to be installed and pushed to my rooted SIII.
Now it hangs before the boot animation. I'm running stock rooted. I changed the ro.build.version.sdk = 16. It was 15 now 16 ha. Then also renamed the googlequicksearchbox.apk to .apk1. Tried to reboot and now I'm stuck. I tried booting into CWM Recovery and that works just fine. Also mounted the /system but I can't adb pull the build.prop. No devices detected, USB debugging was on because that's how I was going to push the google now app. Adb also worked before I edited it.
Thanks for your help! :laugh:
I'll just restore my backup I made haha, but for future reference I would still like to know how to adb during cwm recovery .Thanks guys!
Sent from my Transformer TF101 using xda app-developers app
Related
I've done the simple root with NAND setup without hiccup but when trying to backup with ROM manager it says it doesn't have permission.
I have a terminal app and it goes from $ to # when I type su
is there anything I can type in terminal to see if my NAND is actually unlocked?
I also cannot get clockwork to install but titanium has busybox installed.
"An error occurred while attempting to run privileged commands!"
jesusispimp said:
I've done the simple root with NAND setup without hiccup but when trying to backup with ROM manager it says it doesn't have permission.
I have a terminal app and it goes from $ to # when I type su
is there anything I can type in terminal to see if my NAND is actually unlocked?
I also cannot get clockwork to install but titanium has busybox installed.
"An error occurred while attempting to run privileged commands!"
Click to expand...
Click to collapse
seems like you have partial root.
do you have "superuser.apk" installed?
try "adb shell" should give you # automatically.
if not, try the root and nanlock again.
CYBERxNUKE said:
seems like you have partial root.
do you have "superuser.apk" installed?
try "adb shell" should give you # automatically.
if not, try the root and nanlock again.
Click to expand...
Click to collapse
I do have # automatically in adb shell, I'll edit this post in a second when I look for superuser
I do not have superuser.apk
Is there anything I can type in terminal and screenshot that will tell you anything?
did some research and downloaded the busybox standalone app from the marketplace.
It says that I am rooted and I installed the busybox.
No changes. only thing i can think is that my NAND is still locked? any way to check this?
phone info:
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000
RADIO-1.36.00.04.02
MAR 30 2010
do you have a custom recovery?
try this SUPERUSER app
you have to flash it via recovery.
http://bit.ly/su222ef
if you want to check nand..
try this command.
"adb remount"
from command prompt.
if it fails, you dont have nand.
if it completes succesfully you have nand access.
I don't have a custom recovery, can't get any to work or I'm just not doing it right... I'm coming from Windows mobile...
Here's a screen cap of what you requested except on the phone and not adb, don't think it matters for this simple test.
EDIT: Thank you very much for your help with this.
I had the same problem. I re-rooted using OTA SimpleRoot and also tried unrevoked and still had errors trying to flash Clockworkmod recovery. I went into Menu>Settings and clicked on Advanced Mode and it worked.
Will try to help whrn I get to san antonio
Sent from my PC36100 using XDA App
You have nand unlocked since you hboot it 76 not 79
I Actually got it running. Once I got a recovery to work the rest was a snap... now I have damage control Rom and my Facebook contacts won't sync to my phone. Any tips?
Sent from my PC36100 using XDA App
Phone worked great until the 2nd time I changed my battery... locked into bootloop and had to recover.. lame. I have superuser now btw.
Sent from my PC36100 using XDA App
I don't think I can edit from phone? Sorry is I can here's a ss
Sent from my PC36100 using XDA Ap
Uninstall and reinstall. Wait for superuser window to pop up, then grant permission.
Sent from my PC36100 using XDA App
Rom manager works now I can't use nand roms though.
Sent from my PC36100 using XDA App
Bobby_C said:
I had the same problem. I re-rooted using OTA SimpleRoot and also tried unrevoked and still had errors trying to flash Clockworkmod recovery. I went into Menu>Settings and clicked on Advanced Mode and it worked.
Click to expand...
Click to collapse
Thanks a lot for this! I spent all day trying to figure this out. It seems unless Advanced Mode is enabled this doesn't work. FWIW I'm using DC 3.2.3. Once I enabled Advanced Mode I was able to flash to the latest version of ClockworkMod Recovery!
Thanks for this post!
Hey guys
Hoping someone can help me sort out my Galaxy Ace.
I've royally f**ked up my phone while trying to re-install stock email.
Followed some instructions and accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Phone is now in a boot loop.
I've updated from sd card to installed Clockworkmod recovery.
So far I've tried wiping cache and dalvik cache with no joy.
Also tried fix permissions, still nothing.
Hoping you can guide me through a fix for this.
Would greatly appreciate your help.
Cheers
Paul
factory reset it
tried that - not working either
mitchst2 said:
Hey guys
...accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Click to expand...
Click to collapse
Show us the instruction.
What exactly did you do?
Can't you connect your phone to the computer, maybe during recovery.
Open adb shell, and fix the permissions ?
chmod +x /system/app ?
Might have to remount system readwrite before that.
Due to xda new member rules, I have to resort to the General Section. The new ICS kernel, has locked down adb root access. What this means is when you adb shell you will be dropped into normal shell (even though you have su installed). This would probably help ROM creaters who are bundling the kernel. It has init.d support and the bootanimation (this file should be /system/media/bootanimation.zip, if it does not work, link it as sanim.zip)
* This also defaults to bash shell when you (adb shell) not the default ICS mksh. Also, it can read bash_profile from /sdcard/bash_profile
db.tt/RcDapiMg (prepend with) as xda does not allow this yet
Cheers
Click to expand...
Click to collapse
Simply posting this for mohan_kr. This deserves more attention than just the General section.
Original Thread:
http://forum.xda-developers.com/showthread.php?p=24208186
db.tt/RcDapiMg
sorry but how is this different from the kernel romracer released?
I think its exactly the same. Regardless neither one let me delete the .qmg files in system/media in order to add a bootanimation
Swyped from my Galaxy S2 Skyrocket using XDA premium
bts0uth said:
I think its exactly the same. Regardless neither one let me delete the .qmg files in system/media in order to add a bootanimation
Swyped from my Galaxy S2 Skyrocket using XDA premium
Click to expand...
Click to collapse
I was able to use bootanimation.zip on this kernel.
-----------
sent from my calculator with android
does this kernel fix the reboot/power issue? i found that the original ucalc kernel actually made my phone less stable and lagged horribly. i was using it with the ics smooth ice rom.
Bootanimation.zip confirmed working on this kernal along with being able to edit files under /system unlike before
Sent from my SAMSUNG-SGH-I727 using XDA
jnicks510 said:
does this kernel fix the reboot/power issue? i found that the original ucalc kernel actually made my phone less stable and lagged horribly. i was using it with the ics smooth ice rom.
Click to expand...
Click to collapse
Someone said freezing shutdown app fixed it for them in another thread
Power/reboot works for me now, as does a custom boot animation. Great work! Any chance we can get the BLN mod put into this kernel?
+1 for BLN
onearmedscissor said:
Someone said freezing shutdown app fixed it for them in another thread
Click to expand...
Click to collapse
I tried this, didn't work, still gets stuck on Shutting down...
I flashed the CWM Touch recovery and found that the shutdown/reboot freezing was gone.
I used the odin flash with the Roboto font from here: http://rootzwiki.com/topic/19217-recovery-clockworkmod-touch-5504-v2/
oh, and after flashing this CWM, I reflashed the superuser zip and was finally able to mount and modify /system
morehush said:
I flashed the CWM Touch recovery and found that the shutdown/reboot freezing was gone.
I used the odin flash with the Roboto font from here: http://rootzwiki.com/topic/19217-recovery-clockworkmod-touch-5504-v2/
oh, and after flashing this CWM, I reflashed the superuser zip and was finally able to mount and modify /system
Click to expand...
Click to collapse
Did nothing here. Used roboto font version through ODIN and reflashed super user...
Shutdown / restart is still hanging for me.
I still can't modify system.
bts0uth said:
Did nothing here. Used roboto font version through ODIN and reflashed super user...
Shutdown / restart is still hanging for me.
I still can't modify system.
Click to expand...
Click to collapse
Try reflashing this kernel with the new clockwork mod touch, then reflash superuser, then reboot recovery and fix permissions.
morehush said:
Try reflashing this kernel with the new clockwork mod touch, then reflash superuser, then reboot recovery and fix permissions.
Click to expand...
Click to collapse
Got remount,rw of system working by reflashing the UCALC4 one click, then CWM 5.5.0.4, then this kernel and superuser via CWM, only then allowing system to fully boot. Then installed busybox.
Seems that if UCALC4 stock kernel is allowed to fully boot I'm not able to remount system as rw. It appears to remount, but the /proc/mounts shows it as ro and attempts to write system result in 'read-only filesystem'.
cschmitt said:
Got remount,rw of system working by reflashing the UCALC4 one click, then CWM 5.5.0.4, then this kernel and superuser via CWM, only then allowing system to fully boot. Then installed busybox.
Seems that if UCALC4 stock kernel is allowed to fully boot I'm not able to remount system as rw. It appears to remount, but the /proc/mounts shows it as ro and attempts to write system result in 'read-only filesystem'.
Click to expand...
Click to collapse
Yup, the stock kernel the f**ls changed the adbd to not honor the ro.secure flag. If you have any ICS builds, drop in the adbd and viola...
This fixed my power off issue. Thanks mohan and thanks for posting this. Now after this and running silver's rom I am full of Ice Cream Sammich goodness.
Sent from my SAMSUNG-SGH-I727 using xda premium
Ooops never mind. This was meant for a different thread.
Sent from my SAMSUNG-SGH-I727 using xda premium
I posted this in the Nexus 7 section, but this can apply to all AOKP based ROMs that have the "Permissions Manager" option.
Running SmoothROM with 4.2.2 (I think) and I was messing with the "Permissions Manager" settings under "Settings". I turned off several permissions on Facebook, such as SMS view/sender and location on it as well on some other apps. I then rebooted the tablet and now I'm stuck on a boot loop. I don't get how because these aren't system apps, so I don't think it should affect the system booting up at all. Sadly I didn't make a nandroid backup before doing this, since I thought the worse that could happen would be the apps force closing which is easily fixed. Since I didn't make a backup I rather try things that wouldn't make me lose any data.
I can get into recovery (TWRP) and have already made a backup of the current boot looping state. I have already tried deleting cache and dalvik-cache and still won't boot.
I have an idea: Turning the "Permission Management" setting to "Off" would make the apps have their default permissions. I would have to get into /data/data/com.Android.Settings and find the "Permissions Management" setting and set it to "false" or "off" through ADB. So I would have to pull the file and push the edited file back through fast boot or recovery. Anyone think this would work??
FWIW: I updated the kernel (Franco) with his franco.Kernel app 1 reboot ago, but it rebooted fine, not sure if it could be the kernel that has me in this bootloop?
Sent from my DROID RAZR using Tapatalk 4
Fix permissions in recovery mode
Sent from my GT-P3100 using xda app-developers app
sukkukikku said:
Fix permissions in recovery mode
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
I'm not talking about .apk or file permissions. I'm talking about permissions apps request, such as location, internet access, billing, reading contacts, etc. That's something the "Fix permissions" option in recovery mode has nothing to do with.
rda990 said:
Thanks for the reply.
I'm not talking about .apk or file permissions. I'm talking about permissions apps request, such as location, internet access, billing, reading contacts, etc. That's something the "Fix permissions" option in recovery mode has nothing to do with.
Click to expand...
Click to collapse
Im sorry but it sounds like if this issue cant be resolved you might need to reset youre phone but try to go into recovery mode and mess around and see if you can find anything that has to do with booting, good luck and ohh one more thing if all else fails in recovery mode try and find the wipe cache partition option and proceed to that ^.^ :good::good::good:
If you have the backup file you can try to reflash the rom
Sent from my GT-P3100 using xda app-developers app
^ also a very good idea
Sent from my SPH-L710 using XDA Premium 4 mobile app
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 ?