Sending into Samsung for Service - Question - Galaxy Tab S Q&A, Help & Troubleshooting

Interesting question:
I did THIS root procedure recently and it worked just fine. I have knox=0 and no harm done. However, I'm about to send my Tab S 8.4 SM-T700 into Samsung under warranty for service for an unrelated problem. It's for a hardware issue related to the screen that I've had since I bought it. My question has to do with sending it back for service. Sure, my knox is 0, but if they start poking around and see root applications, will it be a red flag and cause problems for me? (even though it has nothing to do with the hardware service issue).
Obviously I could re-flash the stock rom to be on the safe side, leaving a lot of work to be redone when I get the device back. I wanted to get some thoughts from any of you who have perhaps sent any Samsung devices in for service under warranty. Any insight is appreciated.
Note: You might ask why I didn't send it in first, then root after. I wasn't aware at that point that it was a hardware issue and had a theory that re-flashing the stock ROMs (byproduct of this guide) could perhaps solve the problem. It's one of those 20/20 hindsight things. For those who are curious, it's the notorious "screen flickering and sudden reboot" issue that occasionally plagues this device. I know it's unrelated, but my question is about knox=0, root, and sending in for service.

Make a full backup with flashfire then return to stock and factory reset.
Restore the backup with flashfire when you get the device back.

ashyx said:
Make a full backup with flashfire then return to stock and factory reset.
Restore the backup with flashfire when you get the device back.
Click to expand...
Click to collapse
Yeah, that sounds like the best plan. I only have one question about FlashFire (not being well versed in it), will it cause any problems backing up EVERY partition? I mean, the modem firmware seems unnecessary and I won't even be able to restore to protected partitions with FlashFire, right?
Also, I'm on T700XXU1BOE3 (Lollipop). To get root back on the SM-T700, I'll need to revert back to T700XXU1ANF7 or earlier (which will put the KitKat bootloader sboot.bin back on). Once I get root with KitKat (and the ability to restore using FlashFire), I won't be able to flash the necessary bootloader via FlashFire and I'll need to reflash the Lollipop bootloader sboot.bin via Odin after restoring. Does that sound right? Or do you foresee any issues with that method?
Edit: wording and terminology for clarity

FlashFire says: "Bootloader partitions are always protected (regardless of the current binary status) and cannot be flashed by this app. If flashing them with Odin, beware that you cannot flash older bootloaders over newer ones and the bootloader decides which firmwares will boot"
I already knew the main part of that. I'm curious about the bolded part. This makes it sound like even if I flash the official stock KitKat ROM via Odin, the newer Lollipop bootloader will remain. But I'm pretty sure that's not true because I've reverted back before and successfully downgraded the bootloader to the older version via Odin for this device (I know because the older bootloader displays knox value as 0 rather than 0x0000). Any thoughts about that? Is this statement simply incorrect about flashing older bootloaders?

Flashfire doesnt flash bootloaders. Odin does.

ashyx said:
Flashfire doesnt flash bootloaders. Odin does.
Click to expand...
Click to collapse
You've misunderstood my question.

jdmillard said:
You've misunderstood my question.
Click to expand...
Click to collapse
So i misunderstood this? :what:
jdmillard said:
Once I get root with KitKat (and the ability to restore using FlashFire), I won't be able to flash the necessary bootloader via FlashFire and I'll need to reflash the Lollipop bootloader sboot.bin via Odin after restoring. Does that sound right? Or do you foresee any issues with that method?
Edit: wording and terminology for clarity
Click to expand...
Click to collapse

I had two questions:
jdmillard said:
...Once I get root with KitKat (and the ability to restore using FlashFire), I won't be able to flash the necessary bootloader via FlashFire and I'll need to reflash the Lollipop bootloader sboot.bin via Odin after restoring. Does that sound right? Or do you foresee any issues with that method?
Click to expand...
Click to collapse
<already making the point about bootloaders, FlashFire, and Odin>... I was making sure that there was no flaw in this plan since I've never done a restore this way. It appears that the answer is that there will be no issues with this method.
jdmillard said:
...beware that you cannot flash older bootloaders over newer ones ..."
Click to expand...
Click to collapse
I was asking whether or not this statement is correct. It seems that it is not correct because I know I've reverted back to an older bootloader before (when I reverted back to KitKat to get root).

Related

[Download]AT&T Kitkat OTA file

Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.

SuperSU and Stock Recovery

is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
You need a custom recovery (TWRP or CWM).
bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.
BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.
ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....
bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.
ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"

Verizon LG G Pad 8.3 system update

I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G
I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512
OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..

What happens if flash fails?

I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.

Help – I'm lost. New to HTC and quite confused about flashing/rooting/...

