Database Users

help unrooting (before warranty expires)

I need to return my g2 for warranty reasons (part of the touchscreen doesn't respond) but I'm having alot of trouble unrooting it.
the bootloader never recognized the pc10IMG.zip on my sd card.
I'm wondering if it's an issue with my bootloader?
I have S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
any help will be greatly appreciated!

after having this issue for about 3 months, I've finally got it.
Formated a 2 gb sdcard and used that instead, it worked.

My rom is now stock, and so is my recovery, but the bootloader still looks the same, with fastboot and the skateboarding androids and everything.
is that the stock bootloader? I can't really remember, would like to make sure before I send it in.

Yes the bootloader is stock.
The only thing you might need to change is S-OFF back to S-ON
-Nipqer

s- on is a must *from experience*

MRguyandhis2 said:
s- on is a must *from experience*
Click to expand...
Click to collapse
What experience ?
I've swapped 3 g2's on hardware defects, no issues, very smooth process. I'm about to swap my last g2 for a cracked camera lens cover, if the warrantee is still valid. Yes, I received this g2 as a warrantee replacement, and notified them of the crack on arrival.
I keep reading about people having issues with warrantte, but never specifics.

lucky I didn't send it in yet, I completely forgot to check for S-off.
I'll have to check later, looks like I'm not sending it back till Saturday anyhow, but it's not as if I can actually use it while it's on stock since I'm on at&t and it's locked
when I was rooted with gfree, it unlocked itself, but now it's locked again, anyway to unlock it without voiding warranty? if not it's hardly going to matter.
Update: I put my sim in it and it's still unlocked! Hooray!
>update (again) : I can make calls, but no data
>>update: I'm absent minded sometimes.. that was because I needed to set att's apn
Also:
How do I check exactly (sorry, noob question) I can look for it a little more thoroughly tomorrow

don't think they care about the root, sent mine in many times with rooted roms and they seem to send my replacements and I'm on t-mobile, but just to be sure I don't think they care about S-on or off they might just care if the rom is significantly different like sense roms

I'm just really trying to make sure I get it unrooted correctly.
according to the guy on the phone, If I don't qualify for the warranty, my options will be to either pay for the repair, or pay $34 for their diagnostics on it (WTF?).
and the repair is going to be $100, since they'll going to replace the whole screen, even though I'm pretty sure the only issue is with the ribbon cable.
It's not going to hurt to make sure I have S-On, and it could potentially save me a lot of cash, so I might as well do it.
I'm pretty sure I only have to type something into the terminal emulator to find out?
not sure what that was though..

Well, my boot loader says S-off, and I can't figure out how to make it S-on since I don't have a part-7[something].bin on my SDcard.
from what I can find, I think I can make it S-on by using the official RUU, but I'm having trouble finding this, and almost tried to flash an ruu from the european HTC Hero (aka G2) by mistake.
[it's quite annoying that people call that the forums label that phone the G2 even though I don't think htc or any other carrier does in any case]
any help here? can I use somebody else's backup or would that result in a brick?
any alternative methods?
Update:
well apparently I can "Use gfree to set secu_flag = 1 and CID = T-MOB010 (or your corresponding original CID)."
although I'm not sure exactly how to do that.
I pretty sure it means that I could Gfree to gain temporary root, and then use the Terminal emulator to open up and modify a particular file in the system, and change the value of the parameter "secu_flag" to 1 (I'm not a complete n00b)
as for the CID, I think I may already have it set correctly, but it never hurts to check.
Am I on the right track?

almost right track.
Use psneuter to get temp-root, then run
./gfree -s on -c TMOB_010 (or whatever the cd is meant to be)
though psneuter only works for adb shell so you can't use term emulator to unroot.
and gfree only works on the 1.19 rom.
-Nipqer

If the screen is broken I believe all they do is change the screen and flash sense back on to it. I sent mine in with the screen not working and got the phone back with sense installed again + s-off. It looks like (for mine) they didn't care that it was rooted simply because it was a hardware fault and therefore did not matter whether it was rooted or not.
It is up to you whether or not you want to risk it, but with mine it was ok
Will check back with this thread when I get back from work in case I can help further!
Sent from my HTC Vision using XDA App

video
Zedomax has a guide on how to unroot the g2 on youtube. (not allowed to post a link)

I still can't get the S-off
Zedomax's video tutorial was pretty useless, he did the same thing I did, then booted into the bootloader and said "wierd it still says S-off..."
as for the the psneuters thing:
$ adb shell /data/local/tmp/psneuter kept getting permission denied
eventually I gave up and used vissionary to temp root.
then I pushed and did the chmod 777 step with gfree
but "# /data/local/tmp/gfree -s on -c T-MOB010" led to "/data/local/tmp/gfree: permission denied"
maybe I should try the "rage against the cage" root method?
I'm on 1.19.531 btw

Tired of Waiting for 4.4 OTA

Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.

Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.

badboy47 said:
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
Click to expand...
Click to collapse
I mean People have had trouble when they have been at a Official Servicecenter.
Apparently the servicecenter said that the customer have had a open bootloader then locked it before going to repair, so the Servicecenter refused to repair the phone.
I dont know if its a myth or not?
so its 100 % secure not damaging any hardware just unlocking the bootloader with nexus toolkit.

Eastliin said:
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Click to expand...
Click to collapse
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data, again.

iowabeakster said:
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data when you unlock in the future.
Click to expand...
Click to collapse
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?

Eastliin said:
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Click to expand...
Click to collapse
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.

iowabeakster said:
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
Click to expand...
Click to collapse
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha

Eastliin said:
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Click to expand...
Click to collapse
actualy google says to unlock,flash and then relock for"security purposes".

opssemnik said:
actualy google says to unlock,flash and then relock for"security purposes".
Click to expand...
Click to collapse
Thats fun haha, you got a link of where they state that?

Eastliin said:
Thats fun haha, you got a link of where they state that?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.

opssemnik said:
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
Click to expand...
Click to collapse
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!

Eastliin said:
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Click to expand...
Click to collapse
^, they tried to screw with me, but as i know lg here in brasil, i carried a book of "consumers defense code", i showed them the link,and the guy from the service center had to get my n4 and fix for no fee (my screen was broken, and no touch, but the screen broke because of overheating).

S-Off Achieved by Firewater Devs

https://www.xda-developers.com/firewater-devs-htc-u11-s-off/
https://twitter.com/firewaterdevs/status/889118758865960961
Exciting.:good:
don't bug them, but this is good news.

riggsandroid said:
https://www.xda-developers.com/firewater-devs-htc-u11-s-off/
https://twitter.com/firewaterdevs/status/889118758865960961
Exciting.:good:
don't bug them, but this is good news.
Click to expand...
Click to collapse
We will need to learn how to work around having temporary S-Off, so paying attention to the new flashing instructions is going to be important.

nice! :good:
no we can install AOSP to replace the factory version, and or install Lineage OS

Kisakuku said:
We will need to learn how to work around having temporary S-Off, so paying attention to the new flashing instructions is going to be important.
Click to expand...
Click to collapse
Well they'll for sure dig a little bit further until they release it. So let's see if temporary may become permanent on the initial, or any follow up, release. First of I'm glad to see that they found out how to do it. Those are the great news many have been waiting for.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
Well they'll for sure dig a little bit further until they release it. So let's see if temporary may become permanent on the initial, or any follow up, release. First of I'm glad to see that they found out how to do it. Those are the great news many have been waiting for.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it. I was reading about it in the XTC2Clip forums. The product manager said that HTC may backtrack on it though because it's causing problems but didnt go into any further details. Also, it's impossible to set the phone back to factory right now. If you unlock the bootloader, the only thing that you can do is set the relocked flag thanks to temporary S-OFF which sucks considering HTC went back on their "U11 warranty even with unlocked bootloader" selling point. They say they are working on fixing that problem as well as adding SIM unlock in a future software update for the clip.
Things that the XTC2Clip can do right now with all the modules on the U11 (a 175 USD investment) - change CID, MID, downgrade firmware with temp S-OFF, unlock bootloader, etc.
If we don't get an engineering leak or HTC doesn't change course and put S-OFF back in, I doubt we will see it for awhile from the SunShine devs. Just because they got temp S-OFF doesn't mean they can make a nice easy to use tool. The phone now not only checks when the command is issued, it checks at boot and resets the flag. Trusted Reboot only works on that boot. It's going to be very easy to brick since the device goes right back to S-ON. If something wasn't successful, you've got a brick as soon as it reboots just like when people forgot to flash a RUU to go back to stock before going back to S-ON after modifying the firmware.
HTC engineering leaks have happened in the past when S-OFF couldn't be achieved so we will have to wait and see.

EtherealRemnant said:
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it. I was reading about it in the XTC2Clip forums. The product manager said that HTC may backtrack on it though because it's causing problems but didnt go into any further details. Also, it's impossible to set the phone back to factory right now. If you unlock the bootloader, the only thing that you can do is set the relocked flag thanks to temporary S-OFF which sucks considering HTC went back on their "U11 warranty even with unlocked bootloader" selling point. They say they are working on fixing that problem as well as adding SIM unlock in a future software update for the clip.
Things that the XTC2Clip can do right now with all the modules on the U11 (a 175 USD investment) - change CID, MID, downgrade firmware with temp S-OFF, unlock bootloader, etc.
If we don't get an engineering leak or HTC doesn't change course and put S-OFF back in, I doubt we will see it for awhile from the SunShine devs. Just because they got temp S-OFF doesn't mean they can make a nice easy to use tool. The phone now not only checks when the command is issued, it checks at boot and resets the flag. Trusted Reboot only works on that boot. It's going to be very easy to brick since the device goes right back to S-ON. If something wasn't successful, you've got a brick as soon as it reboots just like when people forgot to flash a RUU to go back to stock before going back to S-ON after modifying the firmware.
HTC engineering leaks have happened in the past when S-OFF couldn't be achieved so we will have to wait and see.
Click to expand...
Click to collapse
Yeah that's exactly what I thought but didn't explicitly state in my post above.
Sent from my htc_pmeuhl using XDA Labs

EtherealRemnant said:
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it.
Click to expand...
Click to collapse
Unless the development fuse isn't blown.

Patiently waiting

Kisakuku said:
Unless the development fuse isn't blown.
Click to expand...
Click to collapse
Which helps practically nobody. So again, it's back to the drawing board.

If testers are needed I am willing to have a crack at it. I have Australian Telstra firmware if that's of any use

Here you go.

HTC 10 back to stock for RMA

Welp, my power button has decided to do some funky things lately and I decided to RMA it. Just wanted to double check on the steps to bring it back to stock. First, download an official RUU and flash it to the phone. IIRC this will also bring back stock recovery which will replace twrp. Then lock the bootloader and then go back to S-on. I sent my phone to J-case before unlocking was available on Sunshine, so is there anything special that I need to do to lock the bootloader and go S-on? I will be following the steps outline in this guide to help me out https://theunlockr.com/2016/08/18/unroot-htc-10/. With that being said, is there anything special that needs to be done that this guide does not outline for our phones? Also, if my terrible googling skills missed a thread that already has the steps outlined, please link it to me and after I get the phone back to stock I will then delete this thread.

WS-99 said:
Welp, my power button has decided to do some funky things lately and I decided to RMA it. Just wanted to double check on the steps to bring it back to stock. First, download an official RUU and flash it to the phone. IIRC this will also bring back stock recovery which will replace twrp. Then lock the bootloader and then go back to S-on. I sent my phone to J-case before unlocking was available on Sunshine, so is there anything special that I need to do to lock the bootloader and go S-on? I will be following the steps outline in this guide to help me out https://theunlockr.com/2016/08/18/unroot-htc-10/. With that being said, is there anything special that needs to be done that this guide does not outline for our phones? Also, if my terrible googling skills missed a thread that already has the steps outlined, please link it to me and after I get the phone back to stock I will then delete this thread.
Click to expand...
Click to collapse
Honestly, if you are just returning it and anticipate a replacement warranty device, as opposed to a repair, just factory reset it and don't worry about it. They're not even going to power it up; they'll bulk erase it and reflash it and nobody will ever know it was S-OFF and/or bootloader unlocked.

hgoldner said:
Honestly, if you are just returning it and anticipate a replacement warranty device, as opposed to a repair, just factory reset it and don't worry about it. They're not even going to power it up; they'll bulk erase it and reflash it and nobody will ever know it was S-OFF and/or bootloader unlocked.
Click to expand...
Click to collapse
I kinda figured that is what they would end up doing with it. But I also did not want to go through the headache in case they decided to check. Thanks for the advice!

Hgol is probably right but when I was on the phone getting my device set to be replaced they told me that if the phone was physically abused or had software modifications they would charge me a 300$ unrefundable fee so for me I ruu to stock and went back to s-on locked to be safe I would too you never know if your device is gonna be that one that they actually check

Recovering from Idiocy - Relocked Bootloader with TWRP Recovery and Custom Rom in Pla

I'm posting this here half for help and half as a warning to others. Got burnt tinkering a bit to carelessly.
The story in short: unlocked bootloader, TWRP and Leedroid. Wanted to remove the start up "Unlocked Bootloader" message + possibly gain use of GPay. Googling around XDA stories of both bricked devices and people who had no problems. I figured I'd see what happened if I locked the boot loader and if I had problems I could just unlock it again, right? Wrong. After flashing Leedroid developer options, of course, had defaulted to disabled as well as 'Allow OEM unlock'. So after my device refused to boot, as I half expected it would, it also wouldn't let me un-lock it again, which I didn't expect.
So here I am stuck with a bricked device that has S-On and won't boot (corrupted device message). Only way out is Stock RUU from the original carrier of my device (Telstra, Australia). Unfortunately that seemingly doesn't exist on the internet for gods knows why and because S-ON can't change CID (TELST001) to flash something else.
I do have one half-baked idea that I don't see robustly covered already. I happen to have a second Telstra U11. My thought was to perhaps take that, image it using nandroid and then flash that image onto the bricked device via fastboot. Is that an option, or is that a no-go for some other reason?
Moral of the story: Don't play with fire unless your sure you have a fire extinguisher. And don't try and re-lock your bootloader no matter how much that warning bugs you.
Neil

Does anyone know whether I could nandroid image the stock U11 and use fastboot to flash that image to the soft bricked device?

You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.

TeroZ said:
You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.
Click to expand...
Click to collapse
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs

@TeroZ seems that with the bootloader re-locked any fastboot flash x.img command is rejected by default. Seems you can only flash in RUU mode. Does that make sense to you? That closes the only other alternative to sending it back to the official repairer just to have them rather than me flash the official RUU. What a scam.

5m4r7ph0n36uru said:
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.

TeroZ said:
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.
Click to expand...
Click to collapse
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N

Try contacting Telstra customer service instead and see if they provides ruu.

ngodber said:
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N
Click to expand...
Click to collapse
Try this thread. Similar sort of issue with bricking. HTC 10 Batch tool was used
https://forum.xda-developers.com/u11/help/help-ruu-firmware-t3716144/post77822986#post77822986