Right now I just want root access with Adb. ( And I know there is manual updates)
So I was wondering what checksum system Asus uses for updates.
A simple change to default.prop and touching back to the same date, may pass a checksum.
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
Looks like I have something to play with this weekend.
Related
Using the stock 9.2.1.11 kernel in recovery, I noticed that adb is disabled completely. When new OTAs come out, I usually smash the ramdisk from roach's 3.2.0.1 recovery onto the new kernel. With the 9.2.1.11 update, this had the effect of disabling adb because the init.rc and props have changed.
I'm certainly not an expert and I think few people actually update the recovery kernel, but here's how I got it working again...
I poked around in the stock recovery ramdisk and copied over the ueventd*.rc (3) and init.rc files to roach's ramdisk. I changed the default.prop as below and, after mkbootimg, blobpack, zip, sign, etc., ... voila! The stock init.rc has all the extra partitions and mounts them right off the bat -staging, cache, btmac? ... again, I'm not a pro at this, and to be blunt, I barely know what I'm doing at this level. I think most of the magic happens in init.rc and the old version doesn't pick up the same default props. I'd make a flashable zip, but I think it will cause more bootloops and mismatched bootloaders and kernels.
I should note that flashing the recovery and the rom at the same time isn't advised if you don't have access to nvflash!
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1 #probably don't need this anymore
persist.service.usb.config=adb
service.adb.root=1
ok so im not responsible for anything that happens to you or your tablet....
this will add HW acceleration and adb in your build.prop(not fully test on g tab) and some other things with the kernel
lets begin
this has been only tested on ICS right now ill test on GB later
this WON'T work with a build.prop editor you are going to have to open the actual file
you NEED to be ROOTED
there are 2 ways of doing this and i will show both methods...
method 1.)
Code:
1.) with a root file explorer goto /system
2.) long press on the build.prop file till the menu comes up
3.) press "open in Text Editor
4.) paste the code into your build.prop and hit back
5.) when it ask if you want to save your changes hit yes
6.) reboot
note:**this was done with Root Explorer; it might and very well could be different in other apps.**
method 2.)
Code:
0.) you need the android sdk and adb working
1.) adb remount
2.) adb pull /system/build.prop
3.) open the file and paste the code into your build.prop
4.) adb push build.prop /system
5.) adb reboot
here is the code please add it to the end, so after whatever your last line is add this
Code:
ro.secure=0
ro.debuggable=1
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.mount.playsnd=0
persist.service.debuggable=1
ro.ril.disable.power.collapse=1
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
com.qc.hardware=true
debug.enabletr=true
ro.min.fling_velocity=8000
ro.max.fling_velocity=12000
ro.config.nocheckin=1
video.accelerate.hw=1
Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:
Naphtha said:
Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:
Click to expand...
Click to collapse
Hello,
As a senior member, you probably know that logcat is your friend. Since you may not have found how to simplify adb access for 4.4 builds, temporarily add this to your device tree (in the <your chipset name>.mk):
Code:
# Since Android 4.2.2, USB debugging requires authentication, something that is not possible during boot.
# To disable this, set the following property in default.prop (inside initrd):
# ro.adb.secure=0
# To get root access this is a must:
# ro.secure=0
# will allow you to run adbd as root via the adb root command:
#ro.debuggable=1
#service.adb.root=1
ADDITIONAL_DEFAULT_PROPERTIES += \
ro.secure=0 \
ro.adb.secure=0 \
ro.debuggable=1 \
service.adb.root=1 \
persist.service.adb.enable=1 \
persist.service.debuggable=1
Build that, flash, and then take a logcat while booting. You should be able to see what;s going on (even if you need another set of eyes...even then this thread is good for that).
Hope this helps, and good luck!
Thanks so much!
Inviato dal mio MX4 utilizzando Tapatalk
I am very sorry if this is a dumb question, I have been having sex with this phone for a few days and I have no idea what I am doing. and my wife is going to kill me if I don't get her phone and data up and running soon :crying: so I was trying to recover some files that got acidentally removed from the device and I decided to root it. I thought, it's not going to be a big deal... and so I didn't backup. (facepalm)
So I used instruction on gadgethacks dot com (can't post a link because I am new here), however I ignored the part where they say you need to validate that your phone is compatible. (again, facepalm)
I flashed AP = CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5 using Odin3-v3.10.6.exe and now when the phone restarts I get "Verification failed Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase your data."
Then I discovered that in download mode it says that my phone is SW-G930W8
Then I found this file and I tried to flash it.
CF-Auto-Root-heroltebmc-heroltebmc-smg930w8.tar.md5
same error message.
Then I flashed twrp-3.2.3-0-herolte.img.tar
I can get into the twrp recovery, but still can't boot the system. then I used adb in twrp mode but can't see any of my wife's files in internal memory, I am guessing because they are on an encrypted partition or something like that. but I can access /system/ and so I found a file called build.prop where it says that my Android version is G930W8VLS3BRC2
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.display.id=NRD90M.G930W8VLS3BRC2
ro.build.version.incremental=G930W8VLS3BRC2
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2018-03-01
ro.build.version.base_os=samsung/heroltebmc/heroltebmc:7.0/NRD90M/G930W8VLU3BRB2:user/release-keys
ro.build.version.security_index=1
ro.build.date=Thu Mar 8 14:44:49 KST 2018
ro.build.date.utc=1520487889
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHE9410
ro.build.tags=release-keys
ro.build.flavor=heroltebmc-user
ro.product.model=SM-G930W8
ro.product.brand=samsung
ro.product.name=heroltebmc
ro.product.device=heroltebmc
ro.product.board=universal8890
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-CA
ro.wifi.channels=
ro.board.platform=exynos5
so I found this amazing site called firmware.mobi where I was able to get a recovery from that specific version of android... and still the same error message comes up.
So I was following the instructions of the root manual so I have developer mode turned on and "OEM unlock" enabled if that helps at all.
Please help me Any advice is very much appreciated.
Question 1: Is it possible to save the data in the internal memory of the phone? i.e. either boot the system or fetch and decrypt the partition? How?
Question 2: If not, then how do I at least get the phone to work again? Just do what it says and wipe it? Or flash some complete stock ROM?
So nobody knows? Or is my question so dumb that no one wants to bother to answer?
Is it possible to enable root debugging from the command line. The rom that I'm using is missing the setting in developers options. When trying adb root I get the
Code:
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I don't believe it's totally disabled because I don't get the "adb root is not allowed in production builds". I think it's there but no switch to toggle. Haven't found anything searching for setting name and would need correct value and table if it can be set. Anybody know how to toggle it on from shell ?
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
jwoegerbauer said:
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
Click to expand...
Click to collapse
Thanks, actually looking into it, I don't know what to think about it. It is a user build of crdroid. I can not and absolutely do not understand the point of building a user build to post on XDA. The fact that someone is installing a custom rom kinda throws a user build out the window AFAIFC. It didn't even dawn on me to check if it was userdebug or not, in my mind, of course it is. That's what I get for thinking I guess. I like CrDroid so syncing source now, time to sync and build I should have an eng build in about 3 hours.
Take note that if adbd in your phone's firmware is build without ALLOW_ADBD_ROOT then you're wasting your time.