SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?
atulclassic said:
SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?
Click to expand...
Click to collapse
It should not work on stock OOS as it is not a userdebug build.
MisterCoolBeans said:
It should not work on stock OOS as it is not a userdebug build.
Click to expand...
Click to collapse
but we can change it to userdebug build by modifying the build.prop
atulclassic said:
but we can change it to userdebug build by modifying the build.prop
Click to expand...
Click to collapse
You can try but I believe it won't work.
Our build prop has "ro.build.type=user", Did some searching and found several mods that required changing
"ro.build.type=user" to
"ro.build.type=userdebug"
Go ahead and try it and let us know if it works.
Related
Hi I tried flashing a custom rom on my ZE550ML last week and now have a soft brick(i think). I have looked through many threads and cannot seem to get the answers I need.
During the flashing of the rom I forced restart after about 15 minutes without indication of installation. I didn't make a nandroid backup like i normally do and wiped system cache. I have nothing on the internal storage now and am trying to push the latest firmware from the asus site to the phone but cant get it right.
I am not sure what I am doing wrong with adb. I have the drivers and the firmware. When I reboot to recovery to apply update from adb, I get error saying "closed".
I change the firmware zip filename after watching other vids and reading different posts. Can someone help me understand if either I can't restore my phone or what I am doing wrong.?Thanks in advance!
my command line reads C:\adb>adb push ULZ008WW.ziip /sdcard/ .
eborden said:
Hi I tried flashing a custom rom on my ZE550ML last week and now have a soft brick(i think). I have looked through many threads and cannot seem to get the answers I need.
During the flashing of the rom I forced restart after about 15 minutes without indication of installation. I didn't make a nandroid backup like i normally do and wiped system cache. I have nothing on the internal storage now and am trying to push the latest firmware from the asus site to the phone but cant get it right.
I am not sure what I am doing wrong with adb. I have the drivers and the firmware. When I reboot to recovery to apply update from adb, I get error saying "closed".
I change the firmware zip filename after watching other vids and reading different posts. Can someone help me understand if either I can't restore my phone or what I am doing wrong.?Thanks in advance!
my command line reads C:\adb>adb push ULZ008WW.ziip /sdcard/ .
Click to expand...
Click to collapse
Adb sideload not adb push
miku1024 said:
Adb sideload not adb push
Click to expand...
Click to collapse
I had tried both. Perhaps I was in the wrong location when i tried them. Do I have to go to apply adb update when issuing the adb push command or should i be somewhere else when issuing the adb push command?
Thanks in advance.
eborden said:
I had tried both. Perhaps I was in the wrong location when i tried them. Do I have to go to apply adb update when issuing the adb push command or should i be somewhere else when issuing the adb push command?
Thanks in advance.
Click to expand...
Click to collapse
Yes first apply adb upadate, then adb sideload command
miku1024 said:
Yes first apply adb update, then adb sideload command
Click to expand...
Click to collapse
Ok. I get that part. I do have a couple of other questions:
1. can the firmware be flashed from an external sd card? If so, can it be any firmware version or should it be the most recent I had installed or earliest version?
2. can the windroid universal android toolkit be used during the flashing of the firmware.
I used the toolkit to install drivers that didn't seem to be different from what i already had installed and when I checked that I had the adb drivers it said i had them.
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
808phoneaddict said:
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
Click to expand...
Click to collapse
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
JimSmith94 said:
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
Click to expand...
Click to collapse
Yeah I tried it didn't recognize su...I'll try again later
808phoneaddict said:
Yeah I tried it didn't recognize su...I'll try again later
Click to expand...
Click to collapse
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
JimSmith94 said:
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
Click to expand...
Click to collapse
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
If you have root installed and reboot to recovery, then "adb shell" should get you a # prompt.
If it does, then you're already ADB with root.
If you get $ prompt then you don't have root.
I don't think you can push system files without root?
You certainly can't "adb root" without root. That's for sure.
808phoneaddict said:
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
Click to expand...
Click to collapse
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
JimSmith94 said:
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
Click to expand...
Click to collapse
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
808phoneaddict said:
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
Click to expand...
Click to collapse
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
JimSmith94 said:
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
Click to expand...
Click to collapse
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
808phoneaddict said:
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
Click to expand...
Click to collapse
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
JimSmith94 said:
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
Click to expand...
Click to collapse
O yeah I rooted, was rooted for a while but I ran into the data drain that others are reporting when there is an OTA update...knowing that December is upon us I was trying to unroot but push modified hosts file so I wouldn't get ads. Honestly, if it wasn't for the ads, I have no problem with a stock pixel xl...there hasn't been much development for it just yet, understandable since it's so new...
My goal is to be able to build stock AOSP from source, sign the .img files with my personal keys, flash them to my devices via fastboot, re-lock the bootloader, and then apply updates via adb sideload (with locked bootloader). Verified boot is thus preserved on my device and I can update monthly with the latest security updates. Profit. I followed the procedure as described here:
https://source.android.com/devices/tech/ota/tools.html
https://source.android.com/devices/tech/ota/sign_builds.html
Distilling the instructions, results in this code:
Code:
. build/envsetup.sh
lunch aosp_bullhead-userdebug
make dist DIST_DIR=dist_output
ls -l dist_output/*target_files*
./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs dist_output/*-target_files-*.zip signed-target_files.zip
./build/tools/releasetools/ota_from_target_files -k ~/.android-certs/releasekey signed-target_files.zip signed-ota_update.zip
I was successful in accomplishing my goal (stock AOSP, locked bootloader, updates via adb sideload) with my old Nexus 5 (hammerhead) following the code above. But I have been unsuccessful doing the same with my newer Nexus 5x (bullhead). After loading ~50% of the process via adb sideload, the result is:
RecoveryScreenshot
Any ideas on how to resolve the error? Any ideas what Status 6 means?
Thank you in advance.
Try this HowTo to solve this.
ulxerker said:
Try this HowTo to solve this.
Click to expand...
Click to collapse
Thanks for the advice. My system is Ubuntu so Notepad++ is not available as a text editor. And Gedit doesn't have the options referenced in the video to edit the updater-script.
Mawth said:
Thanks for the advice. My system is Ubuntu so Notepad++ is not available as a text editor. And Gedit doesn't have the options referenced in the video to edit the updater-script.
Click to expand...
Click to collapse
then try it without the spript and just "adb sideload" the ota.zip via twrp and pc command shell.
ulxerker said:
then try it without the spript and just "adb sideload" the ota.zip via twrp and pc command shell.
Click to expand...
Click to collapse
My bootloader is locked. I am trying to use the "stock" recovery that I signed with my keys to sideload the update. TWRP is therefore not an option.
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.
Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all
Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem
Could some with a stock version (not the UK version) upload a unmodified build.prop? My default is missing...
Thanks
Can I do that without root?
SeriousFlash said:
Can I do that without root?
Click to expand...
Click to collapse
If you have adb debugging enabled and the drivers installed on your PC, you could run "adb pull /System/build.prop" from a shell window