ADB on bricked devices - Android Q&A, Help & Troubleshooting

Hello
My tablet is soft bricked so i want to apply update from ADB but it keep saying "E: Failed to open driver control. Permission denied"
My tablet is: Lenovo TB-X605F
I tried everything to repair this tablet but nothing work
Please help me

XX_MRBEAN_XX said:
Hello
My tablet is soft bricked so i want to apply update from ADB but it keep saying "E: Failed to open driver control. Permission denied"
My tablet is: Lenovo TB-X605F
I tried everything to repair this tablet but nothing work
Please help me
Click to expand...
Click to collapse
Do you have a custom recovery installed to sideload a stock/custom ROM flash able zip? You won't be able to use stock recovery for flashing. Usually ADB isn't accessable unless set in the default.prop file

@XX_MRBEAN_XX
What ADB subcommand returns that error?
Typically "Permission Denied" is returned when a subcommand gets invoked that only works on a R/W-mounted device or requires ROOT.

jwoegerbauer said:
@XX_MRBEAN_XX
What ADB subcommand returns that error?
Typically "Permission Denied" is returned when a subcommand gets invoked that only works on a R/W-mounted device or requires ROOT.
Click to expand...
Click to collapse
In recovery menu, i select "apply update from ADB"
Beforce i connect my tablet to my pc it's say "E: failed to open driver control. Permission denied" Stopping adb
And my tablet is not recognized in adv devices

XX_MRBEAN_XX said:
In recovery menu, i select "apply update from ADB"
Beforce i connect my tablet to my pc it's say "E: failed to open driver control. Permission denied" Stopping adb
And my tablet is not recognized in adv devices
Click to expand...
Click to collapse
That's NOT an ADB subcommand, but an option offered by your tablet's Recovery Menu.
Take note that ADB consists of three components
A client, which runs on your desktop computer
A server, which runs as a background process on your desktop machine. It manages communication between the client and the daemon running on the Android-powered device
A daemon, which runs as a background process on the Android device. FYI: That automatically gets started when device boots up if enabled in Android's system settings - keyword: system file named build.prop, there settings ro.secure=0 & ro.debuggable=1.
My advice: Download from Lenovo's website the USB-driver that matches your tablet and install it: never use any other USB-driver !

jwoegerbauer said:
That's NOT an ADB subcommand, but an option offered by your tablet's Recovery Menu.
Take note that ADB consists of three components
A client, which runs on your desktop computer
A server, which runs as a background process on your desktop machine. It manages communication between the client and the daemon running on the Android-powered device
A daemon, which runs as a background process on the Android device. FYI: That automatically gets started when device boots up if enabled in Android's system settings - keyword: system file named build.prop, there settings ro.secure=0 & ro.debuggable=1.
My advice: Download from Lenovo's website the USB-driver that matches your tablet and install it: never use any other USB-driver !
Click to expand...
Click to collapse
Okay i'll try that !
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??

XX_MRBEAN_XX said:
Okay i'll try that !
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??
Click to expand...
Click to collapse
Yes, but stock recovery may fail unless it accepts test-key signed zips. If not then you'll need a custom recovery that allows to do so or to disable a signature check
That or if your bootloader is unlocked you can modify the recovery file to replace /res/keys with a test-key one and use stock recovery to flash test-signed files

XX_MRBEAN_XX said:
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??
Click to expand...
Click to collapse
Using ADB sideload, you can easily sideload any signed and/or unsigned ROM and any signed and/or unsigned MOD zip files: no need for any external SD-card. IMHO that's the most convenient method.
Code:
adb devices
adb sideload <PATH-TO-ZIP-FILE>

Related

Official "How To" root Lenovo Tab S8-50

Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.

Bypass secure USB debugging prompt on phone with broken screen

