Related
Phone is going full retard now
I have been using CyanogenMod 10.1 nightly 'till now.
I fell down one day and since then it's stuck on the CyanogenMod boot logo. forever.
Recovery is accessible, and I've tried flashing the rom again but I can't get past the point when I should type in adb "fastboot flash boot boot.img"
It's just "<waiting for device>"
and nothing's happening.
even though the device appears on the adb devices list.
I also can't mount storage through recovery.
What the **** is happening to my phone and what can I do to fix it?
Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?
Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta
bananagranola said:
Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?
Click to expand...
Click to collapse
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
humzaahmed155 said:
Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Wait, adb and fastboot are not them same...
humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4
YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Have you tried re installing the drivers with the phone unplugged? if you are using windows OS. Try using a different USB port, plugged directly to the motherboard. Do not use a usb hub
humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
humzaahmed155 said:
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
YagFrazier said:
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Hmm that wifi issue seems interesting, glad i could help
YagFrazier said:
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:
ammo12 said:
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:
Click to expand...
Click to collapse
Get yourself a CodefireXperiment rom. Together with Nova launcher it's the same as CyanogenMod and even better.
Wifi's good.
I usually stay away from Android Revolution, I developed sincere hate for Sense 3.6 and below.
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
myhtconeV said:
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
Click to expand...
Click to collapse
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
red de0392 said:
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
Click to expand...
Click to collapse
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
myhtconeV said:
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
Click to expand...
Click to collapse
Hahahah...That's a Beast
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Recently I have seen one interesting issue that might appear like solution to your problem. According to the description you may try turning off your phone and plugging in a charger. If you will have the same behaviour your phone should start into recovery mode. =)
Edited: Doh! TWRP...
You may try All-In-One-Kit as well. It has high level interface to run adb commands (including Boot into Recovery). Yeah yeah, I've seen your note that adb does not recognize your device, anyway...
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes.
I have given it for repairs.I have decided not to sell or dispose it.
Its only sometime before I buy a moto g or xperia device. Waiting for my new credit card :fingers-crossed:
which phone would you suggest?
Vickrant.
If you are good with 16gb storage better buy Moto G if not there are a few options like Xperia M , Canvas series and all..
Sorry to be so late to the party, but in case other people get this issue. ADB will often work just after the kernel finishes loading, before it gets shut off. So between the htc boot screen and when the boot anim starts you have a window to commit abd commands. I often use this to save time when flashing kernels etc, notably because my WIP roms rarely make it past bootanim!
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
You sure about this?i am stuck there and i have cwm recovery installed,will it switch itself straight to recovery after the battery is dried up?i am using sony xperia c
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
souvenir1977 said:
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
Click to expand...
Click to collapse
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Still_living714 said:
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Click to expand...
Click to collapse
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
souvenir1977 said:
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
Click to expand...
Click to collapse
have you tried putting it into download mode?
Still_living714 said:
have you tried putting it into download mode?
Click to expand...
Click to collapse
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
hmm very weird. I had a similar problem were the phone wouldn't boot unless I had it plugged into the charger or my computer,give that a try.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
when I had that problem I figured out that it was the battery that was making the phone act weird. Since LG sent me another battery when they had the promotion I used the other spare and that fixed it for me.
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
souvenir1977 said:
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
Click to expand...
Click to collapse
well it's hard to say but without the phone being able to boot there's not anything you can do.....
you are right, flashing need the download mode....
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
jkjambo said:
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
Click to expand...
Click to collapse
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
souvenir1977 said:
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
Click to expand...
Click to collapse
that's what i mean , lge serial xxx , don't remeber exactly . it's in qhsusb mode , hardbricked ...
there is some indian guys who do that , some for free, some for little amount of money ...
search for lg g3 unbrick Qhsusb 9008... don't waste time on tutorials , non of them works with D851 ... i'm in same boat (again ) and tried everything .. nothing works , unless you're connected to lg servers directly , search for people which fixs them
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
jkjambo said:
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Click to expand...
Click to collapse
souvenir1977 said:
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
Click to expand...
Click to collapse
This is why You don't flash the boot chain unless you absolutely must. I was running 20B with the old boot chain (other than rpm, that was updated) and it ran just fine. If you get a bad flash on the boot chain your sol.
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
Try hold power and volume down for like 30 seconds ,to try to get into bootloader
cwalker0906 said:
Try hold power and volume down for like 30 seconds ,to try to get into bootloader
Click to expand...
Click to collapse
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader
cwalker0906 said:
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader
Click to expand...
Click to collapse
i tried while pluged, how else would i recognize the sounds in windows. Hmm i really dont know if the pixel is on or off, so this could take weeks... is it hard to open it and unplug battery ?
Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...
molletit said:
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...
Click to expand...
Click to collapse
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
tried it, doesent make any difference, screen is still black, no flicker, nothing.
molletit said:
tried it, doesent make any difference, screen is still black, no flicker, nothing.
Click to expand...
Click to collapse
You might have to wait until the battery runs out to see if when it's plugged in to charge to see if anything happens!
I've never had an issue with a force reboot unless it's just a screen issue, which could be addressed with Google or whom you got it from
Sent from my Google Pixel XL using XDA Labs
Try it on a different PC. Worked for me, when I bricked my Nexus 6, the same Way you did. Hope it works.
If you tried to boot slot b without first flashing a bootloader to slot b then you're screwed. That's a legit brick.
molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.
then iam screwd, normally fastboot should install it on both slots, or iam wrong ?
its a hard brick, not softbrick because i cant load bootloader
the_rooter said:
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.
Click to expand...
Click to collapse
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
molletit said:
then iam screwd, normally fastboot should install it on both slots, or iam wrong ?
Click to expand...
Click to collapse
you would have had to flash Imgs to your non active slot and you didn't do that correct?
molletit said:
its a hard brick, not softbrick because i cant load bootloader
Click to expand...
Click to collapse
yeah it's a hard brick I know someone personally that did the same thing you did.
Tigerstown said:
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
you would have had to flash Imgs to your non active slot and you didn't do that correct?
yeah it's a hard brick I know someone personally that did the same thing you did.
Click to expand...
Click to collapse
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
I never heard of a soft brick being unfixable in my life period. I need to google it lol that's funny. Soft bricks are easy fixes. Why don't you fix it for him?
the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
Maybe you should read more carefully. Hes not getting sounds from the phone itself. The computer makes a sound when he plugs it in cuz it recognizes a USB charging device. The phone can still recieve power from the computer regardless of the bootloader. However because he has no bootloader on his active slot he's toast.
molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
It sounds like you may be booting into a low level Qualcomm boot mode. It is possible to recover with Qualcomm tools, but you would almost certianly need Google's specially signed versions.