hey can anyone help why would this p6 boot loop?
https://imgur.com/a/hBw3Flk
i tried wiping the phone in recovery its gives me bunch of errors
https://imgur.com/a/XPFctCo
any idea how i can repair this?
I see install from adb completed, what were applying from adb and the other pic shows your bootloader is locked.
alvin14 said:
I see install from adb completed, what were applying from adb and the other pic shows your bootloader is locked.
Click to expand...
Click to collapse
? yes it has locked boot loader i tried wipe from recovery to fix it bootlooping when its gives me errors any idea how to get it to boot>
yzydog said:
yzydog said:
? yes it has locked boot loader i tried wipe from recovery to fix it bootlooping when its gives me errors any idea how to get it to boot>
Click to expand...
Click to collapse
Applying back stock rom via fastboot should fix however you have not answered what you were applying via adb sideload so we can figure why you are in a bootloop in the first place.
Click to expand...
Click to collapse
I got it like this second hand as it's video . So what commands and files do I need? ( sorry was a bit confused about your first reply )
Follow the instructions here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just sideload the ota but don't try to downgrade. You don't need an unlocked bootloader to adb sideload
fil3s said:
Just sideload the ota but don't try to downgrade. You don't need an unlocked bootloader to adb sideload
Click to expand...
Click to collapse
thx i will try hope that fixes it
yzydog said:
thx i will try hope that fixes it
Click to expand...
Click to collapse
Any luck?
Related
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Tried looking through threads and have spent all day trying to fix it.
Phone was working fine a couple days ago until it ran out of battery. Since then nothing.
If I try to turn on normally I get stuck on the Google screen. Only other thing I can do is boot into fastboot/bootloader but from there, if I try Recovery mode it sticks in a bootloop
I think you have a hardbrick bootloop, There is fortunately a kernel and recovery developed by developers to overcome this problem, but you'll need a unlocked bootloader as it involves flashing recovery and boot.img. If you have boot loader unlocked, go to general section where you'll find a thread regarding the same. All the best
I tried that - flashed the recovery but when I try to launch recovery mode I just get a bootloop again.
Euskadi said:
I tried that - flashed the recovery but when I try to launch recovery mode I just get a bootloop again.
Click to expand...
Click to collapse
What recovery are you flashing?
Phalanx7621 said:
What recovery are you flashing?
Click to expand...
Click to collapse
This one:
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
Click to expand...
Click to collapse
Euskadi said:
This one:
Click to expand...
Click to collapse
Are you sure it's flashing ? And you do have an unlocked bootloader right ? And you're flashing with fastboot?
Phalanx7621 said:
Are you sure it's flashing ?
Click to expand...
Click to collapse
Fastboot command line says it is
And you do have an unlocked bootloader right ?
Click to expand...
Click to collapse
Of course
And you're flashing with fastboot?
Click to expand...
Click to collapse
Yep, didnt even know there was another way tbh!
Euskadi said:
Fastboot command line says it is
Of course
Yep, didnt even know there was another way tbh!
Click to expand...
Click to collapse
Oh I don't know if there is, I know there are programs out there that make the process easier just figured I'd ask if you were doing it the way I normally do it. Still having this issue?
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
vibraniumdroid said:
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
Click to expand...
Click to collapse
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
ROM_HUNTER said:
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
Click to expand...
Click to collapse
does not work
vibraniumdroid said:
does not work
Click to expand...
Click to collapse
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
flashallthetime said:
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
Click to expand...
Click to collapse
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
vibraniumdroid said:
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
Click to expand...
Click to collapse
Hard bricked for sure
flashallthetime said:
Hard bricked for sure
Click to expand...
Click to collapse
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
vibraniumdroid said:
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
Click to expand...
Click to collapse
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
so you are sure that it is impossible to make a flashable zip of bootloader. Maybe it is just my computer I'll try booting of linux on usb and then see if fastboot can see it.
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
how do you fix a hardbrick?
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
flashallthetime said:
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Have you tried using these albus (Z2 Play) blank flashes as mentioned here to repair your bootloader? https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181
https://forum.xda-developers.com/showpost.php?p=73411048&postcount=206
These may hopefully get your device to the point where it's recognised in fastboot and you can then flash the stock ROM via fastboot.
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
You don't. That's why it's called a hard brick.
flashallthetime said:
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
Click to expand...
Click to collapse
booted of linux from a usb and that worked thanks
I've unlocked my bootloader but now each time i try to use the bootloader it won't do anything !! it keeps showing me FAILED (remote: unknown command) ! does anyone facing the same problem ? because i cannot even stock flash my phone !
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Dielahn said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Click to expand...
Click to collapse
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Did you unlock critical?
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
murphyjasonc said:
Did you unlock critical?
Click to expand...
Click to collapse
No and everytime i try to do that it keeps telling me the same error
Dielahn said:
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
Click to expand...
Click to collapse
i downloaded the latest version
Khalid_am said:
i downloaded the latest version
Click to expand...
Click to collapse
Can you explain exact steps you are taking so we can help you better?
Dielahn said:
Can you explain exact steps you are taking so we can help you better?
Click to expand...
Click to collapse
I downloaded the platform-tools and started the cmd from the platform folder then each time i try to flash anything or interact with the bootloader it just keeps showing me this message (FAILED (remote: unknown command)
can anyone tell me how to flash TWRP on my redmi note 5 global version? I've tried searching and it does not work after entering fastboot flash twrp.img on cmd fastboot mode. Thanks in advance guys
goodygoods said:
can anyone tell me how to flash TWRP on my redmi note 5 global version? I've tried searching and it does not work after entering fastboot flash twrp.img on cmd fastboot mode. Thanks in advance guys
Click to expand...
Click to collapse
Have you unlocked the bootloader yet? Do you get a success/failure when you try to flash using fastboot? Do you have twrp.img in the same folder as fastboot.exe?
goodygoods said:
can anyone tell me how to flash TWRP on my redmi note 5 global version? I've tried searching and it does not work after entering fastboot flash twrp.img on cmd fastboot mode. Thanks in advance guys
Click to expand...
Click to collapse
go to masik thread and in 2nd post download 1click twrp installation
goofball2k said:
Have you unlocked the bootloader yet? Do you get a success/failure when you try to flash using fastboot? Do you have twrp.img in the same folder as fastboot.exe?
Click to expand...
Click to collapse
yep, bootloader is already unlocked and no, haven't seen the result of flashing if it succeeded or failed cause it only said waiting for device
goodygoods said:
yep, bootloader is already unlocked and no, haven't seen the result of flashing if it succeeded or failed cause it only said waiting for device
Click to expand...
Click to collapse
Sounds like you need to update the fastboot drivers. While the device is in fastboot, go to device manager and look for an unknown device that is probably your phone. You'll need to update the drivers to have it show Android Bootloader Interface.
goofball2k said:
Sounds like you need to update the fastboot drivers. While the device is in fastboot, go to device manager and look for an unknown device that is probably your phone. You'll need to update the drivers to have it show Android Bootloader Interface.
Click to expand...
Click to collapse
there was an error while I flashed twrp, it said about anti rollback fail, can you guys help me how to flash twrp on this?
goodygoods said:
there was an error while I flashed twrp, it said about anti rollback fail, can you guys help me how to flash twrp on this?
Click to expand...
Click to collapse
I think method 1 is what you need to do
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
goofball2k said:
I think method 1 is what you need to do
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Click to expand...
Click to collapse
which img should I download from this? the stable or the beta? I'm on miui 10 by the way