*HELP!!* locked bootloader with no OS - Nexus 6 Q&A, Help & Troubleshooting

So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??

prestigiousboi said:
So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??
Click to expand...
Click to collapse
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
^ this. You'll still be able to flash a rom because you have twrp.

prestigiousboi said:
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​
Click to expand...
Click to collapse
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
why not m? it booted fine for me via twrp, the twrp flashable version at least.

simms22 said:
why not m? it booted fine for me via twrp, the twrp flashable version at least.
Click to expand...
Click to collapse
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
I love you man. Thank you for helping me (a noob)

prestigiousboi said:
I love you man. Thank you for helping me (a noob)
Click to expand...
Click to collapse
I guess that means you got it working. :victory: :good:

Evolution_Tech said:
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.
Click to expand...
Click to collapse
doesnt require the radio flash, but does require the bootloader flash. I did forget though, you're right. I updated that via twrp as well. but you are very right about keeping it simple

i got excited when i found this thread. then I realized I have no recovery. this phone is seriously screwed it isn't showing any screens or anything

Related

Wiped O.S. without backing up, help, or is it too late?

I screwed up, I wiped my nexus 6 in recovery before I backed up original O.S., now I have no operating software to install. Is there anything I can do, or is it too late????
slammer1 said:
I screwed up, I wiped my nexus 6 in recovery before I backed up original O.S., now I have no operating software to install. Is there anything I can do, or is it too late????
Click to expand...
Click to collapse
its too late for whatever app and system data you had, but you can always adb push or adb sideload a rom, gapps, and supersu to your phone then flash them.
If you had a unlock bootloader you can fastboot the stock images to you phone to go back to stock.
Ok, so, while in TWRP recovery, how do i do that? I see in Advanced tab there is "ADB Sideload", is that where i start? I did unlock the boot-loader already.
slammer1 said:
Ok, so, while in TWRP recovery, how do i do that? I see in Advanced tab there is "ADB Sideload", is that where i start? I did unlock the boot-loader already.
Click to expand...
Click to collapse
google it, youll find instructions.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
ive never sideloaded anything(just used adb push), but they are similar ideas.
slammer1 said:
Ok, so, while in TWRP recovery, how do i do that? I see in Advanced tab there is "ADB Sideload", is that where i start? I did unlock the boot-loader already.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZNEXCY-wHpw&list=FLnc-CzjhL7xC4l3z7QahZlA
jongie123 said:
If you had a unlock bootloader you can fastboot the stock images to you phone to go back to stock.
Click to expand...
Click to collapse
Does the bootloader have to be unlocked to do this?
Also, for the system partition I think you need mfastboot.
JulesJam said:
Does the bootloader have to be unlocked to do this?
Also, for the system partition I think you need mfastboot.
Click to expand...
Click to collapse
If you want to use the fastboot method yes the bootloader needs to be unlocked.
Use wugs toolkit. You can force flash os
The easiest thing to do IMO is to flash the stock img in fastboot. Check out this thread.
http://forum.xda-developers.com/showthread.php?t=2954008
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader

[6.0.1][STOCK][ROOT] Android one boot img for root

