I followed this guide in order to root my brand new p8lite.
The thing is that now I have a black screen. If I plug my phone via usb, adb shows me that the device is in recovery.
By adb shows me that the device is in recovery I mean this:
Code:
# adb devices
List of devices attached
W3D7N16712000718 recovery
What I did:
Checked the model. It's an ALE-L21
Chapter 1: not a windows user, but managed to get adb up and running on my linux machine.
Chapter 2: everything went fine, bootloader unlocked
Chapter 3: my phone booted up just fine
Chapter 4: skipped it, as my phone was booting fine into system
Chapter 5:
So you want to convert to a single/dual sim?
Click to expand...
Click to collapse
My answer: "no thanks", so I skipped it
Chapter 6: I did the upgrade through OTA BEFORE reading the guide. Double checked I was running 6.0, so I skipped it
Chapter 7: Downloaded the file, flashed trought fastboot. And now I'm here.
I think I may have ****ed up things in the last 3 chapters.
What I tried to fix this:
Code:
# adb reboot bootloader
phone rebooted then huawei logo then blackscreen. adb still shows it's in recovery
After searching in the forum, I came by
Code:
adb reboot-bootloader
(notice the hypen). Firing that command put my phone into fastboot. Couldn't believe it, but I took the chance to flash the files found in chapter 4 (bootloader, recovery, cust and system, in this order). No luck, still reboot, logo, black screen
Now, no matter the presence of the hypen in the command, my phone keeps going into recovery (after the usual reboot, logo, black screen)
Tried to hold down POWER to shut it down. After a while it reboots, logo and black screen again. Laptop keeps saying device is into recovery
Tried to download the official 6.0 update, put on a sd card (dload/UPDATE.APP), held down POWER+VOLUP+VOLDOWN. Again, reboot, logo, black screen. recovery mode, again.
Frustrated, I unplugged the phone. After a while, it rebooted, logo and blackscreen without me touching it. Weird. It did it again a couple of times, but now it has stopped (with a black screen and, if plugged in, adb. says is into recovery)
I really don't know what to do, please help me.
UPDATE:
After leaving a night on its own, the phone was noticeably hot.
Also, when unplugged, if I hold POWER it shows me the logo a couple of time before going black screen.
Ok. But can you enter in recovery?
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
tamaskurti said:
Ok. But can you enter in recovery?
Click to expand...
Click to collapse
Apparently yes (or at least, adb says I'm into recovery). However, I just get a black screen.
Tapping randomly on the screen doesn't give any kind of feedback (no vibration, no beeps, nothing).
tamaskurti said:
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
Click to expand...
Click to collapse
Since I started having those problems after I flashed TWRP, I thought it was a better idea to flash stock recovery (alongside bootloader, cust and system) and restart from there.
I have the same issue...
Have you solved the issue? In case you solved, how?
mmennella said:
I have the same issue...
Have you solved the issue? In case you solved, how?
Click to expand...
Click to collapse
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Mmmmmm... I go to buy new One. Huawei must have a way to reflash, but i can't wait. Thanks a lot
Inviato dal mio Redmi 3 utilizzando Tapatalk
S1cK94 said:
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Click to expand...
Click to collapse
i brought it to my local repairshop and they sent my phone to manufacters central repair and they fixed it for free.
AfrikanDionysus Solution
Huawei P8 lites are region specific like Middle east asia america etc so before you go in make sure you know your build number in my case ALE-L21C185B560 its the UAE variant now if you've messed go to the huawei website download the rom specific to your region any other region won't work!!! get a clean sd card extract the file and copy it to the root of the sd card its normally an update.app inside a folder named dload shutdown the phone now press vol+ and vol - and the power button till it starts installing.. If you've messed up your recovery and can get to fastboot by plugging in the phone then pressing vol down and power.. use the Huawei extractor tool and extract the recovery from the just downloaded rom and flash it.. then retry the restore as stated.. im sure you can google all the tools you need to get so im not putting any links !!! Ahsante !:good::good::good:
Related
my problem is kind of abnormal. i couldnt find solution anywhere so i came here. my device was zenfone 5(t00f)/lollipop.
so i wanted to root my phone. i followed this guide >>
HTML:
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
the tool i used is called ZenfoneToolkit_20160719, downloaded from here
HTML:
https://drive.google.com/drive/folders/0B0AFmAAcGS5xbWpTQzBQVTN3b1k
. its a bundle of .exe, .dll, .img, .bin files. but no need to work on them seperately, there is a simple cli tool from which you can choose what you want to do and it executes that file for you. below is the list what you can do.
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash Boretz Kernel Lollipop
so wiped cache[1] first then i tried to root[7]. sadly it didnt work, when i turned the phone on it took me to fastboot screen, there i had only a few options like, normal boot(doesnt happen), recovery mode, restart. when i turned it off and pressed power and volume up together it would go to recovery where none of the options works. i though that was what called brick, so followed this guide to make my life better
HTML:
http://zenfone-blog.blogspot.com/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
.
my phone by default came with kitkat. so when i downloaded the firmware i wanted to get a kitkat. but i couldnt find a matching recovery img and firmware for kitkat on asus official page. so i downloaded jellybean. ASUS ZenFone 5(T00F/T00J) software Image: V1.18.40.9 ww for firmware from here
HTML:
https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
. and recovery img is 1.18.40.9_ww_recovery.img from here
HTML:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
. i dont know what "ww" means in those name but i saw it in my software version before so i went with it.
All the steps went smoothly, by the end of it i guessed my phone charge would be low so i put it in charge and turned it on. first time it turn on without a problem. i checked out a few things and leave it for charge. after a while i came back and battery was 0%. i thought i would be wise to plug out and in charging port again. as soon as i pull out the pin, screen instantly turned black and the phone went dead after a looooong ass vibration.
now when i try to charge the orenge light at top lights up but the animation that shows battery always show its empty. if i try to turn it on while plugged, it shows asus logo/intel logo and goes dead again. if i try to turn it on without being plugged, it shows a battery logo with a question mark, which i think means the phone cannot find battery.
i am stuck here.... plz someone be my savior.
Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!
matheusgcdj said:
Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!
Click to expand...
Click to collapse
i tried. but just cannot get to the fastboot screen. :'(
nooblett said:
i tried. but just cannot get to the fastboot screen. :'(
Click to expand...
Click to collapse
use this thread and perhaps there is hope
matheusgcdj said:
use this thread and perhaps there is hope
Click to expand...
Click to collapse
thnx. i am gonna try it now.
@matheusgcdj: yes it worked
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
Click to expand...
Click to collapse
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
tabletalker7 said:
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
Click to expand...
Click to collapse
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
xDaDeevellopar said:
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
Click to expand...
Click to collapse
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
tabletalker7 said:
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
Click to expand...
Click to collapse
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
xDaDeevellopar said:
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
Click to expand...
Click to collapse
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
tabletalker7 said:
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
Click to expand...
Click to collapse
What does it mean by "navigate to your adb location."?
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
xDaDeevellopar said:
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
Click to expand...
Click to collapse
Do yourself a huge favor - there is a giant box in the top left of the screen as you read this. It is called a search bar. Everything (and I mean EVERY SINGLE THING) you have asked about thus far has been gone over to COMPLETE EXHAUSTION many times over. I am trying to be nice and help you through this whole process but wow, come on already. http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544 read this post from front to back, then back to front, and then if you still have questions the people over there odds are have your solution
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
Click to expand...
Click to collapse
hey, could u please tell me how u managed to boot up ur device again... i've also bricked my a2017g to a point where i can't even boot into edl mode...
i submitted this post - https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990#post70561874
The reason I'm making this thread is because I was trying to root my Honor 8 and things just didn't work out in TWRP. Rebooted my phone and I realized I had bricked it since it would not boot after 10 minutes. Solutions seem to be scattered throughout different threads so here's guide for when you're stuck in a boot loop or you bricked your Honor 8.
What you'll need:
1. The firmware currently you are on. @Coolyou posted a guide for a firmware finder. Here is the post.
2. SD Card
What to do:
Step 1.
Download the correct firmware. It will be a .zip file.
Step 2.
Create a folder called dload in the root of your SD card, not your internal storage. Copy the .zip file the folder and unzip it or unzip it else where and copy the content into the dload folder
Step 3.
Power off Honor 8 (if possible, sometimes it'll auto boot up when forced shutdown)
Step 4.
Make sure your device is not plugged into a computer as it will load into something else.
Hold Vol+ & Vol- & Power. It will being to install the firmware from the dload folder if done correctly. If it instantly fails that means you downloaded the incorrect firmware the device is already one.
You're done! However, if your device does not go past the startup logo within 3 minutes proceed to step 5.
Step 5 is probably necessary as everytime I've bricked my device, I've had to do the next step.
Step 5.
Power off. Hold power and Vol+. Once in Recovery mode (not eRecovery), clear cache and format your device. Once done, reboot.
Ta-da, you're device is now back to normal.
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Let go off the power button after the first vibration. Also make sure your phone is not plugged to a pc. With pc connected it boots into eRecovery instead of recovery. Good luck!
Edit:Also the guide does not make it 100% specific but the dload folder on the sd card needs to have the update.app file right inside it. If the structure is sd\dload\folder\update.app it also won't work.
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
i have same problem, you can fix this? help me please
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
thekubiaks said:
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
Click to expand...
Click to collapse
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Hi, my device is still not booting up after installing the matching dload firmware on my device from the honor 8 website (FRD-L09).
Is there still anything I can do to maybe get this fixed?
I created a nandroid backup of all partitions that I were able to back up, but even rolling back all partitions did not make it boot again.
Sadly, I am not able to get the device into e.g. fastboot mode anymore because it is not booting anymore and therefore cant get an adb shell on it.
I can still enter recovery mode, but when trying to boot it just stays at the blue screen with the white "honor" text after the short boot animation with the 3d text
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Lorog said:
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Click to expand...
Click to collapse
Same here on a Note 8 did you find a solution?
thekubiaks said:
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Click to expand...
Click to collapse
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
nickp22127 said:
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
Click to expand...
Click to collapse
Its erecovery
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...can u tell how did u managed to solve it???
oops, wrong thread
abbassbhai said:
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
i have the same pblm...can u tell how did u managed to solve it???
Click to expand...
Click to collapse
Do you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Did you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi, I have the exact same problem. Have you managed to fix it?
Same problems as other people above, couldn't load any recovery. Anyone can help us out?
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi even I have the same problem with Honor 8 Pro.. Did you get any solution??
Hi even I have the same problem with Honor 8 Did you get any solution??
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
Press vol+ vol- + power at the same time until phone vibrates
Sent from Mi A1 with Tapatalk Pro
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I also had this issue I think it is because of any xposed modules or magisk modules.
When I flashed xposed uninstaller, the phone revived
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I have the same problem, my Mi A1 dont boot and i cant open fastboot mode (and screen dont turn on when charging), how you solved it?
Stuck on black screen
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
ideepeshtiwari said:
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
Click to expand...
Click to collapse
im also having the same issue. while flashing aex v6.2 on my mi a1
help me out from the same problem
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
khadar709 said:
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
Click to expand...
Click to collapse
Flash the previous rom and everything will be back to normal.
Shilldas said:
Flash the previous rom and everything will be back to normal.
Click to expand...
Click to collapse
I am not able to do that I can't go to twrp mode here also same black black screen.I can go to fastboot mode but I am not enabled usb debugging mode and system is not recognising mobile.
Help me how can I solve this..
Thanks in advance. ?
Install 'scrcpy' in your PC. Try to flash twrp from PC using fastboot and adb method. (I hope fastboot shows up on your phone) if u can boot to twrp via PC then go ahead and install any other rom. If u can't then connect your phone to PC and open scrcpy.exe here you can control your screen. (Most custom roms come with usb debugging enabled, if not try " AEX V.6.1 rom)
Usb debugging is compulsory. Thanks a lot for the information I will try this.
So i had this exact same issue. It was booting to twrp but screen was just blank.
i was trying to root the devive so i flashed the zip file by following command through adb
adb shell twrp install /sdcard/Magisk-v23.0.zip
it flashed the magisk and it was done. Similarly you can flash any zip file. If zip file is not copied to internal memory you can copy it using following command
adb push Magisk-v23.0.zip /sdcard/
I hope it helps someone in need.
Thanks.
Hi similar problem. Phone was locked in bootloop. I use reset pin and flash latest fw, flash successful in 220sec. Then screen stays black. Holding any combination will power up phone with black screen... wonder if it burn resistor or it is a flash issue. Trying to reflash again, however it stays 1000sec and still flashing.
Hi have mine FIXED.
Tried again to flash with android 9. Not able to finish flash in 4hrs. Then disconnect. Screen show battery 100%, then again only black screen but powered. Also 3 buttons are lighting. So I start pushing them and the screen, got some feedback and sound from touching the screen. Then the phone restart, screen ON. Show the normal white screen and ENCRYPTING storage screen that should come after flash. Then again reboot itself and start installing android (just taking a lot of time). Now all work on android 9, not giving option for OEM update to android 10, however afraid to flash again... good enough for my son (either way will break it in an year).
p.s
Im Samsung S class user for 10 years, so it is quite unfriendly phone... (need debugging on to connect to PC, for file transfer )
At last I found a way to run TWRP on tissot correctly without black screen.
Just install oreo 3.2.1-2 on Mi A1 (tissot).
This file (recovery-3.2.1-2-oreo.img) is working well.
Download it from this site:
https://androidfilehost.com/?fid=818070582850498337
Reference:
https://forum.xda-developers.com/t/...2-1-2-oreo-touch-recovery-2018-03-06.3688472/
Download Android 13.00 unofficial ROM for Mi A1 and install it easily by TWRP oreo 3.2.1-2:
https://sourceforge.net/projects/lafactorial-tissot/files/
Good luck,
Sed
Releases ยท zignas/twrp_device_xiaomi_tissot_treble
android 9.0 Device tree for TWRP 3.5.2 with Tissot manager - zignas/twrp_device_xiaomi_tissot_treble
github.com
also working fiine