Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.
bashme said:
Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
that is the BOOTLOADER.:silly:
to enter TWRP
go to HBOOT then enter RECOVERY
if not entering then its messed up . flash it again with new file or try different version.
+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.
gazza35 said:
+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.
Click to expand...
Click to collapse
It does not do anything unless you have just the correct files in your SD card that define the network and so on. Only service centers and network providers have such files.
Silly me lol
I selected HBOOT then RECOVERY but it goes back to the bootloader menu??
I have already re-flashed it. I guess i will have to find another file to flash.
Thanks for the advice guys
OK guys.
I flashed a different version of TWRP img file and it still does not boot into TWRP?
I noticed something else. When i select HBOOT, for around a two seconds several lines of info are displayed:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
I pasted a copy of the TWRP img file in the root of my SD card. But still it comes back to Bootloader??
Not sure what to do now?
Any advice guys, please?
Hi guys.
Still not able to load into TWRP. I briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Can anyone help please?
Cheers.
bashme said:
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
Click to expand...
Click to collapse
You are flashing the wrong recovery. Considering the m4 at the end of the image name, this is for the One Mini not the One Mini 2. Which is why you are not able to boot into TWRP.
Get the correct image from here
Hi csoulr666.
Thank you for your reply.
I downloaded the image from the link you kindly provided - recovery-twrp-2.8.5.0.img
When i issue the command fastboot boot recovery-twrp-2.8.5.0.img i get the following response
downloading 'boot.img'...
OKAY [ 1.489s]
booting...
OKAY [ 0.004s]
finished. total time: 1.499s
Then the device reboots into the standard htc home screen and NOT into twrp. At this point the USB cable is still attached to the device and PC. Not sure if this has any bearing on the normal boot??
I performed the above steps several times, but still the device boots up to htc home screen and not twrp.
In bootloader, i also selected HBOOT, i briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
i then select RECOVERY, however the device stays in bootloader??
Very frustrating to say the least.
Am i missing something else?
Thanks for the advice up until now.
P.S please excuse me, i am a newbie so not that much familiar with rooting.
Cheers.
bashme said:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
if you dont want keep seeing this just remove SDCard while you performing the actions.
try this recovery instead
its normal the device boot into the rom unless you press the buttons to get into bootloader.
Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.
bashme said:
Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.
Click to expand...
Click to collapse
not sure what you asking and for what but after a search i found this:
open command prompt and type
adb devices (if your device shows continue)
adb shell
su -c 'setprop sys.usb.config diag,adb'
nothing happened on mine but i don't have HTC drivers installed. All you need in here
Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Previously, I was able to enable HS USB diag port using the above adb command on the Xperia Z and Samsung Mini S4. But I've not been able to activate HS USB on Xperia Z3 and now HTC One Mini 2. I was under the impression that if I rooted and flashed a custom rom onto the HTC One Mini 2, all developer features would be automatically available, especially the HS USB diag port??
To compound the misery, after much reading on rooting and flashing for HTC One Mini 2, I flashed cm-NostromoPop-v2.0-20150430-1330-memul.zip and open_gapps-arm-5.0-nano-20160401.zip. Thankfully the device is not bricked. However, now i get the following problems
When accessing Google Play Store - 'Check your connection and try again'
'Google Play Services won't run...' message repeatedly appears
I cannot boot into twrp recovery so that i can flash another rom
I read on the net that installing the wrong GApps file produces the above google problems? Could i have installed the incorrect GApps file?? Not sure how to verify this? Could the rom i installed be incorrect?
And what can i do to get into twrp recovery again? Not even the twrp recovery image i earlier flashed and successfully booted into has helped this time.
I am rigorously searching the net for answers, to no avail thus far.
Ahh the joy of messing with a phone. I'm very tired but will keep trying lol
Any help would be warmly welcomed.
Thanks in advance.
bashme said:
Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Click to expand...
Click to collapse
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.
kativiti said:
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.
Click to expand...
Click to collapse
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.
bashme said:
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.
Click to expand...
Click to collapse
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.
kativiti said:
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.
Click to expand...
Click to collapse
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again
bashme said:
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again
Click to expand...
Click to collapse
you can use ADB push but you need TWRP for that.
kativiti said:
you can use ADB push but you need TWRP for that.
Click to expand...
Click to collapse
OK so after much fretting i managed to get my device working.
I managed to boot into bootloader and then flashed an earlier version of twrp and it immediately booted into recovery.
From here i wiped cache, system...... and then installed CM12 with corresponding GApps.
Device now working...PHEW!
OK so now back to trying to get HS USB port activated using ADB commands, which i am trawling the net to find. I just don't understand why it is possible to activate HS USB port in Windows for Samsung and Sony, but not on this HTC One Mini 2?? The ADB setprop command you listed earlier is usually the one that triggers windows to open up the HS USB Diagnostics port, but it is not happening with this HTC One Mini 2? Anyway, i'll keep checking the net.
I have added an image just to show what it is i am trying to activate - Qualcomm HS USB Diagnostics Interface Port
Once again many thanks for your assistance kativiti.
reserved
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
I'm having the same problem.
basically when i am on slot b, I can't use any fastboot commands and ive also not installed twrp.
those same commands worked when i was on slot a.
now i am stuck in slot b. don't know any fix.
ZuNNN said:
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
Click to expand...
Click to collapse
Use Windows PC (preferably 7 with Intel and USB 2.0), latest platform tools and try again. I generally do not install TWRP, rather boot it (use the latest one) and carry out the tasks since I use Stock ROM.
I had that problem before.
Things that solved:
Use another usb-c cable
Run fastboot on linux
Use an usb 2.0 HUB (the ones that have 3 or 4 ports)
did u check usb debug box,and OEM as well?
and if you did all of that , did unlock bootloader?
hi guys, after the really buggy android 10 update from xiaomi i decided to install a custom rom on my device, i hadn't installed a custom rom in ages and never on an a/b device so it was new to me, i was kinda stumbling but managed to install twrp, install pixel experience rom and then switched to slot a and it booted
but now my device does not accept most fastboot commands! fastboot getvar all only works 1/3 of the time, most of the time it either fails with FAILED (remote: 'unknown command')) or FAILED (Write to device failed (Unknown error)) which boots me to the same black screen as OP. fastboot boot twrp.img always fails. the phone boots successfully but im unable to switch slots or boot to recovery when everything was working perfectly before switching slots. ive tried 2 cables with 3 usb ports on my laptop.
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not