Hello,
I´m looking for the ADB command to fix the bug that after a revocery with TWRP the SIM card and / or the modem is not working correctly. I did this once before, unfortunately I lost that bookmark of this specific page with the solution.
There is a ADB command to fix this problem. Something with ADB SHELL /auto or like that. Anybody know what I´m talking about ?
Thanks,
regards, Gopher.
I'm also curious about this ...
Related
So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.
Go into partitions menu and mount /system then try.
No go doesn't even change the error.
so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?
Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.
cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help
LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...
The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.
i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found
I have rooted and flashed to the latest recovery image. i can not get into adb recovery. every time i try i get the following prompt ~# followed by my command and then file not found. Anybody had this problem that knows how to fix. thanks
shadow635 said:
I have rooted and flashed to the latest recovery image. i can not get into adb recovery. every time i try i get the following prompt ~# followed by my command and then file not found. Anybody had this problem that knows how to fix. thanks
Click to expand...
Click to collapse
sounds like you are getting adb. What happens if you just run "adb shell"? What is the exact command you are trying to run?
cd/system/app is the command entered. i am following the post for removing apps. i have entered clockwork, gone to partitions and then went to unmount. connected to pc and type adb remount. get remount succeeded. type adb shell and the following prompts
~#cd/system/app (command)hit enter
cd/sytem/app
/sbin/sh: cd/sytem/app: not found
did u mount the system and SD partitions?
Yes tried both mount and unmount and get the same messages
Sent from my ADR6300 using Tapatalk
shadow635 said:
~#cd/system/app (command)hit enter
cd/sytem/app
/sbin/sh: cd/sytem/app: not found
Click to expand...
Click to collapse
Need a space between "cd" and "/".
If you're not a unix person and are entering these commands without knowing what they do, it's important to enter them exactly as described. Better yet, cut & paste rather than type them.
thanks will try that i did cut and paste will try adding space to command
Sth went wrong and I can't use adb in recovery anymore. It was working fine and suddenly stopped. Any ideas as to what might be causing this?
Whats not working, adb or your handset?
If you do,
Code:
adb devices
what happens?
I got DEVICES LIST ATTACHED. No adb command would work, phone wouldn't respond to anything or even mount sdcard via USB. But no worries, as it turned out sth was wrong with my mac. quick restart and everything works so some OP might delete this thread.
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.
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
TioNacho said:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
Click to expand...
Click to collapse
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.
ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!
Just root your phone using Magisk and execute these commands using adb on your PC/laptop:
Things to note before you start executing commands below:
1. Make sure that USB debugging in your phone is turned on.
2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.
3. After "su" command, you have to grant root access to adb shell within 10 seconds.
4. "adb reboot" command will immediately reboot your phone, don't panic.
5. You are doing this at your own risk.
Code:
adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot
Commands have been used from this thread: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Good morning!
Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards