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.
Related
Hi guys,
I've been playing around with my Nexus S for about 3 weeks and I've decided to root it, but I have some question, I've been searching the answers in older posts but it's not quite clear yet, hope you can help me.
When I unlocked the bootloader, what kind of data will be wiped? It's just the SD card or also all the apps I've already downloaded? what about SMS, pictures and videos?
Is there anyway I can backup that data considering I haven't root it yet???
Thanks in advance.
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
lol what? its nobodys fault but your own. all the resources are available, just because somebody isnt responding to your threads and holding your hand to restore a nandriod backup doesnt make it a "lack of a community".. and your phone isn't bricked, it can be recovered but you are too close-minded and cant install Clockwork Recovery / get drivers working
The data that will be wiped are most likely your SMS/settings/etc. This is standard procedure. And its something you'll go through a lot when you are using custom ROMs.
There are complete instructions for rooting, unrooting and unbricking your phone. It's all here in the forums, and many other places, you just have to look and learn. I read for two weeks before I unlocked and loaded a ROM into my NS.
If you don't have a need to root your phone I wouldn't do it just because you can. I wanted to run the Voodoo app so I had to root and load a ROM. It took a little while but it was painless and I liked learning about the Android system.
You do have to backup your app and your SD, but that was the easy part.
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
RogerPodacter said:
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
Click to expand...
Click to collapse
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
"brick" describes a device that cannot function in any capacity (such as a device with damaged firmware)
In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement.
http://en.wikipedia.org/wiki/Brick_(electronics)
Click to expand...
Click to collapse
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
Netconn said:
You do have to backup your app and your SD, but that was the easy part.
Click to expand...
Click to collapse
What's the best way to do it? It's there an app or I have to day it by myself?
Make a nandroid backup first and foremost! Use Titanium Backup to make a backup of all your apps. If you want a backup of your sms, go sms pro really does a great job of that. Dont forget your contacts as well! Then copy your sd card and place it on the hard drive of your computer. When you unlock the bootloader, it does wipe your sd card. Once your unlocked and rooted, you should be able to restore everything once you replace the copy of your sd card back on the phone. Coming over from a Vibrant, I was nervous about rooting the phone but its an easy process. Just take your time and do lots of reading! Hope this helps!
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Woops..yeah, your right there. Too quick to reply. I followed this method here..
http://forum.xda-developers.com/showthread.php?t=895545
and had no problems. Once you get unlocked/rooted and clockwork recovery, then you can make the fore mentioned backups. Export your contacts to the sd card then copy the sd card to the hard drive of your computer before unlocking the boot loader. I do not think apps get affected during the sd wipe unless you have them stored there.
zephiK said:
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
Click to expand...
Click to collapse
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
may i suggest a noob proof guide|? i postted 1 in the htc desire forum and people love it. yesterday i returned a moto xoom because ti was overheating , got a nexus s and 2day il b returning that because it wont turn on. can any1 help me think of a good idea i can tell the future shop return people?
kmhil said:
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
What's the best way to do it? It's there an app or I have to day it by myself?
Click to expand...
Click to collapse
you are forced to lose your data to initially root your device. then after that point, you can always create backups and never lose data again while you switch between ROMs and flashing etc. but i think to initially root, you have to lose everything. not the sd card though.
LINKSLOVESANDROID said:
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
Click to expand...
Click to collapse
Do keep in mind, we don't have an i9020 or an i9023, we have an i9020A So the instruction out there all need to take that into considerations. I rooted mine fine with no "Bricking" I had to follow the instruction for the i9023, but it worked. I figure it took me all of 1 minute to root my phone. Admitedly, the "One click root" for the Galaxy series was easier.
I try to make it a point to never be the "First" person to do something on their phone. Much safer that way.
I also find it very unusual that you've managed to brick two phones, I've also had the pleasure of owning the telus fascinate, and not once did i get it bricked, I tried Bionics, CM7, Darky's and a bunch of other ones. Just never mess with the boot loader. When you went back to stock, did you make sure it was a stock ROM for the I9020A?
Have you tried connecting the USB to a computer, holding the volume up (or in the case of the galaxy, both up and down) While powering on the device? I've had to use that a few times to recover my galaxy (Thank you odin!!).
Now in regards to the OP, I would recommend using a program like Ti to back everything up, unlock the bootloader then restore from Ti, it's a little more hassel, but you can pretty much keep your settings and data. Personally, i rooted my phone before configuring a single thing on it.
kmhil said:
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
there is no way to make a good backup without rooting.
basically yes, you will lose all your settings
there are a few apps you can use to backup your apk before unlocing/rooting the phone.
look for App admin on market https://market.android.com/details?id=az.mecid.appadmin&feature=search_result
the stuff backed to SD does not get wiped
only the internal storage stuff
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
i took about 12 minutes total to unlock my bootloader, flash clockwork, and flash a custom rom. its not difficult if you pay attention to what you read. youre phone is not bricked. btw, i read your threads. if you werent so demanding, i would have helped. use the pdanet website the next time you need to install the proper driver, and follow the directions that they give you.
When I unlocked I used Astro to back up my apps, I turned on the Google data sync to back up my contacts and I did a back up of my SD on my computer.
When the unlock and recovery was done NS asked for my Google account then it restored all my contacts, Astro restored all my apps and I restored my files from my computer. A few steps but not difficult at all.
You will have to redo your accounts and data, and maybe an app or two won't load but the market will show them installed, just reinstall any that didn't.
Make sure you follow the directions properly in the forum. I had to use two computers to get it to work, but it did work and nothing was damaged.
With all that said.... This was the first time I have ever owned or altered an Android phone. Sure I was nervous... Now I'm hooked.. haha
I wound up using NSCollab .17 so far so good..
First thing I did when I got my phone was fastboot oem unlock.
Even if you don't want to root, use another ROM. Fastboot unlock it so your data doesn't get wiped.
If your hardware and everything seems okay, then flash Clockwork Recovery and do a nandroid backup so you can restore to pre-flashing point if you need it for OEM purposes.
Afterwards, go crazy and flash like theres no tomorrow and find something that you'll like.
And agreed with simms. You've made so made so many threads about this. I would help you step by step but I've been busy so I can't do that anymore. But if you search, you'll find about two or three threads where I did help somebody get their phone to a working state.
The basic idea is... if your phone doesn't boot but you can get to recovery.
- Download a ROM or Nandroid backup
- Install USB drivers
- Fastboot oem unlock (if you haven't)
- fastboot flash recovery recovery.img (or whatever the recovery.img is named) should be in /sdk/tools
- reboot into recovery (adb reboot recovery)
- mount and storage: mount USB, put the nandroid backup or ROM onto phone
- nandroid restore or flash a ROM (wipe factory,dalvik,cache --> flash ROM (if its CM7.. flash gapps afterwards)
- reboot
your phone boots. alternatively, you can use Odin but thats not a popular method but the choice is available if you wish to go towards that approach
in the worse worse possible case scenario there is always ODIN to the rescue
Why did you guys wait at all?
Once i got the phone i immediately plugged it into my computer and rooted it.
Hi folks,
There was this wonderful guide on how to root a phone. Well, I'm stupid. I admit it.
I have NO idea what flashing means or what ROMing does...
regardless, my sole aim & purpose here was to figure out a way HOW to get my phone in a state, where i can delete ANY APPLICATION tmobile puts on my bloody phone that i don't want or need. much like getting a new HP laptop...i buy my own OS and delete everything and start from scratch...
so first i got my unlock code from tmobile...so my phone is unlocked...but i still can't delete any app
so guy next to me who i know and writes apps for android says i should root my phone
well i think i'm rooted...but can't confirm...
regardless, going through this process of rooting...it cleared out phone contents...which i knew it would...you know SD data, sim card data...photos, etc etc...
lol...well now i forgot what gmail ID i used to store all my phone contacts that sucks for me...
So HOW do i get my phone to a state where i can delete anything i want on my phone?!! Thx
Unlock bootloader, flash recovery e.g twrp (v 2.3.3 recommended, higher versions have problems) flash super user then download system tuner and delete the bloat or stuff u don't want under system tab
Sent from my HTC One S using xda app-developers app
This guide makes it pretty easy.
http://forum.xda-developers.com/showthread.php?p=24478083
Follow the steps to unlock bootloader, get a new recovery, and a custom Rom.
Customs Roms don't come with all that tmobile bloat. If you like Sense, try Viper One S.
Goodluck and enjoy the wonderful world of xda.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
This guide makes it pretty easy.
http://forum.xda-developers.com/showthread.php?p=24478083
Follow the steps to unlock bootloader, get a new recovery, and a custom Rom.
Customs Roms don't come with all that tmobile bloat. If you like Sense, try Viper One S.
Goodluck and enjoy the wonderful world of xda.
Click to expand...
Click to collapse
I don't know what a ROM is
But yes, I don't like ANY of the Tmobile bloated software...my INTENTION is to delete all the apps it puts on and just put my own on.
I also don't know what new recovery means.
I'm a guy that pretty much has used Win7 for ages & ages..this is my "realistically" first smartphone, because the "actual 1st" had a broken screen and didn't play with it much. All of this Android stuff is pretty new.
So yeah, I just like clean slates...I pretty much just want my phone to play the music I add on it, my Pandora & watch a few TV shows that I add to the phone via USB from my PC.
As a side question, is it OKAY to ask about "cracked" apps...meaning finding apps that are free but are normally billable..thanks.
Earlier this morning I did go to one of the threads here to start "rooting" but I don't know if I'm done or not...how do I know?
get to know xda, not just these threads--ck out the wiki
http://forum.xda-developers.com/wiki/Main_Page
i read and searched everything when i started
you cannot discuss cracked apps as the are illegal
if you are rooted you can dl and use apps like titanium backup and root explorer from market
all this takes time but effort like everything else we do
enjoy the advantages of being rooted
and once you are make a backup (nandroid) asap and a copy of your sdcard. put both on pc also
Hi
My Verizon S3 (SCH-i535) has been off contract for a few months now. I'm considering buying a new phone, but I think the S3 is still a pretty good phone. However, I would really like to customize it a little if I'm going to keep it.
It has the latest OTA update (4.4.2), so I understand I can't load custom ROM's. But I can root it if I'm not mistaken. If that's right what I would like to do it remove some of the apps that I don't want or have no need for, but aren't uninstallable.
So, my questions are, does root let me do this? If so, is it fairly straight forward to do? And, how do I find out what is safe to remove and what will break my phone?
I'm at the point where if I can't 'make it my own' (short of a custom ROM) I'm going to by an unlocked phone. Which hopefully will give me more control than this one .
Thanks,
Jon
Yes, you can remove "unremovable" apps with root. Use Titanium Backup or a file explorer with root access. You just need to be careful that you don't remove something critical for the phone to operate. I would highly recommend installing the unofficial Safestrap for our bootloader locked phones and make a backup of the rom before you remove anything.
Sent from my SCH-I535 using XDA Free mobile app
roaddog665 said:
Yes, you can remove "unremovable" apps with root. Use Titanium Backup or a file explorer with root access. You just need to be careful that you don't remove something critical for the phone to operate. I would highly recommend installing the unofficial Safestrap for our bootloader locked phones and make a backup of the rom before you remove anything.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. I had been planning on putting a few examples in the original post as examples. But when I went in the settings and looked at all the apps again (haven't poked around in there in a while) there were dozens. I couldn't decide which to list . So I guess I will have to be careful I don't go overboard.
I'm still trying to understand what Safestrap is, or does (although I did read some of the description). It sounds like even though we can't unlock the bootloader, and therefor replace the factory ROM, we can get the device to boot an alternate ROM stored on the SD card. I keep wondering if I have this right, it sounds a little odd. Or maybe not, I can't decide.
jdnandroid said:
Thanks. I had been planning on putting a few examples in the original post as examples. But when I went in the settings and looked at all the apps again (haven't poked around in there in a while) there were dozens. I couldn't decide which to list . So I guess I will have to be careful I don't go overboard.
I'm still trying to understand what Safestrap is, or does (although I did read some of the description). It sounds like even though we can't unlock the bootloader, and therefor replace the factory ROM, we can get the device to boot an alternate ROM stored on the SD card. I keep wondering if I have this right, it sounds a little odd. Or maybe not, I can't decide.
Click to expand...
Click to collapse
Yeah, safestrap will let you run another rom, but it has to be based off of the stock 4.4.2 rom. I think there are 2 or 3. And the second rom will use the internal phone storage. So if you have the 16gb phone like I do, 2 roms don't leave much space. I just use safestrap as a custom recovery to make backups in case I screw something up and to flash a few things. I just use the stock rom and don't put a second one on. As far as what is safe to remove, if you find one you aren't sure of just Google it and you should be able to find out. There are several lists floating around. I usually disable them with titanium backup and leave them there, although a did remove a few so I could add some other apps to the system. They can't run when disabled so they aren't using ram or battery. If it has the android guy beside it, it is probably important! I think I have all the Samsung stuff and most of the Verizon disabled.
Sent from my SCH-I535 using XDA Free mobile app
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....
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.