I have gone back to stock also back to S on, that part was by mistake. I don't seem to have any recoveries either, I just get the red exclamation mark when I boot to recovery. I have tried to flash both stock and TWRP but get the same error message.
FAILED cannot flash this partition in s-on state.
This happens with both stock and TWRP recoveries.
Has anyone seen this before and what steps can I do to make it work?
potsykate said:
I have gone back to stock also back to S on, that part was by mistake. I don't seem to have any recoveries either, I just get the red exclamation mark when I boot to recovery. I have tried to flash both stock and TWRP but get the same error message.
FAILED cannot flash this partition in s-on state.
This happens with both stock and TWRP recoveries.
Has anyone seen this before and what steps can I do to make it work?
Click to expand...
Click to collapse
Try flashing an SD card RUU.
deakelem said:
Try flashing an SD card RUU.
Click to expand...
Click to collapse
I would but I cannot find a RUU for European version.
Would the zip version from here be the same?
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
potsykate said:
I would but I cannot find a RUU for European version.
Would the zip version from here be the same?
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Click to expand...
Click to collapse
Just flash any RUU to begin with. That will at least give you a recovery. Your only choice is an RUU at this point. (that matches your CID/MID) You are softbricked for sure right now. Sounds like you re-locked your bootloader as well as you are s-on. Otherwise you'd be able to flash a recovery.
tabp0le said:
Just flash any RUU to begin with. That will at least give you a recovery. Your only choice is an RUU at this point. (that matches your CID/MID) You are softbricked for sure right now. Sounds like you re-locked your bootloader as well as you are s-on. Otherwise you'd be able to flash a recovery.
Click to expand...
Click to collapse
There is no RUU for Europe, as far as I know. I have restored the phone earlier and am able to boot it up and use it normally. It's just that I cannot instal a recovery no matter what.
potsykate said:
There is no RUU for Europe, as far as I know. I have restored the phone earlier and am able to boot it up and use it normally. It's just that I cannot instal a recovery no matter what.
Click to expand...
Click to collapse
Try using sunshine to s-off
tabp0le said:
Try using sunshine to s-off
Click to expand...
Click to collapse
I've thought of that. I originally used sunshine to go S-off and had a chat with them earlier and went S-on, accidentally. As I've paid for Sunshine once, do I have to pay again. I'm on the same phone so hopefully not.
The sunshine faq states that you can reuse the same license you purchased as long as you're on the same phone. So installing sunshine again should do the trick
Tarima said:
The sunshine faq states that you can reuse the same license you purchased as long as you're on the same phone. So installing sunshine again should do the trick
Click to expand...
Click to collapse
Thanks for that, I did the sunshine again and went for unlocked S-off. I have now installed TWRP 3026 and downloading Viperrom 3.4 to install. I did have a full backup but formatted my SD card so I've got to start again.
Umm the red exclamation mark is stock recovery. You have to press a combination of buttons to enter it. I think its up and down on the volume
Related
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
chowdyg said:
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
Click to expand...
Click to collapse
What country are you in, which network are you on and did you buy your phone sim free?
If you go into fastboot mode and then boot into CWM using the command:
fastboot boot <CWM img file>.img
You'll then be able to use adb to push the rom zip onto your device which you can then flash with CWM.
If the RUU says you have the wrong version you probably have the RUU for another region/carrier.
It's pretty much impossible to permanently brick the one x (without s-off) so don't worry, you'll get it working eventually.
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
chowdyg said:
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
Click to expand...
Click to collapse
Which RUU did you download?
rogersnm said:
Which RUU did you download?
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
chowdyg said:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
Click to expand...
Click to collapse
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
rogersnm said:
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
Click to expand...
Click to collapse
Thanks so much!!
but i have already relocked the bootloader without flashing the recovery image ... would that make a difference?
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
rogersnm said:
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
Click to expand...
Click to collapse
Thanks again. but how do i do it with the bootloader locked
chowdyg said:
Thanks again. but how do i do it with the bootloader locked
Click to expand...
Click to collapse
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
rogersnm said:
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
Click to expand...
Click to collapse
now it is saying error 170. whenever i try to flash something it just says waiting for device
chowdyg said:
now it is saying error 170. whenever i try to flash something it just says waiting for device
Click to expand...
Click to collapse
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
rogersnm said:
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
Click to expand...
Click to collapse
Thank you so much!! problem solved!!
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware
So what is stopping me from flashing new firmware each time?
yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?
xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.
xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.
yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.
xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.
yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.
Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:
Hi guys. I just bricked my HTC one m9. I was trying to get it back to stock while I had a custom rom, and I set s-on back to true and locked the bootloader..
Fastboot DOES work.
I cannot enter the custom recovery mode, it says that it failed to boot to recovery.
I cannot boot into my custom rom.
I DO have an SD card. I tried to flash the RUU "0PJAIMG.zip", but it said "failed to flash downloadzip" and didn't flash..
What should I do at this point? I don't want $700 down the drain
1) What is your CID?
2) you flash RUU via SDcard?
3) If you ever got your phone back to normal. DO NOT ATTEMPT TO TURN S-OFF BACK TO TRUE, AND LOCKED YOUR BOOTLOADER. BECAUSE ITS NOT NEEDED AT ALL.
I tried to flash an RUU via SD card, but it gave me that error posted above.
My CID is 11111111
OfficialBlox said:
I tried to flash an RUU via SD card, but it gave me that error posted above.
My CID is 11111111
Click to expand...
Click to collapse
What's your actual firmware version? (The one that is stated in Download Mode in the line with "OS" at the beginning?)
once i auto-bricked my phone, ereasing everuthing with twrp, everything......i did enter into bootloader i guess or download mode (dont remeber very well) and with cid BS_US001 i did flash a Ruu-Zip for developer 2.8 and the after that i could restore everything....hopefully yoiu can do the same
Flippy498 said:
What's your actual firmware version? (The one that is stated in Download Mode in the line with "OS" at the beginning?)
Click to expand...
Click to collapse
My OS is 2-8.617.4
OfficialBlox said:
My OS is 2-8.617.4
Click to expand...
Click to collapse
This might be the RUU you need. (2.11.617.15) Its a newer version of 2.8.617.4
Credits clsA
xunus said:
This might be the RUU you need. (2.11.617.15) Its a newer version of 2.8.617.4
Credits clsA
Click to expand...
Click to collapse
Thanks. So does it matter if I am s-on and locked bootloader?
Also, I have an SD card so that's good.
OfficialBlox said:
Thanks. So does it matter if I am s-on and locked bootloader?
Also, I have an SD card so that's good.
Click to expand...
Click to collapse
Because this is a official RUU for the .617. Which matches your OS version. I can only hope it works since you are S-ON and LOCKED
xunus said:
Because this is a official RUU for the .617. Which matches your OS version. I can only hope it works since you are S-ON and LOCKED
Click to expand...
Click to collapse
Okay, I'm currently downloading the file. Let's hope it works. thanks.
OfficialBlox said:
Thanks. So does it matter if I am s-on and locked bootloader?
Also, I have an SD card so that's good.
Click to expand...
Click to collapse
If you're using the SD Card method it doesn't matter at all whether your bootloader is locked or not. And as long as the RUU is the same version as your actual firmware (or if the RUU is newer) it doesn't matter whether your phone is S-ON or S-OFF.
The SD card has to be formated to fat32 and mustn't be bigger than 32gb. Copy the RUU to the main directory of the card and rename it to "0PJAIMG.zip" (that's a zero not an O). If you then put the card back into your phone and reboot to download mode you just have to follow the instructions on the phone's screen.
Let's say I were to flash the wrong firmware version RUU (which I did, and the installation failed), would it say something like "failed to flash zip downloadzip", because that's what it said.
OfficialBlox said:
Let's say I were to flash the wrong firmware version RUU (which I did, and the installation failed), would it say something like "failed to flash zip downloadzip", because that's what it said.
Click to expand...
Click to collapse
Which method did you use? If you used the SD Card method: Are file extensions visible on your pc? If not the file may be named "0PJAIMG.zip.zip" now...
I used the SD card method, but the firmware version was wrong. I just want to know if it would stop me with an error, instead of actually installing the RUU.
OfficialBlox said:
I used the SD card method, but the firmware version was wrong. I just want to know if it would stop me with an error, instead of actually installing the RUU.
Click to expand...
Click to collapse
Since you're S-ON you can't harm your phone with a "wrong" RUU. If it's incompatible it simply won't flash.
Edit with some alternative solutions: There is a RUU.exe for your specific firmware on ir-file. But you need to pay if you want to download there. (At least if there is no xda member who already has an account and is willing to help.) Or you try this RUU Service. But that one isn't for free, either.
OfficialBlox said:
Okay, I'm currently downloading the file. Let's hope it works. thanks.
Click to expand...
Click to collapse
Ohh my, locked and Son...May the force be with you...always.
I do believe the only option would be to download a Ruu-EXE from HTC Developers and run it from PC, also phone must connected in download mode or recovery, hopefully you do it for good.................
OR.....................................MAKE USE OF THE UH-OH GUARANTEE, step the phone under the water for 20 mins or crush the screen and take it to your vendor, they should replace phone with no questions for one completly new as guarantee states!!!!!
In Mexico, Telcel they do Honor this special guarantee
LLegion said:
Ohh my, locked and Son...May the force be with you...always.
I do believe the only option would be to download a Ruu-EXE from HTC Developers and run it from PC, also phone must connected in download mode or recovery, hopefully you do it for good.................
OR.....................................MAKE USE OF THE UH-OH GUARANTEE, step the phone under the water for 20 mins or crush the screen and take it to your vendor, they should replace phone with no questions for one completly new as guarantee states!!!!!
In Mexico, Telcel they do Honor this special guarantee
Click to expand...
Click to collapse
So the RUU.zip that someone linked me won't work? I just spent hours downloading it lol
OfficialBlox said:
So the RUU.zip that someone linked me won't work? I just spent hours downloading it lol
Click to expand...
Click to collapse
I could be wrong but I would say it should work. I don't see a reason why it shouldn't.
OfficialBlox said:
So the RUU.zip that someone linked me won't work? I just spent hours downloading it lol
Click to expand...
Click to collapse
If you met all the conditions listed by @Flippy498 in post #11 it will work just fine
also the newest Developer Edition RUU can be found here direct from HTC >> http://www.htc.com/us/support/htc-one-m9/news/
Stupid mistake, just trying to get a usable phone back, dunno how.
Rooted it, Recovery TWRP.
decided want a custom rom, Android Revo 20.
didnt backup, woops.
was useless, googled, needed different firmware, flashed that somehow.
phone got worse.
reinstalled TWRP
tried to download a backup, 2 even, both dont work.
not sure what to do. think i need another firmware before the backup would work.
any advice will help
currently phone turns on straight to bootloader. can access download mode and recovery.
Bootloader unlocked, S-ON, HTC__J15,
iSammyJ said:
Stupid mistake, just trying to get a usable phone back, dunno how.
Rooted it, Recovery TWRP.
decided want a custom rom, Android Revo 20.
didnt backup, woops.
was useless, googled, needed different firmware, flashed that somehow.
phone got worse.
reinstalled TWRP
tried to download a backup, 2 even, both dont work.
not sure what to do. think i need another firmware before the backup would work.
any advice will help
currently phone turns on straight to bootloader. can access download mode and recovery.
Click to expand...
Click to collapse
Do you have google hangouts or whatsapp? i could help you out.
no =/
well yes i have whatsapp, but no working phone to use that.
Try ruu back to stock?
tried didnt work. still boots directly to bootloader
iSammyJ said:
tried didnt work. still boots directly to bootloader
Click to expand...
Click to collapse
Are you S-OFF?
Did the RUU complete successfully or give you an error?
Was the firmware you flash for your Model M9 or another one?
Tachi91 said:
Are you S-OFF?
Did the RUU complete successfully or give you an error?
Was the firmware you flash for your Model M9 or another one?
Click to expand...
Click to collapse
S-ON unfortunately
RUU failed. error. will try others tomorrow.
I got the firmware off Android Revolution site. I think it was correct.
iSammyJ said:
S-ON unfortunately
RUU failed. error. will try others tomorrow.
I got the firmware off Android Revolution site. I think it was correct.
Click to expand...
Click to collapse
What's your Model?
If youre S-OFF and firmware/RUU are not helping. You're probably trying to flash the wrong ones.
Tachi91 said:
What's your Model?
If youre S-OFF and firmware/RUU are not helping. You're probably trying to flash the wrong ones.
Click to expand...
Click to collapse
HTC__J15?
3.35.401.12 firmware should work with your Cid,
Which version of O.S did you read in download mode?
bzhmobile said:
3.35.401.12 firmware should work with your Cid,
Which version of O.S did you read in download mode?
Click to expand...
Click to collapse
1.32.401.17
I tried to use 3.35.401.12 backup but it still booted to bootloader
You have to flash 3.35.401.12 firmware in download mode before using the backup
and i cant flash firmware while S-ON right? i think i tried flashing higher firmware and it gave me that error.
so ill find 1.32.401.17 backup or rom and that should work?
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.