What is adbd that can be find in kernel and what it do? I'm trying to port a rom and I use CM7 kernel, but every time it stops at adb_open(adbd). I already tried to modify init.rc without luck. Can someone help me, please??
Anyone??? Is it so hard??? It said that it can't find /system/bin/sh but I put it in system/bin/sh!
Related
Hi all,
I am new to the forum and adroid development. I have recompiled the kernel for the Android HTC Hero but everytime while flashing I get a kernel error on booting. A.K.A hero screen reboot.
My question is how do I create an update.zip from the recompiled kernel zImage.
I created the boot.img cleared the mtd2 device with catting the blackhole to mtd2 device.
Code:
cat /dev/zero > /dev/mtd/mtd2
Code:
flash_image boot /sdcard/boot.img
But after the reboot it keeps panicking.
Some help/pm's would be wonderful.
Thanks
I have encountered this problem before......
How big is the boot.img?
Did you use the right unpack.pl repack.pl?the ones with HTC offsets?
I recommend finding bcrook on the magic forums as ur helped me on this matter
Thanks got him to answer me
Mayb you could post your solution here?
In case someone searches for the problem..
(And i'm just wondering.. )
Sure
http://forum.xda-developers.com/showthread.php?t=551711
This
http://forum.xda-developers.com/showthread.php?t=551711
is quite a good guide for beginners.
Hello.
I am new to the SGS2 game, and since there is no recovery for it yet (or am I mistaken?), I was wondering if you could tell me how to flash themes and different root stuff.
I have used the VillainROM (which is already rooted so I just 'downloaded' the rom only to my device and now i have superuser).
I was wondering if you could tell me how to flash a rom (either through ODIN or w/e else). When I try to adb shell, and go 'ls', it gives me weird things on the screen. So I guess adb is out of question for the time being.
Help is much appreciated.
Thanks.
Mo!
Hi to All memebers
This is my very first post here and expecting help to sort out my problem.
My device is Samsung Galaxy SIII:
Android version 4.3
ro.build.product=m3
ro.build.id=JSS15J
I am trying to root my phone manually with the aid of existing exploit binaries using
adb push <binary> /data/local/tmp
adb shell
cd /data/loca/tmp
chmod 777 <binary>
./<binary>
I used following so far with no success.
From SuperOneClick 2.3.3.zip got psneuter:
When I execute the exploit it says: Failed to set prot mask (inappropriate ioctl for device)
From Motochopper used pwn:
No description just says failure.
From Saferoot used getroot: Your Kernel is patched device not supported
Your Kernel is patched device not supported.
I search on internet, but I could not find a way.
So please help me with above error messages.
Is it not possible to use above exploit binaries to root my device manually, I required no permanent root, I need to root until next re-boot only.
Are there any other ways to try out?
Or is this not possible target?
I am really fed up with this, gave try long period no success no tips, Please kindly help at least to confirm this is not achievable.
Thanks a lot in advance,
GradS.
gradstudent said:
Hi to All memebers
This is my very first post here and expecting help to sort out my problem.
My device is Samsung Galaxy SIII:
Android version 4.3
ro.build.product=m3
ro.build.id=JSS15J
I am trying to root my phone manually with the aid of existing exploit binaries using
adb push <binary> /data/local/tmp
adb shell
cd /data/loca/tmp
chmod 777 <binary>
./<binary>
I used following so far with no success.
From SuperOneClick 2.3.3.zip got psneuter:
When I execute the exploit it says: Failed to set prot mask (inappropriate ioctl for device)
From Motochopper used pwn:
No description just says failure.
From Saferoot used getroot: Your Kernel is patched device not supported
Your Kernel is patched device not supported.
I search on internet, but I could not find a way.
So please help me with above error messages.
Is it not possible to use above exploit binaries to root my device manually, I required no permanent root, I need to root until next re-boot only.
Are there any other ways to try out?
Or is this not possible target?
I am really fed up with this, gave try long period no success no tips, Please kindly help at least to confirm this is not achievable.
Thanks a lot in advance,
GradS.
Click to expand...
Click to collapse
Can Some one help me with this, Am I following worng procedure or isn't there a way to root. Plz help
gradstudent said:
Can Some one help me with this, Am I following worng procedure or isn't there a way to root. Plz help
Click to expand...
Click to collapse
Use CF Root from Chainfire.
Sent from my GT-I9505 using Tapatalk
SeraphSephiroth said:
Use CF Root from Chainfire.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, hope you meant to use it with ODIN. In my case I am unable to use ODIN becasue,
Odin runs in Windows, and I want to work it with Linux/Ubuntu
ODIN is Samsung software, is it forensically accepted to use Odin?
Finally I am doing a college project (mobile forensic) with opensource tools, So I am expecting to provide a root mechanism. For an example I can use saferoot. May I know what odin do in rooting. May be I can come up with a manual steps
Please advice.
Edit: Find an answer I can use heimdall instead of odin
I have a NX008HD8G(manufactured after august 2013), with Stock recovery(android recovery 3e)
I edited the build.prop to change "codename" from "REL" to "L". I need to change this back, since it gets stuck on the final bootanimation(bootanimation.zip)!!! I need to access ADB or terminal or change build.prop from the stock recovery!!! How do i do this? Or can someone give me a stock rom I can sideload?
P.S - ADB does not detect my device when in recovery
And I might get in trouble IRL if I don't fix it within a few months
Please, someone help me!
Sorry for bumping, but I need help.
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
I did same, on accident though, trying to bypass fpr lock after factory reset...honestly i think this phone is ****, being as nobody seems to know anythang bout it. I called asurian and got free replacement.
SaitoSama said:
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
Click to expand...
Click to collapse
I did the same exact thing, so far I've figured out that with that being the newest flash of combination we upgraded the bootloader to binary 3 now, the only firmware that will work is going to be the PVPU3ASC2 which is April's update but online you have to have membership or pay to download, unless that's all a scam? I just did this same wipe on a j327p and had no problem going up from binary 2 to 3 and flashing stock ROM. But from what I understand there's a way to just turn factory off in the combination ROM. I've spent hours pouring over different avenues to go. I was going to change device id to j337U being the unlocked version but I'm getting stuck on gaining SU permissions in the Shell with this new factory binary ROM. I can get adb shell while it's running and side load from recovery but nothing installs or flashes. I believe it's running a sort I emulated VM instead of running ON the phones persistent memory.
FINALLY someone to talk to about this specific problem. It was my fault flashing the U3 combo instead of the U2arj2 I should've.
Attaining root J337p? Dirtycow?
To gain su permissions after reflashing stock have you tried using the dirtycow exploit. I have found it to be an almost fool proof method to attain temp root and for flashing twrp or cwm. Depending on the phone you may have to modify the source a bit but basically jus go to github and download the dirtycow zip or if your using Linux then use git clone and clone the Repository then extract it rename to whatever you want i use the simple dirtycow. put that and accompanying files on the root of the phone (/sdcard) . now use ADB push to push it to /data/local/tmp. Then ADB shell cd into /data/local/tmp and chmod 777 *. Once thats done depending on your phone its gonna be a little trial and error but use ./dirtycow /system/bin/applypatch /data/local/tmp/(the name of your dirtycow applypatch file). Then the same process with app_process or app_process64 depending on the phone. Reboot. That should take SElinux to permissive. Here is where things get tricky. ./dirtycow /system/bin/run-as /data/local/tmp/(name of your dirty run-as file). If you have the exact dirtycow applypatch file for your phone then proceed to thw next step otherwise do whatever mods you gotta do to get your file right. Now run-as exec ./(dirtycow)-applypatch boot. Once that is finished run-as su and presto you have temporary root to do whatever you feel like. I do the next step manually if youd like to. Download the appropriate twrp for your phone name it something memorable like twrp.img and move it to the /sdcard root of your phone. now su dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery. Reboot to recovery and you should be free to flash a permanent root method like chainfire supersu or magisk. And that is that. But i warn you not all phones store the recovery image there you may need to search around a bit. I use su ls -al /dev/block/bootdevice/by-name or cat /proc. Between those 2 i usually can find where it is. I claim no responsibility for bricked phones. Thank you. I will be doing this to my j337p later today ill let you know what i come up with
Ps. If your phone is relatively new its more than likley it has a property called dm-verity which is enable that is a huge pain and causes encryption to fail while flashing. There are .zip files online i believe called dmverityopt.zip or something to that effect i suggest flashing that before and after any custom rom flash. Or a custom kernel that doesnt have that problem.