Database Info

Help - stuck, hopefully didn't brick my phone

Hi all,
I hope one of you masterminds is able to help me out.
I tried to root my sensation without s-off with hecdev.com (using One_X_All-In-One_Kit_v1.0) and then tried to install cm9 from one the links here via revcovery with CWM 5.8.0.9.
But then I was stuck with the loading animation...
I cannot run Android now, so I cannot flash a stock RUU.
I can enter bootloader, which seems to be unlocked, here's the info:
"Unlocked"
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
I was on the latest official ROM (ICS, via OTA) before trying that.
I have not succeeded in flashing a ROM anymore.
Do I need to get S-Off first?
Or is HBOOT to new? Do I have to revert? How?
I tried older HBOOT, but it wouldn'T do anything after PArsing
Please help, any hint is appreciated =/

PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time

the_bmg said:
PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time
Click to expand...
Click to collapse
Hi,
Start again using THIS GUIDE

Flash the boot.img from your ROM through fastboot.
Extra step 1 from this guide: http://forum.xda-developers.com/showthread.php?p=25587345
Be sure to use the boot.img from your ROM.
Then make a clean install of the ROM again.
Also, read that thread for the sake of understanding what you're doing.
There is NO need yet to flash an RUU.

Latest OTA comes with hboot 1.29 which is locked.
You might not be in the latest one, perhaps start with an RUU with.the latest fw (3.33).
Sent from my HTC Sensation using xda premium

thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up

@Raven2k: Manually installing boot.img with fastbok seemed to help, at least I come over the white screen, am stuck with the beatsaudio logo right now - thanks so far =)

the_bmg said:
thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up
Click to expand...
Click to collapse
Can you try this again
Flash boot.img again as kgs explained
Then flash the rom again... Don't do any wipe
Sent from my pyramid.. Through blazing fast sonic waves

Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:

the_bmg said:
Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:
Click to expand...
Click to collapse
good
and for thanks ..there is a button for that

Stuck in Bootloop

Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.

We need more details .....which kernels did you flash ??

I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.

sagarsaoji said:
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
Click to expand...
Click to collapse
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE

malybru said:
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
Click to expand...
Click to collapse
I flashed a RUU through the rom.zip. The process seemed to be stuck at step [4] System for quite a while, kept unzipping and updating over and over again. It eventually completed but now I'm stuck in bootloop with a large BEEP sound after "htc simply brilliant" screen, then phone reboots and have to pull the battery out. PLEASE HELP ME

Did you install stock kernel ??
Because some roms need specific kernels which only work on the Rom and your going to stock so its not gonna boot

sagarsaoji said:
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
Click to expand...
Click to collapse
IS the Phone S-OFF?
This step is extremely important, because we are not s-off and there is a problem with creating the "boot.img". T-Macgnolia explained it nicely:
When you use HTC Dev to unlock your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read those partitions. But there is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the .zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed the New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
Click to expand...
Click to collapse
There are 2 ways to enable smartflash, one is a temporary way inside the 4EXT recovery itself (only for first time!) and the second way is permanent, through the 4EXT application.
The permanent way can only be enabled if your phone has ROOT! It's impossible to do it when you are going to flash a ROM for the first time.
Once you have flashed your ROM you have to install the 4EXT application and enable smartflash through it, which is explained in Step 5.
3A. Enable 4EXT Temporary smartflash
Enabling this is as simple is getting into the recovery and enabling it as an option.
NOTE: You only need to do this right before flashing your first ROM, so you should skip this step and come back here when the guide tells you to.
Disable "Fast Boot" on your phone.
Code:
Settings
Power
Untick "Fast boot"
Turn off your phone
Hold the Power AND Volume Down button until you see a white screen which says: "Fasboot".
Navigate to "RECOVERY" and select it, you should now boot into the 4EXT recovery
Select "Tools"
Scroll Down and select "Enable 4EXT SmartFlash"
Again, you only need to do this ONCE, once you have flashed your first custom ROM and enabled permanent smartflash, you don't need to this any more!
Click to expand...
Click to collapse
Source
Hope I am not talking nonsense

wetfoot said:
IS the Phone S-OFF?
Source
Hope I am not talking nonsense
Click to expand...
Click to collapse
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?

Sure thing .......
Do you know how to get the stock kernel from the ruu ?

sagarsaoji said:
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Click to expand...
Click to collapse
Hi,
The RUU contains a stock ROM ,recovery,kernel,firmware,and radio.
It should be the only thing you need to flash/run.
I do not know why the RUU did not work.
Now that it is "Locked", then you cannot flash an RUU with version less than your phone's current version.
The RUU should reset all your partitions,(Except s-off), and restore your phone to stock.
If your current version is the same as the RUU,try running it again by doing it manually (section 4 in the guide)

Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
EDIT: just some further info...can't get adb to find device even though it is in fastboot usb mode..any way to get that working?