Hello everyone,
I have a Samsung Galaxy S II (I9100) with Cyanogenmod 11 (Snapshot M12) installed. Recently I dropped my phone and the screen was completely shattered. The display does not work, neither does the touch. However, the phone works fine as I can turn it on and connect it via USB to my computer and access the data on my internal memory. Although USB debugging is enabled on my phone, I am unable to do anything because the computer isn't authorised i.e. I cannot press "OK" on the authentication prompt that I would have otherwise normally seen on the screen (screenshot attached). Is there any way to bypass this prompt or a workaround for it? I basically need to get a Nandroid backup of my phone and then factory reset it.
P.S.: I tried to access my phone via a program called "Android Control" but apparently it is practically useless without the debugging privileges.
Thanks.
Solved!
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Thanks man.
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
I too am a noob who was trying to follow this guide, which also exactly fit my situation. My status was a broken Sony Xperia screen with USB debugging enabled, but I was unable to click on the "accept" button whenever I hooked my phone up to my PC. I extracted a working adb_key from my new Asus ZooXS phone; neither phone is rooted, and both are running stock Android OS.
Unfortunately, I got stuck right between Steps 7 & 8; Windows did not allow me to use the ADB Push command to copy the key onto my broken Sony Xperia. I could Pull the key from my Asus using ADB just fine, but not the other way around.
I did eventually find an alternative solution: I used an OTG device & hooked up a mouse to my Sony Xperia so that I could get past the broken screen issues & navigate to Settings > Bluetooth. I then borrowed a Bluetooth Mouse & "discovered" it with my broken Sony Xperia. I could then unplug the OTG device & re-connect my phone to my PC via USB, & then click on the screen using the Bluetooth Mouse to "accept" my computer as always being authorized to perform USB debugging. Afterwards, I was able to use Helium backup to pull off most of my important data from my phone.
Hope this helps others who are running into the same problem....
i don't get it - authorizing adb via adb
The steps maq_ posted helped me rescue my data from my broken OP3. Combined with the information from here: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android which indicates the files between the computer (running adb) and the key file you copy to /data/misc/adb should "match" with each other. Indeed, you might need to have been bootloader unlocked (with a custom recovery) to use adb push to copy the adb_keys file to your broken phone. For me, since my broken phone was rooted I used a terminal emulator with the 'su' command (after successfully getting the file onto my broken phone) to copy the file over to /data/misc/adb.
Some tips that might help newbs before following maq_'s steps: First, re-install another copy of adb (remember the path you installed to on your PC). Second, erase contents of c:\Users\$name\.android\ (which contains existing keys generated by adb). Third, run adb kill-server to make sure other instances of adb don't confuse things.
maq_ said:
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Click to expand...
Click to collapse
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
edit2: most recent version of that backdoor script can be found here
https://forum.xda-developers.com/showthread.php?t=4111923
my touch is broken and i cant select usb authorization as ok... device is not rooted...
device name is sony z3...
i have another device with 4.4 and with that device i made a backup of drm keys... now what should i do?
sorry if english is bad... helpwill be really appriciated....
hello, i have te same problem with my huawei p smart. does this work for huawei to?
no, but you can connect OTG keyboard and unlock screen. that should unlock MTP you can at least transfer pictures. even Monitor via MHL/HDMI is possible for some devices
https://dtmedia.tech/list-of-mhl-compatible-phones
speedin said:
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
Click to expand...
Click to collapse
Hi
I have the same connection impact when I use adb command too. Is there any solution for this situation?
Thank you.
aIecxs said:
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
Click to expand...
Click to collapse
ThanK You Senior for posting the solution.
Can you please help me in this.
I am using mediatek device
Didn't find /system/etc/init.d
Didn't find /system/etc/install-recovery.sh
But found "" install-recovery.sh "" inside /system/bin folder
Now do i have to only paste the your given rsa_copy.sh scrip in this file?
and paste the pub_keys from authorize device to /sdcard/
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
I have android 7
mt6753
init.d is n't here
placing code inside install-recovery.sh didn't work because it runs with root privileges
now i am trying to cp /system/adbkey.pub /data/misc/adb/adb_keys
and tring to modify boot.img
aIecxs said:
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
Click to expand...
Click to collapse
Senior Help. (I am extra noob)
I also noticed data folder inside boot.img can I directly put " adb" folder here?
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
I tried this on other working phone
@osm0sis may have a look into boot.img can you upload please?
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
aIecxs said:
@osm0sis may have a look into boot.img can you upload please?
Click to expand...
Click to collapse
Yes please,
LT700 is for testing purpose workig phone.
Both phones are almost from the same manufacturer (Note: but different models) Even unmodified repacked file does make phone boot success.
Uploading both stock and magisk patched working images of both phone