Files are in this link http://forum.turkdevs.com/konu-root-android-6-0-6-0-1-calisan-root-yontemi.html?pid=62642#pid62642
This method will work on 6.0 and 6.0.1
Extract files in adb folder
Enable usb debugging and oem lock
Open adb on your PC and execute "adb reboot bootloader"
Execute "fastboot flash boot newboot.img"
Execute "fastboot boot recovery-twrp.img"
Flash supersu via twrp and reboot system.
Thanks t_sasak for editing boot.img in TurkDevs Forums
nhmanas said:
Files are in this link http://forum.turkdevs.com/konu-root-android-6-0-6-0-1-calisan-root-yontemi.html?pid=62642#pid62642
This method will work on 6.0 and 6.0.1
Extract files in adb folder
Enable usb debugging and oem lock
Open adb on your PC and execute "adb reboot bootloader"
Execute "fastboot flash boot newboot.img"
Execute "fastboot boot recovery-twrp.img"
Flash supersu via twrp and reboot system.
Thanks t_sasak for editing boot.img in TurkDevs Forums
Click to expand...
Click to collapse
I thought i was able to successfully root my phone but after flashing SuperSU using TWRP i get a bootloop. HELP please!
Phone: Cherry Mobile One G1
OS: Android 6.0 Marshmallow
Build No: MRA58Y
Its working. THANKS!
PineappleOwl said:
Its working. THANKS!
Click to expand...
Click to collapse
what's your mobile phone?
kiksilog said:
what's your mobile phone?
Click to expand...
Click to collapse
Cherry Mobile G1 of Philippines
I haven't tried yet. I'm going to flash this today. People in TurkDevs developed and they're successful
Tengri biz menen
ricosuavehhh said:
I thought i was able to successfully root my phone but after flashing SuperSU using TWRP i get a bootloop. HELP please!
Phone: Cherry Mobile One G1
OS: Android 6.0 Marshmallow
Build No: MRA58Y
Click to expand...
Click to collapse
Did you unlock bootloader ? It has to be unlocked.
Yes i did enable OEM unlock bootloader in Developer Options
Choose correct boot file
ricosuavehhh said:
Yes i did enable OEM unlock bootloader in Developer Options
Click to expand...
Click to collapse
enable OEM unlock bootloader in Developer Options
enable USB Debugging Mode in Developer Options
unlock bootloder with "fastboot oem unlock-go" command
choose correct boot file (6.0.1 MMB29K or 6.0.0 MRA58Y)
you can find that files on first post link
---------- Post added at 08:17 PM ---------- Previous post was at 07:50 PM ----------
ricosuavehhh said:
Yes i did enable OEM unlock bootloader in Developer Options
Click to expand...
Click to collapse
what happend ?
cgtylpr said:
enable OEM unlock bootloader in Developer Options
enable USB Debugging Mode in Developer Options
unlock bootloder with "fastboot oem unlock-go" command
choose correct boot file (6.0.1 MMB29K or 6.0.0 MRA58Y)
you can find that files on first post link
---------- Post added at 08:17 PM ---------- Previous post was at 07:50 PM ----------
what happend ?
Click to expand...
Click to collapse
Thanks! i'll check if i did download the correct boot file
ricosuavehhh said:
Thanks! i'll check if i did download the correct boot file
Click to expand...
Click to collapse
Careful! Oem-unlock go command will wipe everything on your device including internal sd
Tengri biz menen
nhmanas said:
Careful! Oem-unlock go command will wipe everything on your device including internal sd
Tengri biz menen
Click to expand...
Click to collapse
You're right.
ricosuavehhh said:
You're right.
Click to expand...
Click to collapse
Problem solved ?
cgtylpr said:
Problem solved ?
Click to expand...
Click to collapse
I'm currently flashing boot.img, recovery.img... will update you later.
I flashed yesterday. It works like charm. And Xposed is working flawless
Tengri biz menen
nhmanas said:
I flashed yesterday. It works like charm. And Xposed is working flawless
Tengri biz menen
Click to expand...
Click to collapse
Nice
Thanks. Successfully flashed boot and superSU, running Xposed too, trying out modules. Thank you very much, OP.
Cherry Mobile One G1
MM 6.0.1
Just out of interest, what do your guys do, when the next OTA-Updates arrive...?
Xposed on mm causes random reboot.. Maybe because of modules I don't know
Tengri biz menen
vel_tins said:
Just out of interest, what do your guys do, when the next OTA-Updates arrive...?
Click to expand...
Click to collapse
Nothing these people who flashed twrp and rooted the phone can do when a new OTA arrives, except whine and hope that somebody is able to capture the OTA file and transform it to a twrp-flashable zip. :crying:

Nexus 6 - Can't unlock bootloader, ROM wiped, only have TWRP and bootloader. Help?