sagarsaoji said:
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
Click to expand...
Click to collapse
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.

malybru said:
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
Click to expand...
Click to collapse
Still not booting, making a beep after "simply brilliant" screen and reboots constantly. I was able to get ADB to finally work. I also followed Step 4 from the guide but even after the RUU flashes completely the phone is stuck in bootloop.

[Q] Cannot flash any roms!

I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!

Flashing boot.img did not work. I'm in bootloop hell.

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app

Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".

Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita

mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE

ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.

mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE

ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*

[Q] Stuck on Hboot/fastboot with full stock phone

Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French

As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.

Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.

Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?

Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.

eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk

Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation

Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.

Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation

He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.

old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.

Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?

old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822

Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks

To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!

old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?

Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk

eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?

Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)

eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.

Cant boot sense roms and some recovery

Ok guys, I've flashed a lots of device in the past, now I'm selling my Samsung S4 and buy this HTC ONE S from a friend. I like the phone a lot, I did s off with moonshine (gave error but in the end its finish).
I flash CM11, everything good, but, the camera is so slow to take picture. My friend told me that before that, it was ok (in stock roms). So, I decided to try a sense rom, I choose liberty rom, The rom flashed ok, but, Never boots, stucks on HTClogo, and restart.
I was with philz_touch_6.19.3-ville, so I decide to flash openrecovery-twrp-2.7.0.0-ville. But still the same problem.
Then I try those recovery: openrecovery-twrp-2.6.3.0-ville and openrecovery-twrp-2.6.1.0-ville. It doesnt even boot, only restart.
If I flash CM11 again, it will boot, but the camera is slow and i want a sense rom. In Hboot show this
Moonshine S-OFF
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.15.4444
RADIO-1.35a.32.45.27
OpenDSP-v31.1.0.45.08.15
eMMC-boot
Dec 14 2012, 17:10:57:-1
I was thinking if upgrade to Hboot 2.16 was good, but not sure. Any advice?
PD: The g-Sensor and camera flash light dont work but is hardware, just said it if that helps in something
PD2: Ok, the slow camera was because I had the flash on, and is damage, so thats make the camera slow, I deactivate and now takes picture fast. But still, want a sense rom
PD3: I try this recovery twrp-2.7.0.8-ville.img but nothing I flash the rom, but again bootloops. I get that recovery from here http://mdmower.cmphys.com/twrp-ville/

What about running last ruu ? You're on hboot 2.15 so no need to downgrade.
Before running flash stock recovery with fastboot

benJX said:
What about running last ruu ? You're on hboot 2.15 so no need to downgrade.
Before running flash stock recovery with fastboot
Click to expand...
Click to collapse
Yes, but what about 2.16? I have this RUU RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
that is what I need? What about s-off? Or the unlocked bootloader? I will lose it?

Hboot 2.16 is needed only if you want to run MaximusHD (this rom is NOT compatible with any other hboots).
Viper rom and Liberty are compatible with both 2.15 & 2.16.
I would add that CM11 is not officialy made for 2.15 hboot. If you want CM11 on 2.16 there are unofficial build made for this. Just in case you would came back to CM11 if you uprgrade to 2.16. Most of the AOSP based roms released here are made for 2.15.
So to resume, if you want a Sense 4+ rom, just run the ruu you told me and it should be fine (flash stock recovery before). If you want to switch to AOSP, no problem. If you want some Sense 5 or Sense 5+ try Viper or retry Liberty.
But if you want MaximusHD you will have to upgrade (all is explained in the rom thread). This is, in my opinion, the best rom so far released for our phone. Stock feeling but tweakable with Sense 5 Toolbox (xposed module). I advise you to try it at least and if you don't like it, just downgrade you hboot, no problem for doing this.
About recoveries, for 2.16 you need a modded 2.6.1.0 TWRP recovery (the only one for this hboot I think, everything is explained in MaximusHD OP). With this hboot and recovery you cannot mount your sdcard from recovery.
In 2.15 I used to use 2.3.3.0 TWRP, no issues in sdcard mounting. Whan I was on 2.15 I had some issues with newer versions. Since I'm on 2.16 I didn't try 2.6.X.X and 2.7.X.X with this hboot.
Good luck to make your choice, it's hard lol

