*edit*
Got it working, I installed a rom with ogt.
I accidentally flashed twrp twice, and for some reason now it won't boot into the system. Everything I've read says to download an official image from https://developers.google.com/android/images and running the bat.
But it only has
06/08/2017 07:48 PM <DIR> .
06/08/2017 07:48 PM <DIR> ..
01/01/2009 01:00 AM 37,616 care_map.txt
06/08/2017 07:48 PM <DIR> META-INF
01/01/2009 01:00 AM 871,127,296 payload.bin
01/01/2009 01:00 AM 154 payload_properties.txt
Click to expand...
Click to collapse
No img or bat like everything (including the page where I downloaded it from says)
I tried a few others and they were all the same.
Also adb devices shows up as blank. I've tried unplugging and re-plugging the phone, killed adb, installed the driver, and ran cmd as an admin but still devices is blank.
**edit**
I just realized I wiped my phone disabling usb-debugging which would make adb not work,
Related
Hi
1.- I want to install a new Rom (Android 4.4.2 KitKat omniROM)
2.- But first I need to install TWRP (.blob), so I need to install and run a fastboot tool (Minimal adb/fastboot tool)
I unlocked the bootloader of the tablet
I install the fastboot
I install the drivers of the fastboot of the Asus
I copy the file.blob to the same folder of the fastboot
I open the fastboot and in the CMD I wrote ''fastboot devices'' and it find the Asus so in the screen was numers and letters like a code...but then I wrote the command Fastboot -i 0x0B05 flash recovery file.blob but then give an error (failed....(no such device or address))
I tried all to solve this problem but I cant.. so I need your help.
I tried:
■Reinstall fastboot tool
■Restart the tablet
■Use all the usb ports of the PC
■Reinstall drivers
■Used apps like SDK Manager
■Used other usb cable
luisldu said:
Hi
1.- I want to install a new Rom (Android 4.4.2 KitKat omniROM)
2.- But first I need to install TWRP (.blob), so I need to install and run a fastboot tool (Minimal adb/fastboot tool)
I unlocked the bootloader of the tablet
I install the fastboot
I install the drivers of the fastboot of the Asus
I copy the file.blob to the same folder of the fastboot
I open the fastboot and in the CMD I wrote ''fastboot devices'' and it find the Asus so in the screen was numers and letters like a code...but then I wrote the command Fastboot -i 0x0B05 flash recovery file.blob but then give an error (failed....(no such device or address))
I tried all to solve this problem but I cant.. so I need your help.
I tried:
■Reinstall fastboot tool
■Restart the tablet
■Use all the usb ports of the PC
■Reinstall drivers
■Used apps like SDK Manager
■Used other usb cable
Click to expand...
Click to collapse
Is your bootloader unlocked?
Edit: wait I read the op and it says you did unlock it..
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
I'd say try to use a completely different USB or computer. If that doesn't work, you can actually flash it from the system itself if you have root. Can't remember the command. Give me a second.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Are you on 4.2 bootloader?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:39 PM ---------- Previous post was at 07:31 PM ----------
To install without using fastboot, download twrp, make sure its one of the newer twrps, I think 2.7 and above is required for KitKat, and..
[QUOTE/] Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
[/QUOTE]
Sent from my SM-N900T using XDA Free mobile app
Problem Solved!
andrewnelson23 said:
Is your bootloader unlocked?
Edit: wait I read the op and it says you did unlock it..
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
I'd say try to use a completely different USB or computer. If that doesn't work, you can actually flash it from the system itself if you have root. Can't remember the command. Give me a second.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Are you on 4.2 bootloader?
Click to expand...
Click to collapse
So, yesterday I clean the Asus Cable, the port of the pc and the port of tablet and finally works, so I flashed my tablet with TWRP recovery and the 4.4.4 omniROM Nightly.
The all problem was the cable and the ports.
:good:
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
tjablonowski said:
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Click to expand...
Click to collapse
Setting up the directory is always a ***** - I always found it easiest to open a command prompt in that folder so you don't need to type the directory first. I'm not sure what version of Windows you are running (if it's Windows at all) but here are some instructions for one version. I believe last I checked it changed but let me know if it helps. https://www.onmsft.com/news/open-command-prompt-specific-windows-10-file-directory
windows 10 fall creator edition... Appears that "adb devices", " adb reboot bootloader" and "fastboot devices" works and returns the correct information..
tjablonowski said:
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Click to expand...
Click to collapse
I just make a new folder put fastboot in the folder then hold shift and click right click then menu will show option to open command window here. Then fastboot devices then the other commands once it shows.
Another thing I do is install HTC sync then uninstall it after it installs htc driver installer. Are u trying what I'm mentioning?
have done both of those, still no joy...
tjablonowski said:
have done both of those, still no joy...
Click to expand...
Click to collapse
what mode are u in when trying? U need to be in download mode
shows the last time I touched a HTC model, the download mode worked. Always have to be different I guess...Tks
tjablonowski said:
shows the last time I touched a HTC model, the download mode worked. Always have to be different I guess...Tks
Click to expand...
Click to collapse
Yea they switched it up around the m9. Happy u got it done.
U11 life has Android One system, not HTC Android. Maybe, the treatment for this phone series is different from U11?
dieterhaack said:
U11 life has Android One system, not HTC Android. Maybe, the treatment for this phone series is different from U11?
Click to expand...
Click to collapse
There's 2 versions 1 with sense and the Android one version
Once I enter the token request, it just says waiting for device, and nothing else happens.
jdmjunkee7 said:
Once I enter the token request, it just says waiting for device, and nothing else happens.
Click to expand...
Click to collapse
Are you in download mode? What operating system are you using? Be specific to get help faster.
Yes im in download mode. Android 7.1.1. Ive checked the option in developer mode for allowing unlocking.
jdmjunkee7 said:
Yes im in download mode. Android 7.1.1. Ive checked the option in developer mode for allowing unlocking.
Click to expand...
Click to collapse
Are u on windows 10 or Linux? Do u have the drivers installed is adb debugging turned on as well?
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
Did you install fastboot/adb?
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
I always uninstall sync and just keep the HTC drivers installer in programs. Are you using powershell because I always use cmd
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
Unzip the files then use cmd and cd /the folder here
Then type fastboot devices while in download mode and if it shows. fastboot with the numbers then your good to go. Or while booted u can do adb devices and it will show if your connected. I do know that on my Asus I can only get fastboot and adb to work on the 2.0 USB port it never connects on my 3.0 ports. I hope this gets u squared away. Report back your findings as it may help others that have the same issue.
So, I think I've managed to salvage my bricked Stylo, I somehow also managed to root my Fiance's LG G Stylo that's on the 6.0 update... this is a guide on how to flash a TWRP Recovery I made of a rooted LG G Stylo that is running Android 6.0 This can get you out of a brick or just give your spare phone root access.
Since I can't find any ways to fix this problem on the internet I'll post what I did here so hopefully I can get some other people out of deep water with their phone.
Stylo.zip
I'm going to assume that if you are following these instructions you have already downloaded and extracted the .zip file named Stylo onto your desktop.
All of these files are in the Stylo folder, so you should only have to download Stylo.zip
Minimal ADB & Fastboot installer
LG Phone Drivers
TWRP Backup file
recovery.img
1. Install minimal_adb_fastboot_v1.4.1_setup into the folder you extracted Stylo.zip in
(Install PhoneDrivers if you have not already)
2. Enable USB Debugging on your phone
(If you are boot looping, you should still be able to boot into the bootloader with
minimal adb fastboot just plug it in and let it do it's bootloop while you try
booting into the bootloader really quick, this may take some trial and error)
3. Launch MAF32.exe
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
5. Next you will need to type:
adb reboot bootloader
Now, the powershell screen should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo>
6. Once you are in the bootloader type:
fastboot boot recovery.img
(If you opened the PowerShell window by holding shift and using the right click menu,
the recovery.img file should load on its own, your PowerShell window should now look something like this)
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.367s]
booting...
OKAY [ 0.011s]
finished. total time: 0.380s
finished. total time: 0.379s
PS C:\Users\Hyperion\Desktop\Stylo>
7. Once TWRP boots up on your device you will need to navigate to Backup
Uncheck everything but boot
Start the backup process
(We are making a backup of boot
so we can take the name of the folder
it makes in /sdcard/TWRP/BACKUPS
and copy/paste that to the rooted backup file.
TWRP will create a backup of your
boot animation that contains your PHONE ID #
In my case it created a file named LGMS6318bb1ce9a )
8. Open your sdcard contents on your computer
navigate to /sdcard/TWRP/BACKUPS
Copy the name of the new folder that was created (Mine is LGMS6318bb1ce9a)
Open the Stylo folder on your Desktop \Desktop\Stylo\TWRP\BACKUPS
Paste the new folder name over the folder titled (Paste Here)
Overwrite the folder in /sdcard/TWRP/BACKUPS that contains
the boot animation with the new folder from \Desktop\Stylo\TWRP\BACKUPS
9. If you are not in TWRP on your phone any more, repeat steps 3. - 6.
10. Once in TWRP click WIPE in the top right, and Swype to Factory Reset
(Unless your backup file is being loaded from Internal Storage)
11. Navigate to RESTORE in TWRP, find your Backup file in the /TWRP/BACKUPS directory
LEAVE EVERYTHING CHECKED!
(If you uncheck anything the phone will not be rooted upon restore of the backup)
(Alternatively you can uncheck Data and have a fresh install of 6.0 with no root.)
The rooted backup should be installing 4144mb worth of data.
I left a few apps on the desktop that I figured would help some people out
Hope this worked for you, getting root on these phones is a *****.
-Mike
Screenshots were taken after the first boot of the Recovered device
Hardware Info
Software Info
Root Check
Can't make it past adb reboot bootloader, phone goes into a unlock mode and freezes up
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
SoonersChuck said:
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
Click to expand...
Click to collapse
I'm still waiting from someone in the comments from that site to confirm it's not a scam.
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
SoonersChuck said:
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
Click to expand...
Click to collapse
You mean a diagram of the emmc?
Anything that shows me where to touch to get the desired reaction
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
Clk Dat0 gnd...those spots
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
ya gotta check all the boxes possible after going into the MOUNT options when in TWRP. always before doing almost anything in TWRP. sometimes its persistant, sometimes not depending on device.
---------- Post added at 08:15 AM ---------- Previous post was at 08:09 AM ----------
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
Enable MTP in the MOUNT options while in TWRP
I can't seem to get my T-Mobile Stylo 5 to go into fastboot mode. Adb reboot bootloader just reboots the phone for me. Maybe a downgrade is required?? Also I just used platform-tools adb and fastboot. Build# PKQ1.190302.001
I have used ADB sideloaded android wear on my HW2 before Oreo update. All drivers have been set up and working previously. After Oreo, I have tried both my Window 10 Laptop and Windows 7 Laptop. I have enabled USB debug from the Watch. However, no device can be recognised by ADB. Can't see any android device in Device Manager. I have to manually install the new OS. What can I do ?
Have you re-enabled ADB Debugging on the watch?
I am able to push files via ADB After update fine.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
Also try the Windroid Tool. See if it can detect the watch by showing status 'Online"
hasn4179 said:
Have you re-enabled ADB Debugging on the watch?
I am able to push files via ADB After update fine.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
Also try the Windroid Tool. See if it can detect the watch by showing status 'Online"
Click to expand...
Click to collapse
Thank you very much for your help. Tried a couple of times on Windows 7 but not working. On Windows 10 finally worked. But when I try to sideload the wear OS 2.10, I was told the intall failed as it is a version downgrade. What can I do?
Ok, thats weird.
I haven't personally done any sideloading yet. But when I was comparing all the details with other peoples' posts, I noticed that even though my OS was 2.9, I also had March security patches installed. Maybe there is a check to see if going to 2.10 may result in downgrading of either the security patch or google play services version, and the system may not allow that.
POINT 1:
We all know USB debugging is important when trying to recover a non-responsive Android phone...
POINT 2:
And we all know people who do NOT set USB Debugging and then their screen becomes unresponsive...
POINT 3:
And yet even if we do set USB Debugging we usually have to connect once to a computer via USB for the authentication keys to be created and even then those keys typically expire within 1 to 7 days and even so most of our usb-debugging adb connections between Android and the desktop are via Wi-Fi nowadays, which uniquely authenticates far more frequently and which instantly deauthenticates when the Android Wi-Fi is turned off....
DATAPOINT 1 & 2:
I'm not sure where those keys are stored on Android, or on Windows, they seem to be stored here:
adb shell ls /data/misc/adb/adb_keys
Directory of C:\Users\username\.android
12/14/2020 01:27 PM 1,732 adbkey
12/14/2020 01:27 PM 709 adbkey.pub
11/25/2022 03:39 PM 936 adb_known_hosts.pb
08/06/2022 08:16 AM 185 analytics.settings
12/16/2020 12:37 AM <DIR> avd
12/14/2020 04:57 PM <DIR> breakpad
08/06/2022 09:15 AM <DIR> cache
12/14/2020 01:26 PM 2,107 debug.keystore
12/14/2020 01:29 PM 0 debug.keystore.lock
12/16/2020 12:36 AM 4,640 emu-last-feature-flags.protobuf
12/16/2020 12:36 AM 67 emu-update-last-check.ini
12/16/2020 12:37 AM 119 maps.key
12/16/2020 12:36 AM 171 modem-nv-ram-5554
12/14/2020 12:59 PM <DIR> studio
10 File(s) 10,666 bytes
Click to expand...
Click to collapse
SUMMARY:
Hence, even if we used USB Debugging the USB-connection keys generally expire and the Wi-Fi authentication changes constantly.... which brings up my question...
QUESTION:
For any given trusted computer, can we make an adb usb debugging connection on day one, and then SAVE those keys for re-use years later?
How?