Exists one way to unbrick a phone without Pc/Notebook? Like using a Other phone with otg or something else
rael7979 said:
rael7979 said:
Exists one way to unbrick a phone without Pc/Notebook? Like using a Other phone with otg or something else
Click to expand...
Click to collapse
Phone? Which phone? What is the problem?
Click to expand...
Click to collapse
Infinix Hot 11 X689F, the problem its because I flashed a wrong twrp in my phone, so because that my phone dont start anymore and dont open reovery mode
Take phone to authorized service center and let them try to fix it.
if the other phone is rooted you can use it for fastboot commands:
adb + fastboot Installer
The link provided let you download and flash an ADB / Fastboot from 2008 what is heavily outdated,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what? type 'adb version' and tell me your version
This got released in 2023
Installing Termux would solve the problem.
pkg install android-tools
jwoegerbauer said:
The link provided let you download and flash an ADB / Fastboot from 2008 what is heavily outdated,
View attachment 5866147
Click to expand...
Click to collapse
[ ] You know how zip signing works.
(the binaries are from Feb 2020)
alecxs said:
if the other phone is rooted you can use it for fastboot commands:
adb + fastboot Installer
Click to expand...
Click to collapse
But i can't enter in fastboot mode to send the commands, i need a tool like mtk bypass to android, do you know one?
WoKoschekk said:
Installing Termux would solve the problem.
pkg install android-tools
View attachment 5866221
Click to expand...
Click to collapse
But termux doesn't recognize my device, I put usb but connect and disconnect all the time, and isnt my usb cable
rael7979 said:
But termux doesn't recognize my device, I put usb but connect and disconnect all the time, and isnt my usb cable
Click to expand...
Click to collapse
pkg upgrade
pkg install tsu
With tsu you are root in termux and able to detect your device. Do not use su because then you will leave the termux shell and the ability to run commands from Termux.
WoKoschekk said:
pkg upgrade
pkg install tsu
With tsu you are root in termux and able to detect your device. Do not use su because then you will leave the termux shell and the ability to run commands from Termux.
Click to expand...
Click to collapse
Ok, after that I run the android tools command yeah? Tomorrow I will try
rael7979 said:
Ok, after that I run the android tools command yeah? Tomorrow I will try
Click to expand...
Click to collapse
Yes, after them run pkg install android-tools and you can use fastboot.
alecxs said:
...
(the binaries are from Feb 2020)
Click to expand...
Click to collapse
Only confirms the binaries you linked to are not really useful because massively outdated.
Yes, binaries are v29.0.6 (2020).
adb-ndk/bin at master · Magisk-Modules-Repo/adb-ndk
adb-ndk. Contribute to Magisk-Modules-Repo/adb-ndk development by creating an account on GitHub.
github.com
Related
OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix
ok when on LL and KK i had no issues running ADB commands using termux or termial imulator.
But for some reason since i upgraded to Marshmallow i get the following error (See Attched Image)
let me know if you know hot to fix this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you're running terminal commands on the actual Android device instead of across a USB cable connected to your PC, you don't include the "adb" part of the command. "adb" is a Windows/Linux/MacOS command telling it to send what follows to the connected device, not an Android one (simplified explanation).
roirraW "edor" ehT said:
When you're running terminal commands on the actual Android device instead of across a USB cable connected to your PC, you don't include the "adb" part of the command. "adb" is a Windows/Linux/MacOS command telling it to send what follows to the connected device, not an Android one (simplified explanation).
Click to expand...
Click to collapse
Sorry,
i have used it before when trying to program my FireTv and my Friend FireTv Stick using the adb commad.
It once worked fine adb kill-server, adb start-server, adb connect 192.1.x.x then adb install kodi.apk etc.
all that use to work with LL and KK but not with MM
I have no idea. I've never seen the "adb" command used from the actual Android device. Why not hook a PC to whatever you're trying to send commands to? Do you have USB Debugging on?
You know what roirraW "edor" ehT? He's right!
I just adb'd into my android device and typed "adb" and it came up! This is on the latest stock LP (35B), not rooted.
Weird.
iBolski said:
You know what roirraW "edor" ehT? He's right!
I just adb'd into my android device and typed "adb" and it came up! This is on the latest stock LP (35B), not rooted.
Weird.
Click to expand...
Click to collapse
Yes as I said it use to work with KK and LP but it does not work in MM
rinnycoop121 said:
Yes as I said it use to work with KK and LP but it does not work in MM
Click to expand...
Click to collapse
I guess my question is, what would you use adb from within the Android device for?
iBolski said:
I guess my question is, what would you use adb from within the Android device for?
Click to expand...
Click to collapse
Sorry,
i have used it before when trying to program my FireTv and my Friend FireTv Stick using the adb commad.
It once worked fine adb kill-server, adb start-server, adb connect 192.1.x.x then adb install kodi.apk etc.
all that use to work with LL and KK but not with MM
iBolski said:
I guess my question is, what would you use adb from within the Android device for?
Click to expand...
Click to collapse
No need to use a PC everything works from your mobile phone
iBolski said:
You know what roirraW "edor" ehT? He's right!
I just adb'd into my android device and typed "adb" and it came up! This is on the latest stock LP (35B), not rooted.
Weird.
Click to expand...
Click to collapse
Yes! Bizarre! I can't believe I've never seen that but I guess I never had a reason to. I wonder if all OEMs have included adb in Android?
Confirmed working on stock Lollipop on my LG G Pad 8.3 VK810.4G too.
rinnycoop121 said:
No need to use a PC everything works from your mobile phone
Click to expand...
Click to collapse
They must not have included the adb binary. Find it on Lollipop and copy it to your Marshmallow, and give it the same permissions as other binaries. I wouldn't expect it to matter which version of Android you run it on.
If 46A is just a leak as it appears to me, it's possible the final Marshmallow OTA will have it.
After updating to android 10, my mobile working fine. But one day my phone automatically restarts and showing EIO state error. Anybody please help me to fix my phone...
Go recovery terminal type
reboot "dm-verity enforcing"
And hit enter
My mobile not able to boot the os, I can't able to go to recovery terminal
Is it red warning "g.co/ABHg.co/ABH"?
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Techgaming432 said:
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Click to expand...
Click to collapse
there's no such thing as command enable in cmd or fastboot.
btw its verify, not verity right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ipta said:
Is it red warning "g.co/ABHg.co/ABH"?
Click to expand...
Click to collapse
Yes, can't be able to open recovery mode... Once we go to recovery, phone rebooted
Techgaming432 said:
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Click to expand...
Click to collapse
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
This is the problem...
LiyasKarthik said:
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
Click to expand...
Click to collapse
Are you sure after you type "enable dm-verity" on CMD in the adb folder, you get respond "waiting-for-device"?
Because there's no "enable" command on fastboot.
ipta said:
there's no such thing as command enable in cmd or fastboot.
btw its verify, not verity right?
View attachment 5175475
Click to expand...
Click to collapse
It's verity not verify
LiyasKarthik said:
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
Click to expand...
Click to collapse
Try this command
fastboot oem enable dm-verity
Techgaming432 said:
It's verity not verify
Click to expand...
Click to collapse
yes, sorry for my mistake but I've tried that also.
see the screenshoot at the attachment.
Techgaming432 said:
Try this command
fastboot oem enable dm-verity
Click to expand...
Click to collapse
FAILED (remote: unknown command)
ipta said:
yes, sorry for my mistake but I've tried that also.
see the screenshoot at the attachment.
FAILED (remote: unknown command)
View attachment 5176169
Click to expand...
Click to collapse
Sadly saying
Locking isn't possible now
I tried the command but my mobile is dead...
Please help me to recover my device
LiyasKarthik said:
I tried the command but my mobile is dead...
Please help me to recover my device
Click to expand...
Click to collapse
Unlock bootloader or flash any ROM
Not able to switch on the mobile... Is there any way to recover my mobile?
Kaspersky detects trojans, but is unable to neutralize them. Would you have a solution to propose me? In attachment you have a screenshot.
The full references are:
Model: Energizer Energy400
Android version: 4.4.2
Kernel version: 3.4.67
Build number: APLS.KK1.MP7.V1
Custom build version: Energy400_FR_4.4_B047_HW1_8GB_V03_201604130900
Hardware version: V1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To get rid off of Trojans/Virusses do a Factory Reset.
jwoegerbauer said:
To get rid off of Trojans/Virusses do a Factory Reset.
Click to expand...
Click to collapse
The factory reset didn't work, there are still trojans in the filesystem (I did Vol Up + Power On, then selected factory reset)
Any other idea than the factory reset? The infected files seem to be deep in the filesystem.
Also, I tried to towelroot the device but it didn't work
thomasbb said:
Any other idea than the factory reset? The infected files seem to be deep in the filesystem.
Also, I tried to towelroot the device but it didn't work
Click to expand...
Click to collapse
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Here is what I found:
Flashtool: https://www.getdroidtips.com/flash-stock-firmware-using-sp-flash-tool/
Energy500 firmware: http://www.mediafire.com/file/14igk2ma27qa385/Energizer_Energy_S500_MT6735M_V005_20161219.zip/file
My phone is an Energy400, would it be ok (no way to find an Energy400 firmware...)? My computer runs under Linux but I guess it works the same: run Flashtool, burn the "scatter" file, and this is it?
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Also, I tried this: https://www.droidthunder.com/unlock-bootloader/
but the terminal is frost saying: < waiting for any device >
All the commands worked until fastboot oem unlock and fastboot flashing unlock though
Re-flashing phone's Stock ROM is done by means of ADB:
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
jwoegerbauer said:
Re-flashing phone's Stock ROM is done by means of ADB:
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
In my case, it gives:
Code:
adb devices
adb reboot sideload
adb sideload Energizer_Energy_S500_MT6735M_V005_20161219.zip
then? Tomorrow I'll try, if it's not the right file to be used, please stop me before that time.
thomasbb said:
In my case, it gives:
Code:
adb devices
adb reboot sideload
adb sideload Energizer_Energy_S500_MT6735M_V005_20161219.zip
then? Tomorrow I'll try, if it's not the right file to be used, please stop me before that time.
Click to expand...
Click to collapse
It's not an update.zip and not for your device.
Try disabling them... maybe it's possible.
CXZa said:
Try disabling them... maybe it's possible.
Click to expand...
Click to collapse
How could I root my device to try to remove the trojans with adb? Thank you for your time though
Regarding the firmware, I asked one to Energizer and they answered they're dealing with my request
thomasbb said:
How could I root my device to try to remove the trojans with adb? Thank you for your time though
Regarding the firmware, I asked one to Energizer and they answered they're dealing with my request
Click to expand...
Click to collapse
For disabling you don't need root.
adb shell pm disable-user --user 0 <package_name>
@thomasbb
try this
App Freezer for Android - APK Download
Download App Freezer apk 1.0.6 for Android. Freeze unwanted app or package on Android (Samsung, Sony, Xiaomi, Huawei, etc)
apkpure.com
what is more convenient than individually disabling packages via ADB, IMO
CXZa said:
For disabling you don't need root.
adb shell pm disable-user --user 0 <package_name>
Click to expand...
Click to collapse
ADB says:
Code:
~/Android/Sdk/platform-tools > ./adb shell pm disable-user --user 0 /system/app/DeskClock.apk
java.lang.IllegalArgumentException: Unknown component: /system/app/DeskClock.apk
at android.os.Parcel.readException(Parcel.java:1476)
at android.os.Parcel.readException(Parcel.java:1426)
at android.content.pm.IPackageManager$Stub$Proxy.setComponentEnabledSetting(IPackageManager.java:2963)
at com.android.commands.pm.Pm.runSetEnabledSetting(Pm.java:1271)
at com.android.commands.pm.Pm.run(Pm.java:141)
at com.android.commands.pm.Pm.main(Pm.java:79)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:243)
at dalvik.system.NativeStart.main(Native Method)
jwoegerbauer said:
@thomasbb
try this
App Freezer for Android - APK Download
Download App Freezer apk 1.0.6 for Android. Freeze unwanted app or package on Android (Samsung, Sony, Xiaomi, Huawei, etc)
apkpure.com
what is more convenient than individually disabling packages via ADB, IMO
Click to expand...
Click to collapse
The application is installed. As soon the ads start to pour, I'll track down the apps that just reinstalled and freeze them. Thank you for you help
Hello guys can someone help me on my redmi note 10,
So basically my problem is adb can detect my phone when its power on but when my phone switches to fastboot adb cannot detect it anymore. I also try the adb reboot bootloader command, it work and it go to fastboot but after that it didnt detected anymore.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
missingN said:
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
Click to expand...
Click to collapse
i already tried that still the same
@ibanezred16 May be you missing add Environment Variables path?
Adb-fastboot PE guide
ibanezred16 said:
...when my phone switches to fastboot adb cannot detect it anymore. ...
Click to expand...
Click to collapse
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Mthw said:
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Click to expand...
Click to collapse
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
ibanezred16 said:
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
Click to expand...
Click to collapse
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Mthw said:
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Click to expand...
Click to collapse
that's also one of my problem when it boots to twrp the touch screen is not working can't touch or click anything when im in twrp
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Mthw said:
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Click to expand...
Click to collapse
yes, thank you very much for your help
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
yeah im trying to install Evox
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
Im succesfully installed twrp I used mouse via otg connector to touch the screen