Hi,
I am trying to root android N Developer preview Emulator, I have used SuperSu to achieve that and was successful.
Once the root is successful, when I softboot the emulator, Its going to the bootloop (only android boot animation is shown).
I have rooted the emulator using SuperSu-2.70 version.
Can anyone help me on this?
Regards
Satya
Related
Hello!
I don't know how to pass this problem. I have downloaded superuser app but it was futile.
TE can install aps from .apk? And other files management?
Sent from my Nexus S using XDA App
Kalimdor said:
Hello!
I don't know how to pass this problem. I have downloaded superuser app but it was futile.
TE can install aps from .apk? And other files management?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did you root your phone? The superuser app relies on the su binary being installed, in other words, just downloading superuser from the market doesn't root you.
Then, in the terminal emulator app, many commands require you to type "su" to enable the terminal to have root access.
To root I have used this topic :
http://forum.xda-developers.com/showthread.php?t=927838
So I can manage my phone from google SDK adb command line but from Terminal emulator I can't.
Now superuser app is asking me to : 'A zip filr (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary' ...
Well...the superboot method shouldn't need you to install su, it's supposed to do it for you.
The message you're getting is telling you to boot into recovery and install that zip. I don't know if it will flash from the stock recovery, but it will certainly flash from clockwork recovery if you boot into clockwork.
Key I will try from clockw. Stock found problem with certificates.
Rencently, my phone update to the ICS4.0.4 ROM via official rom。
I tryed to root my device use a 4.0.3 root tool (which worked fine with official 4.0.3rom),but it doesnt work.(2.3.6 is doesnt work too).
BOOT:locked
Reproduce
1.Flash the signed su update pack.
2.run the root tool.
the problem seems su command cant run use "su -c"
after update su zip pack ,I try run su use "adb shell su" in bat file , the # is appeared ,but the terminal freezed,the cursor flash continued,i can't input anythiny anymore,so other commane can't be run too.
Any ideas?
I don't believe there is a way to 1 click root 4.0.4 yet. It's a brand new update so the tools may not work.
The only way I could think of to keeping your root would be to downgrade back and the download "Voodoo OTA" root keeper and "Root Check" from the android market.
Voodoo is an app that creates files in your phone that will store the su- binary and restore it when you update your phone.
Root Check will do just as it says: Check to see if your phone is rooted.
So you will either have to wait for the 1 click root to be updated. Or Downgrade an try again.
Hope this helps!
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room! :crying:
Any assistance greatly appreciated!
Bumpty bump?
So what ro.debuggable should be 0 with ro.secure
Hi guys and girls !
I have Samsung Galaxy core 2 sm-g355hm rooted by Stratos ,stock ROM ,custom recovery ,kit Kat 4.4.2. When I try to enter any command in terminal emulator I get segmentation fault or not found. Generally I tryed to install L-SPEED and spark -X (not both of them) but when I type su function i give it root access and then menu I get segmentation fault. So can anybody help me with this ? Also it say I have busy box but I can't check what version .
Why are you flashing through terminal? Head into your custom recovery and flash the rom you want through there.
I'm not flashing trough emulator I try to enter menu of tweak mods (L-SPEED and spark - X ). I searched very hard and found that's myb cause of bad busybox and it's applets that's are probably symlinced wrong. So now If anyone can help me how to COMPLETLY delete that applets and install new busybox ?
Sorry i misunderstood. You can try downloading stericson's busybox from play store and it will automatically install the latest version.
It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.
So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.
I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.
I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works
Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26