Related
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
Hi,
I wanted to root my HTC One when it was with android 5.0.2. I did everything which I was suppose to do and installed SuperSu which did not work my mobile. So I tried to update the latest SuperSU binaries but there problem started. After powering it just shows welcome screen and still I can go to developer mode and see fastboot, recovery etc options. Now main problem is adb does not detect my mobile. Could any please help me ?
how about using fastboot? is adb worked on the recovery?
ashokb_409 said:
Hi,
I wanted to root my HTC One when it was with android 5.0.2. I did everything which I was suppose to do and installed SuperSu which did not work my mobile. So I tried to update the latest SuperSU binaries but there problem started. After powering it just shows welcome screen and still I can go to developer mode and see fastboot, recovery etc options. Now main problem is adb does not detect my mobile. Could any please help me ?
Click to expand...
Click to collapse
Hi, U must have turn on developer option, next turn on debbug USB and then the adb see your devices.
U can check in CMD ''adb devices''.
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:
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. Thanks.
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
rohanzakie said:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
Click to expand...
Click to collapse
If you can boot into bootloader, you can fastboot flash the images from https://developers.google.com/android/images (or just try running the entire N9F27N script) from your fastboot folder in cmd prompt or the Mac equivalent if you use Apple.
Sent from my Nexus 9 using Tapatalk
usb-debug is not enabled.
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Can you still access TWRP, if it was already on the device.
Flash any custom rom, enable the option and flash stock again (if you want).
If it is stock recovery, sideload an OTA image instead.
https://developers.google.com/android/ota
Manually boot recovery and you shouldn't need usb-debug enabled, I hope.
A bit of research and it is required unfortunately
Edit: You don't need usb-debugging for fastboot flashing.
Also Nexus Root Toolkit might prove helpful to setup drivers on your pc and restore your device to working order.
^^^ It is out of date software, so hesitant to recommend it.
rohanzakie said:
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Click to expand...
Click to collapse
Boot to bootloader and use fastboot commands. Fastboot flash system system.img
Etc.
Use the files extracted from factory image.
rohanzakie said:
the cmd prompet say ""
Click to expand...
Click to collapse
I've definitely had this experience. You can try disconnecting the cable then reconnecting. When that doesn't work, you have to remove all the drivers or at least run through "updating" the Android drivers in hardware settings. You won't actually be updating drivers just re-installing from the PC. Wug's toolkit mentioned above may be your best choice if you don't have TWRP. The toolkit will provide you with an exe called usbdeview which enables driver removal. I didn't mention an OTA sideload because I thought you did need ADB for that. If you can get PC to recognize the device in cmd, then you can fastboot flash images.
Sent from my Nexus 5X using Tapatalk