Hey there,
I've got my first HTC device some days ago (-> HTC 10), but coming from a Nexus 5 where things are handled differently, I'm currently quite confused on how all of this works with my HTC 10.
I'd like to apologize in advance if the following questions seem to be stupid or unnecessary, but I'd like to use my device to the fullest and therefore I need your help.
My device is not branded (as far as I can tell) and I've already unlocked it via the steps on htcdev.com + I've installed TWRP + SuperSU (thanks to my previous knowledge with my N5 this was somewhat easy).
Now I got my first OTA update and this is when things got complicated. Several questions popped up and I tried to answer them myself while looking over here, but after reading all those threads I'm even more confused than before :/
My questions are the following:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4)
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them?
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty?
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data?
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though?
I'm completely fine with losing my current data if that means that I can set it up my device in such a way that I can avoid any further data wipes when flasing/updating.
I'd be absolutely grateful if someone would answer those questions and help me to understand all of this.
Greetings,
makit_
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
not an expert but here's my thoughts...
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data? Yes. see also #1
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though? I think you meant sim unlocking here?? Generally, "unlocking" mostly mentioned in xda refers to bootloader
Tarima said:
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
Click to expand...
Click to collapse
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
side_flip15 said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
Click to expand...
Click to collapse
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
side_flip15 said:
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
Click to expand...
Click to collapse
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
side_flip15 said:
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
Click to expand...
Click to collapse
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
side_flip15 said:
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
Click to expand...
Click to collapse
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
side_flip15 said:
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
Click to expand...
Click to collapse
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
Click to expand...
Click to collapse
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
Click to expand...
Click to collapse
Data partition can be backed up actually and can be restored.
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
Agree. there is no sense in reverting back to s-on unless if it's for warranty purposes.
Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Click to expand...
Click to collapse
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing
Click to expand...
Click to collapse
Take a look at this link. It provides you a complete explanation between ROM and Firmware.
Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Click to expand...
Click to collapse
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
makit_ said:
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
Click to expand...
Click to collapse
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
side_flip15 said:
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
Click to expand...
Click to collapse
I know that app by name, but never used it. Will take a look into it
side_flip15 said:
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
Click to expand...
Click to collapse
Do you mean like this? (found in another forum):
1. First step is to unlock bootloader:
a) If bootloader unlock is turned off on your phone, you need to turn it on first:
- Boot to Android OS and perform initial setup if necessary
- Go to Menu -> Developer settings and tick "Enable OEM unlock"
Run XTC 2 Tool and open "Bootloader unlock" tab, follow instructions to unlock your bootloader.
2. Reboot to download mode, open "HTC 10" tab and install twrp recovery, you can get it here:
[...]
or
[...]
3. Boot to Bootloader, and press "Reboot to recovery".
4. In "HTC 10" tab press "Do S-OFF button".
5. Wait for the process to finish. Done.
Click to expand...
Click to collapse
side_flip15 said:
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Click to expand...
Click to collapse
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
side_flip15 said:
Take a look at [... ]this link[/URL]. It provides you a complete explanation between ROM and Firmware.
Click to expand...
Click to collapse
Thanks, will look into it.
side_flip15 said:
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
Click to expand...
Click to collapse
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification, I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Is this correct or are there any mistakes?
And thanks a ton, you've helped me so much already!
Greetings,
makit_
makit_ said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
Click to expand...
Click to collapse
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
yankee1390 said:
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
Click to expand...
Click to collapse
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
makit_ said:
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
Click to expand...
Click to collapse
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
yankee1390 said:
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
Click to expand...
Click to collapse
Will also look into this. I've used Xposed on my N5 but wasn't sure the HTC 10 is already fully supported (have read something about that, but those threads were already 3-4 months old). Thanks!
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
makit_ said:
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
Click to expand...
Click to collapse
Link didn't work on my app so can't confirm if that will work. However any TWRP stock backup that matches your current version should work. RUUs will wipe your data if you use them.
Definitely good idea to backup after each ota before modifying system partition to make next ota easier. Though usually someone on here can provide a backup if you don't get one.
I know that app by name, but never used it. Will take a look into it
Click to expand...
Click to collapse
i suggest you purchase a pro version. It's a really a must-have app
Do you mean like this? (found in another forum):
Click to expand...
Click to collapse
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
Click to expand...
Click to collapse
Yeah. They might not know we can s-off. lol
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification
Click to expand...
Click to collapse
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Click to expand...
Click to collapse
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
And thanks a ton, you've helped me so much already!
Click to expand...
Click to collapse
You are welcome.
---------- Post added at 02:22 AM ---------- Previous post was at 01:44 AM ----------
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
side_flip15 said:
i suggest you purchase a pro version. It's a really a must-have app
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah. They might not know we can s-off. lol
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
You are welcome.
Click to expand...
Click to collapse
Thanks for all your help. I will look into it when I need it. For now I'll stick with stock (see below)
side_flip15 said:
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
Click to expand...
Click to collapse
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Piggybacking on this thread because my new-to-me HTC 10 is coming in the mail and I'm planning what to do with it. It is already bootloader unlocked and s-off. I would like to use Leedroid, ElementalX, Magisk, and Xposed.
I've never had an HTC device so I just want to make sure I'm doing this right. So I think this is what I need to do:
1) Flash TWRP via ADB
2) Flash SuperSU in TWRP
3) Flash everything else...Leedroid, ElementX, Xposed, Magisk. In that order? Can I flash them all at once (just keep adding zips to the TWRP list) or do I have to boot between each one?
Xposed is more important to me than a custom ROM, because I need to use Amplify and PowerNap to improve my battery life. Would it be better just to stay on stock instead of Leedroid?
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Click to expand...
Click to collapse
When I said stock ROM, i meant stock HTC ROM and it's not stock Android. It's a skinned android called HTC sense. . If you want a stock android to run in your HTC 10 you can flash a AOSP based custom ROM.
Magnum_Enforcer said:
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
Click to expand...
Click to collapse
Ah yeah, sorry, fastboot is what I meant. Thank you! I haven't had an unlocked bootloader in quite a while (was using TWRP and Sony stock-based ROMs on a locked Z3c), so it will be interesting to flash kernels and such again.
d_Schizzo said:
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
Click to expand...
Click to collapse
not only bootloader, it contains everything. radio.img and any other thing. "low-lewel-stuff", kernel etc, recovery (if stock signed firmware, which is not modded/removed). there are many important things inside.
but firmware is meant for every device the same. it contains everything so that this device can run/work properly.

Categories

Resources