Database Develop

[Q] lost root after 2.3.6 update

hi there every one i updated my nexus one to 2.3.6 (GRK39F) from stock 2.3.4 (GRJ22) sorry but i did not read the post for to upgrade and keep root before upgrading to 2.3.6 and now i am suffering and thought it is not a good idea to post a question there so posting here
my problem is when i upgraded 2.3.6 i was rooted and had clockworkmod recovery image and i had a backup from rom manager as well but before upgrade i wiped the partition and cache and after upgrade i dont have SUPER USER permission nor the clockworkmod recovery tried to flash su.zip from sd card but no luck please can anyone help me get my root back pleaseeeee i need help ....

You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...

danger-rat said:
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
Click to expand...
Click to collapse
Thankyou very much danger-rat really appriciate your help but today was a bit lucky day for me
I tried to flash a recovery image through ADB and then it went well and then flashed the su.zip from sdcard that gave me superuser permission again thanks again for your help
@0mpranav

No need to flash the system partition, no need to use ADB, just flash Superboot:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/

If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759

jboxer said:
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
Click to expand...
Click to collapse
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.

GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
I have purchased two second hand Nexus Ones. The first thing I did after receiving them and charging the battery was to reboot into fastboot mode and issue "fastboot oem unlock" command. Since they were purchased second hadn I didn't thing I had a warranty anyway so unlocking the bootloader seemed to be a non brainer.

GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
Will any version of su.zip, and fastbook.zip work? What about recovery-RA-passion-v2.2.1.img? or should we be using a different version?
If we should be using different versions of those, could you link to where we could get them?
I've had my Nexus one half-rooted since 2.3 came out, and I haven't been able to root it back.

why mess with 2.3.6 just use oxygen 2.3.7...

kuljit55 said:
why mess with 2.3.6 just use oxygen 2.3.7...
Click to expand...
Click to collapse
I'm sorry I have no idea what that is. I don't even know if its helpful at all. Again, I don't even have root, or a custom recovery. Presently, I have an unlocked bootloader, ADB on my PC, and a half-rooted nexus one from before 2.3.
I have absolutely no idea how to do anything presently, and when someone tells me that trying to root on 2.3.6 is futile and to just use a custom update, it doesn't make any more sense to me.
Care to elaborate past one line that doesn't help at all? Hell when using shell commands through adb, it keeps on saying "permission denied" any time I type in su.

You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...

danger-rat said:
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
Click to expand...
Click to collapse
Thanks Danger-rat. Although I know you said nothing different that what was already said in this thread, I figured that since you didn't give me specific info about whether or not there were multiple versions of su.zip or fastboot.zip, I figured I should take that as a "No.", so I went for it. All re-rooted now.
I appreciate the help.
EDIT: So if you are as new to this stuff as I am, anyone else who's reading-
You can DL su.zip from http://www.google.com/url?sa=t&sour...ZxOuf9Kw_URvtvh9Q&sig2=Hj72LDNoiBq2Zoa4QquZWQ
and fastboot.zip from http://www.mediafire.com/?ttdkgamud3j
and amon Ra 2.2.1 from http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
then follow the directions here: http://forum.xda-developers.com/showthread.php?t=1019759
** Note: again, these are for people who have unlocked bootloaders. For that info, you'll have to go elsewhere, but it should be readily available, such as this stuff is. I'm just linking it again because I know how frustrating it can be for people like me who aren't too well versed in rooting/unlocking yet.

Downgrade 2.3.6 to 2.2.2 - Nexus One
Problem:
I would like to downgrade my Nexus One to 2.2.2, because I've had non-stop problems with Gingerbread.
So I've gone through the Bootloader -> Recovery -> apply sdcard:update.zip steps, and it fails. This begs the question, how do I go from 2.3.6 to 2.2.2?
Fix:
Generally, phone manufacturers will not allow you to downgrade for various reasons. The stock recovery does indeed validate the update image, so that it's of a greater (or same) version than the installed system. With the Nexus One being a developer phone, you can unlock the bootloader and replace the recovery image with the one that doesn't perform this check, and will allow installation of any image. The caveat is that unlocking the bootloader voids your warranty with the carrier (and sometimes the manufacturer too,) and wipes all user data off the device.
Unlocking the N1 is dead easy. Just install Android SDK and the USB drivers (located in "google-usb_driver" directory.) Then restart the phone in bootloader mode by shutting it off and powering on while holding down the trackball, hook it up to the computer via USB, and in command prompt issue the following command: C:\<path to Android SDK>\tools\fastboot oem unlock. You will be presented with a confirmation screen with further instructions. Upon successful unlock, you can flash a custom recovery that will allow you to install any custom ROM, including downgrade to 2.2.x stock version of Android OS.
To flash ClockworkMod recovery, download the latest version for Nexus One from here, reboot into bootloader mode (power on while holding the trackball down,) and in command prompt issue command C:\<path to ANdroid SDK>\tools\fastboot flash recovery C:\<path to downloaded img>\recovery-clockwork-3.0.0.5-passion.img
Reboot to bootloader mode again, and then use the Volume keys to highlight the "Recovery" option and press Power button. You are now in ClockworkMod recovery, and can flash any custom ROMs via the "Install zip from sdcard" option.
Here is a "stock" 2.2.2 ROM (with root) off XDA-developers forum.
http://forum.xda-developers.com/showthread.php?t=927935
source:http://android.stackexchange.com/questions/13933/downgrade-2-3-6-to-2-2-2-nexus-one
Try It & Report Back...

