Develop Bugs

Booting to recovery with button combination not working

So, after trying out a few firmwares (JM2, JG8, JM5) and kernels (Samset&OC) I can't no longer boot to recovery with Vol UP + Home + power. I can't really say when this problem first occurred, but maybe with JG8 flash. The strange thing is that I can get to recovery with adb reboot recovery and through android console with reboot recovery (when rooted ofc). Also download mode works great.
Things I have tried:
-flash again to JM2 and JM5 with re-partition checked (512 PIT)
-cleared cache+data through recovery
-factory reset through phone code (this also cleared the internal SD)
-took out the battery multiple times
-booted phone without sim
-flashed phone without sim
-changed CSC with phone code
-restore a nandroid backup of JM2. Recovery worked with this one when I took the backup
-there's no external flash card inserted
Soooo..does anyone have any idea about this kind of problem?

i had a similar problem after trying few ROMs. In my case, when i pres the key combi i get the boot logo and then few seconds later the screen goes black and then i see the boot logo again, and this goes forever. and then i tried pressing the same key combination simultaneously and once i see the boot logo i let go the power button and keep the vol up and home pressed, and then only it went into the recovery mode.
hope it works the same for you
Cheers

Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App

mmthabet: I had the exact same experience. Letting go of the power button when the logo appears lets me enter recovery.

or you may need to take out the battery first for a few seconds... after that, you can reinsert it back and try recovery mode...
at least this work for me...

Thanks for replies but none of the solutions work. The recovery mode button combination DID work for a few weeks, but then just stopped working.
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start. I have also tried to remove battery multiple times and once waited 30 mins before re-inserting it.
Trust me, I'm not doing it wrong :s And recovery is working great through adb reboot recovery and shell.

Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Click to expand...
Click to collapse
More so a timing issue. Buttons not pressed at the same time.
I get it all the time for all combo's.
Just keep trying.

You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.

odyssey61 said:
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
Click to expand...
Click to collapse
this wont work, if you bricked the phone in a bad flash situation.
in times when this app works, you can easily do adb reboot recover
so this app still doesn't address the real issue of how to get the 3 buttons press hardware recovery mode

