Database Info

Temporary Root myTouch4g Slide Latest OTA

Hello everyone. I've done lots of research and I cannot find a solution. I have a completely stock myTouch 4G Slide that I would like to temporarily root so I can get the app data transferred to another phone. The phone is running the latest OTA update:
Android version: 2.3.4
Software Number: 1.63.531.2 710RD
I've tried many methods to try a temp root, but all end up unsuccessful. I already have the Android SDK installed and HTC drivers. I understand I can easily root the phone by unlocking the boot loader (in fact I have the unlock.bin from HTC dev already), but that will wipe the phone, which is something I do not wish to do yet.
I have tried fr3evo, but when I run the command, I just get this: An error occurred while running the exploit (-1) (errno: 25)
I simply want to temporarily root the phone to backup it's app data, then I can have fun with this phone. Any help will be deeply appreciated.

fred30w said:
Hello everyone. I've done lots of research and I cannot find a solution. I have a completely stock myTouch 4G Slide that I would like to temporarily root so I can get the app data transferred to another phone. The phone is running the latest OTA update:
Android version: 2.3.4
Software Number: 1.63.531.2 710RD
I've tried many methods to try a temp root, but all end up unsuccessful. I already have the Android SDK installed and HTC drivers. I understand I can easily root the phone by unlocking the boot loader (in fact I have the unlock.bin from HTC dev already), but that will wipe the phone, which is something I do not wish to do yet.
I have tried fr3evo, but when I run the command, I just get this: An error occurred while running the exploit (-1) (errno: 25)
I simply want to temporarily root the phone to backup it's app data, then I can have fun with this phone. Any help will be deeply appreciated.
Click to expand...
Click to collapse
Don't know about temporarily rooting the phone, but if the goal is to transfer the settings to another phone (particularly if this new phone is also an HTC), there is this app:
https://play.google.com/store/apps/details?id=com.htc.dnatransfer.legacy
It seems to transfer everything but the apps itself (which is easy to re-download from Google Play). And best of all, it doesn't require root!
Hope this helps.

joel.maxuel said:
Don't know about temporarily rooting the phone, but if the goal is to transfer the settings to another phone (particularly if this new phone is also an HTC), there is this app:
It seems to transfer everything but the apps itself (which is easy to re-download from Google Play). And best of all, it doesn't require root!
Hope this helps.
Click to expand...
Click to collapse
Hello, first of all I appreciate the response. Unfortunately, the new phone I'm transferring the data to is a Samsung Galaxy Note 2. I'm really after the app data stored in Android/data/data and you have all of the folders that start with com.* with things like save games, app settings, etc. I'm unable to access that folder with ES Explorer since it's root access only. It's interesting how I was able to use my Galaxy S3's built in file manager to backup the files and then restore them after wiping it (no root required), but I guess either Gingerbread was more strict or HTC locked the folder. Of course if you have more suggestions, I'd be happy to hear them!

Hello,
Samsung has a migration tool as well:
http://www.samsung.com/us/smart-switch/
https://play.google.com/store/apps/details?id=com.sec.android.easyMover
This one looks like it transfers apps, so I would assume settings and other data would go along with it. It's questionable if it will work on Gingerbread (citing compatibility issues, but that may be the destination end), but Google Play can determine that for you.

joel.maxuel said:
Hello,
Samsung has a migration tool as well:
This one looks like it transfers apps, so I would assume settings and other data would go along with it. It's questionable if it will work on Gingerbread (citing compatibility issues, but that may be the destination end), but Google Play can determine that for you.
Click to expand...
Click to collapse
Unfortunately, the Google Play store says that this device isn't compatible with this version. I wish it were easier to backup this phone though, heck it won't even allow the device storage to be mounted, only the SD card. I assume you rooted your phone via an unlocked boot loader? I could do that, but that wipes the device clean.

