Database Develop

Boot loop prior to rooting or s-off, on stock, can't get to main screens

Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.

Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.

MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.

make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.

Thanks pal, fingers crossed eh.
Will let you know if it worked.

It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.

if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.

MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?

dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.

What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.

factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM

Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.

Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.

Lol failed battery low

MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.

I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.

MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.

[Q] Assistance required with altered N1

I recently came across a modified Google Nexus One (N1) that has been experimented on. Upon boot up, I get a black screen with the HTC logo and four exclamation marks inside triangles in each of the four corners of the screen. As I attempted to enter hboot, I saw it has been replaced with Blackrose which leads me to believe it has been unlocked/rooted at some point in time. ( I am fairly new at this, but I lurk around the forum ). I tried hooking the N1 up to RUU to flash it back to a stock ROM, however that proved unsuccessful - the phone boots up to the above mentioned logo and stays that way. When I try to go to recovery/hboot, instead of the usual menu choices, there's only RUU as an option... Is the phone bricked, and if not, how can I revert it to a working state ?
I have attached pictures of what the boot screen looks like, as well as the recovery menu.
Thank you in advance.

It's in the middle of RUU mode, entered by executing "fastboot oem rebootRUU" (I might not remember it 100% correct, so check it with Google).
This should be enough for you to check with Google how you exit RUU mode.

The only way I see to exit this mode is if I flash it with something via fastboot ( since no recovery works, custom or stock ). What image file or zip do I flash it with, in order to revert it back to complete stock ( stock hboot, stock recovery, stock ROM ) - I want the phone like it was out of the box, so I can reroot it and unlock it myself.
I tried flashing it with PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip through fastboot, for a moment it seemed to be going ok, then at the very end, while it was unpacking the [user data] image I get a partition update fail message 51, and after reboot - still the gray HTC letters and Blackrose instead of HBOOT.
Any suggestions ?

Short googling with the error would have revealed you the bad news.
Partition update fail means bad stuff - your NAND is malfunctioning, which equals a dead phone.

Have you tried to uninstall Blackrose?

tommert38 said:
Have you tried to uninstall Blackrose?
Click to expand...
Click to collapse
doesn't the phone need to be working in order for me to hook it up to Blackrose ? As of now, with this screen, the PC doesn't seem to detect it as a working phone, only fastboot. And Blackrose just says waiting for device... how do I uninstall it then?
I also tried this RUU: RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release, flashing the ROM to an image version 3.11.151.3, but at the end I get a message saying ERROR [110]: FILE OPEN ERROR. The RUU cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again. Can someone please refer me to a working RUU package for the Nexus One, I am really scared of experimenting trying to find one by myself, seeing how the phone is already hanging in the balance, I would be thankful

You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT

tommert38 said:
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
Click to expand...
Click to collapse
Thanks for your time friend, I tried the above mentioned steps, it says OK all across the board in fastboot while I flash, but after I reboot it just goes back to the same screen, stuck in RUU. I did some digging around and found this which seems to be exactly my problem:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
However, this is from a thread for the HTC Bravo. Anything similar for the N1 ?
Edit1: Could it be that the hboot partition was resized with Blackrose and therefore the RUU I tried to flash it with needs stock partition layout ?

Your partitions ARE resized. 2nd picture 2nd line JB-220/10/206. If it's b*tching about the resized partitions, then that would be about your cache partition (which is 85MB smaller than its stock size).
Edit: you should also try to wipe your partitions with fastboot, then flash the img's that are inside the passimg

what's the command line to wipe the partition ? fastboot format hboot/recovery/system ?

Dude, your Nexus One is dead, the internal NAND is damaged and therefore unrecoverable.
Sent from my Nexus S using Tapatalk 2

fastboot erase system/cache/userdata/boot

My HTC One is screwed?

Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.

Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.

MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this

MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry

[Q] Help me unbrick my htc one please?

im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:

ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.

ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.

Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app

Can't boot recovery via fastboot

I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?

acejavelin said:
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
Click to expand...
Click to collapse
Only hboot 1.44 will boot recovery .. all the others need to be flashed
TWRP 2.6.3.3 is the most stable
TWRP 2.8.4.0 is what I use with no problems

clsA said:
Only hboot 1.44 will boot recovery .. all the others need to be flashed
Click to expand...
Click to collapse
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?

acejavelin said:
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
Click to expand...
Click to collapse
it was patched in the hboot to not allow it

clsA said:
it was patched in the hboot to not allow it
Click to expand...
Click to collapse
I guess I can see why they would do that, sort of, not that I agree... On my old HTC Rezound you could boot recovery and backup, wipe caches, etc, as long as you didn't write to boot/system/etc, without triggering the TAMPERED flag, you had to flash recovery or write to a system partition in order to set that flag. Oh well, Ill flash it up soon and play with it. I am actually kind of liking the stock lollipop Sense ROM, might just leave it like that for a bit though. Just came back from the range and had a little time before work so I was playing with it and it kind of frustrated me.
Thanks for your help and info.