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 Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
GoRiLaz301 said:
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
GoRiLaz301 said:
Hi Everyone / Anyone,
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
[email protected] said:
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
Click to expand...
Click to collapse
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
In CUSTOM Recovery the USB debugging is enabled by default...so that step of booting into phone and enabling the USB debugging doesn't matter...
the device won't get recognized if u had not installed the HTC drivers...
try installing the latest drivers from here
Install this and try
Code:
adb devices
And what are u planning on do install a custom ROM or Flash the Stock Nandroid backup from the thread I provided.....????
I can only help u knowing what u are trying to do.....
GoRiLaz301 said:
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
Click to expand...
Click to collapse
GoRiLaz301 said:
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
Click to expand...
Click to collapse
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
GoRiLaz301 said:
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
Click to expand...
Click to collapse
Fine and clear..
have u tried the drivers I have put in the previous post.........????
Try different USB ports to on ur PC too.......that will work sometimes.......:fingers-crossed:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
GoRiLaz301 said:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
Click to expand...
Click to collapse
These are the latest HTC drivers can u try this and report whether ur device is recognized in adb recovery mode......
Please try by uninstalling the previous driver u had.........
BTW is it Windows 8.......????????
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it. it will be recognized as HTC MP DEVICE or something similar but with unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognized as HTC device without USB driver device installation problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Earlier before your help, have found and load TWRP version 2.6.3.0 whereas now the version is 2.4.4.0, will earlier or this 2.4xx version be any difference and affect the connection with adb?
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
GoRiLaz301 said:
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it.
it will be recognised as HTC MP DEVICE or something similar but will unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognised as HTC device without USB driver problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
Click to expand...
Click to collapse
From the control panel OFC
If u had installed HTC drivers u must be able to see it like this uninstall that...
O Haa haa )
Blunder me ! That's right ! Think bit exhaust after a few sleepless nights figuring out why and hows on this phone....
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
GoRiLaz301 said:
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
SDK Manager wont show up on Control panel AFAIK....
it will be a zip file which u have to extract.....
in the extracted folder u will be able to see android-sdk-windows\platform-tools from where u have to open the cmd to execute the abd/fastboot commands
I have the setup of android-sdk-windows and the HTC drivers I pointed to....
It works flawlessly so i recommend to uninstall Universal Adb driver since that isn't helping ur phone recognized anyways.....
Install the Drivers I pointed to and try wether ur phone is getting recognized....:fingers-crossed:
Note : Alternately u can try this installer also which is a small package with the necessary adb and fastboot files......
---------- Post added at 06:43 PM ---------- Previous post was at 06:32 PM ----------
GoRiLaz301 said:
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
these drivers can be there ...they are or the installation of bluetooth drivers for our phones I guess....
Just uninstall the Universal USB driver .....
If you have HTC Sync I beleive u must be having the HTC driver as I showed on the Screen shot.....
Anyways if u dont see that in the control panel install the one I gave.....U must be fine
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
GoRiLaz301 said:
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
Click to expand...
Click to collapse
FIne....
From bootloader boot into recovery.....
try whether u r device is recognized.......
If recognized PROFIT for the hectic work done......
then u can push a rom to ur SDCARD using adb push command......
then install as usual from the recovery........
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
JACK POT !!!!
ADB DEVICES listed my device s/n. in recovery mode.!
GoRiLaz301 said:
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
Click to expand...
Click to collapse
Absolutely Fine........
What I meant in While in TWRP connect ur phone to PC
double click on your Start SDK shortcut and in the CMD type
Code:
adb devices
Ur result must be like this
YES, it did show the device listed with serial no.
Now i into the [Recovery Installation] section and at the BACKUP part (pt. 15), now should i also tick Recovery + Cache to perform full backup of actual ROM? (this seem not applicable to me, is it?)
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:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.