I set up my adb in my Ubuntu 16.0.
After a lots of guides I finally made adb detect my device!
I wanted to take a backup and entered the command and the terminal asked to unlock the device and confirm the backup operation.
But there was no popup of the backup operation ? What did I do wrong??
Related
I tried to follow this thread: http://forum.xda-developers.com/showthread.php?t=1356257
But I am getting the errors: adb: not found -or- adb permission is denied. how can I solve this? I have the original framework-res.apk. However, I screwed up with the one on my kindle and now it is bricked at the logo screen.
HELP?
i was having the same problem - where i was going wrong was not remounting the kindle device via adb
once i ran adb remount i was able to get the file back in place.
Sorry, but I really can't mount ADB Remount.
No adb commands will work for me. I either get:
-exec '/system/bin/sh' failed; No such file or directory (2)
-or-
adb: permission denied
-or-
the other error listed above.
My question; can someone walk me through step by step what to do if I bricked by messing up the framework-res.apk? Please?
Do you have TWRP? Did you take a backup first? You shouldn't be messing with system files that are required for booting without doing this first. The procedure for recovering should just be booting into TWRP and restoring your backup. Backups backups backups.
If you don't have a backup, but do have TWRP, does adb work in TWRP so you could try it there? (I'm at work so I can't double check that)
If none of these work, you might be able to get the system to boot into fastboot and get TWRP on there, Vashypooh or one of the TWRP guys would be more helpful than I would be for that. The only other option is a factory cable (there's at least one thread on here for that).
Hello,
I am stuck and it is really anoying. I am trying to flash CM on my LG L5 (e610)
I have installed adb, and rooted the device already. I have su and when i do a check
for adb to work 'adb devices' it shows up with my device. but when i enter 'adb shell' hit enter
and after that typ 'su' it does nothing.. nothing pops up on my phone.. i have USB debuging enabled and
it is in charge mode. What is it i do wrong?
-Fireworkfan
EDIT: I can use other commands, rebooting my phone with ADB works perfect.. what am i doing wrong with adb shell thing.. is there something i need to instal first? i only placed the .bin file in the directory of my phone.. Also i have 'SuperSU' shouldnt 'su' be something els? i am so confused
after you write adb shell, if you have SuperUser or SuperSU on your phone, unlock your phone and accept root for adb comands and after you can go with su and do what you want
Sabyn said:
after you write adb shell, if you have SuperUser or SuperSU on your phone, unlock your phone and accept root for adb comands and after you can go with su and do what you want
Click to expand...
Click to collapse
That is the whole problem, I do not get a grant or decline messages from my SuperSU... I have checked it over a 100 times, on the mainscreen or even with the app itself open. I do however get the Grant or Decline message when I use apps like pimpmyrom on my phone itself.. I have tried it on a different computer to now, again without succes.. anyone an idea? There would be someone that would like to help me over a chat with this problem?
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
How to root the Honor 8: very clear steps for dummiesRequirements:
Unlocked Bootloader
Download TWRP and SuperSU
Make sure USB Debugging is turned on, in the developer’s options.
Download and install the correct drivers and ADB tools.
Watch the video once and then watch it again to make sure you get the flow or the work.
Once you have setup the device with your PC for ADB and fastboot connections we are ready to start.
Installing TWRP
Connect your device to your PC and make sure to grant authentication to your PC over ADB. (You should be able to see your device when you type [ADB devices] in the Command Prompt)
Type [adb reboot bootloader] and wait for the device to reboot into fastboot mode
Type [fastboot devices] to confirm you have a connection to your device
Make sure to save the downloaded recovery .img in the same folder as your are running Adb/fastboot tools, and then type [fastboot flash recovery TWRP image.IMG] ( replace .img with the exact name of the downloaded file)
When complete reboot normally
When the device comes back up, open up ADB and type [adb reboot recovery]
Your device should reboot into TWRP
Do not change to “read/write” keep in read only mode and do a backup
Once backup is complete then enable “read/write” by going to “mount” and disabling the option for read only
Rooting the device
While connected in recovery mode transfer the Supersu2.78 stable to your device and install it. After installed, reboot
After rooting your device may restart 2 to 3 times. This is normal so just be patient.
System will reboot and you should have root. Test root access with your favorite root app ( I like XDA labs)
On my honor 8 I also had to accept in my phone when typing the line fastboot bootloader , if I didn't the phone didn't connect
Also I had to manually pick the driver for the connected Honor 8 in device manager twice. There is a vid about this showing how to choose the correct driver manually (google inc.->the top selection I believe) but if u have no problem connecting in adb in the command prompt typing the commands never mind this.
Good u type where to extract the twrp - MANY MANUALS MISSED THIS took me 30 min to search the info uncessesarily. Just like no one mentioned I had to accept the first command in phone for me atleast.
Does it works for FRD L19 (64GB)?
Nice guide
Everything I've seen so far has resulted in someone bricking their phones, including somehow deleting their IMEI numbers or somehow resulting in their BT/WiFi not working. There were so many threads that it's hard to remember which one is which.
I've decided it's time to unlock/root my phone but I don't want to make the same mistakes and somehow brick my phone. Why was it that the partition with the IMEI was written over? What about the other bricks? What is the best method to unlock/root right now?
Often times mixing firmware from other regions will cause issues. For example flashing the US version with the G or international versions. By firmware, I'm referring to other system components besides /system and kernel. Radio/baseband, BT firmware, etc.
The other issue has to do with the axon7backup program. For greatest safety, this really should only be used to backup and flash recovery while the bootloader is still locked only.
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
There is no way to fully brick a device with the Qualcomm 820 SoC. It is more or less complicated, but even deleting the bootloader it is possible to recover the device with the appropriate Qualcomm flashing tools.
Regarding "easy" bricks, you will be able to recover any brick by using tenfar's Axon7tools, and DrakenFX guides. Also Just keep on had a backup of your boot.bin, recovery.bin (both using Axon7Tool), and the full ZIP for your device model in a FAT formatted SDcard.
The recovery process is just to flash back the boot.bin, then recovery.bin (using the same tool Axon7tool) and then from the stock recovery reinstall the full zip and optionals OTA.
Cyrus D. said:
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
Click to expand...
Click to collapse
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
amphi66 said:
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
Click to expand...
Click to collapse
Sorry I'm new to all this, I'm doing something wrong here.
So just to be clear it's:
- Type in "SU", enter it, then type "reboot disemmcwp", in TWRP's terminal?
That results in "SU not found" for me.
or
- Type in "adb reboot disemmcwp" in a command window opened in the adb folder on my PC while TWRP is running adb sideload?
That resulted in "* daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed"
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Cyrus D. said:
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Click to expand...
Click to collapse
The su binary only exists if you open a terminal in an android app because apps do not have root permission. TWRP and adb shell automatically have root privileges.