Laum said:
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start.
Click to expand...
Click to collapse
I release the buttons right when the first Samsung texts comes on the screen. It will take it to Recovery mode. I also had a "boot loop" few times, if I keep pressing the buttons all the time.
Have you tried release your fingers right in the first texts? I really don`t know what is exactly the right way to press the buttons, but this always have took it to Recovery.

Looks like my latest full wipe with *2767*3855# cured it. Flashed JM5-->full wipe-->samset1.9b-->samset kernel and now it works. It must've got stuck somehow in my previous JM5 installation.

I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!

Igor02 said:
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Click to expand...
Click to collapse
yes
adb reboot download
but it is dangerous, as you can not recover from a bricked state, if your flash is not compatible or if something went wrong with odin, etc.

I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.

arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time

AllGamer said:
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
Click to expand...
Click to collapse
Well I did just get the phone 2 days ago,
Had that problem the same day, discovered the fix two hrs of horror later

Same Problem here i contact samsung here in mexico and a technical aggent tell me if we make a repair our phones we need a jtag and this is so bad alllready contact many people jtag manufacturers in china and honkong trow alibaba.com and no luck don't have other source i try is contact to nspro and z3x and no support for this repairand only hope still have is a reply from the people in the forum SMTi Jtag Repair Tool
Its hard to me go to UK Samsung Service Center i'm in mexico like i said
and i'm waith for a solve this i;m so very sad
http://www.youtube.com/watch?v=g8AIvalzBvY

Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I usually release the power button on the boot screen first and then the other two buttons

arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
Any idea how long you waited? Been waiting 5 minutes, hasn't shut off. Mine's a Bell though so I'm guessing I won't have any luck.

The way i do it (no chance of doing it wrong and timing):
hold down+home and then also press the power button for a little more then 10 seconds (so all 3 buttons for 10 seconds). The phone will reset into download mode, never fails in whatever mode the phone originaly was..

The 3 vibrate brick - Please Help {SOLVED}

Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin

msticlaru said:
Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin
Click to expand...
Click to collapse
call for a refurb. I had it happen twice.

ACD168 said:
call for a refurb. I had it happen twice.
Click to expand...
Click to collapse
I have a refurb sitting next to me lol. I wanted to root the old one so that I could do a backup and then restore that backup on the new phone. Wife saves pictures and videos to the phones memory (i know) so i would like to recover this if possible.
Also, it seems like this is something that has to be recoverable. Some sort of software is telling it vibrate 3 or 5 times. I am still doing research on this

Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?

k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
For referance. I just 5vibed my last inc last week, i know all about it.
k_nivesout: oj + power boots fastboot
For the OP, your device is now in qualcomm diagnostic download mode. Hence qualcomm devices in device manager.
To date this is still a none recoverable issue. NO ONE has ever recovered from this.
Good news is if your still in warrenty VZW will send you out another one for free over night. Just call Tech support directly. Just tell them your phone vibed 3 times and shut off. They'll have you do some things to it over the phone. If what they have you try dosn't work, they'll send you one out over night.
Hope this helps a little and hopefully this will save you from countless hours researching. Took me three days, before I realized I had been beaten, lol.

k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device

msticlaru said:
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device
Click to expand...
Click to collapse
Wait, wait, wait just a minute. i wanna talk to you in private. check your pm

msticlaru said:
The 3 vibrate brick - Please Help {SOLVED}
Click to expand...
Click to collapse
Glad I could help you fix this. Don't forget to post what we did to solve this so others can learn from us

This is written for the HTC incredible, please ensure you get the proper ruu image for your particular phone. For example, the HTC wildfire will be PG76IMG.zip, not PB31IMG as I have written below. the rest of the steps are applicable to all HTC phones.
Click to expand...
Click to collapse
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download (see above comment)
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about

Nicely done! I've never encountered this issue but I'm remembering this for future reference just in case.

Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....

nate2830 said:
Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....
Click to expand...
Click to collapse
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.

wildstang83 said:
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.
Click to expand...
Click to collapse
Oh sorry!! Thought it was a similar problem, but had a feeling it wasn't since the stock image didn't resolve my issue. Thanks!

My DINC was suffering from the 5 vibe syndrome. If I used it for anything that stressed the system or even used the phone for a few minutes it would result in a reboot that ended with a black screen, 5 vibes, and the indicator flashing green. At first I could pull the battery for a few minutes and it would recover. Eventually I ended up putting it in the freezer for a bit to get it running again. This progressively got worse until it was nearly unusable. Then I stumbled upon this thread..
http://forum.xda-developers.com/showthread.php?t=982454
Turns out mine was a hardware failure as the processor's BGA grid was failing. I heated the processor and now have a fully functional DINC. I had nothing to lose by trying this as I bought it second hand and didn't want a fancy paperweight on my desk.

Thanks guys, for helping me out with a 3-vibe brick i just had for no reason at the gym today. Was listening to music, texting, working out. All of a sudden, music stops, phone completely unresponsive. Battery out, 30-second wait, restart gives me boot-screen boot loops. Volume up + power gave me a 3 vibe brick.
Thanks to you guys, I discovered that i could get into hboot, boot into recovery from there, do a full wipe, reflash of CM7.0.3 and get the phone to start again. However, that's when the next BIG PROBLEM started. Screen went to sleep while restoring apps from the Market and now when i press the power button, the soft buttons light up but the screen doesn't. This is just super-duper to have problems like this on the same day I was telling a friend that I wouldn't trade this phone for anything else VZ has right now. Anyone have any advice?
PS - The only thing I did today besides "normal" use, is i updated Handcent and changed the LED flash rate.

msticlaru said:
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about
Click to expand...
Click to collapse
Sounds good, I'm hearing a RUU will work just as well?

This got my phone to turn on, but now im in a boot loop. How could i fix this? I appreciate all the help.

I actually recovered from a 5 vibrate error. I had flashed the leaked GB over a stock sense without doing a wipe and got stuck in a boot loop. Every time I tried to either power up into hboot or recovery (- vol and power, or + vol and power) I would get 5 vibrations and then a blank screen. If I tried to power up normally nothing but boot loop after the white htc screen. So I just kept trying to get hboot to load and then after about 5 tries it worked and I was able to get into recovery and flash a backup ROM. I still have problems getting hboot to load properly and it appears its a problem with how hard I press the volume keys. If I press it too hard I get five vibrations followed by the blank screen and it still takes a number of tried to get it to work right. Getting into recovery from ROM Manager is no problem it works flawlessly and I can flash ROMs with it no problem, just have problems when I manually try it. Otherwise the phone works great.

Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.

k_nivesout said:
Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.
Click to expand...
Click to collapse
Like I said it does it with the - volume and power combination too, + volume and power used to go straight into recovery bypassing hboot.
Its not so much the amount of pressure but the length of time I press the buttons, if I hold them too long I get the 5 vibrates, if I press them both then quickly relase them the phone will usually boot normally into hboot but not always. The button psuhing could all be coincidence and the phone just randomly works right after so many tries so I don't want to mess with the phone too much as I'm sure that eventually it will stop responding at all some day. I've never had problems flashing through ROM Manager so I will just use this and skip trying to do anything manually.

Unbricking Z1 Compact

So, today I've decided to root my Z1 Compact and install some custom roms. I've done this before on many other android phones without any trouble and today is the first time I ran into a brick (not sure whether it's soft or hard, I assume it's hard cause I cannot get into recovery anymore).
Basically, what I did was root the phone using Easyflash (the towelroot method), installed a recovery and then tried to flash PA the same way as I used to do on my other phones, but after the process my phone shut down and only gives a red blinking light while connected to the charger, powering on the device will only make it vibrate. The only thing that seems to "work" is when I hold the volume-up button + power and am connected to my PC, when I do that the device will show a blue LED, but other than that it's still unresponsive.
If anyone knows what to do here, or knows whether I should even bother or not, please tell me. I've tried searching and didn't come up with any relevant results.

Rzarector said:
I've tried searching and didn't come up with any relevant results.
Click to expand...
Click to collapse
"I've tried searching and didn't come up with any relevant results" = I'm lazy.
Try flashing a ftf file and report back. Xperias are different so you need to relearn a little. http://forum.xda-developers.com/showthread.php?t=2631291

Rzarector said:
So, today I've decided to root my Z1 Compact and install some custom roms. I've done this before on many other android phones without any trouble and today is the first time I ran into a brick (not sure whether it's soft or hard, I assume it's hard cause I cannot get into recovery anymore).
Basically, what I did was root the phone using Easyflash (the towelroot method), installed a recovery and then tried to flash PA the same way as I used to do on my other phones, but after the process my phone shut down and only gives a red blinking light while connected to the charger, powering on the device will only make it vibrate. The only thing that seems to "work" is when I hold the volume-up button + power and am connected to my PC, when I do that the device will show a blue LED, but other than that it's still unresponsive.
If anyone knows what to do here, or knows whether I should even bother or not, please tell me. I've tried searching and didn't come up with any relevant results.
Click to expand...
Click to collapse
http://forum.xda-developers.com/sony-xperia-z1-compact/help/lb757-how-to-update-to-rooted-108-t2822957
Just use my guide#5 to wipe the whole phone and reflash everything.
vol up + power will give you blue LED and it is fastboot mode. vol down + power will enter flash mode but no LED light.

XperienceD said:
"I've tried searching and didn't come up with any relevant results" = I'm lazy.
Try flashing a ftf file and report back. Xperias are different so you need to relearn a little. http://forum.xda-developers.com/showthread.php?t=2631291
Click to expand...
Click to collapse
This is the first thing I tried, but it doesn't seem to recognize my phone under windows (even after installing the drivers).

TheEndHK said:
http://forum.xda-developers.com/sony-xperia-z1-compact/help/lb757-how-to-update-to-rooted-108-t2822957
Just use my guide#5 to wipe the whole phone and reflash everything.
vol up + power will give you blue LED and it is fastboot mode. vol down + power will enter flash mode but no LED light.
Click to expand...
Click to collapse
Thanks a lot for the guide, the stupid thing I did was holding the power button and volume down cause it used to be like that with my previous phones. It seems to be flashing now, so hopefully all is well!
EDIT:Flashing ended succesfully but upon booting the phone the only thing I get is a flashing red led, so I'm assuming it's a hardware defect or I did something terribly wrong while flashing a custom ROM.
EDIT2: After holding volume up + power it shut down and then rebooted
I swear, troubleshooting a phone was never this hard/confusing on my HTC/Samsung phones :V but I'm glad it's not a paperweight

I agree that it's very confusing first, but that's mainly because there are so many old, confusing, wrong or incorrect guides. Once you understood how things work in general you start to like it. After getting used to it, I actually feel more comfortable than with my old devices.

Rzarector said:
Thanks a lot for the guide, the stupid thing I did was holding the power button and volume down cause it used to be like that with my previous phones. It seems to be flashing now, so hopefully all is well!
EDIT:Flashing ended succesfully but upon booting the phone the only thing I get is a flashing red led, so I'm assuming it's a hardware defect or I did something terribly wrong while flashing a custom ROM.
EDIT2: After holding volume up + power it shut down and then rebooted
I swear, troubleshooting a phone was never this hard/confusing on my HTC/Samsung phones :V but I'm glad it's not a paperweight
Click to expand...
Click to collapse
If you can get in flashmode and also successfully flashed .ftf but still a no go then you should send it back to Sony.

It's working fine, it just seemed like the phone was still on after flashing. I turned it off by holding power and volume up, and it works fine now.

NOOB: hard bricked op3, volume up button hasn't been working

First off, I did do a search, but as far as I can tell no one has had this problem so far.
This is all after modding using a tool kit: (i can't include the url but it is the toolkit by neisor on the oneplus forums)
tldr: phone stuck in bootloop, computer wont recognize the phone, maybe because it keeps shutting off and then booting to the 1+ logo, then shutting off again, would drivers help? what can I do about the volume up button?
So for a while my volume up button hasn't been working, and the mega unbrick post shows that I need to hold the volume up button for at least 25 seconds and while holding, plug my phone in. I have also seen some posts that say the volume up button could be a software issue, and the button itself could be working, and it is just not registering, as well as someone saying that you could take the back off and manually press the button, instead of using the bar on the outside of the phone (would this work?). I have gotten the button to work in the past by pressing the volume up button to the side instead of straight in, but I haven't been able to get it to work since my phone got bricked.
Another issue: my phone is stuck in a boot loop, I can't access fastboot, and I'm unsure of recovery because my volume up button is not working. would it be worth it to deal with the constant vibrating to try to get it to recovery?
I have been able to shut the phone off by holding the power button for something like a minute and a half, though.
This is my first post, and if I have broken any rules I am very sorry, but I need help and am tired of not having a phone.
Thank you everyone,
Mark
Edit: this is what I did to root the phone:
1. download the toolkit
2. unlock bootloader (when fastbooting the phone said unlocked at the bottom, and a message about not being secure showed every time I rebooted the phone)
3. flashed twrp (no issues, still booted, recovery went to twrp. for some reason I had to flash multiple times as every now and then recovery would revert to stock op, although I did make a backup through twrp)
4. send supersu zip file to phone, install using twrp (phone would not boot, op logo stayed on phone for 2 hrs + until I rebooted to fastboot and tried to reinstall the backup I made, still nothing)
5. Try magisk (still stuck on op logo)
6. try to go back to stock, accidentally lock bootloader (now the phone is stuck in bootloop, don't know what to do from here as I cant get to fastboot and am unsure of recovery's accessibility.)

If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down

This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!

Thanks
150208 said:
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
Click to expand...
Click to collapse
thanks for the correction, I will keep trying the volume buttons, if it doesn't work by the end of today I will search for a new volume button.
Thanks again,
mark

Ouch
badabdba said:
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Click to expand...
Click to collapse
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark

MarkTheFur said:
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
Click to expand...
Click to collapse
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.

MarkTheFur said:
... what can I do about the volume up button?
Click to expand...
Click to collapse
Can you boot into recovery by pressing power+volume down buttons?

Update: Got phone to show on computer as qualcomm under coms and ports
So last night I went ahead and held volume up for about 20 seconds, then plugged the phone in, keeping the volume up button pressed the entire time. my phone stopped bootlooping and showed up as a qualcom device! So I have downloaded the new driver the stock os, and am going to proceed to try to unbrick my phone.
Wish me luck,
Mark

Yes, I did, and its working so far
tnsmani said:
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
Click to expand...
Click to collapse
I still need to turn off the signed drivers features ( a huge bi*ch, I have to use another computer to contact microsoft or something to get my computer to load when I turn off safe boot or whatever its called), but once I do that I can install the driver and attempt to reinstall the stock os. Hopefully everything will go well.
Thank you,
Mark

Not as far as I know
rk2612 said:
Can you boot into recovery by pressing power+volume down buttons?
Click to expand...
Click to collapse
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark

MarkTheFur said:
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
Click to expand...
Click to collapse
Glad to hear that there is some progress. Best of luck and keep us informed.

Question Pixel 6 Pro won't boot / Pixel Rom recovery

Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!

Hi,
If you cannot turn on your phone, it'll be difficult to help you. Pressing other 30 sec power button doesn't run ?
In parallel did you contact the Google pixel support ?
It's not to scare you, but I had the same issue on a old Samsung S8 and it was the motherboard 🫤
Hope it's not the case for you !!

Fadey_Fadington said:
Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!
Click to expand...
Click to collapse
So this is in fact just an undocumented Emergency Download Mode that Google Custom Exynos SoC has natively built into it in case of the rare event of a bad boot loader.
I’ve been doing an extreme amount of research lately about bootROM’s, how they communicate, the Driver rule support for interfacing with the phone while it’s Pixel ROM Recovery. The viewable name for the Exynos USB DownLoading mode.
Can I get you to dm me on Telegram? It might be helpful to have more people. I’ll be glad to help in getting this figured out. It could help a lot of other people who don’t have a Pixel 6 too

I have the same issue after trying to update to 1205. I see the Pixel ROM Recovery and a COM port.

If you cannot enter fastboot mode, no way to recover your phone.

Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.

redplayer5 said:
Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.
Click to expand...
Click to collapse
if u can boot into fastboot just flash the latest factory image from google

w_tapper said:
if u can boot into fastboot just flash the latest factory image from google
Click to expand...
Click to collapse
Can I do that even though my device is locked?
Is there a tutorial?

redplayer5 said:
Can I do that even though my device is locked?
Is there a tutorial?
Click to expand...
Click to collapse
nvm i dont think u can do it if bootloader is locked