I've been trying to restore root to my phone after updating to leaked JB with no luck. I unfortunately forgot to update the su binaries before making a backup so Voodoo is no help. I took a look at Matt's script and ran it trying to get it to work and it installed superSU, but I still don't have root access with it on there. Still tells me permission denied when I do "su" in terminal emulator.
So, I took a look at the script and ran the commands line for line to see what was going on and this is what I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be appreciated as i've been asking this in a couple places and getting ignored.
Alright so I checked permissions on the su-backup and determined that it looks like he's trying to use setuid to inherit permissions. I finally got it working anyway. If they haven't fixed this issue in the first place then couldn't you just do what the original rage against the cage exploit did?
Related
Trying to configure HAVS voltages on my kernel (HTC Evo). Voltage apps function just fine, but I'm trying to push custom voltages using an init.d script (the way viperMOD does -- which also works). Only, my solution isn't.
At first I ran the script from the terminal and it claimed the file vdd_levels_havs doesn't exist (when it clearly does -- I can browse to and view the file). I tried just slipping the file into init.d, rebooting and having it run from there. No voltage change whatsoever. I'm sure it's in the right place -- I'm not Linux noob.
After rebooting, I tried running the file directly again, and strangely it claims the script itself doesn't even exist, when ls clearly says it's right there.
Here's a screen of the weirdness:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What the hell is going on?
Good day!
My android phone is Alcatel OT-978, Gingerbread 2.3.7. After days of extensive research, I really couldn't find a way to root my phone. I had tried each of these methods but they all failed:
- z4root;
-super oneclick;
-gingerbreak;
-zergrush;
-psneuter;
I had stumbled upon some random post on the net saying that another workaround is by "hacking" the bootloader. Using ADB, I had these files on my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My problem is, I can't use the command adb pull on the concerned mtdblock. Every time I use the mentioned command, RE: adb pull /dev/block/mtdblock4 c:\users\ash^03\desktop\system.img, i get the result REMOTE OBJECT '/DEV/BLOCK/MTDBLOCK4' NOT A FILE OR DIRECTORY
Can somebody help me on this. I really need to "hack" or have somebody root my bootloader for me to be able to gain a full root on my device.
BTW, when i type "adb root", it says 'adb cannot run as root in production builds."
Hallo,
i've noticed that when spawning some binaries with (CM10.1 built-in) SSHd they don't work properly. I've tried 'bash' and 'sh' as shell. The same command works properly when executed by adb shell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
sqlite3 /data/data/com.android.browser/databases/browser2.db
Anyone else having these issues or know how to fix that?
Same if you cd to /system/xbin?
Sent from my GT-I9300 using Tapatalk 4 Beta
I couldn't test it yet but there is very likely no other sqlite3 binary than that in xbin. It's also in the path ('which sqlite3'). I guess it has something to do with dependencies. SSHd was completely broken for months (segfault). It was just fixed some weeks ago in CM10.1. Maybe not completely.
It's a shame. Most useful tool ever. Auto completion and colors are not supported with adb shell.
I also tried some dropbear binaries but they don't work at all (segfault).
I could not find any "official" thread forthe Boeffla-Config/Kernel, so I thought I'd give it a chance here.
I am currently running Android 5.0.2, and by looking at Boefflas official page, I could not find a suitable kernel; however I was told CM12 Alpha 9 is supposed to work.
Now to my problem, I just reinstalled my phone, and these are the steps I did concering Boeffla:
Here is what I did:
Downloaded and installed 2.1.67_boeffla-config-v2.apk from official site.
Installed SuperSU among other things (reflashed the phone actually, so Google Play installed alot of apps)
Tried to start Boeffla-Config, granted with SuperSU but was denied.
Removed Boeffla from SuperSU and started it again but no go.
Here is a screenshot of what comes up when I try to start it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had this problem before, but that was ages ago, and I cannot remember how I solved it..
Please, help would be much appreciated.
@maaljen: This is the Link to Boeffla-Thread.
You must flash the Kernel 1st. Then the ConfigApp works. You need the NG-Kernel.
Hi guys
I tried to root my galaxy s9+ android 10
I downloaded a firmware from frija and made a clean installation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed twrp
I made a full data wipe, but it givee errors
I tried to install no-verity-opt-encrypt-6.1.zip but got error also
finally i installed magisk, with no errors
Root checker says that root is ok.
Sometimes phone reboot for nl reason
Do i need to redo the entire operations ? And how to avoid these errors (i tried 3 times with same result)
Thanks
I have the exact problem, I tried every thing I can without any luck, I don't know what is the problem here!
No-one can help us ?