Hi everyone!! I did a really stupid thing today! To remove encryption i tried relocking the bottloader knowing that it will wipe everything and then I will just unlock it again but before that I just tried a rom that went into a bootloop so i just made the usual twrp wipe and completely forgot to flash anything and locked the bootloader directly.
Now, I can't get into even the fastboot mode.
Is there anything i can do or i have to get it repaired by the company itself??
Please help!!
same issue but i dont even have my recovery partition but i have fastboot and im on the stock rom
Never mind!! I got it fixed using @Naman Bhalla guide to unbrick it
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Related
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
So wait you can't use fastboot?, because if you can try flashing our bootloader and then try the unlockboot loader technique.
You can not because the bootloader Original ics A100 is blocked in fastboot mode screen says "operation not allowed in locked mode" or maybe not appropriate commands
As far as I understand it, Your only hope is using fastboot to flash the unlocked bootloader again. I'm not sure why did you do this, since using custom recoveries require either an unlocked bootloader or some other way to bypass the security.
peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck
so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk
oneovakindoldys2 said:
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck
Click to expand...
Click to collapse
Ics because it has the last filtered root vache + + wm, if you boot normally in the upper left "verified boot failed" if I boot in recovery "recovery verified failed" and if you can boot into fastboot "bootloader v0.03.11-ICS: STARTING astboot download usb protocol protocol "and is another option that erases user data, I can not access ADB in any way I have a dmsg.test I drew a serial.no when used to work but not APX EEU-FLASH and a pair backup that I did with cwm when it worked I'm sure some way to restore it to and
regards
Euclid's Brother said:
so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Well do not know why I did it maybe because I'm restless and try to leave the factory but now I have a nice paperweight bad mark
that is amazing over 430 visit of this help request without any answer please give me a Proposal
thanks
Hi ,I unlocked My xperia m with the official method of sony all steps worked but when i tried to reboot my phone got stucked into boot animation (i know that erase all data from phone but it last since 1h30) so is my phone bricked or i need more time for the factory reset ?
Solved:Reflashed with firmware
Inreals said:
Hi ,I unlocked My xperia m with the official method of sony all steps worked but when i tried to reboot my phone got stucked into boot animation (i know that erase all data from phone but it last since 1h30) so is my phone bricked or i need more time for the factory reset ?
Solved:Reflashed with firmware
Click to expand...
Click to collapse
you need to flash stock rom. right after unlcoking bootlaoder. please refer to the bootloader unlocking thread.
Yeah i see that 1H later that we need to flash the rom
Ok first let me start off by saying that I'm an idiot and did something really stupid. I was rooted with an unlocked bootloader on Android 8.1 preview was trying to return to stock and stupidly I locked the bootloader before flashing a factory image. Now I'm stuck on the bootloader screen, if I try to boot it flashes the white screen with the Google logo for a split second then starts going into bootloops. When I tried fastboot oem unlock it says "remote oem unlock not allowed". Does anyone know if there is a way to recover my phone or did I make a very expensive mistake?
bbacon said:
Ok first let me start off by saying that I'm an idiot and did something really stupid. I was rooted with an unlocked bootloader on Android 8.1 preview was trying to return to stock and stupidly I locked the bootloader before flashing a factory image. Now I'm stuck on the bootloader screen, if I try to boot it flashes the white screen with the Google logo for a split second then starts going into bootloops. When I tried fastboot oem unlock it says "remote oem unlock not allowed". Does anyone know if there is a way to recover my phone or did I make a very expensive mistake?
Click to expand...
Click to collapse
From what I know across all devices, a very expensive mistake. :/.
For future reference, yet again, for everyone. PLEASE READ. If you want to relock the bootloader, only do so after you actually boot into the new OS.
Reboot into recovery and factory wipe it. That is your only chance, and it's slim.
RMA
Sideload ota through your recovery.
hi
i wanted to unlock bootloader of my xperia m dual c2004
i did in the official way
I successfully unlocked bootloader
but after leaving fastboot (power on)
the devices was not finishing boot . it was continuously showing that colour waves and not finishing
it is my brother's mobile and i dont want to notice him anything
any help would be appreciated
sorry for bad english
akkiman.01 said:
hi
i wanted to unlock bootloader of my xperia m dual c2004
i did in the official way
I successfully unlocked bootloader
but after leaving fastboot (power on)
the devices was not finishing boot . it was continuously showing that colour waves and not finishing
it is my brother's mobile and i dont want to notice him anything
any help would be appreciated
sorry for bad english
Click to expand...
Click to collapse
Your device is on bootloop. You have to flash stock firmware to get it working normally. For that, using xperifirm, download ftf file for your device and then flash it using flashtool. Make sure you install device drivers right in your pc. The only problem of doing above procedure is you'll lose your data.
If you're not concerned about data, just follow procedure written above.
If you are concerned about data, then install cwm recovery and backup your data first and then flash ftf file.
I thought the same.....
After unlocking bootloader,the data partition is erased so no point of backing up haha..
I did it successfully yesterday.. Thanks though
TA partition gone though :'(
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
you might be able to fastboot boot path/to/recovey.img like when you were flashing twrp but im not sure if that works on locked devices try it with a factory image with the recovery extracted and if that works you can sideload the full ota in recovery.
and possibly lgs flashtool can rewrite the phone with it locked but idk if there are imgs out there or if it works with pixel 2 xl
for next time never lock your phone on a custom rom really never relock once unlocked there is no need to and it only takes away your recovery options
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
How the heck did your bootloader get locked if you didn't do it yourself?? Do you get your phone ID displayed when you type in "fastboot devices" in bootloader mode???
You probably ended up switching slots when you reflashed. You need to use Deuces flashing script. Say yes to unlocking.
Try downloading and installing skipsoft tools. It might not see your device but try. If it doesn't see it, manually select your device. Have it install USB drivers. Restart skipsoft and see if it sees your device then. I got into a situation once where in fastboot it showed something like a corrupt bootloader and my computer could not see my device. After messing with the phone with skipsoft running, skipsoft could see it when my computer couldn't.