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.
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!!
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
blankfile99 said:
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
Click to expand...
Click to collapse
you installed an OTA?
I'm using a Stock from a recovery Nandroid, not mine but the same CID 044... I guess I shold go back to RUU...but I've tried without any success
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
blankfile99 said:
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
Click to expand...
Click to collapse
you are on JB now and you can't run ICS RUUs, you can't downgrade...
matt95 said:
you are on JB now and you can't run ICS RUUs, you can't downgrade...
Click to expand...
Click to collapse
I'm not...I'm on 2.17 yet...JB update does not install...that's the main problem
and I have noticed that NO MATTER I CHANGE...IT WONT CHANGE THIS VERSION... OMG
tks man!
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Sentinel196 said:
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Click to expand...
Click to collapse
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Also, this may sound silly but did you reflash stock RECOVERY?
blankfile99 said:
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Click to expand...
Click to collapse
No worries, let us know how you go, and don't forget the Thanks button.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Well I am currently running Team Venom's Viper but I have HBOOT 1.31. My device's CID is HTC_J15.
I have checked the list of RUUs but unfortunately all of them are older than the version I need, which has to be 3+.
Does anybody know if there's an RUU available for my device? It is an ubranded WWE version, 401 if I remember correctly.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
I'm using the same as the NANDROID, taken from it...right?
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
That's all I need... I'll give my feedback later.
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
In my experience the 2.17.707.xx RUU Asia WWE does not work properly. It does its thing installing everything, relocks the bootloader but somehow it does not reflash the recovery. After 4 hours trying everything under the sun, I gave up and looked for a nandroid of 2.17 for CID_044 and restored from that, reflashed stock recovery and went to town with the OTA.
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Refer custom to stock thread posted earlier. Go through step by step procedure. It will help u to be on stock Rom. After that flash any Rom suitable to your CID only
http://forum.xda-developers.com/showthread.php?t=1859714
Hit Thanks if u like.
Sent from my HTC One X using xda app-developers app
Got It guys!!
What I did... NOTHING else...
Only Reboot the phone...wait to initialize completely, then reboot again, when came a little update about 1.25mb...installed and reboot...after that...JB update installed correctly.
If someone else needs...Someone like me who relocked the phone waiting for JB and Has problems
1. Unlock Phone
2. fastboot flash recovery recovery.img (from nandroid 2.17)
3. fastboot flash boot boot.img (from nandroid 2.17)
4. fastboot erase cache
5. restart bootloader (I like to do this way)
6. Install RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed on windows
7. Wait to boot completely, then restart phone.
8. Update Software ...a little update came before JB. (about 1.25mb)
9 Reboot phone.
10. Update Software... finally to JB.
Thanks guys!
Sentinel196 said:
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Click to expand...
Click to collapse
The RUU ran with no problem, and it relocked my bootloader, but it still did not receive any OTAs. So I had no choice but to do a nandroid restore instead (recommended anyway )
Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
korbs710 said:
Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
Click to expand...
Click to collapse
What ROM, what recovery version, what firmware version, what model version, are you S-ON or S-OFF, did you do a clean flash or dirty flash? and the wipe is preferably before the ROM installation in my experience.
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
korbs710 said:
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
Click to expand...
Click to collapse
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
BUBBA DUB'S said:
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
Click to expand...
Click to collapse
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
korbs710 said:
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
Click to expand...
Click to collapse
Do you have the OEM lock disabled?
DeadPotato said:
Do you have the OEM lock disabled?
Click to expand...
Click to collapse
Says Unlocked on the Bootloader screen. Is that what you mean?
korbs710 said:
Says Unlocked on the Bootloader screen. Is that what you mean?
Click to expand...
Click to collapse
Go into settings, developer options , and then look for OEM lock setting.
BUBBA DUB'S said:
Go into settings, developer options , and then look for OEM lock setting.
Click to expand...
Click to collapse
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
BUBBA DUB'S said:
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
Click to expand...
Click to collapse
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
korbs710 said:
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
Click to expand...
Click to collapse
I am not sure @DeadPotato do you know if it's ok to go backwards with an RUU regarding firmware?
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
iElvis said:
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
Click to expand...
Click to collapse
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
korbs710 said:
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
Click to expand...
Click to collapse
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
iElvis said:
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
Click to expand...
Click to collapse
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
korbs710 said:
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
Click to expand...
Click to collapse
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
iElvis said:
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
Click to expand...
Click to collapse
No, I did not select Allow OEM Unlocking. So am I screwed then? I am trying to flash Maximus 6.0 but if it doesn't work I don't want to fully lock the device by trying the RUU.
BUBBA DUB'S said:
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
Click to expand...
Click to collapse
Ya I was going to gladly pay the 25 bucks if it meant being able to use my phone and supporting the devs is good.
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
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.