Hello guys am basically a Noob when it comes to the new android 6.0+ security system that google included which changed the bootloader unlocking and rooting process a lil bit from the standert ( fastboot oem unlock ... fastboot flash twrp ... flash super su and voila )
let's get to my probleme with my nexus 5x when i unlocked the bootloader with the tool the device has to reboot but everytime i reboot i have to unlock my bootloader again the root works fine but the bootloader keeps getting locked everytime ... problem is that i messed with the boot img in order to disable forced encryption and now i can't flash stock because during the flashing the bootloader has to reboot and gets locked which make the flashing fails ... am on android nougat 7.0 if that matter and if someone have the 6.0.1 (mtc20k) boot image for noforce encrypte please share with me and thanks
You can update manually by flashing the different parts separately using fastboot commands. That way you can skip rebooting after flashing bootloadet
Skickat från min Nexus 5X via Tapatalk
I have the same problem. Bootloader gets relocked every time i reboot. Could not install cm14.1, i just get i bootloop (tried with latest twrp and vendor). Went back to stock with the seperate fastboot commands. It works but really annoying that the bootloader wont stay locked. It worked before i sent the phone to service (emmc problem) and got the motherboard changed. Is there a problem with the bootloader or is it a hardware problem?
Sounds like a HW problem, RMA it again.
RusherDude said:
Sounds like a HW problem, RMA it again.
Click to expand...
Click to collapse
Thanks!
Yeah thats what im thinking too. But what do i claim as the issue? Is a non unlockable bootloader a warranty issue? Bought it unlocked from a store.
frukten said:
Thanks!
Yeah thats what im thinking too. But what do i claim as the issue? Is a non unlockable bootloader a warranty issue? Bought it unlocked from a store.
Click to expand...
Click to collapse
Ask Google (you can open up a chat with them for example on https://support.google.com/nexus/answer/4582729?hl=en&ref_topic=6023296#contact=1 or other links), for me it's a clear issue, you have the right to unlock the bootloader, however not sure how to demonstrate a problem if you bought it on a store...
All phones that come back from service do so in that state. Seems it's a decision from LG. If you go to bootloader you'll probably see that is says "no rpmb" right after secure boot. This is what is causing the issue, from what I know it is because a certain portion is not flashed on the motherboard replacement
The same happend to me, e-mailed the service center asking why they did this but they never reply
Skickat från min Nexus 5X via Tapatalk
Related
Hello,
Today my Phone suddenly started to reboot at first it just did a reboot normaly but afterwards it started to reboot again but now I am stcuk in the screen with the lg logo and the bootloader unlocked message I tried to boot into recovery but after I choose to do factory reset so i can boot into twrp, again it only boots to the screen with lg logo and bootloader unlocked message.
I am on Genesys Rom and did not install any Mods
is there anyway for me to fix this?
Please help me
jizang said:
Hello,
Today my Phone suddenly started to reboot at first it just did a reboot normaly but afterwards it started to reboot again but now I am stcuk in the screen with the lg logo and the bootloader unlocked message I tried to boot into recovery but after I choose to do factory reset so i can boot into twrp, again it only boots to the screen with lg logo and bootloader unlocked message.
I am on Genesys Rom and did not install any Mods
is there anyway for me to fix this?
Please help me
Click to expand...
Click to collapse
unlocking the bootloade voids your warranty.. only way is to send it to LG... or used the modded KDZ to disable big cores... in case you ncaat fix it. or get new motherboard..
raptorddd said:
unlocking the bootloade voids your warranty.. only way is to send it to LG... or used the modded KDZ to disable big cores... in case you ncaat fix it. or get new motherboard..
Click to expand...
Click to collapse
So its not software related? Is there anyway to disable the bootloader unlocked message?
jizang said:
So its not software related? Is there anyway to disable the bootloader unlocked message?
Click to expand...
Click to collapse
bootloop not software but hardware... but you could try flashing KDZ using LGUP. ive seen some claim theirs worked after flashinf stock firmware if it continues then hardware but most likely its hardware..
mines is unlockable.. and trying to keep it that way for the same reason... ive seen a post that says it can be relocked...
heres is the post.. i would like to ask you a favor if you try it.. make video of it .. to prove it works..
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
This is the reason why i swap my G4 H818P to Korean Variant G4. The Bootloop problem. Korean Variant is perfect for me. Strong 4G signal and no more SMS Limits in Marshmallow official update.
Sent from my LG-F500S using Tapatalk
Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?
U_Midrar said:
Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?
Click to expand...
Click to collapse
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Click to expand...
Click to collapse
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?
U_Midrar said:
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?
Click to expand...
Click to collapse
Sure, flashing the factory images is probably slightly easier than the other methods. Note that in your case you would need to actually unlock the bootloader to flash the images. With those added steps it's probably faster to sideload.
The Allow OEM unlock toggle has been around since LP I think. An pretty sure it's in phones that shipped with LP. It didn't automagically mean that the phones bootloader can be unlocked though. It should stop disable FRP though.
Sent from my XT1650 using Tapatalk
Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.
creambyemute said:
Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.
Click to expand...
Click to collapse
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )
U_Midrar said:
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )
Click to expand...
Click to collapse
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.
HebeGuess said:
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.
Click to expand...
Click to collapse
so i shouldnt do it like just leave it be ?
F IT I DID IT
i just read this site and also got to know a bootloop can occur with OTA update so yea i have done it.
Site: http://android.wonderhowto.com/news...ting-before-modding-anything-android-0167840/
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Is it a carrier model or a play store
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
chapelfreak said:
Is it a carrier model or a play store
Click to expand...
Click to collapse
Google store
ASimpleSock said:
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
Click to expand...
Click to collapse
I see the thread but it doesnt seem like theres a fix in it
tryfont said:
I see the thread but it doesnt seem like theres a fix in it
Click to expand...
Click to collapse
There probably isn't, if you've altered system and relock and toggle OEM unlocking off in dev. options you get bricked.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
5.1 said:
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
Click to expand...
Click to collapse
It just says waiting for device and hangs there... I don't think it recognizes the phone
EDIT: IT WORKED!!!!!
It wouldnt recognize it and I ran fastboot continue and it just hanged there but I went into the bootloader mode and for like a quarter of a second it recognized it and forced it to boot
tryfont said:
It just says waiting for device and hangs there... I don't think it recognizes the phone
Click to expand...
Click to collapse
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
5.1 said:
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
Click to expand...
Click to collapse
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
This is whats happening to me- https://goo.gl/photos/2kv9Xo3HM3Mqn8AQ9
tryfont said:
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
Click to expand...
Click to collapse
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
5.1 said:
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
Click to expand...
Click to collapse
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device. Also I couldnt get into recovery when it was bricked so I probably still can't
tryfont said:
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device
Click to expand...
Click to collapse
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
5.1 said:
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
Click to expand...
Click to collapse
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
tryfont said:
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
Click to expand...
Click to collapse
Hey... Flash both slots... Just to be sure both are clean and nothing problematic remains on your device before locking your bootloader!
It could brick installing an OTA or whatever. Better restart 100% clean. :good:
Cheers...
Just flash the flash-all, relock and call it a day. Then you'll be fully stock and locked. I would however recommend rebooting once before locking to make sure its all good.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Hey man I have the same problem you can try calling Google support they can send you a replacement if you still have a warranty
my warranty has expired so I'm on my own
Success is disgusted by some people, and will not share any files for free in the future.
If relock, how about OTA uptdate?
dungnghien said:
If relock, how about OTA uptdate?
Click to expand...
Click to collapse
yes，you can！only support CN firmware，but WW firmware upgrades are not supported. The WW version of the firmware upgrade, you need to download the update package to the root directory, restart the phone to detect the update.
Will this process factory reset or no ???
zinou213 said:
Will this process factory reset or no ???
Click to expand...
Click to collapse
YES！
Damn! I should have waited for this. Too late. I used unlock tool. Now Asus has my unlock info.
One question. Can I relock if I originally unlocked using asus unlock apk tool???
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
BakaValen said:
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
Click to expand...
Click to collapse
There are no disadvantages, the only benefit is that you can unlock your phone through EDL mode, no need to install UnlockTool.apk to apply for unlock! The ASUS server will not get your unlocked status, you can get upgrades via OTA later.
Extreme184X said:
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
Click to expand...
Click to collapse
Oh sorry, I forgot to upload the driver for Qualcomm! You can download and install this tool on your computer, and then follow the steps to unlock it! Download link:https://drive.google.com/open?id=1PRw4jcg0zQKLQnMz7gApMZtCYex1PfJM
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
BakaValen said:
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
Click to expand...
Click to collapse
By unlocking this way, you can enjoy the warranty!
had anyone tried this method on previous unlocked device? did it will regain CN FOTA? thanks!
Hi, i tried but stuck on step 3, any way to solve? tried to change the usb port but same thing happened.
on step 3:.Double click to open “1.update_image_EDL.bat”,
it said: {ERROR: WritePort:5164 Could not write to '\\.\COM10', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times
@johnny886,
Hi, I installed the Qualcomm drivers but for step 3 "1.update_image_EDL.bat”, it still prompts and closes immediately and I'm not sure how to QPST or QFIL. Are there ways to fix the bat file or provide a more detaisl on using QPST or QFIL please?
You can root without unlock bootloader?
Deleted, misread, don't think it's relevant...
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
dennis96411 said:
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
Click to expand...
Click to collapse
Hey, can you please tell me where to get the stock boot image for 1910.44?
Edit: Okay nevermind got it.
Stuck on step 1.update_image_EDL.bat
Almost all of us are stuck on step 1.update_image_EDL.bat . The CMD window just shows and closes fast, and phone doesnt enter fastboot mode. I installed all drivers. Can you post guide on how to do that step using QPST or Miflash tools?
Am I just having a bunk phone or is anyone else having this issue?
Whenever I try to set up the lock screen code on the reconfirm the code screen it freezes after I put in the code and will not proceed.
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
JPower123 said:
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
Click to expand...
Click to collapse
Like no root or anything?
cabagekiller said:
Like no root or anything?
Click to expand...
Click to collapse
Yeah, it's super weird. Just unlocking the bootloader causes this. But yeah from what I understand you should be completely unrooted and with stock boot images and or init boot images when relocking.
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
mvincent2k said:
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
That is unlocked the unlock setting greys out on mine too. I got my lock screen to work as well. Super weird bug though.
mvincent2k said:
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
Only over fastootd or with msm tool (msm tool need authentication )
I just flashed the whole OS on Oneplus 11 using software called Fastboot enhance.
Actually, my op 11 was bootlooping but by using fastboot enhance software I flashed my original OS on the phone. Let everyone know, they don't need Odin or MSM for that. It's very easy and one-click process.
Same problem, was advised to lock and unlock the bootloader. I locked it and didn't realize that I had to go back to stock first and now I'm stuck in a boot loop. I can get into recovery with vol down and power, but cannot get into fastboot with vol up and power. Where do I go from here?
Sorry, I want to identify that this issue happen even I have not rooted?
PowerPC 604e said:
Sorry, I want to identify that this issue happen even I have not rooted?
Click to expand...
Click to collapse
Only when you have a convertet op11 (china ) and flash this to oos than after an oos Update you have flash back an image from coloros without this image the op 11 will bootloop
And when you have root and lock with root the bootloader than you have an bootloop