Help required removing Apps and Files that are write protected

Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.

Root for HAOQIN H7 PRO

Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot of fame for its really affordable price .Unfortunately I was unable to find information on the specific rooting procedure for this device. I hope someone knows how to recommend a way to solve the problem, thanks to everyone anyway
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Tablet information:
Tablet name : H7 pro
Brand name : Haoqin
Device model : H7_EEA
Android version : 9
Android security patch level : August 5, 2019
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406
nubrox99 said:
Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot
...
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406
Click to expand...
Click to collapse
Hi,
Unfortunately I didn't even found the firmware file for your tablet so I doubt someone will be able to root it successfully without those files.
Have a good day
nubrox99 said:
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Click to expand...
Click to collapse
My POV: Those so-called One-Click-Rooters all are crap. Most of them are heavily outdated, not applicable on devices with newer versions of Android as with Android 9 GO what is installed on your device. For example KingRoot you tried only may work on devices with Android versions up to version 5 & Framaroot you also tried only may work on device's with Android version less then Pie.
And worst: They may even inject trackers as it's reported in WEB.
In short: You have to root your device's Android manually by yourself, of course only if supported by OEM/Carrier. To verify this boot into device's Recovery and look for option "apply update from adb".
If NOT present then simply stop further reading.
How-To:
In Android's Settings->Developer options enable "USB debugging"
Install ADB-driver on your computer and make it systemwide accessible, means add its location to PATH environment variable and re-boot computer
Download SuperSU Pro
Rename the downloaded ZIP-file to update.zip and move it to folder where ADB-driver is housed
Make sure your Android is charged over 60%
Connect your Android device with computer via USB-cable
On computer open command prompt: [Win]+[R], input cmd and press Enter-key
Run commands - one by one
Code:
adb devices
adb reboot recovery
Don't close command prompt window!
In Android's Recovery menu select option " apply update from adb" and confirm by pressing power button
On computer run command
Code:
adb sideload update.zip
The zip.file will be sideloaded and written in your Android. The process will take quite a long time, so please enjoy yourself with something during the period. When it completes, you can see something like "Install from ADB complete" on the screen.
As last step on computer run command
Code:
adb reboot
Close command prompt window
You also may delete file update.zip: it's no longer needed
I hope I've made it clear to you.
jwoegerbauer said:
Code:
adb sideload update.zip
Click to expand...
Click to collapse
Hi jwoegerbauer , thank you very much for your timely and detailed reply, sorry if I did not answer immediately.I tried with your suggestions, but when I do this step, it gives me an unrecognized device error (in fact the adb devices command give me an empty list) .Checking on google, I noticed that it is a driver problem and then the phone is not recognized in recovery mode but, always on google I was unable to find a guide to solve the problem. On the android developer site I downloaded a file zip called "usb-driver", but when I update the drivers and set this folder as a directory it gives me this error: "The specified folder does not contain a software driver compatible with the device. if there is a driver in the folder, make sure it is designed to work with windows for x64 systems "
I hope it is not my mistake or that it is something resolvable anyway, I wait and trust in your further clarification if possible
@nubrox99
The driver package usb_driver_r12_windows.zip you downloaded isn't the expected one, it's only meant to be explicitely used with Google devices. Typically the USB-driver gets downloaded from OEM's/Carrier's website. If not provided by them, then the Universal ADB Driver should get installed.

ADB and Fastboot issue on Galaxy Tab S7