benJX said:
Hboot 2.16 is needed only if you want to run MaximusHD (this rom is NOT compatible with any other hboots).
Viper rom and Liberty are compatible with both 2.15 & 2.16.
I would add that CM11 is not officialy made for 2.15 hboot. If you want CM11 on 2.16 there are unofficial build made for this. Just in case you would came back to CM11 if you uprgrade to 2.16. Most of the AOSP based roms released here are made for 2.15.
So to resume, if you want a Sense 4+ rom, just run the ruu you told me and it should be fine (flash stock recovery before). If you want to switch to AOSP, no problem. If you want some Sense 5 or Sense 5+ try Viper or retry Liberty.
But if you want MaximusHD you will have to upgrade (all is explained in the rom thread). This is, in my opinion, the best rom so far released for our phone. Stock feeling but tweakable with Sense 5 Toolbox (xposed module). I advise you to try it at least and if you don't like it, just downgrade you hboot, no problem for doing this.
About recoveries, for 2.16 you need a modded TWRP recovery (the only one for this hboot I think, find it in MaximusHD thread). With this hboot and recovery you cannot mount your sdcard from recovery.
In 2.15 I used to use 2.6.3.0, I had problems with newer versions.
Good luck to make your choice, it's hard lol
Click to expand...
Click to collapse
Ok, I will try that rom, But I will not my S-off? And is easy to change between hboot? and yes, a lot recommended 2.6.3.0 as far I was reading, but that recovery never boots for me, and when I install it, it corrupts my sd and need to recover with 2.7.0.0.
I will run the RUU, I always have a little fear when messing with hboot hehe (Trauma from a bricked G1 a long time ago )
Ahh I will ad taht actually I try viper too and no boot. Only AOSP roms boot

lorddavid said:
Ok, I will try that rom, But I will not my S-off? And is easy to change between hboot? and yes, a lot recommended 2.6.3.0 as far I was reading, but that recovery never boots for me, and when I install it, it corrupts my sd and need to recover with 2.7.0.0.
I will run the RUU, I always have a little fear when messing with hboot hehe (Trauma from a bricked G1 a long time ago )
Click to expand...
Click to collapse
Running RUU wil not mess up your S-OFF. It will only return your phone back to stock firmware/radio/rom.
Switching between hboots (2.15 <--> 2.16) is always pretty the same.
What is annoying is that uprading or downgrading your hboot will format your sdcard, aswell as running any ruu.
To uprade to 2.16, follow the MaximusHD OP.
To downgrade to 2.15, follow this link until step 2.2 then flash the stock recovery and flash the firmware.zip the same way you flash 2.16. Then run ruu.
Some people advised me to use this tool to switch between hboots, but I preffer do it by myself. Have a look maybe you'll find it helpful.
I agree there is always a part of risk by doing this but you will not regret it when you'll find the perfect rom you want
Anyway your problem with Sense roms is kindda strange
Did you try to manually flash boot.img after flashing rom ?

benJX said:
Running RUU wil not mess up your S-OFF. It will only return your phone back to stock firmware/radio/rom.
Switching between hboots (2.15 <--> 2.16) is always pretty the same.
What is annoying is that uprading or downgrading your hboot will format your sdcard, aswell as running any ruu.
To uprade to 2.16, follow the MaximusHD OP.
To downgrade to 2.15, follow this link until step 2.2 then flash the stock recovery and flash the firmware.zip the same way you flash 2.16. Then run ruu.
Some people advised me to use this tool to switch between, but I use do it by myself. Have a look maybe you'll find it helpful.
I agree there is always a part of risk by doing this but you will not regret it when you'll find the perfect rom you want
Anyway your problem with Sense roms is kindda strange
Click to expand...
Click to collapse
Yes, Is strange, I know that the phone has hardware damage, but, only g sensor and flashlight, and everything works with AOSP, right know I'm charging the phone a little more, I've downloaded already viper rom, liberty, maximumHD, cm11 and Beanstalk.
Beanstalk has a lot of force close to me, cm11 just in the start, with a cm account, and when switching from the camera to videocamera.
Maybe there are error with the partition? I will try what you said and report back (will take a while because I read 3 times every step just to be sure)

lorddavid said:
Yes, Is strange, I know that the phone has hardware damage, but, only g sensor and flashlight, and everything works with AOSP, right know I'm charging the phone a little more, I've downloaded already viper rom, liberty, maximumHD, cm11 and Beanstalk.
Beanstalk has a lot of force close to me, cm11 just in the start, with a cm account, and when switching from the camera to videocamera.
Maybe there are error with the partition? I will try what you said and report back (will take a while because I read 3 times every step just to be sure)
Click to expand...
Click to collapse
Yes I thought about partitions, that's why if I was you I would run a ruu to make all clean and begin a clean fresh install.
I didn't test Beanstalk. CM11 works pretty well on both hboot, some FC however.
My favourite AOSP on 2.15 stills vanir aosp
But you will have time to test by yourself when everything will be repaired
I fully agree with you it's far better to take your time and read all threads carefully. Make thing in haste is the better way to do it wrong and have issues So take your time