I did, through HTCdev (would have been the second thing I've done when I got the phone, the first was a test call to make sure it works ). HTC is not like other devices where you put CWM on first as part of the rooting process. At least you could nandroid the whole thing (then pick the archive apart later on).
As far as I recall, temporary rooting uses exploits in the code. So if you are on the latest OTA, then the chances of using said exploits are slim (and closed holes is something you already experienced). Unfortunately, the only way I can think of is to borrow an HTC device (already rooted), nandroid their setup, use the app in my first post, and nandroid that. But the chances of being able to borrow a rooted HTC (or even just an HTC that the friend doesn't mind you wiping and rooting) are probably slim.

joel.maxuel said:
I did, through HTCdev (would have been the second thing I've done when I got the phone, the first was a test call to make sure it works ). HTC is not like other devices where you put CWM on first as part of the rooting process. At least you could nandroid the whole thing (then pick the archive apart later on).
As far as I recall, temporary rooting uses exploits in the code. So if you are on the latest OTA, then the chances of using said exploits are slim (and closed holes is something you already experienced). Unfortunately, the only way I can think of is to borrow an HTC device (already rooted), nandroid their setup, use the app in my first post, and nandroid that. But the chances of being able to borrow a rooted HTC (or even just an HTC that the friend doesn't mind you wiping and rooting) are probably slim.
Click to expand...
Click to collapse
Supposedly, there might be versions of fr3evo that could exploit Android 2.3.4 on this phone, but all of the links I've seen are either the wrong version or corrupted. I actually have access to a HTC Inspire 4G that's fully rooted (it was a toy phone I messed with for fun), but it's being used by a family member so I can't clear it or anything like that. I really wish the boot loader unlock wouldn't wipe the phone. Thankfully everything on this phone works great as it is, since it was bought new. But I find it quite laggy and it takes literally 5 minutes to boot up (compared to my stock GS3 that boots up in less than 1), so once it's backed up, it's time to clear it and put a lighter rom onto it.

fred30w said:
I actually have access to a HTC Inspire 4G that's fully rooted (it was a toy phone I messed with for fun), but it's being used by a family member so I can't clear it or anything like that.
Click to expand...
Click to collapse
Depends on how long you can borrow it without said family member looking over your shoulder
If that phone is fully rooted, nandroid backup their current setup, do what you need to do (get your backup), then restore theirs. They would be none the wiser.
If you are a bit paranoid like I am, make two backups of the original setup, just in case.

joel.maxuel said:
Depends on how long you can borrow it without said family member looking over your shoulder
If that phone is fully rooted, nandroid backup their current setup, do what you need to do (get your backup), then restore theirs. They would be none the wiser.
If you are a bit paranoid like I am, make two backups of the original setup, just in case.
Click to expand...
Click to collapse
Hey that's not a bad idea! At the very least I'll save that as a worse case backup plan. I wonder if the HTC backup app data can be picked apart. At the very least I hope to at least backup the data and be able to construct instructions so other people like me can easily get their data off, then root.
Apparently, this guy got further than me when using fr3evo on his double shot, and he has the same software version too.
http://forum.xda-developers.com/showpost.php?p=26866661&postcount=8
But again, the downloads / version used of fre3vo is very vague. I'll keep looking for either a temp root solution or a backup for non-roots like you suggested.

fred30w said:
I wonder if the HTC backup app data can be picked apart.
Click to expand...
Click to collapse
For the record you can, using any archive tool that handles tarballs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alternatively, when the data is migrated to your family members phone (may want to test to see if your saved games are present), you can root your Doubleshot and migrate the data back. You would be borrowing it for a little longer, but it would be an easier restore.

joel.maxuel said:
For the record you can, using any archive tool that handles tarballs:
Alternatively, when the data is migrated to your family members phone (may want to test to see if your saved games are present), you can root your Doubleshot and migrate the data back. You would be borrowing it for a little longer, but it would be an easier restore.
Click to expand...
Click to collapse
Excellent, that looks pretty good. Ok, I'm downloading the HTC backup tool you linked above and I'll pick it apart and see if it's all there. By the way, I appreciate your help.
EDIT: Ok, this transfer tool wants direct connection between 2 HTC phones. If that's the case, I'll try to "borrow" that phone. Unless I'm using the wrong app of course.

fred30w said:
EDIT: Ok, this transfer tool wants direct connection between 2 HTC phones. If that's the case, I'll try to "borrow" that phone. Unless I'm using the wrong app of course.
Click to expand...
Click to collapse
You are on the right track. Let me know how it turns out.

joel.maxuel said:
You are on the right track. Let me know how it turns out.
Click to expand...
Click to collapse
Ok, I've tried to use the HTC transfer tool. Unfortunately, it has been unsuccessful. For one, it doesn't seem to have the option to transfer apps. Seems to only transfer user data (pictures, videos, etc.). Second, when I actually tried the backup feature, it only works on other HTC phones running stock firmware. I would get a screenshot, but I don't think this phone came with a screenshot capability without a third party app. Anyway, the app says this "To get started, go to "Settings" on your new phone, tap "Get content from another phone" and follow onscreen instructions." Then the app waits for a wireless connection and asks for a pin. Obviously the other HTC phone I'm borrowing is not useful here, since it's on custom firmware and it's even older than the double shot. It just makes me laugh though, you can't really backup too much without root, but the easiest way to root requires a phone wipe. Puts me in an odd spot. :laugh:

fred30w said:
Ok, I've tried to use the HTC transfer tool. Unfortunately, it has been unsuccessful. ... Then the app waits for a wireless connection and asks for a pin. Obviously the other HTC phone I'm borrowing is not useful here, since it's on custom firmware and it's even older than the double shot. It just makes me laugh though, you can't really backup too much without root, but the easiest way to root requires a phone wipe. Puts me in an odd spot. :laugh:
Click to expand...
Click to collapse
Yeah, that's a bit of a catch. Usually when a phone is rooted one is very tempted to replace the firmware (third thing I done with my phone ) so it's hard to find a rooted phone still on stock. You could RUU the borrowed phone back to stock, root it again, and then pair with the app, but that would add a ton of steps (full day's work) and it doesn't sound like stock is new enough to handle the HTC transfer app anyways (as it requires Gingerbread at least).
Well, it was worth a shot anyways. Hopefully someone else pipes up with a better idea. Take care.

joel.maxuel said:
Yeah, that's a bit of a catch. Usually when a phone is rooted one is very tempted to replace the firmware (third thing I done with my phone ) so it's hard to find a rooted phone still on stock. You could RUU the borrowed phone back to stock, root it again, and then pair with the app, but that would add a ton of steps (full day's work) and it doesn't sound like stock is new enough to handle the HTC transfer app anyways (as it requires Gingerbread at least).
Well, it was worth a shot anyways. Hopefully someone else pipes up with a better idea. Take care.
Click to expand...
Click to collapse
Indeed, I really appreciate your help though! I'm hoping someone can cook up something too.
EDIT: Since it has been difficult to find a temp root strategy, I was able to manually pull the app data file by file (painful) via adb. I got everything I needed, so now the phone has been wiped clean and can be easily rooted now.
But here is an interesting fact, before, this phone took 4 minutes and 27 seconds to boot. Now that I did a factory reset, it only takes 33 seconds to boot, I disabled fastboot on both tests.

fred30w said:
Indeed, I really appreciate your help though! I'm hoping someone can cook up something too.
EDIT: Since it has been difficult to find a temp root strategy, I was able to manually pull the app data file by file (painful) via adb. I got everything I needed, so now the phone has been wiped clean and can be easily rooted now.
But here is an interesting fact, before, this phone took 4 minutes and 27 seconds to boot. Now that I did a factory reset, it only takes 33 seconds to boot, I disabled fastboot on both tests.
Click to expand...
Click to collapse
Gee, I never thought about using ADB to pull files. Clever, although it must have been a hard slog.
I came across this link this morning:
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
The Doubleshot isn't in the compatibility list, but the OP mentioned if it's not, to just try and see. The good thing about this rooting process is that it doesn't wipe data.
Anyways, Hope you are enjoying your rooted phone.

New to Maxx, confused about root.

Could anyone point me in the right direction here? I consider myself 'somewhat' technologically inclined, I have rooted a few devices before but none were this complicated. I am running 4.4, 19.5.3, SU2-3.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Should I upgrade/change anything, or keep with the current version(s)? What is the easiest, most stable method to obtain root and an unlocked bootloader (if possible)?
One thing to note, my main absolute need for root is WiFi tether, anything else is just a plus.
Thanks in advance for any help, and my apologies for posting such a general question.

Try sunshine app

That's what I was thinking but, again, seems like there are so many variables when it comes to the maxx and obtaining root. Is there a particular starting point you can link me to? Would be much appreciated (I have not used sunshine app before).

Start with sunshine and just Google search for bootloader unlock and sunshine

rg449 said:
That's what I was thinking but, again, seems like there are so many variables when it comes to the maxx and obtaining root. Is there a particular starting point you can link me to? Would be much appreciated (I have not used sunshine app before).
Click to expand...
Click to collapse
What sunscape said. Sunshine will unlock your boot loader and you will not have to worry about any of the variables.
Sent from my locked but not stocked XT1080 using XDA Free mobile app

Thanks guys. As soon as I get the time to give it a go, I'll post back with results. Much appreciated.

rg449 said:
Thanks guys. As soon as I get the time to give it a go, I'll post back with results. Much appreciated.
Click to expand...
Click to collapse
Here is the link. Sunshine does need root to run but I believe it should be able to get temp root. Download it and run it. If it can gain root it will tell you and ask for $20. If not it will simply fail. If it cant get root, look up slapmymoto which will give you root access. Word of warning unlocking your boot loader voids the warranty.
http://theroot.ninja/download.html
Sent from my XT1080 using XDA Free mobile app

Thanks chuck. That was one of the things that was throwing me. Will slapmymoto give me perm root, or is it temp? Basically, what do I need to do, if possible, to obtain perm root?

Once you get unlocked via Sunshine, you can install TWRP and get perm root.

Sweet. So, as I understand as of now, I should try sunshine app alone first, if that does not work I should try slapmymoto in order to apply the sunshine unlock. Once that is successful, install twrp, and move forward. Is this correct?

rg449 said:
Thanks chuck. That was one of the things that was throwing me. Will slapmymoto give me perm root, or is it temp? Basically, what do I need to do, if possible, to obtain perm root?
Click to expand...
Click to collapse
Slapmymoto is a way to perm root but I'm not sure if it will work for you or not. It has been awhile since I used it and what versions it works for. Try downloading sunshine and run it. It will try and get temp root (which is all it needs) to unlock your boot loader. Once your boot loader is unlocked, you can flash twrp recovery(which installs perm root) and never have to worry about losing root again.
Sent from my locked but not stocked XT1080 using XDA Free mobile app

Nice. Thanks again, I've been looking at these threads for a couple days and haven't come to a conclusion as to what needed be done.
I know this is a lazy question but, will I need a pc for this at any point? Just wondering, as I don't have access to one on hand.

No and yes.
On your phone:
click on the link for sunshine, scroll to the bottom and download the latest version. Once it downloads, run it and agree to the permissions. It will try and gain root access. If it does, then it will run some test and see if it can unlock you boot loader. If it can, it will ask for some money(well worth it in my opinion). Pay the money and it will unlock your boot loader which will allow you to flash anything you want on your phone.
Now the computer comes in.
Download twrp on your pc.. (Just search this forum for the right version) and flash it with adb in fastboot. (Lots of instructions on this as well). Once it's done, reboot into recovery and when you exit twrp recovery it will ask it you want to install superuser(aka root), tell it yes.
I don't think there is a method for rooting your phone with out a PC.
Sent from my XT1080 using XDA Free mobile app

Perfect. Sounds easy enough.
The reason I asked about the pc, I did not have to use one to root my SG3 but, I figured since this particular phone has given the development such difficulty, they likely hadn't worked it all into process that did not require a pc.
Much gratitude, sir. I will be on this asap. I just got the phone in today, ordered from swappa, and am looking forward to moving my line from that SG3 to this much nicer device. Always did prefer Motorola and I think I made a good choice this time. May end up trying a work around to use my upgrade (unlimited on verizon) to get a Turbo in the near future but I am weary of mucking up my UDP.
Anyways, I'll report back with results as they come.

Question, would it be possible to ins TWRP via their app, instead of the fastboot method? I know that the app install requires root but, I am able to gain temp root via sunshine before I bought the license and was able to run and use root apps such as titanium backup and rom toolbox. That being so, would the twrp app work if I ran the sunshine temp root first? How risky is this or are there any known complications from this being tried before.
Bottom line, I am trying to get around having to use a pc as I do not have quick access to one.

rg449 said:
Question, would it be possible to ins TWRP via their app, instead of the fastboot method? I know that the app install requires root but, I am able to gain temp root via sunshine before I bought the license and was able to run and use root apps such as titanium backup and rom toolbox. That being so, would the twrp app work if I ran the sunshine temp root first? How risky is this or are there any known complications from this being tried before.
Bottom line, I am trying to get around having to use a pc as I do not have quick access to one.
Click to expand...
Click to collapse
did you unlock your bootloader via sunshine already?

Yes

Just looked in my app drawer, sunshine app is gone. Does this mean I will not be able to run the 'tests', and acquire temp root via their app, since I have already unlocked?

OK, I reinstalled the sunshine app, ran the test and was told it had gained temp root. However, I was unable to run titanium backup like I was before I unlocked. So, I guess that I maybe should have tried that route before hand. Back to the pc, fastboot method. I have a few questions, as I was at the library earlier but had to leave before I was able to complete the twrp install.
1. Do I need to download and install any drivers if the PC is already able to read my device?
2. Where do I enter the necessary commands on the PC, such as:
From your computer, open a command prompt and type:
adb reboot bootloader
I was a bit rushed and didn't get the time to look over all skd tools, maybe I was supposed to enter the command from there? I would like to get a general idea of how these tools work, or how I am supposed to use them, before I go back to the library so I am not trying to figure all this out while I am in there.
ETA: found most of my answers in post #93 here - http://forums.androidcentral.com/dr...oid-maxx-bootloader-unlocked-root-away-4.html

OK, the last time I had tried to run titanium backup (to confirm root), it wouldn't recognize the root. This apparently was because I had already opened the app and had not closed it. Realized my mistake, closed the app, reopened with root access.
So, I downloaded the TWRP app from Google play, and got so far as completing the download for the install but, did not have the stones to continue further without knowing this has or has not been tried before.
1. Is it safe?
2. I had downloaded the latest version listed within the TWRP app for the motor x (ghost), would this version work?

T-Mobile S4 M919UVSFQA1 OTA update - Should I accept?

Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob

filter4ever said:
Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob
Click to expand...
Click to collapse
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk

Thanks
Thanks. I've had a lot of homework so I haven't had the time to search very deep. I found a Knox less NH7 update and installed it, guess I'm just going to have to wait for the OTA to become available.

qFuse
Droidriven said:
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.

filter4ever said:
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.
Click to expand...
Click to collapse
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk

It's in the partition "SBL3" at offset 0x31160. I have a dump of my phone if interested, but I would like to remove specifics (make sure I'm not signed in, did factory wipe, imei, etc)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It appears to be C code (compiled possibly encrypted) before or after the file name. Please don't let this fall into the wrong hands :0
I bought an app, "MobileODIN", that seemed a bit iffy, but I thought I'd give it a try. T-Mobile has the OTA update, they want me to use Kies (yeah, right) so I am using that stupid RapidGator thing (oh well, at least they dont ask for my credit card, I mean, WTF?, who would do such a thing)? Anyways, EverRoot - Part of the PRO version I bought as I wanted to try Loli but KitKat is the latest. T-Mo just released M919UVSFQA1 on 2/8, if I can do things like EverRoot, do you think it would successfully castrate that code? Even if it can preserve root, if I lost it, I may not be able to get it back. Right now I'm running the M919UVUFNH7 Stock Rooted, Permissive NH7, and NH7 non-hlos and it works good. Read a couple posts on mobile ODIN and it did say it would root firmware, keeping it from being lost, BUT - not a full stock image (which possibly has boot.img - just what that nasty little firebug code is looking for in SBL3). I will post in mobile ODIN, but have you heard of an unlocked boot.img, one that doesn't have this nasty little line of code?

Just took upgrade.
Well i just flashed the ota with odin and even with supersu pro 2.79 runing survival mode it took root from me. Now. I know this may be a shot in the dark here but what about doing something similar of the i337 and flashing a previous kernal rooting locking in survival and then reflashing kernal? I have thr ota file saved on my laptop if you would need it to break it down and see what is possible. I will toy around with it as i have time to. Having 4 youngins gets a little difficult to have a whole lot of time to invest myself to most of this stuff anymore. Eventually it will work right? Lol GL And let me know if we want to give this a shot or not
xXxCyanidexXx

Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.

xXxCyanide87xXx said:
Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.
Click to expand...
Click to collapse
Did you try the Supersume app? Did you try normal SuperSU or did you try systemless SuperSU?
Just make sure you get rid of everything else that came along with Kingroot, it's malware.
Sent from my SM-S903VL using Tapatalk

Switched around some...
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.

xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
Ok, try SuperSU in systemless mode, it'll probably work for you. Good luck.
Sent from my SM-S903VL using Tapatalk

Just got home gonna get twrp .tar for Odin and the systemless zip and see what I don't break lol

New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:

xXxCyanide87xXx said:
New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:
Click to expand...
Click to collapse
Good to go. Actually, the method you used is about the easiest, it's commonly the go-to method if Supersume doesn't work. You did good.
Sent from my SM-S903VL using Tapatalk

Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.

SuperSU
xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
I'm a NooB but the only thing I can think of is that CF may have not updated SuperSU for this kernel version. Can you post your details ("Settings" > "More" > "About Device")? I still haven't updated, NH7 works OK.
Rooting without SuperSU is scary. I make sure to turn off "Auto MMS download" as I once thought I got an MMS virus with rooted firmware and just about had to change my shorts.

Here is a screenshot of my phones info... kernel build ect. Let me know if you need anything else. Or just need help in general with your phone.

filter4ever said:
Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.
Click to expand...
Click to collapse
Yes I flashed it first.
This is the order I did it all
1 - downloaded firmware ( rom https://samsung-firmware.org )
2 - Flashed update using Odin PC version (search forums there are links everywhere.
3- downloaded Kingo root from https://www.kingoapp.com and ran root process (may take a couple times... if it fails immediately run it again
4 - after root was successful I then downloaded Mobile Odin (lite or pro your choice. I used Mobile Odin Pro. Check forums for links to download.
5- Download Twrp 3.1.0-0 follow
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976 follow steps to retrieve .tar file. MAKE SURE IT IS CORRECT FILE FOR INSTALLATION.
Don't flash yet
6- down load SuperSu 2.79 SR3 .zip from
h1ttps://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Now we flash.
7 run Mobile Odin and click recovery. Place Twrp there. Then scroll down to after flash and click. Set it for reboot recovery. Run.
8- After TWRP loads click on Flash .Find SuperSu 2.79 select and flash. Reboot to System (I went ahead and wiped just the regular cache partition then rebooted)
9- Run SuperSu (if prompted by Kingo for root then allow.
10- Using something abe to freeze/Remorvebe (Root Essentials, Lucky Patcher, something of that sort) then proceed to freeze and remove all the kingo junk and bloat.
11- Reboot phone and enjoy.
Now I will warn you the Samsung-firmware is slow for download. So if need be and I am allowed to. I have the firmware file I can upload on here for everyone.
I take no responsibility for any damage that can &/or may happen to your device this method worked for me. Doesn't guarantee that this method will work for you. GL and happy rooting ^__^

qFuse Code
Droidriven said:
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I agree, and I don't have a problem with the qFuse "Warranty Bit" for that reason... when it says "This Will Void Your Warranty" it means exactly that. Like I said, when I buy something it's mine (including, Samsung doesn't have to support it if I screw it up).
Are there any custom variations with permissive kernel of this firmware yet? Tried looking around here and searching, none yet... this post of mine appears to be my latest. If you would like this firmware I'll provide the link.
Now that I have SuperSU Pro and Mobile ODIN pro, do I still have to worry about that bootloader qFuse code (my guess is they flashed the locked bootloader and it's already been executed) I just don't want this new update to screw me, and didn't worry about it for a year, but now my phone is acting funky.... showing ads when I open the "Lock Screen" etc. I got Super SU Pro specifically because... an Android virus... with ROOT privileges = anyone's WORST nightmare. Just look at the /dev folder, not to mention "ps -l -C", or "pidstat -l -C" (and other commands I'm not familiar with yet). Listen to you, take pictures of you, steal your data, your passwords, do something illegal and blame it on you (Use your phone as a PSTN and Internet proxy).... you name it. (also it being mine applies to they don't have to support security updates as well - caveat to all rooters that's the 'Catch 22').

LOL, thats more than my Brain Can Handle
I have the same phone.. samsung s4 with the m919uvsfqa1 . It was from Tmobile, i bought the phone in canada and have it locked to Fido in Ontario , Canada. The fact the phone is Canadian, is likely irrelevant. As the Revision is the same as the phone ASHLEY has rooted.
I want to Multitask Apps, and the Samsung Apps that are Preinstalled do not offer the ones i want.
So I read, that if i Root the Phone then any app can be Multi-Window.
As I see Ashleys , rooting was quite difficult. I ask is it Possible to Root this Phone. For someone that really dont know what they are doing. I would need, a very detailed plan that i could follow but am not able to Follow Ashleys plan. Is there a New Method since your THREAD was POSTED?
I doubt any Local Tech would ROOT THIS for a Price, in Sault Ste Marie Ontario... as the stores wont void warranty and i dont know any Techs.
I need to get something done, so that i can access the Calendar app to add Information while talking on the Phone. So far i have to hang up the phone to enter information to the Calendar. That doesn't seem like a Smartphone....

Basic Root Question

I very recently purchased (as in less than a week ago) a Google Pixel (5") from the Google Play store. I would like to root it, but have a few questions that I could only seem to find vague answers to online. Firstly, does the Google Play purchased version of this phone come automatically with an unlocked bootloader? I saw several posts online that this was the case, but the posts are all pretty old (10/2016, about 9 months ago) and nothing really since then. Is there a way to verify/check if the bootloader is unlocked?
Secondly, the phone I got has Android 7.1.2 (build NKG47L). These - posts look to be the most recent info on rooting this phone, but they mention a different build number. Does anyone know if this is still an accurate process?

Unlock bootloader in developer options by toggling, then use OEM unlock in fastboot, Install TWRP, and flash latest superSU in TWRP. Done.......
Sent from my Pixel using Tapatalk

Are you the same alienjon as on FB, with the Light Whip?
Bootloader is probably locked - it was on mine when new from Google Play - Aus and about 6 months ago, but locked bootloader is part of Google policy so it probably still is. Unlock like this:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
be aware that unlocking the bootloader will wipe your phone (would keep your data secure it someone had stolen it and was unlocking it to hack it), so do that early.
I root as per Chainfire's instructions, there's no easy way to update and keep root at the moment (Flashfire is supposed to work but it doesns't for me) so I reroot after each update, worked for the June update.
There are a few things to be aware of; TWRP is up to 302rc2 but some people have had trouble with that, I still use twrp 302 rc1 which works reliably (just boot it, to flash SU then reboot I haven't installed it). SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
https://plus.google.com/+Chainfire
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.

@maulich That's perfect. Took me about an hour and a half to root, but most of that was reading and re-reading instructions to make sure I didn't mess anything up. I did notice that there is now some device protection feature that gets disabled when you unlock the bootloader. I checked online and it seems that this basically is a feature that factory resets the device in case someone tried to force themselves into a stolen device. I'll look around, but any suggestions for security features to implement for a rooted device?
@Clancy_s Sorry to disappoint, but no relation to an alienjon on FB. You are correct that it was locked, but I really love how easy it is to unlock. I'm used to phones purchased from Verizon that are beastly to unlock. My last phone (Galaxy S5) never got a workaround for the bootloader from what I recall (though after the Towel Root process stopped working it was almost a year and a half before a new rooting procedure was discovered - kudos to the devs that figured that problem out!)
In any event, thanks for the input on unlocking and rooting. I looked at a few different websites, but the procedure appears to be the same for unlocking that you found. This is the rooting procedure I used and worked fine, though the directions weren't as straightforward as you'd think; ie: the latest TWRP has a .zip but no .img to download on their website and I didn't trust anything else I found online that claimed to be the correct .img file. I used the next most recent version (RC1 - I saw several warnings against the alpha builds) and didn't have any problems. I also used the latest SuperSU (2.82, I believe). A few posts mentioned sticking with 2.79 because of bugs with the newer version, but those were from several months ago and elsewhere it stated that this issue was fixed. It seems to be working great for me
Clancy_s said:
SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
Click to expand...
Click to collapse
Unfortunately I didn't see your post until after I rooted. I can verify, though, that flashing the SuperSU zip worked fine without any additional steps. (ie: boot into TWRP image, flash TWRP and SuperSU zips, which I did together).
Clancy_s said:
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
Click to expand...
Click to collapse
I did not. When I tried to submit my initial post I got a server error. It didn't look like anything had gone through so I went back and resubmitted, which worked. I later realized that the first post did, in fact, go through but I couldn't figure out how to delete it. My apologies for the dupe.

alienjon said:
I couldn't figure out how to delete it. My apologies for the dupe.
Click to expand...
Click to collapse
In a web browser either on the PC or on the phone, click the exclamation point in the triangle /!\ in the lower left corner of the post you want to report, report it to a moderator and ask them to please delete it, or move it, if you ever post something in the wrong section.

Thanks. I'll remember that in case it comes up again.

How do you relock a U11 to receive OTA updates?

Aloha to all. So after learning the hard way of relocking my U11 and bricking it (it's on its way to HTC in Texas) what would have been the safest way in relocking my phone to get the OTA update?
When I started getting the OTA update nag screen a couple weeks ago I had the phone download the update file and chose the option to install the update. But as you guys know a unlocked phone will not allow the OTA update to install. I then used ADB to relock and that's when I got my phone in trouble.
Before all this drama, my phone was working fine and I had a few apps installed that may have aided me to do the transition from unlock to relock to get the OTA update then back to unlock. I had the official TWRP app and Magisk installed.
Could someone please explain to me what would have been the best course of action I should have undertaken to have smoothly updated my phone going from having an unlocked phone, to installing the OTA update, to relocking the phone? I would love to understand and follow a failsafe bulletproof method of doing this process (installing the OTA update when my phone is in the unlocked state) I really would appreciate it if the senior members could take the time and guide me or at the very least post some links for the specific process. Aloha and mahalo.
Sent from my HTC6545LVW using Tapatalk

You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build. I then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.

mroshaw said:
You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build.
Click to expand...
Click to collapse
So no need to relock? I'm sorry for being obtuse but what do you mean to "revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build"? How do you revert to official build and where do you find the RUU file to be restore?
mroshaw said:
Then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.
Click to expand...
Click to collapse
How does TWRP and Magisk utilized to reroot? I'm sorry for all the questions and thanks for your reply.
Sent from my HTC6545LVW using Tapatalk

I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.
mauiblue said:
How do you revert to official build and where do you find the RUU file to be restore?
Click to expand...
Click to collapse
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.
mauiblue said:
How does TWRP and Magisk utilized to reroot?
Click to expand...
Click to collapse
TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.

mroshaw said:
I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.
TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.
Click to expand...
Click to collapse
Thanks for the post. I also was wondering what happens when a phone is totally bricked. What does HTC do to repair a phone that was relocked and flashed incorrectly? Is a physical part replaced on the phone?
Sent from my HTC6545LVW using Tapatalk

mauiblue said:
Thanks for the post. I also was wondering what happens when a phone is totally bricked. What does HTC do to repair a phone that was relocked and flashed incorrectly? Is a physical part replaced on the phone?
Click to expand...
Click to collapse
I imagine it depends on a case by case basis and on which support center you end up dealing with. I'd be surprised if HTC don't have some sort of toolset to restore a bricked device without a physical part replacement, but who knows. Could be costly if they do insist on a physical repair.

mroshaw said:
I imagine it depends on a case by case basis and on which support center you end up dealing with. I'd be surprised if HTC don't have some sort of toolset to restore a bricked device without a physical part replacement, but who knows. Could be costly if they do insist on a physical repair.
Click to expand...
Click to collapse
Well I could have used my Asurion phone insurance to replace the phone and the deductible would have been $150 but they would have replaced the phone with a Google Pixel. So if repair/replacement would be about that much, I'm fine with that.

mauiblue said:
Well I could have used my Asurion phone insurance to replace the phone and the deductible would have been $150 but they would have replaced the phone with a Google Pixel. So if repair/replacement would be about that much, I'm fine with that.
Click to expand...
Click to collapse
Well, best of luck from me! Keep us posted as to HTCs response!

mroshaw said:
I think these sorts of challenges and questions are what XDA is all about, and it's often through mistakes that we learn the ins and outs of device modification. Happy to help, as I've been in similar positions during my time tweaking phones and devices.
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
The Holy Grail, in forum post form, for all U11 owners who need to recover their devices. From here, you can pretty much recover from any sort of soft brick situation. This has got me out of trouble many, many times. Having an unlocked bootloader does NOT stop you receiving OTA - having a customer recovery, such as TWRP, prevents an OTA from being installed automatically but it's still perfectly possible to manually apply an OTA with unlock and TWRP.
TWRP (replacement recovery) and Magisk (systemless root tool) are awesome tools that allow you flash custom ROMs, run root tools and hide root from prying eyes. Fairly typical to install a custom recovery and root, as part of unlocking and preparing a device for a custom ROM or some proper tweaking. Restoring from an RUU puts you "back to square one", in a good way, that requires a fresh installation of these tools if you want to continue to mod your device.
The bottom line is that you REALLY need to have an understanding about what locked / unlocked bootloader, custom recovery and root means to your device. You need to understand the power that ADB gives you and be aware of the risk inherent: ADB is the Android Debugger - it's a developer tool, not typically for normal consumption. As you've unfortunately discovered, Android gives you a lot of flexibility, often at the device manufacturers discretion (I'm looking at you Huawei), to modify your device using powerful Android tools. Without a full understanding of the consequences, it's perfectly possible to irrecoverably brick your device. When it all falls in to place, however, there's a sense of enormous satisfaction in having control over the device you've spent hundreds of bucks on.
Click to expand...
Click to collapse
I've tried just about everything I can think of. I'm pretty sure mine is completely bricked.
Nothing works. All RUUs I've tried have failed. I have the EU model. I wanted to use the US unlocked ruu so I rooted, achieved s-off, and changed the cid and mid to match it. I thought I had to relock the phone to flash the RUU like in previous htc phones. I tried the RUUs and they failed. I unlocked it again to try something else, which factory reset the phone. Then I foolishly locked it again thinking I'd try a different ruu. That failed too. When I rebooted, the phone went back to s-on. I cannot unlock the bootloader again because I can't access the OS. It opens to a screen I need a password for and I don't have a password for it.
I thought I was fine, though. On previous htc phones, I could still access twrp. If I factory reset, I could access the OS again and unlock the bootloader. This one gave me a screen that the phone is corrupt and won't boot, so I can't access recovery at all.
Stuck between a rock and a hard place. I hope you get your phone in working order Maui.
Sent from my HTC 10 using Tapatalk

Kaepernick said:
I've tried just about everything I can think of. I'm pretty sure mine is completely bricked.
Nothing works. All RUUs I've tried have failed. I have the EU model. I wanted to use the US unlocked ruu so I rooted, achieved s-off, and changed the cid and mid to match it. I thought I had to relock the phone to flash the RUU like in previous htc phones. I tried the RUUs and they failed. I unlocked it again to try something else, which factory reset the phone. Then I foolishly locked it again thinking I'd try a different ruu. That failed too. When I rebooted, the phone went back to s-on. I cannot unlock the bootloader again because I can't access the OS. It opens to a screen I need a password for and I don't have a password for it.
I thought I was fine, though. On previous htc phones, I could still access twrp. If I factory reset, I could access the OS again and unlock the bootloader. This one gave me a screen that the phone is corrupt and won't boot, so I can't access recovery at all.
Stuck between a rock and a hard place. I hope you get your phone in working order Maui.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I know that I will get the phone repaired (knock on wood) just as long there isn't any issues of the phone getting lost while being in the repair department. I found another thread regarding U11 owners having a very difficult time communicating with the HTC customer service department. Some members are saying they have to wait months (3, 4, 6 months) to finally find a resolution. One member says it only took 4 weeks from start of the repair to actually receiving the U11 back. I will bite the bullet and see how long I can stay in HTC Purgatory. But I really need a phone so I might just buy the U12+ I got a few discount codes that will make the phone cheaper but not a whole lot. I've got to decide soon because the codes are expiring soon,.
BTW, I wish you all the best with getting your phone repaired or replaced. I like HTC and can't see going with a Samsung or Apple.

mauiblue said:
Aloha to all. So after learning the hard way of relocking my U11 and bricking it (it's on its way to HTC in Texas) what would have been the safest way in relocking my phone to get the OTA update?
Click to expand...
Click to collapse
What OTA update? Don't bother for once a year update...

MoshPuiu said:
What OTA update? Don't bother for once a year update...
Click to expand...
Click to collapse
Well I was getting the OTA update nag screen constantly and to get rid of it I would just allow the update to install. It wouldn't. I obviously didn't do my research enough to understand what I could have, should have, would have done.
So now I hope the phone makes it back to Maui without costing too much money.
Edit: Well I can't wait for my U11 to come back from service and ended up getting the U12+. The HTC phone I'm using is giving up the ghost soon and I need a reliable setup now. So this issue is costing me big time. Oh well...
Sent from my HTC6545LVW using Tapatalk

mroshaw said:
You don't need to "relock" to receive OTA. When I needed to revert my FW to an "official" build, I simply used an RUU to restore and immediately received an OTA to the latest build. I then re-flashed TWRP and Magisk to re-root. At no point did I touch the bootloader after initially unlocking it.
Click to expand...
Click to collapse
So I should have followed these instructions since I already had unlocked the bootloader via the HTC Dev website? See below. I did not flash any custom ROM and I was all stock after I unlocked the bootloader. I hope I am using the correct nomenclature (unlocked the bootloader).
5m4r7ph0n36uru said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download the latest Stock RUU for your device over here.
flash your RUU to revert to stock
rename RUU to 2PZCIMG.zip
copy 2PZCIMG.zip to root directory of SD card
reboot to download mode
press Volume Up button to confirm flash of RUU
As soon as your RUU has been flashed sucessfully, that's it. Your are now Full Stock again!
Click to expand...
Click to collapse

Never relock if the phone ain't stock. You don't need to relock anything anyway. S-off and unlocked bootloader don't affect flashing. Just flash a stock firmware, take ota, reroot or leave it as is.

shivadow said:
Never relock if the phone ain't stock. You don't need to relock anything anyway. S-off and unlocked bootloader don't affect flashing. Just flash a stock firmware, take ota, reroot or leave it as is.
Click to expand...
Click to collapse
So since I unlocked the bootloader and rooted my U11 but didn't flash a custom ROM it is not stock anymore? So I needed to flash it a stock firmware then my phone would have taken the OTA update. Then I could have rooted the device again or leave it as is.
If there is a next time (which I know there will be) I'll do more research and do it right.
Sent from my coconut frond hut using Tapatalk

Update:
I just got my phone back from HTC repair department. The battery was dead and I had to charge it. I was able to turn it on and it looks like the bootloader is still unlocked. I didn't get a chance to look around in the phone to see if the os was updated.
There was no documentation on what was done to the phone. Fortunately I was not charged for any repair service. All together it was almost five weeks going to Texas and coming back to Hawaii. I'm going to check the phone out and post back again.
BTW, I am a bit more learned about tweaking the phone now after all these weeks. In fact I just unlocked my replacement phone, the U12+, and rooted it the other day. I'm going back to the U11 when I get all my apps installed and use it for a little bit. I'll be more careful tweaking it this time around.
Sent from my coconut frond hut using Tapatalk

UPDATE:
When I got home the day I received my HTC U11 I was quite excited about getting the phone set up again. When I turned it on it booted up and I decided I wanted to update the software using the software update menu on the phone. I noticed that it had the 2.42.617.6 version. So I let it run its course and when the phone tried to boot up I got the corrupt phone error message. I was disappointed to say the least. The phone was away for 5 weeks and HTC didn't resolve the issue. Well at least they didn't charge me for anything. Thanks for nothing.
I emailed HTC and they were of no help. They sent me an email pertaining to trying to clear the phone cache. I already mentioned that I couldn't even get the phone to boot! So the last several nights (I work a second job) I've been working on figuring out how to resolve the issue with the phone not being able to boot up. As I examined the phone, I found that the phone was still in the "relocked" status. So I decided I would unlock the bootloader first. I got the unlock BIN file after going through the bootloader unlock process on the HTC Dev website and I was able to unlock the phone. I was happy I got that issue resolved. So now I needed to somehow install an OS/firmware that could boot the phone up.
I followed the xda forum guides and I was stumped at first. I used the ADB method and I was met with failure. Either I was not correctly doing the procedure correctly or I was using the wrong files or ??? I then used the SD card method. When I first used the latest OS/firmware version (this is the same version that was on the phone and listed on the download mode) the procedure would produce a couple error messages right at the end. The phone would be stuck in an endless boot loop. So I decided I would use an earlier version of the OS (2.42.617.1) and use the SD method to install the zip file. It was successful in the install and the phone booted up.
I was still pessimistic that the phone issue was resolved until I was able to update the phone completely. I updated the OS using the software update menu on the phone. The phone took a couple OTA updates without issue and booted up and now I am satisfied. I've learned a lot over the past month about my phones (I also have an HTC U12+ that I bought after I sent off the U11). I was also happy to see that there are a few members here on the forum that is considerate to offer their assistance in getting my phone back in order. So no more relocking the bootloader and I will make sure I backup the phone before I do anything to the OS/firmware.
Aloha and mahalo for reading.