Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?
ArmyMan007 said:
Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?
Click to expand...
Click to collapse
You'll still show s-off in Bootloader.
Sent from my One using Tapatalk
ArmyMan007 said:
Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?
Click to expand...
Click to collapse
Short answer is yes. But, you need to know that unlocking bootloader will wipe your phone memory clean and also some default apps will be erased too
Powered by non removable 2300 mAh battery
I already have an unlocked bootloader and the phone is rooted. So, just to be sure: will a nandroid backup be sufficient to return to stock ROM and kernel?
ArmyMan007 said:
I already have an unlocked bootloader and the phone is rooted. So, just to be sure: will a nandroid backup be sufficient to return to stock ROM and kernel?
Click to expand...
Click to collapse
Yes it would. As ghostryder12 mentioned, you'll still be S-Off when you restore the backup but yes you'll be back on stock ROM and kernel.
KidCarter93 said:
Yes it would. As ghostryder12 mentioned, you'll still be S-Off when you restore the backup but yes you'll be back on stock ROM and kernel.
Click to expand...
Click to collapse
Hurry for nandroid backups! ^_^
One final question: is there any tutorial on how to install custom ROMs and kernels as well as preform a nandroid restore?
And what kind of custom ROM and kernel would I need in order to help me get S-OFF?
ArmyMan007 said:
Hurry for nandroid backups! ^_^
One final question: is there any tutorial on how to install custom ROMs and kernels as well as preform a nandroid restore?
And what kind of custom ROM and kernel would I need in order to help me get S-OFF?
Click to expand...
Click to collapse
Instructions for flashing a ROM/kernel are usually in the first post of the ROM/kernel thread. As long as you do what it says, you shouldn't have any issues.
The exact instructions for performing a nandroid are gonna be slightly different depending on which custom recovery you choose to use. Once you've decided which you want to use (it doesn't really matter, as they all work, but I prefer to use TWRP), I'd suggest checking YouTube for a tutorial on how to do it.
Also, it doesn't matter what ROM and kernel you're using when trying to S-Off, as it's a completely separate process. I'd suggest doing a bit of reading around this forum before heading into it as doing something wrong could easily brick your device (especially when dealing with S-Off).
KidCarter93 said:
Instructions for flashing a ROM/kernel are usually in the first post of the ROM/kernel thread. As long as you do what it says, you shouldn't have any issues.
The exact instructions for performing a nandroid are gonna be slightly different depending on which custom recovery you choose to use. Once you've decided which you want to use (it doesn't really matter, as they all work, but I prefer to use TWRP), I'd suggest checking YouTube for a tutorial on how to do it.
Also, it doesn't matter what ROM and kernel you're using when trying to S-Off, as it's a completely separate process. I'd suggest doing a bit of reading around this forum before heading into it as doing something wrong could easily brick your device (especially when dealing with S-Off).
Click to expand...
Click to collapse
Will do. Thanks a bunch!
As @KidCarter93 explained, each Dev has instructions for installation. Also, some devs also prefer one recovery over another. I've used both over the past and like KidCarter93, prefer TWRP because it's very easy to understand and get it to do what I want with little thought.
Always, always make a nandroid backup and always read thru instructions several times before delving into s-off. Some methods are confusing to my feeble brain.
Since there's more than one method, find the one that's the easiest to follow. But like I said, read thru them several times to understand what you have to do and what's going to happen at each step. Nothing worse than your phone doing something that you weren't expecting and panicking for nothing. Not good for your heart.
Sent from my One using Tapatalk
Related
Hey everyone,
Im on a fully stock one, unrooted and everything, but I wish to use greenify. I've been looking around and there are many many tutorials on how to root. Each one us different, like revone, Im so confused! What do I have to do?
For now, planning on staying in a stock rom. As well, I wanna flash this:
http://forum.xda-developers.com/showthread.php?t=2102397
[APP/PORT] Xperia Honami i1 / Z Ultra Launcher [UPDATED-2013.07.13][v5.0][Multi Rez]
Can someone tell me what method to root with?
Please and thankyou!
Actually revone is a method to take security off your phone ..then you cam root...the simplest way is unlock bootloader(this will full wipe your phone back **** up!!!) Then flash a recovery then a rooted Rom or simply flash root
Revone will be easiest and best for s-off and then rooting is child's play. Head ove to Revone thread for instructions.
Sent from my HTC One using Tapatalk 4 Beta
a box of kittens said:
Actually revone is a method to take security off your phone ..then you cam root...the simplest way is unlock bootloader(this will full wipe your phone back **** up!!!) Then flash a recovery then a rooted Rom or simply flash root
Click to expand...
Click to collapse
Thank you both! When you sat backup, it's just saving your files and maybe using go backup right? No nandroid possible until after unlocking bootloader correct?
And s-off unlocks the device for custom roms right?
Sent from my HTC One
Youll have to unlock the phone via htc dev site if you are not on a developer variant of the device,flash a custom recovery, I know twrp can root the device for you,not sure about cwm...As far as wanting to flash that mod, Im 99.9% sure you will need to flash a custom rom as well,as the mod is most likely deodexed and will not work with an odexed rom which would be what your using.Greenify just requires root i believe. And revone is not the easiest way to unlock the device, can easily screw up the phone.IF unfamiliar with adb commands use the htcdev site to avoid issues until your more comfortable.
chc31 said:
Hey everyone,
Im on a fully stock one, unrooted and everything, but I wish to use greenify. I've been looking around and there are many many tutorials on how to root. Each one us different, like revone, Im so confused! What do I have to do?
For now, planning on staying in a stock rom. As well, I wanna flash this:
http://forum.xda-developers.com/showthread.php?t=2102397
[APP/PORT] Xperia Honami i1 / Z Ultra Launcher [UPDATED-2013.07.13][v5.0][Multi Rez]
Can someone tell me what method to root with?
Please and thankyou!
Click to expand...
Click to collapse
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
S-Off is NOT needed for custom roms,kernels or recovery flashing, based on what your wanting to do and being new to adb commands etc, use the htc dev site. In the custom recoveries AFTER unlocking bootloader and flashing one of them, its pretty straight [email protected] backing up the current rom installed.
chc31 said:
Thank you both! When you sat backup, it's just saving your files and maybe using go backup right? No nandroid possible until after unlocking bootloader correct?
And s-off unlocks the device for custom roms right?
Sent from my HTC One
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Youll have to unlock the phone via htc dev site if you are not on a developer variant of the device,flash a custom recovery, I know twrp can root the device for you,not sure about cwm...As far as wanting to flash that mod, Im 99.9% sure you will need to flash a custom rom as well,as the mod is most likely deodexed and will not work with an odexed rom which would be what your using.Greenify just requires root i believe. And revone is not the easiest way to unlock the device, can easily screw up the phone.IF unfamiliar with adb commands use the htcdev site to avoid issues until your more comfortable.
Click to expand...
Click to collapse
Rooting itself seems easy, shouldn't be a problem. Well I could use twrp, which is better, that or cwm? Yea I'm not so good with adb... I get confused a lot, esp with spaces and characters... Like is there a space or whatnot.. long story lol
Yea I had an HTC sensation with greenify.. can't even remember how I rooted it hahaha. But the dev thing seems the way to go. Would you please be able to explain to me what odexed /deodexed means? Thanks!
Sent from my HTC One
chc31 said:
And s-off unlocks the device for custom roms right?
Sent from my HTC One
Click to expand...
Click to collapse
If you don't know what s off is you don't need it yet... Do some more research and etc...but for now head over to HTCdev.com and then flash cwm or twrp..then you can simply flash a stock rooted Rom or whateve you may wish...
And for quaestion about back up...just back up anything you may want to your computer ...sd contents will be formatted with unlock
chc31 said:
Rooting itself seems easy, shouldn't be a problem. Well I could use twrp, which is better, that or cwm? Yea I'm not so good with adb... I get confused a lot, esp with spaces and characters... Like is there a space or whatnot.. long story lol
Yea I had an HTC sensation with greenify.. can't even remember how I rooted it hahaha. But the dev thing seems the way to go. Would you please be able to explain to me what odexed /deodexed means? Thanks!
Sent from my HTC One
Click to expand...
Click to collapse
18th.abn said:
Typically, a rom is supposed to be odexed for smoother and faster loading of apps into memory. Each app(.apk) has a corresponding sister file(.odex). When a app is opened, called to memory, the. Odex has the information needed to start loading the app. A rom that is deodexed has only the.apk file. So when it is opened/called to memory the information to load the app is inside of the .apk and and must be pulled from it to begin loading it into memory. So at this level you would probably ask "then why are most custom roms deodexed?" People really started deodexing roms for themability. It is much much simplier to theme roms that are deodexed. It wasnt for faster speeds but for easier customization. So "themers" could build custom themes instead of have to build a whole themed rom. So now on one side you have odexed for speed, or deodexed for customizations? Well the brilliant devs in the android world came up with pretty good solutions to even out the field. In most any custom deodexed, youll see that they zipalign all the .apks in boot. While boot up time will be slightly longer, zipaligning optimizes every. Apk on every reboot which basically optimizes the information in each. Apk so when it is called to memory, the information is at the ready and quickly loaded witbout the need of a. Odex file. I kinda rambled here but wanted to answer this one as best i could because i kno many people wonder, and not a whole lot always ask. Hope this helps explain a little bit for anyone curious. :beer:
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
There you go!
a box of kittens said:
There you go!
Click to expand...
Click to collapse
Awesome, thank you! Such a helpful community haha. And could I flash the Xperia stuff on a non-deoxed Rom but use zipalign? Am I getting this correctly?
Sent from my HTC One
No,if the mod is deodexed,the rom must be deodexed
chc31 said:
Awesome, thank you! Such a helpful community haha. And could I flash the Xperia stuff on a non-deoxed Rom but use zipalign? Am I getting this correctly?
Sent from my HTC One
Click to expand...
Click to collapse
Wonders_Never_Cease said:
No,if the mod is deodexed,the rom must be deodexed
Click to expand...
Click to collapse
Simple and straightforward, thanks!
revone can be used to unlock, you don't HAVE to S-Off with it.
Hey guys, I'm planning to get an HTC One on AT&T in 2 months when I'm eligible for an upgrade and will install a custom ROM (I'm going for Pacman) as soon as I get the phone. I just wanted to know the basic steps I need to do. Don't bother writing me an in-depth guide; I just want to know the order of things I have to do. I'll look up the specifics for each step myself.
For example:
Get root access
Unlock bootloader
Install custom recovery
Backup everything with Titanium
Etc.
(I just made that list up off the top of my head :silly: I know it is missing things and out of order)
AceofSpades117 said:
Hey guys, I'm planning to get an HTC One on AT&T in 2 months when I'm eligible for an upgrade and will install a custom ROM (I'm going for Pacman) as soon as I get the phone. I just wanted to know the basic steps I need to do. Don't bother writing me an in-depth guide; I just want to know the order of things I have to do. I'll look up the specifics for each step myself.
For example:
Get root access
Unlock bootloader
Install custom recovery
Backup everything with Titanium
Etc.
(I just made that list up off the top of my head :silly: I know it is missing things and out of order)
Click to expand...
Click to collapse
unlock your bootloader
flash(install) custom recovery
make nandroid backup of your stock ROM
backup your apps & settings with Titanium
flash away your desired ROM
restore your apps & settings via Titanium
happy flashing :good:
kamilmirza said:
unlock your bootloader
flash(install) custom recovery
make nandroid backup of your stock ROM
backup your apps & settings with Titanium
flash away your desired ROM
restore your apps & settings via Titanium
Click to expand...
Click to collapse
Does this mean I don't have to root? And do I need to do anything with S-off or S-on?
Also, since I'm planning on flashing the ROM as soon as I get the phone (meaning there will be no apps that didn't come with the phone and the settings will stay default) do I even need to backup with Titanium?
AceofSpades117 said:
Does this mean I don't have to root? And do I need to do anything with S-off or S-on?
Also, since I'm planning on flashing the ROM as soon as I get the phone (meaning there will be no apps that didn't come with the phone and the settings will stay default) do I even need to backup with Titanium?
Click to expand...
Click to collapse
your custom rom will be 'rooted', so no, there's nothing extra to do.
the nandroid backup you take is like a snapshot of your stock rom. can be handy if you ever need to go back to stock for repair etc.
in the circumstances you provided, I probably wouldn't backup the stock apps with Titanium, but there might be some carrier specific stuff you want to keep.
most roms don't need s-off. check and see in the individual rom threads, so s-off is not a mandatory thing to do.
good luck.
cr1960 said:
your custom rom will be 'rooted', so no, there's nothing extra to do.
the nandroid backup you take is like a snapshot of your stock rom. can be handy if you ever need to go back to stock for repair etc.
in the circumstances you provided, I probably wouldn't backup the stock apps with Titanium, but there might be some carrier specific stuff you want to keep.
most roms don't need s-off. check and see in the individual rom threads, so s-off is not a mandatory thing to do.
good luck.
Click to expand...
Click to collapse
In this video, the guy says that the phone needs to be rooted before installing the ROM around 0:48. I found this video from this forum post by the OP of both the m7ul and m7att Pacman threads. Should I root the phone? I'm not sure what to do now.
AceofSpades117 said:
Hey guys, I'm planning to get an HTC One on AT&T in 2 months when I'm eligible for an upgrade and will install a custom ROM (I'm going for Pacman) as soon as I get the phone. I just wanted to know the basic steps I need to do. Don't bother writing me an in-depth guide; I just want to know the order of things I have to do. I'll look up the specifics for each step myself.
For example:
Get root access
Unlock bootloader
Install custom recovery
Backup everything with Titanium
Etc.
(I just made that list up off the top of my head :silly: I know it is missing things and out of order)
Click to expand...
Click to collapse
Backup your info before the unlocking of the bootloader.
And, if your upgrade is in two months, I would suggest waiting for the m8. It should be out by March /April and will pack all the features on the m7 plus more. And it will probably be at the same price.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 01:52 PM ---------- Previous post was at 01:47 PM ----------
AceofSpades117 said:
In this video, the guy says that the phone needs to be rooted before installing the ROM around 0:48. I found this video from this forum post by the OP of both the m7ul and m7att Pacman threads. Should I root the phone? I'm not sure what to do now.
Click to expand...
Click to collapse
You should most definitely root. You should root before the installation of a custom rom because some functions may not work. Since you seem like a beginner, I would suggest using an One - Click. Method called "Kingo Root". This is by far the fastest and easiest method I've come across. Just Google it
Sent from my HTC One using XDA Premium 4 mobile app
AceofSpades117 said:
In this video, the guy says that the phone needs to be rooted before installing the ROM around 0:48. I found this video from this forum post by the OP of both the m7ul and m7att Pacman threads. Should I root the phone? I'm not sure what to do now.
Click to expand...
Click to collapse
it's not necessary/essential.
like I said earlier, the root comes with the rom.
I have had like 8 different devices and never rooted as part of unlocking. never. never had a problem either.
unlock bootloader - install custom recovery (I recommend twrp) - flash custom rom.
I hope one of you kind people can help. I have a HTC one M7 which I need to return to stock to get a warranty repair. It has been s-off'd (?) and is running hboot 1.55 on an ORANG001 cid. I have tried to restore a CWM nandroid backup (which failed) and I don't seem to be able to find an RUU for my CID. Can anyone help with this please ? All the posts I have found have been outdated, or relate to different CID's.
Thanks in advance,
Andy
see this guide for returning to stock with a nandroid unfortunately there is no ruu for your device. But your already s-off that's the hardest part about returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
Specifically posts #5 CWN nandroid and #6 TWRP nandroid
Danny201281 said:
see this guide for returning to stock with a nandroid unfortunately there is no ruu for your device. But your already s-off that's the hardest part about returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
Specifically posts #5 CWN nandroid and #6 TWRP nandroid
Click to expand...
Click to collapse
Thanks, almost there I just don't know which stock recovery I need ??? . My build number (after restoring the nandroid orang001 cid) is 2.24.61.1 is that the version I should be using to try to find the stock recovery ? If so, any idea where I can get it from ?
Thanks,
Andy
kronos1uk said:
Thanks, almost there I just don't know which stock recovery I need ??? . My build number (after restoring the nandroid orang001 cid) is 2.24.61.1 is that the version I should be using to try to find the stock recovery ? If so, any idea where I can get it from ?
Thanks,
Andy
Click to expand...
Click to collapse
This is the closest i could find should work fine for you
https://www.androidfilehost.com/?fid=95864024717070703
Oh poo ! I've got almost to the end (locked bootloader, software update) and I noticed my kernel version is still showing as root. So I think my twrp restore had the root kernel included Now I can't unlock the bootloader to reflash as there is no su on the phone. I'm still s-off, how can I recover from this ?
Thanks for all your help so far,
Andy
kronos1uk said:
Oh poo ! I've got almost to the end (locked bootloader, software update) and I noticed my kernel version is still showing as root. So I think my twrp restore had the root kernel included Now I can't unlock the bootloader to reflash as there is no su on the phone. I'm still s-off, how can I recover from this ?
Thanks for all your help so far,
Andy
Click to expand...
Click to collapse
nothing to worry about their the stock kernel has the word root in it
clsA said:
nothing to worry about their the stock kernel has the word root in it
Click to expand...
Click to collapse
Excellent. Thanks for the tip.
Andy
Danny201281 said:
This is the closest i could find should work fine for you
https://www.androidfilehost.com/?fid=95864024717070703
Click to expand...
Click to collapse
fyi, common mirrors are in post #7, including
HTC One M7_UL - modelid=PN0710000 - cidlist=ORANG001
nkk71 said:
fyi, common mirrors are in post #7, including
HTC One M7_UL - modelid=PN0710000 - cidlist=ORANG001
Click to expand...
Click to collapse
Thanks, I should have known to look there, considering I used your guide myself [emoji5]
Danny201281 said:
Thanks, I should have known to look there, considering I used your guide myself [emoji5]
Click to expand...
Click to collapse
Unfortunately the guide seems to have become a bit of mess ... too much stuff in there, not sure how to write it to make things clearer
nkk71 said:
Unfortunately the guide seems to have become a bit of mess ... too much stuff in there, not sure how to write it to make things clearer
Click to expand...
Click to collapse
Nah I think the RUU guides are fine, The Nandroid guide is a little overcomplicated but I don't see how you can simplify it in any way. There are so many variations of HTC One with different firmware's.
Short of cutting out all helpful link's and addon info and just leaving the bare bone guide for users to figure out for them selves exactly which files they need, which I think would only lead to more cries for help in your thread anyway. It's about as simply/comprehensive as it can be. :good: You've done a great job you should be very proud of your thread. It's help many many people here on XDA, and I've no doubt it will help many more. :highfive:
Danny201281 said:
Nah I think the RUU guides are fine, The Nandroid guide is a little overcomplicated but I don't see how you can simplify it in any way. There are so many variations of HTC One with different firmware's.
Short of cutting out all helpful link's and addon info and just leaving the bare bone guide for users to figure out for them selves exactly which files they need, which I think would only lead to more cries for help in your thread anyway. It's about as simply/comprehensive as it can be. :good: You've done a great job you should be very proud of your thread. It's help many many people here on XDA, and I've no doubt it will help many more. :highfive:
Click to expand...
Click to collapse
thanks mate :good:
I will try (at some point) to make it more readable.... it kinda grew over time... and seems to have become a bit of a dinosaur; so we'll see if i ever get around to that
if you have any suggestions, do let me know
nkk71 said:
thanks mate :good:
I will try (at some point) to make it more readable.... it kinda grew over time... and seems to have become a bit of a dinosaur; so we'll see if i ever get around to that
if you have any suggestions, do let me know
Click to expand...
Click to collapse
Ok well, and this is only a suggestion, but maybe it's time to replace the Nandroid guide with a Guru reset zip guide. I think there are enough 1.xx and 2.xx reset zips to make this viable now. It removes the need to find a separate Stock recovery and the use of modoco with out movie zip for replacing the preload apps as this is all included in the reset.zip and/or firmware.zip.
Only files required are the HTC WWE RUU CWM.img and a reset.zip with matching firmware.zip. It could help to reduce or simplify the extra content in the guide. I'm sure mike1986 would be more than happy for you to link to his firmware repository. I have a txt file mockup of the required steps. If your interested in taking a look i'd be happy to share it. Let me know what you think :good:
Danny201281 said:
Ok well, and this is only a suggestion, but maybe it's time to replace the Nandroid guide with a Guru reset zip guide. I think there are enough 1.xx and 2.xx reset zips to make this viable now. It removes the need to find a separate Stock recovery and the use of modoco with out movie zip for replacing the preload apps as this is all included in the reset.zip and/or firmware.zip.
Only files required are the HTC WWE RUU CWM.img and a reset.zip with matching firmware.zip. It could help to reduce or simplify the extra content in the guide. I'm sure mike1986 would be more than happy for you to link to his firmware repository. I have a txt file mockup of the required steps. If your interested in taking a look i'd be happy to share it. Let me know what you think :good:
Click to expand...
Click to collapse
thanks for the suggestion, but i had considered that a long time ago (even did a few back to stock, using Guru Reset ROMs), and even though it could be simpler (on a case by case basis), several reasons i'm not going for that
1- a lot more nandroids available than Guru Resets
2- one or two Guru Resets are actually "wrong-ish" (can't remember which, but they did have something modified, so OTAs didnt work)
3- i prefer to sticking with 1.xx versions, due to the [possible] tampered coming back (still not sure what/when/why this is triggered)
4- ^^ dont want people using 3.xx+ Guru Reset's and getting the tampered back... had one a couple of days ago
i know it's a bit more complicated, but considering it hasnt failed anybody yet (as far as i know), i'll stick with the longer version
nkk71 said:
thanks for the suggestion, but i had considered that a long time ago (even did a few back to stock, using Guru Reset ROMs), and even though it could be simpler (on a case by case basis), several reasons i'm not going for that
1- a lot more nandroids available than Guru Resets
2- one or two Guru Resets are actually "wrong-ish" (can't remember which, but they did have something modified, so OTAs didnt work)
3- i prefer to sticking with 1.xx versions, due to the [possible] tampered coming back (still not sure what/when/why this is triggered)
4- ^^ dont want people using 3.xx+ Guru Reset's and getting the tampered back... had one a couple of days ago
i know it's a bit more complicated, but considering it hasnt failed anybody yet (as far as i know), i'll stick with the longer version
Click to expand...
Click to collapse
Yeah, all very good points. I certainly hadn't considered the fact that not all lower end guru reset's give a full stock rom with OTA's. :good: and that's exactly why your guide is the best. You have made it as good as it can be. As I say you should be proud of it.
With everything you have in the guide there's no reason why anyone should have to much trouble, as long as they take the time to read through it and understand there requirements before they start the process.
Danny201281 said:
Yeah, all very good points. I certainly hadn't considered the fact that not all lower end guru reset's give a full stock rom with OTA's. :good: and that's exactly why your guide is the best. You have made it as good as it can be. As I say you should be proud of it.
With everything you have in the guide there's no reason why anyone should have to much trouble, as long as they take the time to read through it and understand there requirements before they start the process.
Click to expand...
Click to collapse
i think only one (possibly two) are not entirely correct, nobody's fault in particular, just happened the system dump
wasn't entirely proper
and point 5 (forgot to mention that):
I do expect people to read it over and over and over, until they know what they are getting themselves in to....... i could probably compile Guru RUUs for every nandroid out there, but much of the guide includes a lot of OT information, which (imho) gives a lot of clarity once read :cyclops:
nkk71 said:
i think only one (possibly two) are not entirely correct, nobody's fault in particular, just happened the system dump [emoji14]
wasn't entirely proper
and point 5 (forgot to mention that):
I do expect people to read it over and over and over, until they know what they are getting themselves in to....... i could probably compile Guru RUUs for every nandroid out there, but much of the guide includes a lot of OT information, which (imho) gives a lot of clarity once read :cyclops:
Click to expand...
Click to collapse
I totally agree, everything needed is there if people just take the time to read. I certainly didn't have any problems using the nandroid guide as you know.
I did spend at least 3 days familiarizing my self with the procedure. After all if people aren't prepared to do a bit of reading really they probably shouldn't mess with there phones [emoji12]
Short of traveling the world to doit for people you've made it as easy as possible :good:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Linkalex1 said:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Click to expand...
Click to collapse
Still no RUU's avaiable as HTC wont release them. your best option is to use TWRP backup and restore.
Original stock backup
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Linkalex1 said:
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Click to expand...
Click to collapse
You need to send it as it is to your phone and use TWRP > restore. choose file and done.
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Linkalex1 said:
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Click to expand...
Click to collapse
Yes OTA updates should work just fine. just look for updates in settings>about >software update.
you may have one for polaris office.
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
arm1e said:
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
Click to expand...
Click to collapse
Stock Recovery
To unroot just lock bootloader:
fastboot oem lock
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.