benJX said:
Yes I thought about partitions, that's why if I was you I would run a ruu to make all clean and begin a clean fresh install.
I didn't test Beanstalk. CM11 works pretty well on both hboot, some FC however.
My favourite AOSP on 2.15 stills vanir aosp
But you will have time to test by yourself when everything will be repaired
I fully agree with you it's far better to take your time and read all threads carefully. Make thing in haste is the better way to do it wrong and have issues So take your time
Click to expand...
Click to collapse
I was trying to install maximushd first, but get an error here: fastboot flash recovery TWRP2.6.1.0.img and the green bar of the last command is still there, is normal?
the error is error: cannot load 'TWRP2.6.1.0.img': Unknown error
IT BOOTS!!!!!! Without recovery but boots!!!!!!!!!!!! I try that directly because a fas as i know the hboot manage the partitions, so install a hboot reinstall partitions right? But boots Sense again!!! I really misse it from my HTC ONE
I cant flash recovery, any advice? the error is
sending 'recovery' (8900 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.087s
I have still the recovery 2.7.0.8 but i need this version for hboot 2.16 (want to try other sense roms hehe) TWRP_2.6.1.0_ville_4.2.2.zip
Ok guys, sorry, my error, the bootloader got locked again. I did that and inmediatly I flash the recovery, Its seems everything is ok. it also clear internal storage but I wil see how is everything (hope to try sense 5.5, but as far as I read is not too much stable is that true?)

lorddavid said:
I was trying to install maximushd first, but get an error here: fastboot flash recovery TWRP2.6.1.0.img and the green bar of the last command is still there, is normal?
the error is error: cannot load 'TWRP2.6.1.0.img': Unknown error
IT BOOTS!!!!!! Without recovery but boots!!!!!!!!!!!! I try that directly because a fas as i know the hboot manage the partitions, so install a hboot reinstall partitions right? But boots Sense again!!! I really misse it from my HTC ONE
Click to expand...
Click to collapse
Yep you're right for the hboot & partitions.
Do not install normal TWRP on 2.16 hboot. The modded TWRP recovery from the OP which have to be used for this hboot is a .zip and have to be flashed when you're in ruu mode, just after flashing the firmware zip !
Did you follow all the install guide steps ?
Edit : you will find the recovery in this package. What afraids me is that you already should have downloaded this package to make a correct install of this rom. Your ~12gb of usable memory are correctly recognized by the phone ?
If not I suppose you did only one install of the rom. You need to flash recovery to make another install. Follow these steps :
1 - Boot in android, connect your phone and put the rom on your internal sdcard
2 - Reboot to fastboot
3 - You need to have file "TWRP_2.6.1.0_ville_4.2.2.zip" in your adb folder
4 - Type :
Code:
fastboot oem rebootRUU
fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.zip
fastboot reboot recovery
7 - Flash MaximusHD (full wipe !). This should be the second time you do it.
8 - Reboot

Yeah. the problem is that for some reason its locked again, the bootloader, but in unlocked, and flash the TWPR of the package, and my pc see 11.9gb so its ok I think. (My mistake was copy al my data haha when i unlocked again the bootloader, its clear the storage again)
I just want to see sense 5.5, but if what I read is truth, i will use maximumhd as daily, hope that sense 5.5 gets better in a future
And just another question. Maximumhd and all sense roms are rooted? I dont see superuser. And can i enable beats with the speakers?

lorddavid said:
Yeah. the problem is that for some reason its locked again, the bootloader, but in unlocked, and flash the TWPR of the package, and my pc see 11.9gb so its ok I think. (My mistake was copy al my data haha when i unlocked again the bootloader, its clear the storage again)
I just want to see sense 5.5, but if what I read is truth, i will use maximumhd as daily, hope that sense 5.5 gets better in a future
Click to expand...
Click to collapse
So I edited my last post for nothing lol
You mean your bootloader was relocked ? It doesn't matter, being S-OFF is what is important here. Don't care about bootloader locked or unlocked.
Yes it is rooted, but it uses SuperSU not superuser. All roms released here are rooted, except if it is stated in the thread Beats cannot be enabled with speakers, only with headphones

benJX said:
So I edited my last post for nothing lol
You mean your bootloader was relocked ? It doesn't matter, being S-OFF is what is important here. Don't care about bootloader locked or unlocked.
Click to expand...
Click to collapse
Edited: you answered editign your post haha sorry. Maybe was because I still need the second flash

lorddavid said:
Edited: you answered editign your post haha sorry. Maybe was because I still need the second flash
Click to expand...
Click to collapse
You're welcome, glad it works
Liberty rom is quite smooth and usable but it stills in alpha for now. MaximusHD is rock stable It's based on the official release we should all have had.

benJX said:
You're welcome, glad it works
Liberty rom is quite smooth and usable but it stills in alpha for now. MaximusHD is rock stable It's based on the official release we should all have had.
Click to expand...
Click to collapse
Thanks, I try Liberty and boots Everything is working now, thankyou so much. So, it will better to wait a little more to use Liberty, thank you
(I will use MaximumHD for a while)