Related
renamed spl to update.zip and placed in root of SD
did alt+s, think i pressed alt+w accidentally, now when booting / rebooting
trying to get my home + power screen to reload, get "ROGERS" with the red "FASTBOOT USB" at the top, according to this
Rogers, heres your real root
http://forum.xda-developers.com/showthread.php?t=544654
"(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)"
then alt+s to load the rom, well the rom isn't on there becausei was following
installing the new spl
http://forum.xda-developers.com/showthread.php?t=532719
anyway to load the actual rom some other way, can't access the SD card with the fastboot skateboard screen or the rogers with the red "Fastboot usb" screen.
Confused, and frustrated, some help would be wonderful if you have the time, Thanks !
Did you flash the SPL before you flashed the radio?
xsnipuhx said:
Did you flash the SPL before you flashed the radio?
Click to expand...
Click to collapse
what i was trying to do
note: when attempting to flash
fastboot flash radio radio.img
Error: FAILED <remote: signature verify fail>
fastboot erase system -w
-okay
fastboot erase boot
-okay
fastboot erase recovery
-okay
fastboot flash recovery recovery.img
Error: FAILED <remote: signature verify fail>
Try redownloading the recovery.img There may have been a corrupted file somewhere.
xsnipuhx said:
Try redownloading the recovery.img There may have been a corrupted file somewhere.
Click to expand...
Click to collapse
Just did, receiving same error as before
"FAILED <remote: signature verify fail>
?
Check the original thread and see if anyone else is having the same problem.
xsnipuhx said:
Check the original thread and see if anyone else is having the same problem.
Click to expand...
Click to collapse
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
JsnLlnd said:
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
Click to expand...
Click to collapse
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
h.nocturna said:
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
Click to expand...
Click to collapse
Tried, won't go into recovery. stays at the Rogers start screen.
Anything else?
Quick update, was able to get into
fastboot boot recovery.img
and it loaded cyanogen cf 1.5? did alt+s and alt+w but theres no rom on the sd card right? hence its not doing anything?
am i figuring this out correctly here?
when i type in the fastboot boot recovery.img
downloading 'boot.img'...OKAY
booting...OKAY
where is this thing and how do i do this right im confusing myself blahhh
--------
rebooted, now i can't get into fastboot -_-
is this thing bricked now ?
use my fastboot boot recovery.img and it goes fastboot real quick, see a loading bar, then bam back to plain rogers screen. gonna try different recovery.
possibly adb push ? im learning this all just now more or less, so a direct path from my c:\android\sdk1.5_r3\tools: adb push ??? what goes here?
as far as the alt+x option goes , i can do it , but ums_enable isn't doing anything , any more details on that so i can get that rom on the SD card, think i will be good to go after that.
I've got a nexus one with a broken power button and a corrupt OS. It rarely successfully manages to boot. Since this is the case, I'm not able to turn on USB debugging to follow some of the tutorials here..
My next try was fastboot.. I downloaded these two files:
recovery-clockwork-5.0.2.0-passion.img
update-cm-7.1.0-N1-signed.zip
But it seems like I wont be able to flash a recovery file if I have "s-on" displayed on my hboot or fastboot screen..
How do I gain "s-off"? And is it possible to flash a stock rom via fastboot?
And yes, my phone's got stock gingerbread 2.3.4 rom.
HBOOT 0.35.0017
MICROP 0b15
Touch panel SYNT0103
Radio 5.08.00.04
Please help me with this matter as I have been trying to accomplish this task for over three months now..
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
troby86 said:
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
My phone's power button is broken so I'm not able to select the recovery option
Jack_R1 said:
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Click to expand...
Click to collapse
It's already unlocked, as there is a small open lock displayed at the bottom of the boot screen.. and fastboot displayed it as already unlocked as well.. still.. i need a way to go to recovery without the power button
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Jack_R1 said:
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Click to expand...
Click to collapse
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
knaphih said:
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
Click to expand...
Click to collapse
Do you have the fastboot command on your computer?
troby86 said:
Do you have the fastboot command on your computer?
Click to expand...
Click to collapse
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
And if none of that seems to work:
http://www.androidguys.com/2010/09/08/manage-nexus-broken-power-button/
OR
http://www.yamihoshi.nl/tech/tutorial-google-nexus-one-power-button-soft-fix
Both are the same, the second one is easier to follow.
OR
Put your recovery .img file into the same folder as your fastboot command, and run this: "fastboot boot recovery-clockwork-2.5.1.4-passion.img"
^^^^^USE YOUR RECOVERY NAME...NOT THE EXACT ONE ABOVE^^^^^
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
Click to expand...
Click to collapse
I've attached an image showing proof that I've tried your method but still kept on failing to reboot to recovery..
When i try the command "fastboot boot recovery-clockwork-5.0.2.0-passion.img", the phone simply restarts and goes back to the 'X' boot screen and gets stuck there.
Could anyone please find me an genuine unedited gingerbread 2.3.4 ROM so I can PASSIMG it? ... I've downloaded several rooted ones.. but all seem to need the "android-info" file
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
Click to expand...
Click to collapse
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
knaphih said:
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Click to expand...
Click to collapse
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/showthread.php?t=1312540
You guys are life savers troby86 and Jack_R1..
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
Click to expand...
Click to collapse
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/show....php?t=1312540
Click to expand...
Click to collapse
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
knaphih said:
You guys are life savers troby86 and Jack_R1..
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
Click to expand...
Click to collapse
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
troby86 said:
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
Click to expand...
Click to collapse
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
mally2 said:
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
Click to expand...
Click to collapse
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
bassmadrigal said:
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
Click to expand...
Click to collapse
well what do you know, he may just ask the OP to send him his nexus to get it fixed and you will never hear from him again.... just warning y'all thats all....
Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.
The phone can't boot in bootloader?
Guich said:
The phone can't boot in bootloader?
Click to expand...
Click to collapse
When i chose from CWM recovery menu "Reboot recovery", phone boot into download mode, and thats all. Fastboot or adb dont see it.
But. In usb device list:
In download mode:
Bus 002 Device 061: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt (Charge Mode)
In recovery mode:
Bus 002 Device 063: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Assuming you didn't corrupt your boot loader you should be able to get at the boot loader and use fastboot to flash a new recovery.
Power the device off
Hold power and volume down, the phone should turn on and load into the boot loader.
From there you can select fastboot (navigate menu with volumn buttons, power button to select fastboot).
You can use this command to flash a recovery:
Code:
fastboot flash recovery recovery.img
If you can enter bootloader,you may try formatting partitions from fastboot,and flashing them afterwards,that is if bootloader is unlocked.
You can also lock your bootloader and try installing RUU,it will put your phone back to stock,
P.S. - I'm new to this,so please consult with more experienced members,before doing anything
ZloY909 said:
Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.
Click to expand...
Click to collapse
you "fastboot flash boot recovery.img"? you may want to check this thread: http://forum.xda-developers.com/showthread.php?t=2478438&page=3
if that doesn't help, post back
Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?
ZloY909 said:
Has the same problem, flashed CWM Recovery to the boot partiotion. Can you give me more info about that magic what you are done to cennect your phone to fastboot? =)
Thanks.
Best Regards.
Click to expand...
Click to collapse
fastboot shouldn't be affected.
when you connect your phone to the PC, does it the text in bootloader change from "FASTBOOT" to "FASTBOOT USB"
Guich said:
Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?
Click to expand...
Click to collapse
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
"screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds" -> that's stock recovery
Before, when you are in bootloader (image attached), are you able to "fastboot devices" and it shows up? because the bootloader is not affected by the recovery.
basically "fastboot flash boot recovery.img" put the custom recovery where the kernel is supposed to be.
First thing you need to get/confirm working is bootloader/fastboot.
ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?
Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.
herrfricke said:
Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.
Click to expand...
Click to collapse
I will check this out. Thanks for your reply.
Now i reinstall to win8, reinstall drivers and adb.
Guich said:
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?
Click to expand...
Click to collapse
Thanks for your reply. This help me to get to the bootloader.
Now i try to flash boot.img into boot =)
Ok. I have working phone =)
Thanks for yours replies.
I have traied a few different recoveryies and fastboot and mfastboot, but I can not get any recovery to ACTUALLY flash to the phone.
It is a XT1053 running 4.4.4. Even when everything says it flashed fine, the recovery is still not there when i try to boot into it.
Any ideas?
Use the Vol+ button to select recovery, not power.
knitler said:
I have traied a few different recoveryies and fastboot and mfastboot, but I can not get any recovery to ACTUALLY flash to the phone.
It is a XT1053 running 4.4.4. Even when everything says it flashed fine, the recovery is still not there when i try to boot into it.
Any ideas?
Click to expand...
Click to collapse
What @nhizzat has said, is the most common mistake.
Beyond that, you don't mention if your bootloader is unlocked or not. I'm guessing it is, otherwise you should get some kind of error from fastboot/mfastboot on your PC.
One other thing that some have run into is... after flashing a recovery, having to reboot into bootloader before trying to enter recovery.... For example...
Start the phone in Fastboot/BootLoader mode and connect it to your PC.
open command prompt file and change to the folder your recovery IMG file resides in.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
Note: the recovery could be twrp.img, cwm.img, etc.
The device will reboot then display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select it.
nhizzat said:
Use the Vol+ button to select recovery, not power.
Click to expand...
Click to collapse
I'm aware of that. I still have the stock Recovery.
KidJoe said:
What @nhizzat has said, is the most common mistake.
Beyond that, you don't mention if your bootloader is unlocked or not. I'm guessing it is, otherwise you should get some kind of error from fastboot/mfastboot on your PC.
One other thing that some have run into is... after flashing a recovery, having to reboot into bootloader before trying to enter recovery.... For example...
Start the phone in Fastboot/BootLoader mode and connect it to your PC.
open command prompt file and change to the folder your recovery IMG file resides in.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
Note: the recovery could be twrp.img, cwm.img, etc.
The device will reboot then display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select it.
Click to expand...
Click to collapse
My thread title says its Unlocked, I will try rebooting to the bootloader first then trying recovery. I did not try that. I have been rebooting to the OS then rebooting to Recovery,
knitler said:
I'm aware of that. I still have the stock Recovery.
My thread title says its Unlocked, I will try rebooting to the bootloader first then trying recovery. I did not try that. I have been rebooting to the OS then rebooting to Recovery,
Click to expand...
Click to collapse
that is your issue right there after you flash a custom recovery you need to boot into the recovery before letting your phones boot into the OS.
if your phone boots into the OS then the recovery will not stick and you will be back on the stock recovery.
so
1.boot into bootloader
2.flash Custom recovery of your choice
3. make sure the phone does not boot into OS it can reboot back into bootloader and it can reboot into recovery with no issues but if it boots into the Phone OS then you will be back on stock recovery.
hope this helps enjoy
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