Develop Bugs

[How-To][tutorial] Bootloader Unlock, Custom Recovery Razr M

So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw

sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.

As long as we do this first, future OTAs can't relock our bootloaders, can they?

Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.

BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...

sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.

trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl

dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium

new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?

CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...

Does this wipe our phone
Sent from my XT907 using xda app-developers app

Nope

ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?

Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app

I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2

mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).

Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks

Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD

Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.

sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.

Where can I find an easy guide to root the pixel C?

This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Sent from my Pixel C using XDA-Developers mobile app

DrKaotica said:
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Sent from my Pixel C using XDA-Developers mobile app
Click to expand...
Click to collapse
I've not rooted my Pixel C, but this http://www.wugfresh.com/nrt/ works seamlessly on my Nexus 7 2013. Page suggests that it supports Pixel C.

Yes, you have to unlock the bootloader-- I found a posting here on doing it-- it's pretty straight forward.
After that all you basically need to do is boot into TWRP to install supersu. I had the bootloop issues actually flashing TWRP for whatever reason however I found another posting here noting that you don't actually HAVE to *flash* TWRP, you just need to boot into it.
First get a version of SuperSU-- I *may* have used UPDATE-SuperSU-v2.76-20160630161323.zip that I got from here somewhere-- not sure now exactly-- probably just get the latest one.
Push that to the pixel via something like "adb push UPDATE-SuperSU-v2.76-20160630161323.zip /sdcard/" from your Mac, Linux or Windows box.
So I've got a stock bootloader now ( I had to revert the whole thing to make it usable again) and to boot into TWRP I first put the pixel into fastboot mode (boot up and hold down power and volume down, then select fastboot), then go:
fastboot boot recovery.img
..where recovery.img is one of the files like TWRP-3.0.2-0.recovery.img or twrp-3.0.0-0-dragon-ryu-02112016-1.img
After you are booted into TWRP you then select (I believe, from memory) "INSTALL" and select the supersu zip file you put on the device earlier. After it installs that reboot and you are root.
DrKaotica said:
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Click to expand...
Click to collapse

Can I install CWM via the fastboot command?

I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.

Fiksdal said:
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Click to expand...
Click to collapse
Worth checking general section
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236

Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works

Fiksdal said:
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Click to expand...
Click to collapse
Tip
It is always worth googling
and put an XDA on the end

timbernot said:
Tip
It is always worth googling
and put an XDA on the end
Click to expand...
Click to collapse
Haha, you know, I had been struggling with this problem for like 2 days. So many hours on the computer and Google trying to figure it out. I was trying to get the scripts to work, then CWM, then TWRP. I was just really confused and didn't know how to do it since most guides on Google said I had to use the scripts for Windows. Then finally I realized that it was as simple as using fastboot from OS X Anyway, sorry to bother you guys. But Everything is working now, root, Xposed and permanent TWRP. Awesome

Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip

timbernot said:
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
Click to expand...
Click to collapse
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again

Fiksdal said:
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Click to expand...
Click to collapse
You are doing great now :victory:

[Root Asus Zenfone 3 Deluxe ZS570KL Z016S] Android 7.0 Nougat, How to Root?

Hello Everyone,
how to root Asus Zenfone 3 Deluxe ZS570KL 2.15Ghz with Android 7.0?
It's possible? There are root solutions without unlocking bootloader?
Thank you

I believe you might be able to with a systemless root. This may cause issues though without the bootloader unlock.
What I'd do, and I've already unlocked my bootloader, is boot TWRP, this won't replace your recovery and will disappear next boot, then flash magisk systemless root.
This should allow root with a locked bootloader BUT I can't try this now as I have an unlocked bootloader.
You'd do this through fastboot.
Be prepared to reflash your stock rom if you do get a soft brick...

ultramag69 said:
I believe you might be able to with a systemless root. This may cause issues though without the bootloader unlock.
What I'd do, and I've already unlocked my bootloader, is boot TWRP, this won't replace your recovery and will disappear next boot, then flash magisk systemless root.
This should allow root with a locked bootloader BUT I can't try this now as I have an unlocked bootloader.
You'd do this through fastboot.
Be prepared to reflash your stock rom if you do get a soft brick...
Click to expand...
Click to collapse
Thanks ultramag69 for info. Have you a guide for safe root? The only guide that seemed trustworthy that I found on the internet, unfortunately it was written in Chinese.

vodafonever said:
Thanks ultramag69 for info. Have you a guide for safe root? The only guide that seemed trustworthy that I found on the internet, unfortunately it was written in Chinese.
Click to expand...
Click to collapse
OK, if you are game...
As I said, my phone has bootloader unlocked so this worked fine, I don't know if it will work.
Essentailly you replace the stock recovery with TWRP TEMPORARILY, just one boot.
Download magisk systemless root file and put on sd card. Also activate developer settings and tick " USB Debugging".
Put TWRP file in folder with fastboot files on PC, hold shift and right click. Select "open CMD window here".
Put phone in fastboot mode. Attach to PC with usb.
Type in cmd window "fastboot devices", you should see you're serial number come up on another line if you are connected.
Type "fastboot boot twrp.img" - make sure the twrp file is named this.
You should reboot to TWRP. Make sure you DON'T select "Alter system files" as you're bootloader is locked.
Install magisk systemless root file from TWRP.
Reboot and see if it works...
As I said, I did this after I unlocked the bootloader but as magisk is a systemless root I don't see this not working.
That said there is always a risk when doing this sort of thing and I would urge you to unlock bootloader 1st as this makes it a bit easier to fix if things if something does go bad...