I've got one you've never heard of before. A Nexus 6 with TWRP loaded. Phone will boot to Recovery or Bootloader, but 'System' boot goes to "Google" and never loads. ROM is gone. Bootloader is locked. Do I have a 3-week-old brick? Phone was previously rooted and functioning, but change from Sprint to Google Fi required the stock ROM. Somehow the bootloader got locked and there was no option to enable developer mode in the ROM. So now we're here. What options do I have, other than buying another phone? I can't RMA, since it's been rooted and unlocked. I'm just screwed out of my $300 phone.
Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!
Didgeridoohan said:
Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!
Click to expand...
Click to collapse
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
Have you tried? 'Cause the method I describe above have been known to work when people mess up their phones by locking the bootloader without a bootable system.
can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.
SamsonIncorporated said:
can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.
Click to expand...
Click to collapse
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?
istperson said:
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?
Click to expand...
Click to collapse
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.
SamsonIncorporated said:
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.
Click to expand...
Click to collapse
1. Any valid suggestion, yes, but a shot in the dark doesn't help much, does it now. More so, if we know that toolkits are nothing more than graphical frontends to comandline tools. So if typing fastboot oem unlock gives you error, then executing the same command from the toolkit will give you the same error.
2. There is not enough information on how @mightymichelob tried to flash a rom. Because fastboot flash will fail, while flashing a zip, e.g. cm-13.0 should not.
He has twrp installed what's the big deal, move a rom to SD card from twrp and flash it, am I missing something?
if you have twrp installed, then your bootloader IS unlocked, period. you can not flash twrp with a locked bootloader.
edit.. nevermind, assuming op locked his bootloader. format cache and userdata via fastboot then flash a rom.
Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.
Have you tried the repair option in twrp?
mightymichelob said:
Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.
Click to expand...
Click to collapse
nope, nothing "magical" exists. the only way to unlock your bootloader is to enable the option in developer settings first. formatting cache and userdata in fastboot should let you flash a rom via twrp.

Flash TWRP using Wugfresh on Nexus 6 w/ N

I've been trying to flash the latest TWRP recovery on my N6 using Wugfresh NRT. I am currently running Android N DP3. I go the advanced utilities and Recovery under Fastboot Flash. NRT goes through the whole process of flashing TWRP and the perm-recovery-signed.zip then reboots back to normal. When I try to reboot into recovery it always goes to the android on his back with a red exclamation and says No command. I've tried rebooting into recovery using NRT and trying from the bootloader, neither works. Any ideas?
sherpajosh said:
I've been trying to flash the latest TWRP recovery on my N6 using Wugfresh NRT. I am currently running Android N DP3. I go the advanced utilities and Recovery under Fastboot Flash. NRT goes through the whole process of flashing TWRP and the perm-recovery-signed.zip then reboots back to normal. When I try to reboot into recovery it always goes to the android on his back with a red exclamation and says No command. I've tried rebooting into recovery using NRT and trying from the bootloader, neither works. Any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008/
NLBeev said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
I get invalid thread notice when I click on this.
wtherrell said:
I get invalid thread notice when I click on this.
Click to expand...
Click to collapse
It's in Nexus 6 General.
"http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008"
Paste in Chrome or browser without quotes.
---------- Post added at 12:30 PM ---------- Previous post was at 12:18 PM ----------
wtherrell said:
I get invalid thread notice when I click on this.
Click to expand...
Click to collapse
I edited the link adding a slash at the end.
Than it works also in Tapatalk
Toolkits are stupid ESPECIALLY on a glorious Nexus device.
-Make sure you have OEM Unlocking enabled under developer options
-Boot into bootloader. When the phone is powered off, hold power, volume up and volume down simultaneously.
-Download the latest TWRP from here (at the time of this writing is
twrp-3.0.2-0-shamu.img)
-If you don't already have ADB and Fastboot from the Android SDK install this: [TOOL]Minimal ADB and Fastboot [4-27-16]
-Move the TWRP file you downloaded into the same directory where you installed ADB and Fastboot
-Open a command prompt window in this same directory and run the these two commands (first one might be unnecessary): "fastboot oem unlock" and then "fastboot flash recovery twrp-3.0.2-0-shamu.img" with no quotes
-Reboot into recovery, and voila, you have the latest TWRP booting on your device.
NLBeev said:
It's in Nexus 6 General.
"http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008"
Paste in Chrome or browser without quotes.
---------- Post added at 12:30 PM ---------- Previous post was at 12:18 PM ----------
I edited the link adding a slash at the end.
Than it works also in Tapatalk
Click to expand...
Click to collapse
Thanks
OEM Unlocking enabled under developer options Is greyed out
anyways to fix this

Bricked P8 lite 2017

Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:
Which firmware you had before brick?
MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?
MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly
70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.
This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).
You still need help?
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.
MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot
:good:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too

Categories

Resources