Related
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
ICruentusI said:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
Click to expand...
Click to collapse
Adb doesnt work in fastboot. Use fastboot flash boot boot.img then flash the kernel modules in recovery.
Sent from my HTC6435LVW using xda app-developers app
Wow
Thank you very much. Complete noob at playing with Android devices .
When you flash a kernel, you have to make sure to also flash the kernel modules in recovery. That's what caused the wifi to stop working. Same thing happened to me haha.
Sent from my (Viped out)³ DROID DNA
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
PROBLEM SOLVED: I switched out the Motherboard c:
merlise said:
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
Click to expand...
Click to collapse
This is from another thread about a boot loop thought it might help you.
powerpoint45 said:
I do not know if this would work or even the steps, but you can download the stock firmware from here: www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201596860
Also the ????????????? Besides your device from "adb devices" just means you need to install the driver for it. That should not be too hard to find out how to do. But really I think you'd need the fastboot drivers more. But in the past I have fixed a bootloop by just looking at the logs to figure out where the crash is coming from via adb logcat, then fixing that issue. But since this is using xposed it'd probably be too complicated to fix manually. Don't ask me for drivers tho cause I use Linux.
Note: the firmware update downloads as a bin file but it is just a zip file. A fastboot update might actually work with it since it is signed by Amazon.
Something like:
Wipe your device. (only if necessary)
fastboot -w
Update your ROM.
fastboot update
---------- Post added at 11:03 PM ---------- Previous post was at 10:45 PM ----------
I've gotten into fastboot on this device. I think it was either "adb reboot bootloader" or "adb reboot fastboot" that works. Keep in mind when in fastboot mode the fire hd6 screen is completely blank.
Click to expand...
Click to collapse
AlbusAngelus said:
This is from another thread about a boot loop thought it might help you.
Click to expand...
Click to collapse
Thanks for trying to help I tried just about everything, but nothing is working.
I decided to just get another used HD 6 and switch out the motherboards and see what happens. I'll come back to the rooting game as soon as there is a working custom recovery and rom up, haha. Thanks.
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
meganoahj said:
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
Click to expand...
Click to collapse
Yours was actually the first I looked at! I tried but I unfortunately couldn't get ADB to recognize the device properly. I've already switched out the motherboards so my problem is somewhat fixed for now.
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
ryanyz10 said:
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
Click to expand...
Click to collapse
I have a fastboot cable, but it still didn't put me into fastboot
merlise said:
I have a fastboot cable, but it still didn't put me into fastboot
Click to expand...
Click to collapse
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
ryanyz10 said:
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
Click to expand...
Click to collapse
I have haha, I honestly tried everything but I just couldn't get it into fastboot. When I'm feeling adventurous, I'll probably try it again, but I just ended up switching out the motherboards with another HD6 for convenience.
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
jnelsoninjax said:
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
Click to expand...
Click to collapse
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
matze19999 said:
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
Click to expand...
Click to collapse
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
jnelsoninjax said:
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
Click to expand...
Click to collapse
You said windows can't detect the watch in adb mode? What about the fastboot mode?
matze19999 said:
You said windows can't detect the watch in adb mode? What about the fastboot mode?
Click to expand...
Click to collapse
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
jnelsoninjax said:
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
Click to expand...
Click to collapse
Did you enter the fastboot mode?
matze19999 said:
Did you enter the fastboot mode?
Click to expand...
Click to collapse
The watch is showing CSC Fastboot Mode! So I would assume that it is in Fastboot mode
Were you able to get this fixed?
No, I have but been able to resolve this issue. It is not being recognized by Windows, therefore I can't flash the original os back to it.
Did you have TWRP installed prior to the failed flash?
CVertigo1 said:
Did you have TWRP installed prior to the failed flash?
Click to expand...
Click to collapse
No
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
CVertigo1 said:
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
Click to expand...
Click to collapse
I am running Windows 10 X64 build 1803
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
CVertigo1 said:
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
OK, I will mess around and see what happens! I will have to do it tomorrow, but I will play around and see what happens!
Let me know how it goes and I'll walk you through it some more.
Any luck?
Sorry for the long time to reply. I installed ubuntu in window and installed the appropriate packages, however both ADB and Fastboot show nothing connected, even though the device is in CSC Recovery mode. Is there anything else I can try?
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
CVertigo1 said:
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
Click to expand...
Click to collapse
OK, I got windows to see the watch via fastboot and I downloaded the image that you posted (bloat free) now the watch started to boot, but so far it is just showing spinning dots, and has been for ~5 minutes or so, is this normal?