Database Users

Nexus 6P stuck on google screen - bootloop (bootloader locked)

Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???

GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.

superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
This won't work. The bootloader is locked and he has no way to unlock it.

GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Can you get into the stock recovery?

@GlorySy, you seem on the same issue as this. Please have a look and confirm it is what we got to worry. http://forum.xda-developers.com/nexus-6p/help/main-board-failure-story-t3409400

Not applicable
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
I cannot install any thing with locked boot loader :crying:

Yes
Heisenberg said:
Can you get into the stock recovery?
Click to expand...
Click to collapse
Yes I can, but can do nothing except for turn off the device. :crying:

GlorySy said:
Yes I can, but can do nothing except for turn off the device. :crying:
Click to expand...
Click to collapse
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.

Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.

Just got finished with Google phone support. They're sending me a new device. It must be a hardware failure.
Background: I got OTA notification on Friday night. I downloaded and hit install. Then after a while it said there was an upgrade error, and to please try again. But it was going to have to download the 1+ GB OTA file again, so I just said screw it, i'll do it later. Here am I 2 days later with a broken phone. Thinking this has to be related.
Stock phone, locked bootloader. Running 6.0.1

GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
busbeepbeep said:
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
I am hoping to collect enough data to figure out a solution for all effected.

is your BL locked and device encrypted?
When you try to load recovery, does it ask for password?
try entering your last google account email password if so.

Help!! Stuck in Google screen
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,

Azeem00 said:
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Click to expand...
Click to collapse
Hello... Try to look here:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
For your second question, it's hard to tell... Making regular backups may help protecting your datas, but can't help your new phone to start acting crazy...

I have been doing weekly backups to my pc. I backup my TWRP, TBU, Super Backup, DCIM and download directories.
Sent from my Nexus 6P using XDA-Developers Legacy app

Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Any ideas are any solution when I have custom rom?
EDIT: Not needed, seems that wife phone has motherboard problem because now it will stuck in TWRP screen.

I am pretty sure I had this problem before. Actually within hours of purchasing and rooting. Lol go into fastboot and install factory images. If you were able to get into recovery you could use adb to oem unlock.. but that doesn't sound like an option.

My phone died last night in a bootloop death. Thankfully here in the UK we have a 2 year warranty so Huawei are taking it back. I mentioned "bootloop issue" and the tech guy stopped asking the standard stuff and just sent me a returns bag.

Try this:
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Quickly enable bootloader unlocking, then follow the tutorials already known for 4-core recovery

Well I've now got a different phone back from Huawei as they told me they no longer have replacement motherboards available.
Sent from my MHA-L29 using Tapatalk

Axon 7 brick

I've spent the whole night trying to figure this out, but to no avail. Here goes...
Hey guys, so I was innocently playing around with GravityBox when I restarted my phone so some new settings would kick in, and it sends me into a bootloop. I went into TWRP Recovery, and at first factory reset my phone, hoping it would solve the problem, but it didn't, so I ended up "Formatting Data", which still didn't work. I'm kind of new to this whole flashing/rooting/ business, and I was wondering how I could fix my phone. If turned on, it stays in the booting process with the golden "Axon" letters forever. The model is the US variant, it's bootloader is unlocked via the ZTE Request Form, and it currently has TWRP as it's custom recovery. Help will be much appreciated. Also, it's on OTA B20
Edit: Alright so I've tried to flash to boot.img as well as recovery.img in twrp, but both give me an error. Strangely enough, if I wait out the Axon logo for about 5 minutes, it actually boots up, but as if it was the first time turning it on (asks you to sign in to google, wi-fi setup, fingerpring setup, etc). Another thing I noticed was that it says I only have 4gb of storage, instead of the 64 it originally came with. Every time I reset it/turn it off, it makes me set up the phone again.
Edit #2: Fixed with the help of this thread http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895 Only problem seems to be that Wi-Fi does not work. /:

I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk

raber111 said:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
Click to expand...
Click to collapse
I don't have a TWRP backup to restore to ): if that's what you mean, any other solutions?

I didn't have to but I found a backup on XDA . And I don't really know if you should use it or you should wait till full stock image will release.
Отправлено с моего HTC One M8 через Tapatalk

Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895

reddrago said:
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
Click to expand...
Click to collapse
I'm in the process of doing this as of right now, thank you. Will update.

It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!

Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.

Barsky said:
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Click to expand...
Click to collapse
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk

flyer_andy said:
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Click to expand...
Click to collapse
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.

bricky23 said:
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,

Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
I'm in the exact same boat. Did you ever figure out how to get wifi back?

Pollito788 said:
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Click to expand...
Click to collapse
Am I missing something. that dev-host site sends me exploit installers. good thing I do nightly acronis images.

Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
Flapjack said:
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Click to expand...
Click to collapse
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Would not mind fixing this rather than shipping my packed up axon7 to newegg. Think I have a few days before it has to ship, so I am open to working on it some more.
Thanks.
---------- Post added 08-29-2016 at 12:00 AM ---------- Previous post was 08-28-2016 at 11:51 PM ----------
Flapjack said:
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
Click to expand...
Click to collapse
Try flashing the 2.65 ver over it

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .

Barsky said:
Try flashing the 2.65 ver over it
Click to expand...
Click to collapse
That's the thing.... I've restored it repeatedly. All traces of 2.67 should be gone. I've completely restored it three times now.
I'm honestly thinking I'm better off returning this phone while it's still working. I wonder if something is wrong with it.

DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
tysm bro <3

DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
Brings DrakenFX some coffee and nudges him awake. :cyclops:

Is this normal after unlock/root?

I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.

convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk

dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...

convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk

It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.

GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?

I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?

convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck

wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.

convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.

wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?

convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.

wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?

convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.

wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...

convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.

spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.

delete

If it works, you should worry about that message at all.

convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory:

note 3 not booting - pls help

[email protected]
thx for taking a look on my Problem
3month old note 3 no root, stock Rom, 3months no Problems,
was last week outside and i guess i was low on battery it was off as i had it in Hand
was loading all the evening and the battery is fully green
it starts, i can see mi logo, it changes to Android with loading dots at the Bottom and then it goes off
tried several times
fastboot is available
and main menu with reboot/wipe data/connect with mi assistant
i already tried:
wipe data - finished with ok (all my data gone) but still same issue
connect with mi assistant - no connecttion to Software
someone any ideas - thanks for any help
greetz

Since you already lost your data, try to flash the ROM again. I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked), if you can at least dirty install it as an update it may work too (google it). Unfortunately, providing more information over unlocking the phone is inappropriate.

GreatApo said:
try to flash the ROM again.
Click to expand...
Click to collapse
How?
GreatApo said:
I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked)
Click to expand...
Click to collapse
yes it locked
GreatApo said:
Unfortunately, providing more information over unlocking the phone is inappropriate.
Click to expand...
Click to collapse
can u pm me please?
u are the onle one who relied to my post
thanks in advance

Since your bootloader is locked, your options are limited.
To expand a little what i mentioned, your best try it may be to try and update the current from from the stock recovery. That may fix a potential corrupted partition. To do so, you can follow the steps of method 2 in this article. However, I am not aware if you can transfer the update.zip in the phone... I suppose that the stock recovery doesn't mount the phone to the PC. Thus, you probably need to try and transfer if through fastboot but that may not be possible too (could check if adb push works or if you can boot a twrp recovery, not flash just boot, but you probably wont be able)...
If you can't do the above steps, you are in a half-brick mode right now with a locked bootloader. Generally, there is no official way to get around this.

Help ! Redmi 2 (2014811) keeps restarting after booting

Hello everyone, that's it. I have a Redmi 2 enhanced version (2014811) . It can be turned on now but it keeps restarting as soon as it enters the first page. Now it can enter the fastboot mode. How can I save it? (The phone should not be rooted before)
Postscript: If possible, can I take this opportunity to use a third party ROM to upgrade to a higher version of Android? (e.g. Android 10 or higher）
Thank you for your comments, thank you very much ! ! !

Deleted.

LR7875 said:
If you know how to use fastboot, try installing TWRP. (Execute command fastboot flash recovery twrp.xxx.img where twrp.xxx.img is the filename of twrp placed into the fastboot folder on your computer. If you don't understand ask me further.)
Wingtech Redmi 2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Then wipe> factory reset in twrp
Then flash this rom
[ROM][11.0][UNOFFICIAL][wt88047x] LineageOS 18.1
Important information: This thread is for LineageOS 18.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Click to expand...
Click to collapse
First of all, thank you very much for your advices, bro! Do I need to unlock/root first before installing TWRP? Because I have not been rooted it before, can I just flash in TWRP directly under the fastboot environment without rooting? Sorry, I still don't know how to do it, maybe some concepts have not been figured out yet. .....

If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...

blackhawk said:
If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...
Click to expand...
Click to collapse
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?

Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.

2021redmi2fans said:
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?
Click to expand...
Click to collapse
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.

LR7875 said:
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.
Click to expand...
Click to collapse
He should be able to reflash the stock rom though, right?

LR7875 said:
Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.
Click to expand...
Click to collapse
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......

2021redmi2fans said:
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......
Click to expand...
Click to collapse
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.

However, before the loop occurs, Mokee 7.1.2 was installed and used it normally for a period of time, does that matter?

blackhawk said:
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.
Click to expand...
Click to collapse
Bro really thank you

2021redmi2fans said:
Bro really thank you
Click to expand...
Click to collapse
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.

blackhawk said:
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.
Click to expand...
Click to collapse
redmi 2 runs on stock rom android 4.2 right? you can not install any single app on that.
when the op fixed it it is advised to install a custom rom.