So I have OnePlus One screen problems. First I dropped it and the screen cracked, so I had it replaced. After it got replaced I now have it back, but before screen worked and touch didn't, and now touch works and screen doesn't. The screen doesn't turn on at all, but when it is plugged in I know it is turned on and I can browse through the filesystem of the OnePlus One via my computer and also when I swipe I can hear the unlocking sound. However, data, WiFi and ADB is disabled so I can't get into there. However, saying Ok Google I can hear the response it gives me so I tried calling a friend but the call never went through. It's running CyanogenMod 12S with TWRP and Xposed flashed if that helps any. I did try following the guide using ColorOS to restore it as if it's hard bricked, but since it never seems to boot into fastboot (spamming fastboot devices in cmd never shows anything) I can't seem to do anything. I tried this on both of my computers running Windows 7, and it never shows up in fastboot, so I don't know which COM port it is to finish the guide, because it wouldn't show up abnormally. Can anyone help me figure out how to get the phone into fastboot? Thank you all so much! Also I don't really have any pictures or videos because I don't have another phone/camera to take them with. Sorry!
Update: I was able to get it into fastboot by getting it into recovery and then typing adb reboot bootloader, but that's about the extent of it. I have Bacon Root Toolkit and stuff and I'm willing to wipe my phone (because there isn't anything that I don't have a backup of) but all I really want is a solution to fix it. It did show up a few times as QHSUSB_BULK (twice, actually) but it also seems to be working, because if I take a screenshot, then reboot to recovery, I can pull the screenshot from the memory to my computer. For some reason the phone isn't showing up at all except in fastboot and recovery now.
I had the same issue with my OPO on Exodus, what I did was I pressed the power button to open the screen then unlocked the screen like usual and then brought the notification bar down and change the brightness by pressing on auto brightness button multiple times and in this whole process my screen was black then I successfully turned on my phone's screen. It also work if you just reboot the phone.
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
Also this issue was in the ROM itself and it was fixed in an update.
Related
Hi,
Problem: my desire s is not Booting up!! {not even in recovery mode} it is S-off and rooted
Symptoms: if i try to boot up it just vibrates for 2-3 times and the Red Charge indicator light, turns on. if i try to hold down the volume key & press the on key then it vibrates for 2-3 times & the Green indicator light turn on. That's it!! it is stuck there... doesn't boot up or anything.
What might have happened last night!!:
1. i downloaded some games apk from different websites and installed those.
2. tried to update ROM manager but failed
3. suddenly the volume increase indication came up in my screen (without even touching the volume keys!!) this kept coming...then i decided to give it a restart...after restarting everything came back to normal
4. but again it started to show up this morning...so decided to restart it again...and thats it....it wont boot up again!!!
Guys please DO help me out!!
Thanx in advance
Hello
Attempt to put charge into the phone by plugging it into the main charger.
Does the charge light come on when the phone is being charged?
Now download and Install the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on you PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb devices[/COLOR][/B]
?
whats the response?
thanx for the reply bro...
if i enter "adb devices" it shows:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
list of devices attached
C:\android-win-tools>
Now what shall i do???...please help me out...i m very novice in this matter <to be mentioned that... i had a given factory reset before this!!>
After startup and the two vibrates, what's on the screen?
were you forced to pull the battery at any point?
Sent from my HTC Desire S using xda premium
after the vibration the screen doesn't show anything!! its just pitch dark...
yeah last night i had to pull the battery out as the Red light wont turn off!!
this isnt sounding good!
check out the link in bens signature regarding emmc chips...
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
shariaphobia said:
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
Click to expand...
Click to collapse
Very strange indeed, can you recall any part of the warnings?
Unless the phone semi-boots or can at least be recognised by adb (which yours doesn't) then you can use the HTC ROM utility to re-flash your phone)
Does sounds frightening like a hardware related issue, although it's difficult to tell as it appears to intermittently boot!?
The good thing is if it won't boot then hopefully the service centre won't be able to tell that you S-off'd so may well replace unit or motherboard for you under warranty.
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
shariaphobia said:
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
Click to expand...
Click to collapse
Yes that's good news.....Although I'm at work now so bit busy...
Try
Code:
adb reboot recovery
from the PC if it loads into recovery Good!
From recovery try to format the CACHE partition, write what happens?
I'd then say download a wipe script and a safe custom ROM and then load them onto your SD card, ie like LBC Mod v0.6.0
If no errors, then first flash the wipe ZIP file and then the LBC ROM ZIP file using the "install from sdcard/zip file options from your recovery....
Report back any errors...if you're not quite sure of any of the steps then ask questions....I'll check back later...
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
shariaphobia said:
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
Click to expand...
Click to collapse
I'm getting out of my depth here....As we don't know what version of ROm you're now running especially if you ran the OTA. There is a possibility that the OTA has removed your custom recovery, S-OFF and root. As as you can't see the HBOOT screen you can't confirm that you're even still S-OFF..
You could try to start to run an RUU as this might tell you want you current ROM version is......
But I'd wait for someone else to provide some more advice...as I don't know what the "recovery" next to your device serial number from adb devices quite means ( I assume it means that your device is in recovery)...
---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------
google adb yourself and see what safe options and commands of it you can use that will provide you with further information about your phone
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
shariaphobia said:
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
Click to expand...
Click to collapse
Well done in discovering the fault
But, I'm afraid that I don't know of any way to disable the buttons, without obviously dis-mantling the case from the unit (which is way over my head) ...
this maybe a daft question but have you tried the command
Code:
adb reboot
(not adb reboot recovery)?
if this does not work you may have to take your device to HTC
Ok so here is the issue. My Nexus S i9020a has a power button that is no longer working. Whenever I put the battery in, it automatically boots up, to reboot I take the battery out and slide back in. I want to bring it back for warranty since my bro got the warranty until 2014 or so. I had previously had a couple of custom ROMs on it. I wanted to flash stock ROM and lock the bootloader.
When I boot into recovery (hold up while I put the battery in), I can't do anything. Even the volume up/down doesn't do anything, and of course pressing the power button doesn't select anything. So I got ROM Manager and found a copy of the stock rom. ROM Manager was supposed to install the rom from the .zip file, which it sort of did. It wiped everything and installed. I left it on while I went to do something. When I came back, the phone is stuck in the bootup animation.
If I was able to do anything in recovery I would just reflash a different ROM and go again.
I have watched some videos, and tried the Oneclick Unbrick, but doesn't work. I've read some other threads here that talked about getting Linux on a USB, or other mod. But I am trying not to go that route, as it seems pretty complicated.
When the phone is in the bootup animation and I connect it to the computer, I hear the sound that Win7 detects new hardware. If I am in the bootloader Win7 does not play any of that sounds.
I remember using adb and I still have the files on my computer from when I unlocked and rooted.
Not sure what should I do now?
also, all of my soft button lights are on during the boot animation. read in one of the threads that different lights on mean different modes. so not sure if this means anything.
hi, I am afraid the bad functioning of power button is responsible of all of these problems,
probably you can send it for warranty as is now
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
have you tried already the linux app UnBrickable Resurrector ?
maybe you would be able to install the stock rom via fastboot
Possible fix: Remove all drivers and reinstall via Nexus root toolkit. Go to adb and flash TWRP, or CWM Touch Recovery (make sure it's touch-enabled), then flash a new rom.
Permanent fix: As far as I can remember (I also had this issue about 6 months ago) samsung will still recognize the warranty even when your bootloader is unlocked, at least in my place. The issue you're returning with is a hardware issue, not a software issue. So tell them to just replace the power button and you'll do the rest. As long as the samsung warranty sticker on top of the screw is in-tact, you're good to go. Again, this is my experience in a samsung service center near my place. I don't know how they deal with things elsewhere.
if this can help, I read in forums that also in Italy samsung support fixes nexus s in warranty even with unlocked bootloader, this is not a direct experience though
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
eugene188 said:
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
Click to expand...
Click to collapse
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
ej8989 said:
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
Click to expand...
Click to collapse
I just tried the PDAnet, I choose the Samsung drivers, then once it pops up with the screen to ask me to connect the phone then I'm stuck. Whether I put the battery in and let it bootloop or hold vol+ and put the battery in, it doesn't get past the screen. Only thing I could do was "skip USB" which still installed PDAnet but possibly without USB support and just bluetooth support.
I even tried it on my brother's laptop which is still in a relatively clean OEM state but the got stuck at the same place.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
OK...so have had my phone for about a week and wanted to flash my system back to stock due to a few force closes I couldn't get rid of...
After fastboot flashing everything where it needed to be I fastboot boot'd twrp and wiped data and sdcard...clicked reboot and chose slot b to boot from (thought slot b was where I flashed system but it turns out that where I flashed system_other). Now my phone is stock on a black screen and nothing I do will change that! My computer makes a sound when its plugged and unplugged but I can't get the screen to do anything but stay black (no backlight)! Do I have to RMA this thing or is there something in haven't found in searching that I can do to fix this?
I have tried holding the power button till it hard reboots and when its plugged in to my computer, you can't hear the it reboots but back to the black screen when the computer makes the sound that its plugged in. (Just trying to make sure I have all info here so we can hopefully find a solution fast)
Has anyone had this issue and recovered from it?
I had a similar issue back when the HTC One first came out. I had TWRP installed but for some reason it wouldn't flash any ROMs or stock images. It especially sucked because there was no removable storage to ad any other files, ROMs, stock images, etc and I had inadvertently wiped the phone.
For one reason or another, TWRP itself was the issue, so I installed CWM recovery and was able to reflash everything without a problem. If possible, try and change your recovery and reflash
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
magnumtripod said:
I had a similar issue back when the HTC One first came out. I had TWRP installed but for some reason it wouldn't flash any ROMs or stock images. It especially sucked because there was no removable storage to ad any other files, ROMs, stock images, etc and I had inadvertently wiped the phone.
For one reason or another, TWRP itself was the issue, so I installed CWM recovery and was able to reflash everything without a problem. If possible, try and change your recovery and reflash
Click to expand...
Click to collapse
Actually I just re-read your post and my issue was not similar, but regardless, at the time, TWRP was giving me all kinds of problems. I'm not sure if theres another recovery out there yet, but try one if there is and see what happens
My pixel is on stock recovery and I can't even boot fastboot to get to recovery....screen just stays black...now that the battery finally died, I get a red led when I plug it in but when it tries to power up the led stops blinking red and it just stays at a black screen
Hi all,
I unlocked the bootloader with the tool provided by Asus, but when I want to flash TWRP to root it all I have is a black screen when I try to boot in recovery again and the phone vibrate when I touch the screen but impossible to see or flash something...
It seems that I am the only one having this issue, I don't know what to do.
I tried the latest version of TWRP and some of older versions (from shaka's, of course)
Can someone point me to somewhere with a start of solution... ? (Tried everything in ZF3U's XDA sub forums)
Thanks in advance guys
Hi! I have experienced this issue whilst trying to fix a problem with my firmware upgrade+root+recovery installation. In my case the display was extremely dimmed almost impossible to see twrp options. The way to resolve this problem is to flash the original stock recovery and then reflash the firmware of choice and clear dalvik/cache and you should be able to get it sorted. Once you have reflashed original firmware and reset the device with original recovery then you can reinstall twrp on the bootloader screen and using correct fastboot drivers installed beforehand once you have successfully been able to boot to the OS to home screen following successful initial setup of the device after firmware install. Hope this helps but compared to my issue yours is very minor as with my issue (desribed extensively in another thread) I have no in-call sound either way, fingerprint sensor not functional, device serial number does not show correctly under device/aboit settings. ASUS customer services was very unhelpful to say the least.
Hi it's me again
Thank you very much AWFRONT, I will try this when I'll be back at home.
I hope that you will find a solution to your problem very soon man.
If I see something I'll post it in your thread.
Thanks again !
AWFRONT said:
Hi! I have experienced this issue whilst trying to fix a problem with my firmware upgrade+root+recovery installation. In my case the display was extremely dimmed almost impossible to see twrp options. The way to resolve this problem is to flash the original stock recovery and then reflash the firmware of choice and clear dalvik/cache and you should be able to get it sorted. Once you have reflashed original firmware and reset the device with original recovery then you can reinstall twrp on the bootloader screen and using correct fastboot drivers installed beforehand once you have successfully been able to boot to the OS to home screen following successful initial setup of the device after firmware install. Hope this helps but compared to my issue yours is very minor as with my issue (desribed extensively in another thread) I have no in-call sound either way, fingerprint sensor not functional, device serial number does not show correctly under device/aboit settings. ASUS customer services was very unhelpful to say the least.
Click to expand...
Click to collapse
Hey Awfront. You wouldn't happen to know where I can find the stock recovery? I tried the one from Shaka's megadownload page but that didn't work. Unless I am doing something wrong it wasn't letting me boot into it.
I Have The Same Problem In MI A1
After {fastboot boot twrp.img)
All Screen Comes Dimmed
But I Cant REBOOT OR EVEN ACCESS FASTBOOT MOD
ONLY BLANK BLACK SCREEN
---------- Post added at 07:57 AM ---------- Previous post was at 07:54 AM ----------
AWFRONT said:
Hi! I have experienced this issue whilst trying to fix a problem with my firmware upgrade+root+recovery installation. In my case the display was extremely dimmed almost impossible to see twrp options. The way to resolve this problem is to flash the original stock recovery and then reflash the firmware of choice and clear dalvik/cache and you should be able to get it sorted. Once you have reflashed original firmware and reset the device with original recovery then you can reinstall twrp on the bootloader screen and using correct fastboot drivers installed beforehand once you have successfully been able to boot to the OS to home screen following successful initial setup of the device after firmware install. Hope this helps but compared to my issue yours is very minor as with my issue (desribed extensively in another thread) I have no in-call sound either way, fingerprint sensor not functional, device serial number does not show correctly under device/aboit settings. ASUS customer services was very unhelpful to say the least.
Click to expand...
Click to collapse
I Have The Same Problem In MI A1
After {fastboot boot twrp.img)
All Screen Comes Dimmed
But I Cant REBOOT OR EVEN ACCESS FASTBOOT MOD
ONLY BLANK BLACK SCREEN
AWFRONT said:
Hi! I have experienced this issue whilst trying to fix a problem with my firmware upgrade+root+recovery installation. In my case the display was extremely dimmed almost impossible to see twrp options. The way to resolve this problem is to flash the original stock recovery and then reflash the firmware of choice and clear dalvik/cache and you should be able to get it sorted. Once you have reflashed original firmware and reset the device with original recovery then you can reinstall twrp on the bootloader screen and using correct fastboot drivers installed beforehand once you have successfully been able to boot to the OS to home screen following successful initial setup of the device after firmware install. Hope this helps but compared to my issue yours is very minor as with my issue (desribed extensively in another thread) I have no in-call sound either way, fingerprint sensor not functional, device serial number does not show correctly under device/aboit settings. ASUS customer services was very unhelpful to say the least.
Click to expand...
Click to collapse
Thank you very much, Awfront!
You saved me!
T.edward said:
I Have The Same Problem In MI A1
After {fastboot boot twrp.img)
All Screen Comes Dimmed
But I Cant REBOOT OR EVEN ACCESS FASTBOOT MOD
ONLY BLANK BLACK SCREEN
---------- Post added at 07:57 AM ---------- Previous post was at 07:54 AM ----------
I Have The Same Problem In MI A1
After {fastboot boot twrp.img)
All Screen Comes Dimmed
But I Cant REBOOT OR EVEN ACCESS FASTBOOT MOD
ONLY BLANK BLACK SCREEN
Click to expand...
Click to collapse
Me tooo