Hello Gentlemen's
I am having One Plus One A0001
I need to install SU on it , but i cant install Update SU.zip from Cyanogen Recovery
(there were 4-5 option's)
{
1. Reboot
2. Apply Update
3. Wipe Disk/Factory Reset
4 .Wipe Caches
5. Wipe Media
}
When i tried to install SU from Apply Update
It was giving me signature error .
So please you people help me?
I get this information from this forum
Code:
You can s-off and after it gets root and you have s-off, (after you run revone -s 0) then:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 04755 /system/xbin/su
Then you just simply install the SuperUser app from the playstore.
I was not able to understand any of this ,
So Please help me to install SU as i need root access for a particular app.
PS:
I dont want to install Custom Recovery , as i want to keep like it only .
Thank You Very Much
Hi
Thanks for writing to us at XDA Assist. You can't install SU from the CM recovery because the CM recovery can only install zips signed by CM. In order to root your phone you need to do this:
1. Unlock the bootloader.
2. Install a custom recovery.
3. Use TWRP recovery to install SuperSU.
I put together a guide specifically for this phone which is very detailed and will explain all you need to know, you'll find it here:
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Good luck, and if you have any questions please don't hesitate to ask in the guide thread.
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. You can't install SU from the CM recovery because the CM recovery can only install zips signed by CM. In order to root your phone you need to do this:
Good luck, and if you have any questions please don't hesitate to ask in the guide thread.
Click to expand...
Click to collapse
Firstly Thank You for your valuable reply .
So we can't push files manually in /system/bin like locations ?
After reading deeply about rooting and what is actually does , I understand that twrp just pushes files for us that busybox and Superuser.apk in read-only file systems which cant be accessed by side-load or MTP's .That UPDATE-SuperSU-v2.46.zip it is a universal kind of rooter, it is having all kind of files for rooting almost all kind of phone with different architecture's.
My Point is cant we manually push those files by adb interface in USB debugging mode , by SDK's or other command-line executable ?
and my issues are in those method's like ./psneutor is not working for me
Reference
http://forum.xda-developers.com/showthread.php?t=2684210
No you can't just push it. The way to root this phone is how I outlined it above. Is there a reason you don't want to unlock your bootloader?
No response, thread closed.
Related
Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.
Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?
Here's the SE link with my issue.
https://android.stackexchange.com/questions/131577/cannot-remove-rename-move-build-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
XDA Visitor said:
Here's the SE link with my issue.
https://android.stackexchange.com/q...-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
Click to expand...
Click to collapse
Hello,
Since adb works for you. You can try these (One by one)
Code:
adb root
adb remount
adb pull /system/build.prop
Make the required changes which you messed in build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
Alteratively, you could register for a XDA Account so you could reply to the threads in the forums as well as get expertise help
-Vatsal
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
UsernameNotRecognized said:
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
Click to expand...
Click to collapse
Hello,
You need to get adb root working, Try running it as administrator.
If still doesnt work, then give a try to this
-Vatsal
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
UsernameNotRecognized said:
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
Click to expand...
Click to collapse
Hello,
Well, you edited build.prop and saved that so that would mean you were rooted? Isn't it?
ADB commands work without root. However the /data partition is only accessible by rooted users* and while /system can be read by anyone, it's a read-only partition and root is needed to remount it as writable.
-Vatsal
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
UsernameNotRecognized said:
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
Click to expand...
Click to collapse
Hello,
You may try posting your query here regarding this.
Android Q&A, Help & Troubleshooting or [URL="http://forum.xda-developers.com/showthread.php?t=2259645]General Q&A[/URL]
The experts there maybe able to assist you
-Vatsal
Abstrk_2dx said:
just flash the stock build.prop it will boot up
Click to expand...
Click to collapse
Yeah.... How
Spflasher doesn't work.
I do have a rom, but spflasher does not work.
UsernameNotRecognized said:
I do have a rom, but spflasher does not work.
Click to expand...
Click to collapse
Hello,
Read the post above, You may try asking there in that forum/thread. The experts there may be able to assist you
-Vatsal
I have but no one has replied as of yet.
UsernameNotRecognized said:
I have but no one has replied as of yet.
Click to expand...
Click to collapse
Hello,
I would recommend you waiting and having a bit of patience untill they figure out your problem and reply to it.
Thank you
-Vatsal
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
Hey have a Nploe tablet rooted and wanted to put a custom rom one it. I'm having trouble finding one.
How'd you root it? I can't get mine to root at all.
Npole 10.1 nt103
MLP1295 said:
Hey have a Nploe tablet rooted and wanted to put a custom rom one it. I'm having trouble finding one.
Click to expand...
Click to collapse
Mine has 6.0 interested in 7.0 upgrade
How did you root this tablet? Please share.
Successfull Root! (still need android 7?)
Hi All,
I just rooted this device!
Since OP is not responding, I thought I would share (BTW I really want to get this device to android 7. Or at least get multi window into android 6, so hopefully someone can help)
SO!
Roughly speaking I followed this guide with some notes (below):
https://forum.xda-developers.com/showthread.php?t=2684210
Notes:
dont adb push the files where the guide says, dont use nautilus, Do use their files.
Once you have downladed their zip, and unzipped, in terminal:
adb start-server
adb reboot recovery
On the tablet (once you see recovery): mount /system
then back to their tutorial, push all the files they sugest, but push them to /, E.G.:
adb push su /
adb push busybox /
adb push Superuser.apk /
then adb shell, and do the chmod they sugest (remember your files are just there in root)
then move the files to the corret location
then reboot.
Job done.
If you have any issues ill try to help, but really I just followed that guide and guessed hard when it didnt work.
If anyone can take us from Root to Android 7, that would be great!
Regards,
code-forger