Can someone with an S-on unrooted phone please create a file in the root of the sdcard called cw.prop containing the following line
Code:
persist.service.adb.enable=1
then reboot into recovery and try to access the phone via adb. I am exploring the OTA update recovery and /init.rc contains the code to enable adb while /sbin/recovery has a reference to the above file.
PS: if that fails please do the same with /data/cw.prop and /cache/cw.prop
Related
If This has been posted already, I apologize...I Take No Credit For This.....This is the Recovery that was released with Toastcfl's Unlocking NAND. It's not much different from R.A-evo-v1.7.0.1 but I like it.
Assuming you have adb and fastboot access.....
TO INSTALL USING FASTBOOT:
1. Unzip NANDrecovery.zip and put attached file (NANDrecovery.img) in sdk/tools
2. Boot into Fastboot USB
3. Open command prompt and execute this command: fastboot flash recovery NANDrecovery.img
4. Reboot Recovery
ALTERNATE INSTALL:
1. Make sure the "flash_image" that Toastcfl provided during NAND unlock is in the /system/bin folder and also put NANDrecovery.img on root of sdcard(Unzip flash_image.zip)
2. Go into adb shell and execute command: mount /system ENTER execute command: mount /sdcard ENTER
3. Execute command: flash_image recovery /sdcard/NANDrecovery.img
4. Reboot Recovery
Can you post a couple images?
snandlal said:
If This has been posted already, I apologize...I Take No Credit For This.....This is the Recovery that was released with Toastcfl's Unlocking NAND. It's not much different from R.A-evo-v1.7.0.1 but I like it.
Click to expand...
Click to collapse
It's Toastcfh, fyi
if you wouldve posted this 2 days ago, i wouldve been estatic but after going through my files for 2 days i finally found the recovery image. the recovery image in the part2 thread doesn't work.
what is this, is it recovery 1.7.0 vs 1.7.0.1
This is the recovery you had to plug into usb and run the windows.bat file after flashing Toastcfl's PC36IMG...To temporarily see what it looks like and does: Boot into your recovery mode, open up the evo-recovery file from when you unlocked NAND, for windows; run recovery-windows as admin and the recovery will push to your phone temporarily; for linux do recovery-linux and for mac do recovery-mac ....These recovery files are in the "evo-recovery" folder
ahh i rememeber that recovery
Can you please dump the system as I want to see what has been changed/updated from 2.40. It's actually quite simple, no root needed, just run this command through adb in Windows. Zip the folder and upload somewhere
Code:
adb pull /system c:\system
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Shedopen123 said:
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Click to expand...
Click to collapse
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Shedopen123 said:
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Click to expand...
Click to collapse
You don't flash SuperSU.zip with adb/fastboot.
Move the SuperSU.zip file to your device's internal storage or put it on an external sdcard, then boot into TWRP and choose the "install" option, then browse to where you stored SuperSU.zip and flash it.
In my first reply to you, I didn't say anything about flashing SuperSU.zip in a terminal, I told you to boot into TWRP and flash SuperSU.zip. Pay attention to what is told to you, word for word.
You could have easily done some searching to understand those instructions. Learn to search for answers.
You need to be rooted first, then you can find and edit build.prop.
Build.prop is very easy to find, again, learn how to search for answers.
Build.prop is located in /system/build.prop. It's in system partition, not in your internal storage.
Try using adb pull to get a copy of build.prop then edit the copy, save the copy and adb push it back to its location in /system/build.prop.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Can someone who has an Essential Phone (PH-1) upload a zip of the system dump. Run the command below in ADB to pull the dump (no root required):
Code:
adb pull /system PH1_system_dump
The dump will be pulled to a folder called "PH1_system_dump". Zip and upload that folder so we can begin development on this device.
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
cabegol said:
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
Click to expand...
Click to collapse
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Shawn5162 said:
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Click to expand...
Click to collapse
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
bmg1001 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
Click to expand...
Click to collapse
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Shawn5162 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure: I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Click to expand...
Click to collapse
Someone in this thread managed to get the boot.img. I downloaded it and tried rooting it with Magisk but it didn't work. He already has TWRP and Lineage but they're still unreleased as its being worked on. I can't try the boot image anymore since I'm on the newest update and the image posted was for the previous update.
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583/page3
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Look on the post below the guy already pulled the zip file already. I pushed it to my device via adb.
invisiblek said:
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Click to expand...
Click to collapse
is the touchscreen daemon the last piece of the TWRP puzzle? Can it be manipulated with vol + - and power buttons?
Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes