Hoping you guys can help me
I s offed my phone using rumrunner, downgraded my hboot to 1.44 and restored my 1.29.206.7 O2 stock nandroid backup. I ran revone, locked the bootloader, removed tampered and updated to the latest 3.62.206.1 firmware. I need to send the phone back for repair so I did fastboot oem writesecureflag 3. I rebooted the phone and on first reboot the phone boot to the lock screen, froze and then reboot. This kept happening until a factory reset, after which the bootloader read as tampered and locked
My bootloader was 1.55 and not a modified hboot as I had come from hboot 1.44, although I don't think this hboot was for my model id or cid (I changed the android.info file to flash it)
How do I safely go to s-on for repairs? Or should I leave it as s off and locked bootloader. I'm sending it to o2 rather than HTC
Related
I had s-off and unlocked bootloader by revone, but decided to make it stock to claim warranty.
Since Australia doesnt have RUU, I used European RUU since 1.29.XXX are same then I used my own nandroid backup to have Australian rom.
I tried to update with OTA, but it just rebooted to bootloader and gave me TAMPERED..
So I used revone again to s-off and unlock bootloader then removed TAMPERED.
I locked bootloader and s-on again, but needed to flash radio.img to have matching baseband.
Therefore I re unlock and s-off to have CWM, however this time wasnt easy to achieve s-off, so I tried to factory reset before I try revone again.
But once again rebooted into bootloader and another TAMPERED..
I managed to remove TAMPERED, but what is wrong with my phone?
I can not OTA update 4.2.2 to have Australian rom and Australian firmware.zip..
I can not factory reset with 4.1.2 Australian rom and European firmware.zip
I can take my phone as 4.1.2 with s-on locked to service center, but what if they factory reset the phone and TAMPERED appears?
How big is stock recovery for 4.1.2? I bet 4.1.2 and 4.2.2 are same but the one I used was 9.4mb
Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
broli-zn said:
Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
Click to expand...
Click to collapse
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
You just need to downgradethe firmware. It contains the hboot.
But as @godutch said, it's not necessary.
Sent from my One using XDA Premium 4 mobile app
Ok cool, thanks guys, so I just need a flash a firmware zip containing 1.44 Hboot and im good to go?
Basically i just want to get rid of the tampered flag.
Iv done the 4.3 upgrades with supposedly fix the camera but its made no effect on mine :crying: so the only other option I have to try and get them to change the camera module.
Thanks again guys. Much appreciated. You will get a thanks each
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
criszz said:
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
Click to expand...
Click to collapse
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
broli-zn said:
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
Click to expand...
Click to collapse
it does but you need to be s-off and rooted for it to work but you don't have to do what you are trying to do and you will regret it later....
just try with 1.54 , multiple times
hboot 1.55
godutch said:
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
Click to expand...
Click to collapse
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
amauryaa said:
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
Click to expand...
Click to collapse
not recommended, as far as i've seen, going from s-off to s-on (on 100% stock everything), after a few reboots, has a high chance of resulting in "tamper detected - rebooting" and the TAMPERED sign is back.
Well, I'm usually able to dig myself out of messes I get myself into but this one has had me hunting a few hours. Here's the run-down.
1) S-OFF with 1.44 a while ago, rooted and unlocked bootloader
2) Got camera problem, would like to return phone to stock for warranty
3) Flashed a stock RUU, went fine. Stock recovery and bootloader work fine, hboot was upgraded to 1.55 (my mistake, should have noticed this)
4) Got sidetracked when trying to lock the bootloader and entered fastboot oem lock
So now I have a 're-locked' bootloader on 1.55 with S-OFF. I don't want to unlock through HTCDev, I can't use revone to unlock because I'm on 1.55, and I don't have a custom recovery, and can't flash one because I'm relocked.
Any ideas how I can unlock the bootloader here (or downgrade hboot, I have the zip but can't flash it)? I can probably handle the rest myself, after I smack myself over the head a few times.
The goal here is to have the bootloader 'LOCKED', and I'll then take my chances with S-ON, with the latest firmware but a downgraded (1.44) bootloader before handing it over for warranty purposes.
OK, it looks as though I can patch hboot files OK. Will take a look around for a patched one.
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
SaHiLzZ said:
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
Click to expand...
Click to collapse
Sorted, thanks. Found an older ROM that flashed fine with supercid. Think I'll keep S-OFF and just lock the bootloader. With this being a likely hardware issue I'm hoping I'll be fine with just that.
My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards
anarchyuk said:
My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards
Click to expand...
Click to collapse
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear
raghav kapur said:
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear
Click to expand...
Click to collapse
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?
anarchyuk said:
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?
Click to expand...
Click to collapse
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again
raghav kapur said:
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again
Click to expand...
Click to collapse
I think I have already done most of it, i got the md5 check error to go away, and installed a standard HTC that had the CID HTC_002 available in the build prop. I then flashed stock recovery. Fastboot booted in to CWM and ran the remove tampered. Lock bootloader.. I have just changed the CID From 111111 to HTC__002 and its booted fine. So The bootloader shows locked, no tampered or HTC red developer message under the logo but still hs S-OFF on bootloader screen? what would happen If i s-on now?
edit: Not to worry I done the secuirty flag 3 command and its now s-on and still boots, ty to you both.. really appreciate it
edit: 2 the tampered has came back
edit: 3 back to s-off and bootloader unlocked, tamp flag back too
Hi everyone. I searched for around half an hour through google and failed to find a situation identical to mine (maybe i havent looked long enough).
I was one step away from resetting the warranty by removing root and locking bootloader again so that i could send it to HTC for repair (its under warranty.
I locked the bootloader and turned s-on. Then after flashing a stock ruu (i was sure i had the correct version) it returned to bootloader and all of a sudden it says TAMPERED again with s-on..
The phone now will not get out of bootloader. Since its s-on i cant flash a rom or recovery or flash a ruu. When trying to flash a stock ruu it says signature verify fail
ran fastboot getvar all
Phone details:
Bootloader: 1.44.0000
Baseband 4V.13.3231.27
Currently TAMPERED bootloader, LOCKED with S-ON.
How do i now get s-off again from this position?
Thanks in advance!
UPDATE:::: I unlocked bootloader through HTCDEV. THis can be closed
You should be able to get S-off again using Revone with HBOOT 1.44. You should be able to find everything you need here http://forum.xda-developers.com/showthread.php?t=2314582 . I was unable to flash any RUU file until I achieved S-off, but I had to use firewater as I couldn't get revone to work with HBOOT 1.57. Here is the firewater link http://forum.xda-developers.com/showthread.php?t=2632351 .