I am having trouble using the adb pull to root a brand new Samsung Galaxy Tab S7 with Android 11 using Magisk. I did the date change to get the OEM unlock available. I was then able to unlock the bootloader and turned on the USB debugging and get the message every time it starts that the bootloader is unlocked. I downloaded the Magisk from github.com v23.0. Then copied the AP TAR file for my stock firmware to do the patch in Magisk. I have a file in my download folder named “magisk_patched-23000_H5VRc.tar”. I am using the “adb pull /sdcard/download/magisk_patched_[random_strings].tar” but keep getting things like:
1) adb: error: failed to stat remote object '/sdcard/download/magisk_patched_[random_strings].tar': No such file or directory
2) adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Any ideas what I am doing wrong? I would be open to any sugestions.
Code:
adb pull
is used to copy files / directory from your phone to your computer
Synthax:
Code:
adb pull <device file location> <local file location>
To copy files / directory from computer to phone you have to use
Code:
adb push
why adb? just copy it by using windows file manager.
Ok so in the internal storage of my tab is a file called “download” in that file is something named “magisk_patched-23000_H5VRc.tar”.
So I guess my question is if I use “adb pull /sdcard/download/magisk_patched_[random_strings].tar” will the computer go to the internal storage on the tab in the download folder and get the “magisk_patched-23000_H5VRc.tar” file?
Or should I use “adb pull /internal storage/download/ magisk_patched-23000_H5VRc.tar”? If so do I need to use underscore between internal and storage?
Android's file / directoy names are case sensitive.
Knowing this the directory name in question is /sdcard/Download.
CXZa said:
why adb? just copy it by using windows file manager.
Click to expand...
Click to collapse
According to the instalation guide it could corrupt large files
Take note that also ADB's pull command is size-limited.
It might therefore be advantageous to first unpack the TAR file on the phone, and then transfer the desired files to the computer with adb pull
wolfyj1 said:
According to the instalation guide it could corrupt large files
Click to expand...
Click to collapse
Hardly. If in doubt check the tar with 7zip or whatever. Or compare file hashes...
jwoegerbauer said:
Android's file / directoy names are case sensitive.
Knowing this the directory name in question is /sdcard/Download.
Click to expand...
Click to collapse
I was hoping that it was as simple as the capitalization of Download. Here is the message now.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull /sdcard/Download/magisk_patched_[random_strings].tar
adb: error: failed to stat remote object '/sdcard/Download/magisk_patched_[random_strings].tar': No such file or directory
Is it possible that my adb and fastboot program is not working correctly? I was hoping that there would be a simple fix for this. Guess not.
/sdcard is a sym-link, try to use /storage/emulated/0 as file's actual path.
fastboot flash boot magisk_patched.img is the most common way.Be sure to use real ADB tools from Google.
I'm pretty sure that Samsung devices don't support fastboot mode. I've owned lots of them and fastboot has never been available. Instead we have download mode, which must be interfaced with via Odin or Heimdall, etc.
Of course, ADB should work, and is universally available on all Android devices.
AnonVendetta said:
I'm pretty sure that Samsung devices don't support fastboot mode. I've owned lots of them and fastboot has never been available. Instead we have download mode, which must be interfaced with via Odin or Heimdall, etc.
Of course, ADB should work, and is universally available on all Android devices.
Click to expand...
Click to collapse
Anon you are so correct. I've spent so many years flashing Pixels I forgot I was discussing a Sammy Tablet. Thank you.
Jonathanpeyton said:
Anon you are so correct. I've spent so many years flashing Pixels I forgot I was discussing a Sammy Tablet. Thank you.
Click to expand...
Click to collapse
I've only ever used fastboot once, it was on an HTC phone. I was just unlocking the bootloader and installing TWRP for a friend.
Never owned a Pixel/Nexus, I'm put off by them because they don't have MicroSD slots. But if they want to give us 1TB+ internal storage, I may reconsider. On the other hand, they do have lots of custom ROMs, lots of developers, and alot of users. So on that front, they have a ton of advantages if you're an Android enthusiast looking to get the most mileage out of your device for the longest time possible.
Samsung devices are what I prefer, but I'm open to trying new things. Almost all of my phones have been Samsung, with the exception of an LG v10, ZTE Axon 7, and a Huawei Honor. After using all those for quite awhile, I went back to what I know best.
I did run into device not authorized error today when I was trying to mod my S7.
Turns out that although I enabled USB debugging beforehand the tab wasn't able to ask for permission.
I had to disable and enable USB debugging again, revoke previous authorization, reconnect and wait for the popup to show up.

Categories

Resources