Related
I'm having a problem with my wifi randomly turning itself off and customer care told me to just switch it out through the buyers remorse policy at a T-mobile store. I know you have to erase all signs of having rooted the phone before sending it to HTC under the limited warranty or else they charge you. Do I also have to set it back to stock before returning it directly to T-mobile through buyers remorse?
I'm asking because a) its a pain in the rear end to get it back to stock and b) I haven't found the stock recovery anywhere and have already flashed ClockworkMod Recovery so I'm not sure at this point I can get it back to stock.
Please post questions in Q&A section
Thanks for moving it.
Sent from my HTC Glacier using XDA App
I remember one time sending my Touch Pro 2 to T-Mobile for a new one with the HSPL on it. HSPL allows me to flash any custom ROM basically.
But I never got a call back or charged, but I only did that one time because I was being lazy.
Good question.
I have to return mine actually due to a hardware defect which I can't put up with like I thought I could but I also rooted my phone and turned S OFF but I turned the S ON the other day so I am hoping that will be enough lol. Well plus make sure none of the files I've d/l are on the sd card but I don't think I have to worry about that seeing as I'm not using the sd card that came with the phone but my own.
However, I think I might do this once I figure out if it's needed (cause I'm kind of nervous about doing it and messing it up you know) and after I do more research on this hex editor stuff. http://forum.xda-developers.com/showthread.php?t=832642
likeitnot said:
Good question.
I have to return mine actually due to a hardware defect which I can't put up with like I thought I could but I also rooted my phone and turned S OFF but I turned the S ON the other day so I am hoping that will be enough lol. Well plus make sure none of the files I've d/l are on the sd card but I don't think I have to worry about that seeing as I'm not using the sd card that came with the phone but my own.
However, I think I might do this once I figure out if it's needed (cause I'm kind of nervous about doing it and messing it up you know) and after I do more research on this hex editor stuff. http://forum.xda-developers.com/showthread.php?t=832642
Click to expand...
Click to collapse
Its very easy to do, it really is. I did it just today to switch out phones for another color. Just follow the directions carefully. They won't know because it literally puts stock right back on the phone. Just make sure that's what you want because there is no link for the 2.2.1 update right now. And people are having problems getting the updates again.
timbo1083 said:
Its very easy to do, it really is. I did it just today to switch out phones for another color. Just follow the directions carefully. They won't know because it literally puts stock right back on the phone. Just make sure that's what you want because there is no link for the 2.2.1 update right now. And people are having problems getting the updates again.
Click to expand...
Click to collapse
That's the easy part but how do you get the stock recovery back on? I haven't seen a download for it, don't think HTC has released it either.
Sent from my HTC Glacier using XDA App
If you are returning it to a store under buyer's remorse, then you don't need to unroot or do anything, as it is not a warranty exchange. You should be able to swap it out within a few minutes there, and never hear of it again.
When you follow the other post to downgrade it.puts the stock back on it. That is the point of it.
Sent from my HTC Glacier using Tapatalk
^^ I finally got it to work but I did notice that after a while superuser app and a few others I had downloaded are appearing again... uhhhhh
When I got into the terminal on the phone and type su + enter it says permission denied and another $ appears...am I safe to say its not rooted and it just put the apps back cause of the google backup?
Plus S is back to SON (it was SOFF cause of the root) & Titanium Pro will not let me upgrade the busybox always comes back with an error and then when I go back in the application it says "Error" Sorry I could not acquire root priveleges. This application will *not* work!..." Not to mention the application ShootMe no longer works cause it says I don't have root access.
OKAY *phew* I take it they only appeared again because of the google backup!
I had the exact same problem. My wifi and GSM signal would disappear. I would have to reboot the phone to get it back.
Anyway I took it back to tmo and they didn't even power it up or anything. I put everything back in like it was when I go it and no questions asked.
btmec said:
I had the exact same problem. My wifi and GSM signal would disappear. I would have to reboot the phone to get it back.
Anyway I took it back to tmo and they didn't even power it up or anything. I put everything back in like it was when I go it and no questions asked.
Click to expand...
Click to collapse
You bought your's from a Tmo store though right?
I ordered mine through add a line with 611..
I have dust under my sceen and am thinking about sending it back.
Odds are you all would be just fine, but honestly? Why take that chance...if you rooted it, you can unroot it. Just set it all back to stock and dont sign back in with the phone.
c_licious said:
I'm having a problem with my wifi randomly turning itself off and customer care told me to just switch it out through the buyers remorse policy at a T-mobile store. I know you have to erase all signs of having rooted the phone before sending it to HTC under the limited warranty or else they charge you. Do I also have to set it back to stock before returning it directly to T-mobile through buyers remorse?
I'm asking because a) its a pain in the rear end to get it back to stock and b) I haven't found the stock recovery anywhere and have already flashed ClockworkMod Recovery so I'm not sure at this point I can get it back to stock.
Click to expand...
Click to collapse
just flash the RUU from the downgrade post since you're already rooted and s-off you shouldn't need to do any of the hex editing or anything just download the RUU and put it in /sdcard/ named PD15IMG.zip and it will take care of it... and it will restore everything including recovery... the only thing that won't go back to normal is if you ran gfree for radio s-off... if you did that follow the guide in that post for restoring radio s-on then flash the RUU... http://forum.xda-developers.com/showthread.php?t=832642
slhpss said:
just flash the RUU from the downgrade post since you're already rooted and s-off you shouldn't need to do any of the hex editing or anything just download the RUU and put it in /sdcard/ named PD15IMG.zip and it will take care of it... and it will restore everything including recovery... the only thing that won't go back to normal is if you ran gfree for radio s-off... if you did that follow the guide in that post for restoring radio s-on then flash the RUU... http://forum.xda-developers.com/showthread.php?t=832642
Click to expand...
Click to collapse
Where can I get the RUU?
And the method I used was with Visionaryr11 and a download that had a script.
I just ran Visionary, used Terminal Emulator to access the script and then rebooted and I was perma rooted.
http://www.youtube.com/watch?v=eHrtVzlsA_s
nguyendqh said:
Where can I get the RUU?
And the method I used was with Visionaryr11 and a download that had a script.
I just ran Visionary, used Terminal Emulator to access the script and then rebooted and I was perma rooted.
http://www.youtube.com/watch?v=eHrtVzlsA_s
Click to expand...
Click to collapse
the download that the link I posted says to save as PD15IMG.zip on your sdcard and reboot in the boot loader is the RUU... it will put you back to stock 2.2 everything including recovery and bootloader
I accidentally deleted my part7 .bin created by gfree and could not get s=on. I exchange anyway at the tmo for a better screen. They didn't even pretend to check if it had been rooted.
Sent from my HTC Glacier using XDA App
exchanged my G1 which was rooted and had a version of android we werent supposed to have yet, I exchanged it through HTC though, my screen all out stopped working, maybe thats why they didn't notice anything, that or they just don't really care.
QUESTION - it seems that flashing PD15IMG.zip is the same process as flashing SAPPIMG.nbh for the original myTouch 3G.
1. Is the hexeditor stuff necessary or can we just copy to sdcard and flash away?
2. Can PD15IMG.zip be flashed from hboot S-OFF or do I need to turn S-ON first?
c_licious said:
That's the easy part but how do you get the stock recovery back on? I haven't seen a download for it, don't think HTC has released it either.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
The Unlockr
Has a stock ROM and a Stock Recovery Image that you can flash.
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!
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.
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