Related
Sooo I despite the many times I reminded myself to unlock booloader as soon as I got my phone...yup I forgot . .I was so excited when I got my phone that started messing around with it. Now two weeks later I come to realize that I forgot to unlock it....****. sooo now question being; how can I make the transition painless as far as back up, restore, home screen widgets...I am aware of the any options but I want to see what was easier from experience...thanx
Sent from my Galaxy Nexus using XDA App
Accept the pain.
Sent from my Galaxy Nexus using xda premium
Make a backup, unlock, restore backup.
Not seeing too many difficulties with that concept myself...
djmcnz said:
Make a backup, unlock, restore backup.
Not seeing too many difficulties with that concept myself...
Click to expand...
Click to collapse
And what do u suggest I backup with? Google does that for me...I'm talking about my system data and app data.
Sent from my Galaxy Nexus using XDA App
pr3cision said:
And what do u suggest I backup with? Google does that for me...I'm talking about my system data and app data.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
How about good old TitaniumBackup? It has been updated for ICS.
Petrovski80 said:
How about good old TitaniumBackup? It has been updated for ICS.
Click to expand...
Click to collapse
Titanium backup needs root. You cannot make a nandroid backup without root/custom recovery either. Unless you found a way around the bootloader, you need to unlock it before you have root access. So, you're in a pickle.
Honestly, I'd say to just use the built in screenshot function to save what your screens look like. Rely on the Market auto-restore feature to make the restoration quicker, and set it up over again.
If you want to save your texts, use SMS Backup and Restore (free app). Save your images and vid to your computer to stick back on there after.
Good luck!
Wait a minute...
Couldn't you just flash clockwork mod through fastboot without root?
Or does fastboot only work once unlocked?
Sorry if I sound ignorant, I don't know the answer myself because I unlocked immediately. Therefore I don't know what would happen if you were to try and flash CWM via fastboot while locked.
Anyone know?
thanasisc4 said:
Wait a minute...
Couldn't you just flash clockwork mod through fastboot without root?
Or does fastboot only work once unlocked?
Sorry if I sound ignorant, I don't know the answer myself because I unlocked immediately. Therefore I don't know what would happen if you were to try and flash CWM via fastboot while locked.
Anyone know?
Click to expand...
Click to collapse
You have to unlock the bootloader in order to make changes to recovery.
With the bootloader locked, it won't let you make any changes to system image files.
On other phones, there are exploits available to trick the phone into unlocking the bootloader. On Nexus devices, all you have to do is "fastboot oem unlock"
Nothing bad will happen if you try to flash it with the bootloader locked. It'll just simply deny you the access to override the existing recovery with the one you wish to flash.
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Follow instructions in Method 1 here.
simms22 said:
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
Click to expand...
Click to collapse
He's asking how to root, not how to flash a rooted custom ROM...
efrant said:
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
simms22 said:
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
Click to expand...
Click to collapse
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
simms22 said:
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
Click to expand...
Click to collapse
Which is exactly what i said to do: flash cwm and flash su.zip. nothing else.
morfic said:
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
Click to expand...
Click to collapse
Not sure I understand what you are saying.
Sent from my Galaxy Nexus using Tapatalk 2
Moved to Q&A
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
i think this method is pretty easy. i had no issues using it.
http://forum.xda-developers.com/showthread.php?t=1392310
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
thos25 said:
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
morfic said:
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
Click to expand...
Click to collapse
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
thos25 said:
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
the newest twrp touch recovery is sweet, cwm doesnt even come close. when you do decide to set your nexus free, give it a try
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Install GNex Toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310. First do option 1 (drivers) and than option 7 (one-click for all). You have root and cwm, works like a charm and is the easiest way to do it.
Jubakuba said:
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
Click to expand...
Click to collapse
Im bootloader unlocked, cwr.
im very computer savvy, and tech savvy, i know what im talking about, so everything i say i am completely positive of, i am experienced with android, i just dont know how to root. I have the su.zip on my sd card btw.
Good Lord,
One question and so many answers, no wonder new users are confused--
Don't pay attention to me--just bored atm and trying to decide btw the GN tmobile or One S to replace my N1--
Nothing like hijacking a thread either--
I prefer to use Galaxy Nexus Root Toolkit. Its very simple and do the job well. Never experiencing any problems with it.
Sent from my Galaxy Nexus using Tapatalk 2
Hey I recently got a glxy nexus, have some questions about rooting and flashing and some problems,
1.the first thing I don't understand is why my phone doesn't update to latest android? Still on 4.2.1, its a nexus ,so I think it should get update since first boot, anybody else have this problem?
2.so the device is not updating, I plan to root and flash it, so I'm doing this, 1. Unlock bootloader via fastboot ,,2. Flash twrp via fastboot , and start flashing roms! (These steps are my mind generated) so tell me , did I miss anything? Do I need to do something else, ? Really appreciate your answers,
Sent from my Galaxy Nexus using xda app-developers app
or you can use toolkit, if you are not sure of what u are doing.
razi914 said:
Hey I recently got a glxy nexus, have some questions about rooting and flashing and some problems,
1.the first thing I don't understand is why my phone doesn't update to latest android? Still on 4.2.1, its a nexus ,so I think it should get update since first boot, anybody else have this problem?
2.so the device is not updating, I plan to root and flash it, so I'm doing this, 1. Unlock bootloader via fastboot ,,2. Flash twrp via fastboot , and start flashing roms! (These steps are my mind generated) so tell me , did I miss anything? Do I need to do something else, ? Really appreciate your answers,
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
1- it will not update (or take a lot longer to) unless you're running yakju/takju.
2- perfect, you did your homework.
a manta wrote this.
beekay201 said:
1- it will not update (or take a lot longer to) unless you're running yakju/takju.
2- perfect, you did your homework.
a manta wrote this.
Click to expand...
Click to collapse
hey just curious , is flashing a kernel the same way as rom? i mean do we have to flash boot.img via fastboot? and what is download mode? i heard it is used to flash stock roms on samsung devices , does it do the same on a galaxy nexus ?
razi914 said:
hey just curious , is flashing a kernel the same way as rom? i mean do we have to flash boot.img via fastboot? and what is download mode? i heard it is used to flash stock roms on samsung devices , does it do the same on a galaxy nexus ?
Click to expand...
Click to collapse
kernels are normally packaged into recovery flashable zips. some include all they need inside a boot.img, some don't. if all they need is boot.img, then yes, 'fastboot flash boot boot.img' would be the correct command.
download mode is indeed the interface by which normally Samsung devices interact with a computer. It's far more easier to get an updated factory image in "fastboot format" than in Odin package files, in part because, if you're running yakju or takju, Google takes care of the software, and that's why fastboot should always have higher priority than Odin.
But yes, download mode is one more option.
Read this: http://forum.xda-developers.com/showthread.php?t=1812959
Ok, one more thing , that one thing which is scaring me , what is this omap44 thing going on? I read somewhere that galaxy nexus bricked after installing cm,, or while charging,, is this thing has anything to do with unlocking bootloader or flashing roms?
Sent from my Galaxy Nexus using xda app-developers app
razi914 said:
Ok, one more thing , that one thing which is scaring me , what is this omap44 thing going on? I read somewhere that galaxy nexus bricked after installing cm,, or while charging,, is this thing has anything to do with unlocking bootloader or flashing roms?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
who knows.. maybe, maybe not.
beekay201 said:
who knows.. maybe, maybe not.
Click to expand...
Click to collapse
ok , just tell me,, what are the basics to avoid bricking gnex?! i had a htc desire s before , which was not very easy to brick,bcoz i knew the basics,,but im a newbie here,
razi914 said:
ok , just tell me,, what are the basics to avoid bricking gnex?! i had a htc desire s before , which was not very easy to brick,bcoz i knew the basics,,but im a newbie here,
Click to expand...
Click to collapse
don't operate the device while on low battery, put it to charge, don't let it shutdown by itself;
flash stuff for your own variant (variants: maguro, toro, toroplus) i.e. try to stick with your own variant's dev subforum, although kernels should be compatible across all variants;
give priority to fastboot, it seems you're no stranger to the tool, you have way more "freedom" with the Nexus's fastboot than with HTC's (which also uses it, I believe?);
keep platform-tools (bundled with android-sdk or in a separate package) up-to-date; current version is R17
read the thread i linked you to, you'll also want to read up on http://forum.xda-developers.com/showthread.php?t=1626895
Will I be able to apply/receive software updates when root enabled? I am worried that I won't be able to apply google updates once root enable, is this an issue? Is there a workaround?
Thanks!
Sent from my Nexus 7 using xda app-developers app
geocine said:
Will I be able to apply/receive software updates when root enabled? I am worried that I won't be able to apply google updates once root enable, is this an issue? Is there a workaround?
Click to expand...
Click to collapse
If you install the simple fix here:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
You can install future OTAs successfully and keep root.
geocine said:
Will I be able to apply/receive software updates when root enabled? I am worried that I won't be able to apply google updates once root enable, is this an issue? Is there a workaround?
Thanks!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Just rooting doesn't prevent updates. You just lose root and have to reapply after update.
Custom recovery means you probably need to download the update file and apply it via the recovery instead of the automatic updater.
Changing or removing system files will almost definitely prevent updates being applied.
Sent from my Nexus 7 using Tapatalk 2
gbroon said:
Just rooting doesn't prevent updates. You just lose root and have to reapply after update.
Click to expand...
Click to collapse
Actually I was surprised also, but SuperSU does prevent the OTA from completing successfully.
Read the referenced link.
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
I JUST did this. I had TWRP and rooted. I has 15J. Booted my nandroid. Downloaded the 15Q update, restarted to install. TWRP caught the stock image and flashed it.
Then I booted into 15Q. I lost root and TWRP. Flashed over TWRP through fastboot and rooted.
No issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
player911 said:
I JUST did this. I had TWRP and rooted. I has 15J. Booted my nandroid. Downloaded the 15Q update, restarted to install. TWRP caught the stock image and flashed it.
Click to expand...
Click to collapse
Are you rooted using SuperSU, what version, and can I examine the zip file.
Thanks guys, actually I haven't rooted this device yet. Because I am still reading on stuff here on xda how to do it the right way and the links you posted
Sent from my Nexus 7 using xda app-developers app
sfhub said:
If you install the simple fix here:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
You can install future OTAs successfully and keep root.
Click to expand...
Click to collapse
hi sfhub, do I need to do
fastboot oem unlock
before doing
fastboot boot twrp.img ?
I've been rooted since day one and gotten ota updates fine.
I use twrp and just make sure to flash supersu each time and call it good. Not a single problem on my end.
Even still if you bork it just flash factory image. It's pretty simple to get out of a pinch. But rooting and ota should work fine as long as you keep stock image. Just reflash supersu each time and you're good to go.
Sent from my Nexus 7 using xda app-developers app
geocine said:
hi sfhub, do I need to do
fastboot oem unlock
before doing
fastboot boot twrp.img ?
Click to expand...
Click to collapse
If you aren't already unlocked then, yes.
Most people will already be unlocked though if they are rooted.
fastboot oem unlock process will force a factory reset for security purposes so backup anything important.
sfhub said:
If you aren't already unlocked then, yes.
Most people will already be unlocked though if they are rooted.
fastboot oem unlock process will force a factory reset for security purposes so backup anything important.
Click to expand...
Click to collapse
I haven't rooted my device yet , I am on all stock. Does 'fastboot boot' just loads the twrp image and not flash it?
How will I be able to backup stuff, are there any other options aside from titanium backup that requires root .
sent from flo
geocine said:
I haven't rooted my device yet , I am on all stock. Does 'fastboot boot' just loads the twrp image and not flash it?
Click to expand...
Click to collapse
Yes.
geocine said:
How will I be able to backup stuff, are there any other options aside from titanium backup that requires root .
Click to expand...
Click to collapse
There are some backup apps that don't need root, but probably need to restore.
You can also try adb backup, but it may not backup 100% of your stuff.
I'm not the best person to ask on the backup as I always unlock before I do most of the software installs just so I can avoid losing customizations later on.
sfhub said:
Yes.
There are some backup apps that don't need root, but probably need to restore.
You can also try adb backup, but it may not backup 100% of your stuff.
I'm not the best person to ask on the backup as I always unlock before I do most of the software installs just so I can avoid losing customizations later on.
Click to expand...
Click to collapse
Thanks, I am currently backing up using adb., a non 100% backup is better than no backup at all. I hate redoing things.
sfhub said:
Yes.
There are some backup apps that don't need root, but probably need to restore.
You can also try adb backup, but it may not backup 100% of your stuff.
I'm not the best person to ask on the backup as I always unlock before I do most of the software installs just so I can avoid losing customizations later on.
Click to expand...
Click to collapse
While we are it, I just want to ask if it is also possible to bring back the bootloader to a locked state. thanks.
geocine said:
While we are it, I just want to ask if it is also possible to bring back the bootloader to a locked state. thanks.
Click to expand...
Click to collapse
Yes, very simple, just type
fastboot oem lock
I would advise against doing so unless you plan to return the unit though, as if you ever need to do stuff to your system (even factory restore) then you'd need to unlock again, which would factory reset again.
sfhub said:
If you install the simple fix here:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
You can install future OTAs successfully and keep root.
Click to expand...
Click to collapse
Here is a post from sfhub
Sent from my Nexus 7 using xda app-developers app
geocine said:
Here is a post from sfhub
Click to expand...
Click to collapse
BTW the author of SuperSU recently implemented the change I made so starting in v1.55 the separate fix is no longer necessary.
sfhub said:
BTW the author of SuperSU recently implemented the change I made so starting in v1.55 the separate fix is no longer necessary.
Click to expand...
Click to collapse
The 1.55 update doesn't appear to want to install properly for me from Google Play. Is this an issue of having the OTA fix installed?
Nevermind...i guess i needed to reboot...but, this does beg the question, is there anything related to the OTA fix that needs to be "uninstalled" in general?
The Holocron said:
Nevermind...i guess i needed to reboot...but, this does beg the question, is there anything related to the OTA fix that needs to be "uninstalled" in general?
Click to expand...
Click to collapse
No, there is nothing to uninstall. It is very clean.
sfhub said:
BTW the author of SuperSU recently implemented the change I made so starting in v1.55 the separate fix is no longer necessary.
Click to expand...
Click to collapse
Is there anything I should do if I already have your fix installed?
Sent from my Nexus 7 using xda app-developers app
I'm writing this short little post to give an idea of a good starting point for the HTC One as it stands right now. There are a lot of threads and they get out-of-date quickly (just as this one will). I just picked-up my new HTC One on Tuesday of last week from a Verizon store. This just gives a fresh idea of what can be done to get started on it.
Obviously you're running these instructions at your own risk. I'm not responsible for you bricking or otherwise damaging your phone. Doing these things may (will) void your warranty and may prevent you from being able to return your phone. Run these things at your own risk.
AN IMPORTANT PUBLIC SERVICE MESSAGE: When you get your phone out-of-the-box, it's probably going to offer you an OTA update. I recommend that you do not accept an OTAs as this usually makes this process even harder than it has to be. Verizon hates having us enjoy our devices!
First, let me describe my goals here:
Unlock the bootloader and obtain S-OFF
Install a custom recovery (CWM)
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
Get wireless tether working without jumping through tons of hoops.
I'll go through the list and just describe what I did:
Unlock the bootloader and obtain S-OFF
This was fairly straightforward. Rumrunner has an excellent package that does this very easily. I checked my phone's ROM version and saw that I was running 1.10.605.15. I grabbed the Rumrunner package from here for that level.
In looking over the requirements for Rumrunner, it wanted 32-bit Linux and I run 64-bit. The easiest way to solve this problem for me was to just boot to a Xubuntu 12.10 32-bit ISO that I had on my system. If you have it burned, just boot to it. If you don't (like me), use grub2 (if you have it) and boot the ISO directly. Either way, get yourself into a live environment.
Once the ISO was booted, I got it on the network and installed adb and fastboot from the Ubuntu repositories (after I did apt-get update, of course). Connect the phone via USB and enable USB debugging:
Go to Settings -> About -> Software Information -> More
Tap the Build number field 7 times
Back up to the Settings screen again and you'll now see Developer options
Enable USB Debugging under the developer options
Verify that you can see the device on your system using adb (this should result in a device being listed by serial number):
Code:
sudo adb devices
Follow these instructions for executing Rumrunner. It worked perfectly as described. Once complete, the phone was unlocked and S-OFF with a stock ROM.
Keep the live environment up as it will just make life easier to do the next steps.
Install a custom recovery (CWM)
I pretty much always use CWM if I can. I saw that there were no issues with doing that on this phone (like there are on other phones like the Rezound). I grabbed version 6.0.4.7 of CWM (non-touch) for the HTC One from here. If I recall correctly, the device is booted back into the stock ROM at this point. Make sure your device is still connected USB and has USB debugging enabled.
Reboot into the bootloader from the command prompt:
Code:
sudo adb reboot bootloader
Once the phone comes up, it should be at the Fastboot screen (it should actually show Fastboot USB). Verify that you can see your phone with fastboot (should get your device serial number again):
Code:
sudo fastboot devices
Now you can flash CWM recovery using this command from the directory where you stored the CWM file you downloaded (such as the one I provided a link to):
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.7-m7vzw.img
After the flash is successful, reboot back into the bootloader:
Code:
sudo fastboot reboot-bootloader
Now you can choose BOOTLOADER and then RECOVERY to get access to CWM. If you really want to, you can take a backup of the stock ROM at this point. I did not because I thought it was a waste of space. I just booted back into the stock ROM and disabled USB debugging so I could stick a real ROM on the system.
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
I really wanted to give this HTC Sense 5.0 a run. I've used Sense before and it wasn't awful. This seemed less annoying than previous versions (plus, there are some nice camera features which are important to me). For that reason, I selected the stock 2.10.605.1 rooted, deodexed, debloated ROM from this thread. I also opted to do the firmware upgrade at the same time, so I grabbed the firmware for the 2.10.605.1 as well.
The instructions in this thread are easy to follow so just use those. Just a note though: Flash the firmware and ROM at the same time if you're going to do firmware at all. Instructions are in the second post on that thread.
Once the ROM was up, I did my typical setup of accounts and such. The last thing I needed was Wireless Tether support.
Get wireless tether working without jumping through tons of hoops.
I don't particularly care how I get wireless tethering (infrastructure mode) as long as it works on my phone reliably. I first tried the stock tethering as this sometimes works because the authors of "stock" ROMs sneak hacks into their ROMs. It did not work. I then tried messing around with the WiFi Tether TrevE Mod that I saw recommend a few times but this didn't pan out on the 2.10.605.1 ROM (I temporarily went to 1.10.605.15 and it worked; I went back to 2.10.605.1 when someone recommended the solution below):
http://forum.xda-developers.com/showthread.php?t=2576548
I flashed this package onto my system and, without a problem, built-in wireless tether started working. I've seen no problems.
Getting my one today. I guess I will give this a go tonight. Thanks. Anything else to look for? Thanks.
Sent from my HTC Rezound.
Rumrunner worked perfectly fine for me on Ubuntu 12.1 64 bit both times I ran it. I would try it first before downloading s 32 bit distro if 64 bit is already installed.
Sent from my HTC6500LVW using Tapatalk
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
onthehole said:
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
Click to expand...
Click to collapse
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks.
No problem.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
No problem.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
onthehole said:
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
Click to expand...
Click to collapse
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
onthehole said:
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
Click to expand...
Click to collapse
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
onthehole said:
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
Click to expand...
Click to collapse
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
will do. thanks.
onthehole said:
will do. thanks.
Click to expand...
Click to collapse
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
onthehole said:
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
Click to expand...
Click to collapse
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
disconnecktie said:
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
onthehole said:
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
Click to expand...
Click to collapse
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
disconnecktie said:
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
understood. I will flash fresh if things aren't up to par.