[Q] Bootloader questions

From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?

cytherian said:
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
Click to expand...
Click to collapse
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.

Shelnutt2 said:
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Click to expand...
Click to collapse
Thanks for the info, Shelnutt.
I'm kind of in a peculiar "Nexus" that I'm trying to extricate myself from. I have S-ON presently. I would like to change it to S-OFF, but I can't seem to do it. I suspect it's the bootloader preventing me, which is hboot 1.7. So, I tried to replace the bootloader and the attempts fail. I've tried it through the adb shell, fastboot, terminal emulator on the phone, and via the recovery manager (TWRP). Attempting to replace the bootloader results in "signature verify fail". Through TWRP, it also said verification failed.
I also tried to retrieve the identifier token (HTC dev) so that I could unlock the phone that way, but "fastboot oem get_identifier_token" fails with a "Command error" (although I can execute "fastboot oem rebootRUU" with no problem).
I also tried to use Regaw's boot mod tool, which replaces the bootloader and turns S-OFF. But it aborts because my Hero is already rooted. So I went into my z4Root application and selected "un-root". It said "done", but the phone remains rooted. I even tried to "Re-root" but it wouldn't complete (thinking if I root it again, I could then try another un-root).
I'm thinking I should just flash back to stock, but... I don't have any fresh nandroid backups to use. TWRP doesn't do nandroid. It does its own thing, which becomes a problem because TWRP needs Android 2.2 or higher. So... does that mean I need to install ROM Manager again, do a nandroid backup, then run an RUU back to full stock again?

For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k

Shelnutt2 said:
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Click to expand...
Click to collapse
Thanks, you're right... in TWRP there's a checkbox to control that. There's also one to verify md5, but it requires a file (I guess it looks for [filename].md5). In any case, getting past that resulted in failure to load hboot 1.46 as you surmised.
The issue with Regaw doesn't seem to be the radio. It simply reports that there's nothing to do because the phone is already rooted. Apparently it will only run if the phone is not rooted. And to unroot, it appears the only way is by RUU. Z4Root is supposed to allow it, but when selected it doesn't do anything.
So, I finally came up with something that got me on the right path. :good:
I re-installed ROM Manager and flashed the latest ClockworkMod to Recovery. From there I could apply the hboot 1.46 ENG-SPL with no issues. I rebooted into the bootloader and saw................ HERO XC ENG S-OFF, HBOOT-1.46.2000. :highfive:

[Q] Problems with OTA Upgrade

I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.

Check PM

sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...

[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.

Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.

Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?

sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off

bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.

sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom

Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??

After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!

Yes you need to unlock your bootloader again to be able to flash twrp

I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!

You can get SuperSU or Superuser from the playstore or install a custom rom.

A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.

A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?

phone wont boot

im not really sure what happened...
i was trying to root then s-off today. i got htcdev.com unlocked, was able to flash custom recovery (philz) and flash superuser. when i tried to s-off (firewater) i got the whelp this sucks error (im still not really sure why or what that means)
i tried to then flash a custom rom, and now it wont boot past the htc flash screen with the red text ( this may be because i didnt flash firmware with the rom i tried to install?)
i have tried to flash firmware, and run a ruu and nothing is doing anything...
please please please someone help

What firmware version do you currently have installed? What ROM were you trying to flash?
Take a look at this thread below for info on how to flash the latest RUU. If you have a HK version you'll need the HK RUU. After you run the RUU you'll need to reroot your phone. You'll also need to use the SunShine exploit to gain S-off (the "whelp" message means Firewater won't work on your device). I also recommend Captain Throwback's TWRP 2.8.0.0. recovery.
http://forum.xda-developers.com/showthread.php?t=2880328

im not sure which of these are the firmware...
hboot - 3.16.0.0000
radio - 1.05.20.0321_2
os - 1.54.654.9

Firmware is your radio version. Use the RUU from the link below. Follow the instructions for the manual system update. You'll need to relock your bootloader beforehand using the command "fastboot oem lock" while connected via Fastboot USB mode.
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/

ohh i forgot about having to relock for ruu
trying that now

I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader

knock.back said:
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
Click to expand...
Click to collapse
RUU's are run from the bootloader...make sure it says fastbootusb when connected to your PC.

it did say that

Make sure you have HTC Sync installed on your computer.

I have that installed too... I got it to boot, ended up flashing different recovery then a different rom and that worked... Never got the ruu to work tho... Anyway, thanks for your help

Softbrick (kinda) problem

Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance

soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.

I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.

Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.

soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at

dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember