im trying to run hardspl, it checks my device then it loads up the command prompt window and it stays at 0 on the progress
Related
HI i'm sticking in the KITL, in the KITL i can see the USB in the white area.
i Try to connect mtty.exe but there is only the prompt
Cmd>
why? i need ....
USB>
i need to unbrick my TyTn
my IPL is 1.04
SPL 2.10.Olipro
i try to flash shaps rom but then come the [error 286] after 12%
now i dont know what i can do.
and yea i have install Hard Spl V7
PLS help, yea i have read the WIKI and yea i have search in the forum..
Did you select 'USB' in the Mtty Port drop down and not the 'COM's?
You press Enter key twice and USB> will appear.
I had the same issue, although I chose USb from the drop down menu and hit enter twice, the prompt still kept saying CMD>
Nevertheless, I went on to input the same commands (my Tytn was semi-bricked after a botched radio upgrade). After the password 0000000000000000 command , I got back an 'incorrect password' response, or something like that, but went on. I managed to then flash TNT 2.0 again and recovered from the no gsm problem by removing teh battery several times and resetting. Not sure if the CMD > prompt actually accepted the commands or not.
I can run the initial ADB command via command prompt, but any other command like, kill-server, push, or devices causes my prompt to freeze up. My Thunderbolt is plugged in and is in charge mode. I am looking to root, but can not because it freezes on push command. Am I doing something wrong?
Hi everyone.
I apologize if this was already asked.
I own a Symphony H50. I am trying to install windows via change my software but it shows device too slow or protected by manufacturer.
So googled it and found that i need to unlock my boot loader.
So I installed adb,fastboot,drivers including bootloader interface driver. And booted into fastboot mode. And typed "fastboot oem get_unlock_data" and the command prompt shows 3 dots (...) And the cursor keeps flashing. And no confirmation message shows up on my phone.
It only shows "FASTBOOT mode".
Another thing i found out while installing adb drivers that it listed my phone manufacturer as HTC.
So is the problem with my phone?
And how do i fix it?
It may be a problem with driver, uninstall the previous one and install Koush universal adb driver from kaushikdatta.com
Use the link given below for a thorough tutorial to replace drivers.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Thanks for reply,
I'll try the drivers.
Though my adb drivers are working fine. My issue is with fastboot.
When i boot into fastboot mode it shows "FASTBOOT mode" on a black screen.
But i would try with the
That black screen with fastboot mode written at the bottom comes up on every phone when you boot into bootloader.
Please read the whole guide before proceeding.
You may skip the driver and adb installation part if u have already taken the measures I stated before.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.
I was attempting to flash lineageOS from https://forum.xda-developers.com/mi-pad/development/lineageos-16-0-07-12-2019-shield-blobs-t4015965. Keep in mind my firmware knowledge was less than ideal so when I got to step 5 which was "5) execute command: fastboot flash tos your path to tos.img", I copied it word for word into fastboot and obviously it didn't do anything (I didn't understand the "your path to" portion was supposed to be the file directory then) I then searched the internet trying to look for a solution, thinking I had missed a step. I came across this article https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/ and got up to step five where I executed the "fastboot oem unlock" command and unlocked my mipad's bootloader I couldn't understand the next few steps so I gave up on this set of instructions. When I reattempted to use fastboot after figuring out what "your path to" meant on the first set of instructions, my device couldn't be detected through executing "fastboot devices", my computer's device manager, or MiFlash even though all ADB drivers were initially installed and I even installed it again just to be safe. How do I get my computer to detect my mipad again? Note: my mipad is now rebooting straight to fastboot
TLDR: unlocked mipad 1 bootloader using fastboot, mipad no longer detected by computer and only reboots to fastboot. How to get mipad detected by computer