Related
So i just flashed my vox with dr.gonzo's new 1.0 rom...and I did it the same way i've been doing it for months now (since his first rom 0.1) and it all went good, but when it was suppose to reboot turned off but never turned back on....I turn it on manually and i see the htc logo, it vibrates and then black screen... nothing happens afterwards...please dont tell me its bricked...please.....
If you're not able to get it into the bootloader to run an RUU then I suggest that you flash a signed HTC ROM, flash USPL and then re-flash New Guava v1.0
how do i flash a signed htc rom? when i turn it on, the htc logo comes on, then vibrates, and then a black screen.... when i try a hard reset, it asks me to confirm by pressing send. i press send (correct me if i'm wrong, send is the green 'phone' button right?) and it loads up the htc logo, vibrates and then shuts off. I've never had a bricked phone before, this all just doens't make sense i did the same steps that i've always done.
Seriously? Your phone is not bricked.
If you've flash a ROM before, it's the exact same procedure - what you can try and do is load into the bootloader by holding the camera button and plugging in a USB cable, it will start into the tri-color screen and should show USB is connected then you can flash a signed HTC ROM.
If the ROM is corrupt, this is your best way of "recovering" your phone, if the ROM was flashed properly, after getting into the bootloader, run ruurun 0 and ResetDevice to boot it back into OS.
oh ok, i haven't tried that yet (bootloader mode that is). Now you say i do this by plugging the usb and holding the power button and camera button? is that how it works? h4waii, you just lightened up my day by giving me some hope!
That is how you can enter the boot loader.
1). Turn off and unplug the Vox from external power/USB cable
2). Press and hold the camera button
3). Insert external power/USB cable
4). Continue to hold camera button until you enter the tri-color screen
At this point, you should have a "USB" text label on the bottom left hand side indicating USB is detected - you can then run an RUU from a signed HTC ROM to update it.
press and hold the camera button alone? i tried that, it doesn't power up the unit though?
Yes it does. Hold camera and plug in your USB cable (making sure it's also plugged into your computer).
ok i got it to the triband screen, but when i ran dr.gonzo's rom it got to 3% and said its corrupt. so i'm gonna do what you said and flash a signed htc rom. hopefully it works....
Yes, 3% because SPL is not patched to allow an unsigned ROM to be loaded, flash an HTC ROM to it, once that is complete you can run USPL to re-flash New Guava.
It will work, don't need to hope
you are a godsend! literally have no idea how depressed i was yesterday! being a university student money is very tight right now so was a total shock when i realized i bricked my $350 phone....I wish i had money cause i'd send you some for being so helpful but I dont... So just please understand i REALLLY appreciate your help, thank you.
That's what we're here for. Glad to be of service.
Hi, i've got a big problem...
After a system crash i pull-out the battery and then pull-in to reset the device.
after that now when i turn on the telephone it remain stucked on the white screen with htc logo. tryed to factory reset but remain stucked after i press on it.
my htc has original rom. no modification. what can i do? i don't really want to spend 3 weeksfor htc assistance.
Thanks
Semi-bricked phone E:Can't mount /cache/recovery/command
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
For everyone who Bricked their phone - Help prevent the others
[Guide] How to brick your Desire S
Have i to flash a stock rom? how can i do without remove warranty? in the case it does'nt work i have to take it to htc center
You probobly fried your EMMC chip when you removed your battery.
it would be best to return it in for repair.
I think you may have same problem with me before. No choice but to bring it to repair.
Sent from my HTC Desire S using XDA App
It was s-off before? Can you boot 2 recovery?
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
chris5s said:
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Same problem as topic poster, i,ve been messing a lot with custom roms on win 6.5 phones, but I havn´t done anything fancy on my Desire S , as to rooting or custom roms. (work phone!) Now I´m just curious as how I get a recovery going, when the PC doesent recognice the device when USB connected.
The eng-off file (mine is ON) with the .bat file cant connect to phone, and maybe im better off sending it to repair, but my pride wants me to solve it myself.
-Damn phone just went AWOL last night after an marked Angry Birds update, rebooted it a couple of times, because of a lot of process errors, and then all dead. (white HTC screen on -until morning)
Have the latest FOTA (DK, Nordic)
ROM: SAGA PVT SHIP S-ON RL
Hboot: 0,98.0002
Radio: 3805.06.02.03_M
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
psudo said:
Same problem as topic poster ....
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
Click to expand...
Click to collapse
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
chris5s said:
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
Click to expand...
Click to collapse
"ROM on SDcard": what format would that be in? RUU.exe or?
I can get into recovery menu (HBOOT) but chosing recovery option results in "a green recycle icon with an arrow on black background" screen, a few seconds then it virbrates 6-8 times, and then fades to black, so to speak!
Factory reset option: Locks the HBOOT screen and nothing but a battery pull, will change that.
I MAY have pulled the battery and not left it out for the 30 sec bricking danger senario, that I wasn´t aware of, until resently.
So the diag. is that is probably bricked!
Thanks for the reply
/Psudo
Rom on sdcard would have to be *.zip to be flashable. If you're unrooted + stock then you won't have Clockwork recovery or similar.
Tough that factory reset doesn't give any joy. These devices.....
Looking like masonry then, unless someone else can help.
Peace
Sent from my HTC Desire S using xda premium
surprisingly i got the same issue yesterday after i installed proxuser's official htc rom. Everything started fine went through setup so i assume it's not because of the rom because i don't think the phone would've started up in the first place. Anyway i am about to try and install some different roms and have also copied a backup over from my other desire s.
Will let you guys know if it worked.
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Can you still boot to recovery?
adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
t1j said:
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
Click to expand...
Click to collapse
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
In the end, I just flash a different rom, specially Candy5 as found here: http://forum.xda-developers.com/htc-one-s/development/rom-t2964931 and it worked.
It's possible I accidentally flashed a rom that was incompatible with my device, not sure.
EDIT: I also switched from CWM to TWRP. Not sure if that helped.
t1j said:
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
Click to expand...
Click to collapse
I have broken volume down button, what can i do? face the same problem
What does it mean by manually flash boot.img? After flashing a custom rom, do not reboot first but flash the boot.img via twrp which can be found in zip for the rom?
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Pra7ul said:
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Click to expand...
Click to collapse
adb reboot bootloader
waterdaan said:
adb reboot bootloader
Click to expand...
Click to collapse
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Pra7ul said:
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Click to expand...
Click to collapse
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
noahvt said:
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
Click to expand...
Click to collapse
Even If my volume button dosent work then why wont it enter bootloader via advance reboot it just restarts to system after selecting reboot to bootloader,so i should hard brick my device once again, P.S. i have done that twice before though.