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
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
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.
I searched everywhere but I couldn't find nowhere how to backup efs or persist partition, I just read the thread for twrp flashable stock oreo for moto g5 cedric and it says it is useful to backup them to save the phone in case of IMEI or VoLTE or 4G problems after the zip install but TWRP doesn't seems to backup them and online I didn't found guides.
EDIT:
To help people with the same problem I'll write here.
Thanks to TheFixItMan I've found the most easy solution which is to flash the TWRP 3.2.3-2 arm64 that has backup option for EFS and Persist, I'll quote here the answer with the link.
Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1ML...yBHyg81cHdW1cB
Click to expand...
Click to collapse
Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
TheFixItMan said:
Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Click to expand...
Click to collapse
So the command I should use is:
Code:
dd copy persist to <location dir>
?
Should I use this on twrp Advanced > Terminal?
Are unofficial twrp safe?
OnionMaster03 said:
So the command I should use is:
Code:
dd copy persist to <location dir>
?
Should I use this on twrp Advanced > Terminal?
Are unofficial twrp safe?
Click to expand...
Click to collapse
The command should look something like this - not tried it and don't own this device
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Yes enter it in twrp terminal - once done it will output persist.img to sdcard
To copy back just reverse the if and of parts of the command
Unofficial twrps are perfectly safe - all official builds that aren't build by twrp start off as unofficial and are just submitted to their repo to become official
You can always flash what ever recovery you want after
The one I gave I think has the backup option for persist - if not just try the terminal command
OP, did you try the command? I'd like to backup mine as well
same question here! any updates?
EDIT: Managed to do it myself. I ended up pulling up the image through adb.
For all of you who are still wondering all I did is start adb and type the following:
adb pull /persist C:\platform-tools/persist.img
Click to expand...
Click to collapse
Substitute C:\platform-tools with your local folder.
You can also use the code provided in the thread, but If you wanna retrieve the file, you should copy it to /external_sd instead of microsd (also you can do it from the adb shell instead of the twrp terminal, which is more convenient).
persist backup and restore - 9008 mode
maybe this tool is useful too...
works in 9008 mode and has some firehose-loaders inside
moto g5 has qualcomm 8937 chipset, so should work...
https://mega.nz/#!dIcE0ApR!DEZIBxdxCqVEVRZRKevRr_Z_EXMF1I1PCJb-k7wvyGc
BR
1rdc said:
OP, did you try the command? I'd like to backup mine as well
Click to expand...
Click to collapse
I haven't tried this yet, I'm going to do in the next hours
Most of my the question/topic was explained here.
@steadfasterX
Re the WiFi pls share also the boot logs (see LOS faq).
Click to expand...
Click to collapse
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
Ok the choose "format" data in twrp and try to boot first without your userdata backup into stock. Lemme know if that works.
Click to expand...
Click to collapse
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
emperordogma said:
Most of my the question/topic was explained here.
@steadfasterX
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
Click to expand...
Click to collapse
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
steadfasterX said:
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
Click to expand...
Click to collapse
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
emperordogma said:
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
Click to expand...
Click to collapse
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
steadfasterX said:
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
Click to expand...
Click to collapse
Ahhhh, I assumed everything I saw was in a "copy/paste" format so, I didn't think to even try to exclude the adb from it.
I was able to mount system, and browse apps, there was stuff in there.
I used the "bs=512" method, and it gave the same result. I'm starting to think I'm just boned honestly. I'll upload my boot.img here in a few (in case you see this before I do).
I was hoping I could back up my texts/call logs (I was able to salvage a few, but I'm missing about a months worth), properly backup WhatsApp, get my Nova settings, and make sure I'm not missing anything else (I had a list, but can't think of it now). And I was hoping by doing it, it would fix the annoying Wifi bug.
Edit 1: I don't think it's "bootlooping", because I read that you could boot into TWRP while it's doing it (if your timing is good), I tried and couldn't get into TWRP at all, it's "stone walling" at the LG screen.
Edit 2: My stock Boot.img
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
steadfasterX said:
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
Click to expand...
Click to collapse
Huh, I am not sure how that happened. I'm starting to wonder if after the first try with adb push if I was even using my Stock Boot.img, magisk must've messed with me (they said the recommend way to to patch a boot.img) and I got them mixed up? Or at least that's the only thing I can think of.
Anyways, this should be the right one. Boot.img
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
emperordogma said:
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
Click to expand...
Click to collapse
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
steadfasterX said:
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
Click to expand...
Click to collapse
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
emperordogma said:
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
Click to expand...
Click to collapse
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
steadfasterX said:
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
Click to expand...
Click to collapse
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
emperordogma said:
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
Click to expand...
Click to collapse
Its just there by mistake. Not by LG but the OEMs. The OEMs like verizon, etc are not doing a good job but that's not new..