Hello all,
I've been looking for the firmware zip and I couldn't find anything I could use in order to be able to flash CM12. The few files I could find were ones that kept returning "signature verify fail." I'm on the HTC One M8 Developer Edition.
Help is appreciated.
US Developers Edition, or otherwise?
redpoint73 said:
US Developers Edition, or otherwise?
Click to expand...
Click to collapse
US Developers Edition.
shiroi_kage said:
US Developers Edition.
Click to expand...
Click to collapse
S-off or s-on?
redpoint73 said:
S-off or s-on?
Click to expand...
Click to collapse
I don't know what that is so I'm going to assume it's on.
shiroi_kage said:
I don't know what that is so I'm going to assume it's on.
Click to expand...
Click to collapse
If you don't know what it is, then you're right that its most likely s-on. You can check by booting into bootloader, and it will either say s-on or s-off near the top of the screen.
That being the case (s-on), I think you best bet is to run the 3.28 US Dev Edition RUU, which I've seen posted on the AT&T forum section. I'll try to find it, once I have a chance.
http://forum.xda-developers.com/att-htc-one-m8
Backup your personal data before RUU, as your phone will be wiped. Also need to relock bootloader to RUU with s-on.
redpoint73 said:
If you don't know what it is, then you're right that its most likely s-on. You can check by booting into bootloader, and it will either say s-on or s-off near the top of the screen.
That being the case (s-on), I think you best bet is to run the 3.28 US Dev Edition RUU, which I've seen posted on the AT&T forum section. I'll try to find it, once I have a chance.
http://forum.xda-developers.com/att-htc-one-m8
Backup your personal data before RUU, as your phone will be wiped. Also need to relock bootloader to RUU with s-on.
Click to expand...
Click to collapse
So you're saying I have to flash the stock recovery and lock the bootloader? Because right now I have Clockwork recovery and CM11 on the device. RUU.exe faied to update. Is there a signed ZIP for HBOOT anywhere by any chance? Or could I just change it to S-OFF somehow? Please advise.
shiroi_kage said:
So you're saying I have to flash the stock recovery and lock the bootloader? Because right now I have Clockwork recovery and CM11 on the device. RUU.exe faied to update. Is there a signed ZIP for HBOOT anywhere by any chance? Or could I just change it to S-OFF somehow? Please advise.
Click to expand...
Click to collapse
You don't need to flash stock recovery to RUU. But you do need to relock the bootloader since you are s-on. If your bootloader is unlocked, this why the RUU is failing.
---------- Post added at 10:22 AM ---------- Previous post was at 09:59 AM ----------
It seems you've found the Dev Ed RUUs. But in case others reading it want the link: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
redpoint73 said:
You don't need to flash stock recovery to RUU. But you do need to relock the bootloader since you are s-on. If your bootloader is unlocked, this why the RUU is failing.
---------- Post added at 10:22 AM ---------- Previous post was at 09:59 AM ----------
It seems you've found the Dev Ed RUUs. But in case others reading it want the link: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
Took me a while to get back as I go busy.
So should I be using SunShine to unlock this? I found something called FireWater but that shows up as discontinued.
shiroi_kage said:
Took me a while to get back as I go busy.
So should I be using SunShine to unlock this? I found something called FireWater but that shows up as discontinued.
Click to expand...
Click to collapse
I never said to s-off. I said, since you are s-on, do this: relock the bootloader and run the RUU.
Confirm on the bootloader screen whether it says UNLOCKED or RELOCKED.
You don't need s-off to run an RUU for the Dev Edition, if you have the Dev Edition. And as long as the RUU version is not "older" than what is on the phone ("downgrading" not allowed with s-on). As long as you follow the rules (right CID and right version), s-on is fine to run RUU.
s-off certainly opens up more options, but not strictly necessary in your case. Yes, firewater was discontiued, and sunshine is your only option to s-off.
redpoint73 said:
I never said to s-off. I said, since you are s-on, do this: relock the bootloader and run the RUU.
Confirm on the bootloader screen whether it says UNLOCKED or RELOCKED.
You don't need s-off to run an RUU for the Dev Edition, if you have the Dev Edition. And as long as the RUU version is not "older" than what is on the phone ("downgrading" not allowed with s-on). As long as you follow the rules (right CID and right version), s-on is fine to run RUU.
s-off certainly opens up more options, but not strictly necessary in your case. Yes, firewater was discontiued, and sunshine is your only option to s-off.
Click to expand...
Click to collapse
You didn't, you're right. I was thinking of another thing.
Well, I figured it out finally. Toolkit got things relocked and I had to get the unlock token (developer's edition comes unlocked) to restore CM11 with all the apps and use their updater from there.
Thank you so much for the help! I now have wonderful Lollipop running on my phone. Feels great
Related
Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks
Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.
In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks
Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.
No they weren't. I'm just going to stop worrying too much about it. Thanks
If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?
It can be on stock rom/firmware of any version. Just no custom roms or anything.
Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340
What does sunshine do that HTCDev doesn't do? I'm really very confused.
Sunshine S-off's your phone, as well as unlocking the bootloader. HTCdev unlocks your bootloader but leaves security/signing on (S-on) Also, the method Sunshine uses to unlock your bootloader doesn't trip a factory reset.
You don't typically need to turn security/signing off unless you want to change your CID/MID (to convert your handset to a different region) or go back to an older version of firmware/software.
AlecRobertson said:
What does sunshine do that HTCDev doesn't do? I'm really very confused.
Click to expand...
Click to collapse
HTC dev only unlocks the boot loader, sunshine or firewater provides full s off which lifts restrictions to partitions that are normally locked down.
Check the below thread for explanations.
Thread updated
http://forum.xda-developers.com/showthread.php?t=2744194
Thank link is invalid.
Also, I have got s-off previously without using this?
AlecRobertson said:
Also, I have got s-off previously without using this?
Click to expand...
Click to collapse
So in bootloader (or alternately, adb getvar all) it indicates s-off?
If so, and you didn't do firewater or sunshine, then its factory s-off. Its rare, but I've seen it here from time to time.
Hello ,
I have an HTC M8 ( HTC__203 CID ) and i want to bring it back to fully stock. Lock my bootloader and install official ROM.
I follow this GUIDE but i have to be s-off in order to finish it.
http://forum.xda-developers.com/show....php?t=2735235
How can i turn my m8 to S-OFF from S-ON ?
I cant pay SUNSHINE 25$ ..
Is there any other way?
Or any way to lock my bootloader?
Without s-off you can put the flag from UNLOCKED to RELOCKED
only with s-off you can let it show LOCKED. sunshine is the only real (and cheapest) way to s-off the device. No other method available.
The nearest you can get to stock is to run the appropriate RUU with a relocked bootloader. Or restore the matching stock nandroid backup for your device and flash back the stock recovery, then relock the bootloader.
That's about it. Ow yeah and please post questions in the Q&A section next time. This is the GENERAL section.
alexis333 said:
I have an HTC M8 ( HTC__203 CID ) and i want to bring it back to fully stock.
Click to expand...
Click to collapse
The only real reason to return the phone to full stock with LOCKED bootloader is for warranty purpose. Is that what you are trying to do?
If so, then sunshine is the only way to s-off.
redpoint73 said:
The only real reason to return the phone to full stock with LOCKED bootloader is for warranty purpose. Is that what you are trying to do?
If so, then sunshine is the only way to s-off.
Click to expand...
Click to collapse
Yeah something like that. I want to sell it so the person who will take it to have full warranty access.
Thanx both of you. The problem is that in Greece ( where i live ) i dont have the access to my paypal in order to pay Sunshine because of Bank System.
We have Capital Controls so we cant buy anything from outside of our country.
Mr Hofs said:
Without s-off you can put the flag from UNLOCKED to RELOCKED
only with s-off you can let it show LOCKED. sunshine is the only real (and cheapest) way to s-off the device. No other method available.
The nearest you can get to stock is to run the appropriate RUU with a relocked bootloader. Or restore the matching stock nandroid backup for your device and flash back the stock recovery, then relock the bootloader.
That's about it. Ow yeah and please post questions in the Q&A section next time. This is the GENERAL section.
Click to expand...
Click to collapse
So whats the proper RUU to flash. And how can i flash it in relocked bootloader ?
I tried this -> 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
and this one -> One_M8_4.16.401.10_stock_system_dump.zip
but after i type " fastboot flash zip ruu.zip " in the end it shows me this error -> 12 signature verify fail
What does it mean ?
After relocking the bootloader, my phone is doesn't boot to system it just shows the htc logo and goes straight into bootloader.
Here is the info that it shows:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.24.21331147A1.09G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-4.16.1540.8
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
I saw it on this thread that I can download an run RUU to fix this, and I've download this file for my AT&T M8. My question is, will it be all right to run this? I'm just making sure as I don't wanna brick my device. And if this not the way to go, can anyone help me in any way? Any help would be great.
gamesprin said:
After relocking the bootloader, my phone is doesn't boot to system it just shows the htc logo and goes straight into bootloader.
Here is the info that it shows:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.24.21331147A1.09G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-4.16.1540.8
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
I saw it on this thread that I can download an run RUU to fix this, and I've download this file for my AT&T M8. My question is, will it be all right to run this? I'm just making sure as I don't wanna brick my device. And if this not the way to go, can anyone help me in any way? Any help would be great.
Click to expand...
Click to collapse
That's the wrong RUU. You need this one.
1. But my HTC One M8 is AT&T, don't I need one for that?
2. Will it be all right if I do this? Will I brick my phone or damage the software in any way?
gamesprin said:
1. But my HTC One M8 is AT&T, don't I need one for that?
2. Will it be all right if I do this? Will I brick my phone or damage the software in any way?
Click to expand...
Click to collapse
You have the Developers Edition model of the M8, which was sold by AT&T. You can tell that from your firmware version (OS) in your bootloader readout.
Regular AT&T models will show the firmware version being x.xx.502.x
Dev Ed model will show x.xx.1540.x
You won't damage your phone, but you might have to flash the firmware first before running the RUU if it fails. I'm not sure where to find a signed firmware (you need signed if S-On) but you could search for it.
Try running the RUU first to see if it works. You won't brick, you'll just get an error and the installation will abort if it won't work (if you need to flash the firmware first).
You could also try out the methods in this thread to return to stock ROM and recovery, and update via the official OTA.
Okay, thank you very much.
I'll try the RUU first and see what happens. Thanks again.
xunholyx said:
......I'm not sure where to find a signed firmware (you need signed if S-On) but you could search for it.
Click to expand...
Click to collapse
Post #5 in my backup thread is MM signed firmware collection.
ckpv5 said:
Post #5 in my backup thread is MM signed firmware collection.
Click to expand...
Click to collapse
Cool! I haven't been in your OP for a while now. Very nice addition.
Hey, I got a 155 error saying RUU can't update my phone, I need to download the proper RUU. Please help me. I'm freaking out.
EDIT: I found this from this site, saying that 617 has replaced 1540 after the M9, maybe i need to download another RUU?
gamesprin said:
Hey, I got a 155 error saying RUU can't update my phone, I need to download the proper RUU. Please help me. I'm freaking out.
Click to expand...
Click to collapse
Crap! I forgot to tell you that since you are S-On you will need to relock your bootloader first
In fastboot: fastboot oem lock then run the RUU again
xunholyx said:
Crap! I forgot to tell you that since you are S-On you will need to relock your bootloader first
In fastboot: fastboot oem lock then run the RUU again
Click to expand...
Click to collapse
Did it. says 'bootloader already locked". Sorry for not including this info in the previous reply.
i guess, this has made s-on after flashing wrong firmware. (MID has changed or has flashed modified firmware; you or someone else). you have to s-off again to flash ruu.
post a fastboot getvar all without S/N & IMEI to see exactly what has happened.
gamesprin said:
I found this from this site, saying that 617 has replaced 1540 after the M9, maybe i need to download another RUU?
Click to expand...
Click to collapse
This is for the M9 and devices made after (M10). This doesn't apply to the M8.
The RUU linked by xunholyx is the right one.
Did you try to flash the stock firmware (6.12.1540.4) then the RUU, as already advised?
---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------
gamesprin said:
1. But my HTC One M8 is AT&T, don't I need one for that?
Click to expand...
Click to collapse
How do you know its the AT&T version? Does it have the AT&T "globe" logo on back cover?
If so, it was probably s-off at one time, than had its CID changed, and RUU flashed to "convert" it to US Developer's Edition software.
You need to flash the RUU that matches the current CID, it doesn't matter what it was "originally". And most folks won't want the AT&T bloat and limitations, anyway.
After getting the error, I flashed the firmware mentioned here.
After that the RUU ran flawlessly.
Hi everybody,
I'm sorry, I'm sure this question may be asked so much time, but after 1 hour searching I don't find anything usefull for me... (Maybe a keywork issue ?)
I don't know what I've done, but after I locked again the bootloader in order to flash on a RUU, I blocked my HTC 10 and can't boot on android again.
When I tried it the phone is only going to bootloader mode and don't want to get to my Os. I have TWRP and was on the custom LeeDroid 7.0.
I can't backup or do anything and while i try the dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota on the terminal, it won't work...
And I can't unlock again the phone, I've tried and it's "relocked".
Has someone have the same issues ? Really need your help ! :crying:
Thank you !
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
You might wanna try using a RUU.exe to get your OS back. What firmware and model do you currently have?
bamidrol said:
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
Click to expand...
Click to collapse
Yes it was lol...
But i've read that it was better to be on a locked bootloader to flash ruu :crying:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Tech_Savvy said:
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Click to expand...
Click to collapse
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------
hadory said:
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
Click to expand...
Click to collapse
The download mode works, bootloader too
I'm not able to flash with an unlocked or a locked bootloader, i've tried the RUU and the custom ROM like Leedroid for example.
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
Click to expand...
Click to collapse
I don't think it's the US MID, my IMEI is German and the phone works great on 4G / LTE in France (where I live) and i've read that 4G won't work with an US version in France, but maybe you're true and their is no RUU for my version ... (fragmentation pleasures).
Do you know how i can s-off this phone in order to change those CID which block me ? ^^' because i can't use sunshine bc no OS installed and can't flash one ...
In fact, the only think i can flash / unflash is TWRP and the recovery stock..