Yes, right. No root and TWRP for Anus ZendFone 3 Deluxe ZS570KL yet.
May be it become later. Right? Right!

PaulPP said:
Yes, right. No root and TWRP for Anus ZendFone 3 Deluxe ZS570KL yet.
May be it become later. Right? Right!
Click to expand...
Click to collapse
If you unlock your bootloader then yes there is a TWRP you can flash and from there gain root by either flashing SuperSU or Magisk.
I prefer not to replace my recovery as when I was trying to gain root there was a problem with TWRP registering the touches in a reversed position, top right corner would register bottom left corner and so on. So instead I booted TWRP and installed Magisk, this gained root access but allowed flashing OTA updates instead of having to download a 2gb rom by keeping stock recovery.
Twrp has since been fixed and should be fine now but I still prefer to keep stock recovery, it's really up to you, either use "fastboot boot twrp.recovery" to temporarily replace stock (it reverts to stock when you reboot) or "fastboot flash twrp.recovery", this will flash twrp to your device permasnently (or until you want to replace it).
At the moment, magisk is not allowing safety net to pass but there should be an update soon that will fix this, flashing supersu will never allow a safetynet check to pass...
Again, up to you and how you use your device but either way will give you root access....

ultramag69
I have questions:
1. Where I can download fresh TWRP for Z016D model?
2. After install Magisk I must restart device for remove TWRP to stock recovery?

[RECOVERY]Honor 7x stuck in bootloop

Hello everybody, my Honor 7x BND-L21 entered in a bootloop (i haven't flashed custom rom or anything else).
I'd like to solve this problem without loosing my data.
Is there any way to unbrick the phone without loosing data?
Or is it possible to flash a custom recovery (TWRP), make a full back-up, and after that unbrick the phone?
My phone isn't rooted and the bootloader isn't unlocked.
Thanks

Oloccin said:
Hello everybody, my Honor 7x BND-L21 entered in a bootloop (i haven't flashed custom rom or anything else).
I'd like to solve this problem without loosing my data.
Is there any way to unbrick the phone without loosing data?
Or is it possible to flash a custom recovery (TWRP), make a full back-up, and after that unbrick the phone?
My phone isn't rooted and the bootloader isn't unlocked.
Thanks
Click to expand...
Click to collapse
To touch on the custom recovery idea... To install a custom recovery, you would need an unlocked BL. Even if your device was still able to do the BL unlock command (they locked that down a long time ago, but some have been able to downgrade to a version that allows it still), it wipes the device on BL unlock. Since you are looped, you can't get into ADB to use pull commands for example. I think you are out of luck regarding not loosing data.

sliding_billy said:
To touch on the custom recovery idea... To install a custom recovery, you would need an unlocked BL. Even if your device was still able to do the BL unlock command (they locked that down a long time ago, but some have been able to downgrade to a version that allows it still), it wipes the device on BL unlock. Since you are looped, you can't get into ADB to use pull commands for example. I think you are out of luck regarding not loosing data.
Click to expand...
Click to collapse
OK thanks for your answer. And what about flashing the stock rom of the device through the standard procedure (I saw that I should copy the rom in a folder named dload, press simultaneously volume + and -, and it will flash the rom, am I right?). Is this going to erase all data too?
Moreover, I was trying to connect the phone to the laptot through ADB but I can't see the device when I send the command <adb devices>. Can I solve this or this was what you were talking about here: "you can't get into ADB to use pull commands for example" ?
Thank you

Oloccin said:
OK thanks for your answer. And what about flashing the stock rom of the device through the standard procedure (I saw that I should copy the rom in a folder named dload, press simultaneously volume + and -, and it will flash the rom, am I right?). Is this going to erase all data too?
Moreover, I was trying to connect the phone to the laptot through ADB but I can't see the device when I send the command <adb devices>. Can I solve this or this was what you were talking about here: "you can't get into ADB to use pull commands for example" ?
Thank you
Click to expand...
Click to collapse
ADB only works with a booted ROM, so yeah that was what I was talking about. I'm not sure about that method of flashing stock. I've only seen the update procedure through system and not manually.

sliding_billy said:
ADB only works with a booted ROM, so yeah that was what I was talking about. I'm not sure about that method of flashing stock. I've only seen the update procedure through system and not manually.
Click to expand...
Click to collapse
Ok i understand. Is there any method to install again the original firmware/rom without unlocking the bootloader? Because mine is locked and I would like to keep it

Oloccin said:
Ok i understand. Is there any method to install again the original firmware/rom without unlocking the bootloader? Because mine is locked and I would like to keep it
Click to expand...
Click to collapse
Can you get into stock recovery for a factory reset?