Related
What do I have to do to install a custom recovery and get root?
Where do I get the ASUS specific drivers for all of normal, recovery
and boot-loader modes, for adb, fastboot and 'disk drive'?
I can use ADB and fastboot SDK utilities from the Win7 console prompt.
the appropriate dll's and exe's are in windows path.
Are there special things to do like HTC's hboot unlock procedure?
I saw an apk file on ASUS's website for unlock, how does that work?
I found 1-click root script that is supposed to install an CWM
custom recovery and get root for you. Do I need to do anything prior
to running that to unlock the boot loader, so it will accept the fastboot
commands? Besides setting usb debug and any allowing any apk?
I don't know how to interact with the ASUS boot loader for
loading updates. For HTC I only needed a specially named zip
file on the root of the ext sd card and push buttons to start
the process. Is it similar? :fingers-crossed:
Try reading this.
http://forum.xda-developers.com/showthread.php?t=1697227
All of your questions and answers have been posted a long time ago and is readily available for your reading enjoyment. At least make an attempt to research on your own. Reading is your friend....
Sent from my SGH-I777 using Tapatalk 2
OK -- RTFM *sigh*
Can I flash cwm via fastboot w/o unlocking? I just want to root
to be able to run Titanium backup and Root Explorer tools.
Stock ROM is fine, only need cwm to get root.
The device was purchased a few days ago, (waiting for it
to arrive), so its probably .29 or .30 from factory.
I discussed the issues with ASUS and they kept reading
the text of the warning message about unlocking
instead telling me how / what to do to root.
If I understood correctly, after turning off 'fast boot'
and turning on 'USB debugging', I should be able to get the
stock boot loader into fastboot USB mode following the power on
volume button presses, then use fastboot flash recovery to
store the cwm recovery.img in the recovery partition.
I'm unsure what it is that unlock boot loader apk actually does ?
With HTC it was the hboot software version that determined
if fastboot commands were accepted. Perhaps when I actually
have the device, I'll understand better.
With that done, flash the root-signed.zip from cwm to root?
Cavsoldier already advised you to do your own research. All your questions have been answered, both for your first post and your second.
I'm not entirely sure why you seem so determined to flash CWM for root. They are completely unrelated. You only flash CWM when you unlock the bootloader. You do not have to unlock your bootloader to root the device. Just use this thread.
Also not sure why you're asking Asus how to root their product. That's a big no no. Companies don't like when you root their products. Even if the CSR knows how to root the device, they're not allowed to tell you. They'll just read from a script like they did to you.
Honestly, I'm not sure why I'm bothering to answer this. All the info you could possibly need is in the thread that was linked in the second post. All of it, for every question you've asked in both of your posts in this thread. Anything root or ROM related is in that thread. It links to several rooting methods, most of which do not require CWM, let alone an unlocked bootloader. So, basically, why haven't you clicked the link in the second post? Do it.
*sigh* sorry for being dumb
Alright -- I admit I couldn't find the search forum
button on the phone interface. After I looked via a
laptop (so I had the desktop view) it was where I
thought it was.
In any case, I found the utility script debugfs-root-v1.8
which uses all adb commands so it doesn't need to be able
to run fastboot boot loader commands. It looked like the
tricky stuff was being run on the tablet via adb shell
commands and adb control commands. If I understood
it, it leaves the tablet rooted without unlocking the boot
loader. So if I can live without nandroid backups, I can just
leave the OEM stock recovery alone.
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
fuzzynco said:
*snipped*
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
Click to expand...
Click to collapse
To unroot, there's an option in superuser. Installing the new firmware will not wipe data.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Thank you.....:good:
Hi All,
Of course the first thing I did after getting my new HTC One SV is root it and install LBE privacy protection to stop data leakage. However recently ive been getting a notification of an update to jelly bean through my phone provider (Vodafone Australia). However this will not install due to custom recovery image so the pre-install check fails. I cannot find stock recovery images anywhere and even if I did, due to presence of clockwork mod cant push images via Android SDK (skips straight past hboot to clockworkmod so isn't detected as an available device).
Can anyone help me get my phone back in a state where I can install the new update and the re-root?
Am not 100% noob, am familiar with custom roms and basics required to root and use SDK, this is my 3rd android device ive played with so hopefully this question is not tooooo SIGH.
Seems like HTC one SV is too new to have its on page in XDA support?
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Not helpful
marceli-szpak said:
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Hi there,
Unfortunately I don't have permission to post messages in that thread, nor does it seem the appropriate place to ask my question as it is an area for resources not help.
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
RE HTC One SV Revert to Stock Help (for update)
marceli-szpak said:
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
snorglamp said:
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
Click to expand...
Click to collapse
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
old.splatterhand said:
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
Click to expand...
Click to collapse
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
snorglamp said:
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
Click to expand...
Click to collapse
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
?????????????*
ismailnayir said:
?????????????*
Click to expand...
Click to collapse
If's there anything you don't understand, ASK!
So nobody knows, what you want, sorry.
old.splatterhand said:
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
Click to expand...
Click to collapse
Yes I thought that might be the case but was not having any luck with search results to find out what to do. Thank the internet gods for you! Going to your thread now XD!
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
madpausa said:
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
Click to expand...
Click to collapse
DUDE! THATS TOTALLY WHAT I WANNA HEAR, however, ive been having enormous trouble getting fastbood/ADB to recognise the phone is attached, I have tried the universal clockwork mod ADB driver which didnt work, and I havent had any luck folloing the instructions on Splatterhand's other threads in getting it recognised. The command fastboot devices just leaves a flashing cursor FOREVER! Other commands leave the message "waiting for device". According to splatterhand ADB/Fastboot wont recognise the phone as attached because of clockworkmod and therefore I cant push any commands or files...how did you solve this?
OMG
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhead for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
madpausa said:
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
Click to expand...
Click to collapse
So I took your advice and pulled a recovery image from the ICS Cricket (using the link in splatterhand's thread to stock resources) image. Downloaded the OTA and went to apply it, got past boot/recovery screen checks and all was looking good until i got to a screen with what looked to be an SD card icon and a loading bar under a larger phone icon with a green recycle type circle over it. That loading bar stopped about half way with a red triangle and exclamation mark (i.e. during the update process). Fortunately not bricked. It may be that I need the original Vodafone AU recovery image, or that there was something about the ICS OTA image that I used that made it fail. Not sure. Will try to find another stock recovery image.
Applied recovery from EU RUU stock and while that went fine and can boot into htboot no problem, when applying the OTA update it skips the fastboot and gets stuck on HTC One screen like normal loading except stuck.
I think I will try old.splatterhand's recommendation now that I am able to push things to the phone through adb/fastboot, so thanks for your commandline tip but now I must try flashing the JB recovery etc as outlined in his post.
The problem may be that the OTA is expecting a vodafone australia stock recovery as i seem to be getting different outcomes depending on which stock recovery image I apply...
I have sent Old.Splatterhand the Vodafone Australia JB OTA file for the main thread collection in case anyone wants it or the images therein, but at the moment it is of little use to me hehe.
SUCCESS! How to update to Jelly Bean from modded/rooted HTC One SV ICS
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Good to see you got your problem sorted out!:highfive:
And the download of OTA was succesful, thanks!:good:
snorglamp said:
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Click to expand...
Click to collapse
This is the exact problem I had. I started trying to root my HTC One SV (Boost Mobile) a couple of months ago. I got past the HTC unlock bootloader, but I got confused by the rest of the rooting guide, so eventually I gave up on finishing the rooting process. Ever since then, it has said ***TAMPERED*** in hboot when I go in there. Well, just like you, I started getting the JB update notification in the OTA. I tried to install it like 15 times, but it always just rebooted into the existing image I had, which was the stock image.
So today I decided to try and finish the root and then find a JB ROM to install. old.splatterhand helped me out with getting it rooted, and it was a success. But when I asked him about JB ROMs, he said I had to have S-off. When we spoke a little more about it, he pointed me here, telling me that he helped you get the root back after you got through the OTA update.
So now, I guess I need to try and follow your instructions on getting the OTA update, and then go back to the thread where he helped you get the root back.
I'm a complete n00b to rooting android devices, but I'm pretty confident that I can do this with the proper guidance. I have rooted 2 Samsung SCH-i500s and today I finally got this HTC One SV rooted. I'm starting to see how it all works.
If you don't mind, let me know of any details of issues you faced that may not be in the guides you followed. That would be a great help.
Congrats on getting yours all done.
Thanks.
---------- Post added at 07:32 PM ---------- Previous post was at 07:15 PM ----------
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Do you type "adb reboot bootloader" in the command line? I wanna be clear on this before I make any moves.
I hope there is still people on this mytouch forum lol? I need help rooting my mytouch 4g slide its on kitkat I looked around how to on kitkat first time tryna root. Also any help out there that can guide me to not brickin it or if other steps need to be takin because of kitkat?
Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.
SOEBOMB said:
Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.
Click to expand...
Click to collapse
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
...you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
Click to expand...
Click to collapse
joel.maxuel said:
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
Click to expand...
Click to collapse
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?
SOEBOMB said:
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?
Click to expand...
Click to collapse
I don't think it's possible to be able to install a ROM without the bootloader unlocked (prerequisite for CWM, and in turn KitKat ROM). Unless you got the phone with KitKat (eBay special?) but no root (which would be weird for a seller to do), you must have lost root along the way (it can happen).
In either case, we are not talking about the bootloader. The way to check that though, is to turn on the device while holding the Vol-Dn button. This will take you into fastboot. If it says ** RELOCKED ** up top, then you're in trouble. If it says ** UNLOCKED ** or * JuoPunutbear *, it looks like you just need superuser reinstalled, and you don't need to downgrade for that.
To do this, download and install the adb binary and drivers (if you're a linux user, all you need to do is an 'apt-get install adb' or whatever your distro uses). Turn on the device normally, go into Developer under settings (may need to go into About phone first and tap Build Number 7 or 8 times for Developer menu to appear). Turn on USB debugging. Now connect a cable between your device and your PC. Fire up a command prompt on the PC (can be left open after installing ADB, as you want to be in the same folder as it) and type:
Code:
adb devices
If you get a device, and is listed as online, you are ready to enter the commands for the second part, in the order as they appear in my previous post.
If the first command does not work (as I cannot find the appropriate folder on my 10.1 distro), try:
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/mmcblk0p22 /system
Or to see if that folder exists for you first, try:
Code:
adb shell ls /dev/block/platform/msm_sdcc.1/by-name/
If you get a list of partitions, (including system) you should be good to proceed with that command. If not (by-name not found), use the above command. Hope this helps.
Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also
SOEBOMB said:
Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also
Click to expand...
Click to collapse
Okay, so that's Gingerbread, not KitKat.
I used this guide when I did mine (second pin down in the MT4GS Developer forum):
http://forum.xda-developers.com/showthread.php?t=1801106
jjbz said:
Here’s a breakdown of the process:
1. INSTALL HTC DRIVERS ON YOUR PC.
2. INSTALL ADB AND FASTBOOT ON YOUR PC.
3. REGISTER AT HTC DEV.
4. UNLOCK BOOTLOADER THROUGH HTC DEV.
5. INSTALL A CUSTOM RECOVERY.
6. ROOT YOUR DEVICE.
7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).
-PREREQUISITES-
Before getting started, please visit the MT4GS Compendium and read over Section One to learn the XDA Lingo. You really need to know this stuff if you’re going to tinker with the MT4GS.
Also, all information in the guide assumes you are using a Windows PC and a MT4GS with the STOCK ROM AND HBOOT-1.45.0013. If you are not on the Stock ROM, please use Blue6IX’s post “How-To: Restore to Stock.” Be sure to use the latest OTA (1.63.531.2). Once you're all set, let’s begin, shall we?
Disclaimer: I am not responsible for anything that happens to your phone. You assume all risks associated with modifying your phone.
-1. INSTALL HTC DRIVERS ON YOUR PC.-
Install the HTC Drivers on your PC from here.
Before connecting your phone, make sure USB Debugging is enabled (Settings>Applications>Development>USB Debugging).
Tip: to save time later, turn off your phone, hold down Power & Volume Down simultaneously until you reach the bootloader. Use the volume buttons to navigate to FASTBOOT and select it with the power button. Connect your phone via USB and the bootloader should now say FASTBOOT USB mode. Allow your PC to install the required drivers automatically. It may take a few minutes for your PC to search for and install drivers, so be patient.
-2. INSTALL ADB AND FASTBOOT ON YOUR PC.-
Installing ADB and fastboot on your PC is easy. Follow this guide and you’re good to go. To confirm that you have successfully installed ADB and fastboot, connect phone (with USB Debugging enabled) to PC via USB, open command prompt, and type “adb devices”. Your device ID number should be listed. Here are some useful commands for ADB and fastboot.
-3. REGISTER AT HTC DEV.-
Self-explanatory. Visit HTCDev.com and sign up with a valid e-mail address, as you’ll be receiving your Unlock_code.bin from HTC through this e-mail. Use an alternate browser such as IE, Google Chrome, or Mozilla Firefox if HTC Dev doesn’t play nice with your current browser of choice. Personally, I had to switch between Chrome and Firefox to get the HTC Dev website to cooperate.
-4. UNLOCK BOOTLOADER THROUGH HTC DEV.-
Make sure you’re logged in to HTC Dev and follow on-screen instructions to unlock bootloader. FYI, our device is listed as “myTouch 4G Slide (T-Mobile US)”. You can skip HTC’s instructions until step 5 since they're just telling you how to install ADB and fastboot, but you should already have ADB and fastboot installed .
After you finish unlocking the bootloader, the first line in your bootloader should read “*** UNLOCKED ***”.
-5. INSTALL A CUSTOM RECOVERY.-
Download official ClockworkMod Recovery 5.0.2.7 from the ROM Manager website or download another custom recovery from the MT4GS Development section. For instruction purposes, I will assume that you use official CWM Recovery 5.0.2.7. Save the img file to C:\.
Put your phone in bootloader FASTBOOT mode and connect to PC. Go to command prompt on PC and type “fastboot devices”. Once your device ID is listed, type “cd\” to get to “C:\” directory. Then type “fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img”.
After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping.
NOTE: Use volume buttons or trackpad to navigate through CWM Recovery 5.0.2.7. Select items by pressing the trackball. Power button may make your screen go blank and Back button returns you to the previous menu.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
-7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).-
Achieving S-OFF will make your life a lot easier if you want to flash custom ROMs, especially ICS ROMs. Follow instructions for JuopunutBear at unlimited.io and check out the JB S-OFF thread for other users’ experiences.
As I said before, if you are S-ON, flashing ICS ROMs will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
Click to expand...
Click to collapse
For step two, you can use the adb binary I mentioned earlier. Same thing, different location.
As said above, you don't need to do step 7. If you are afraid of potenitally ruining your phone with the "wire trick" I wouldn't bother with the step, just keep in mind when you do put KitKat on your phone, you will have to extract the boot.img from the package, go into the bootloaders fastboot mode and run the following command (from your PC):
Code:
fastboot flash boot boot.img
And you can apparently do this before or after (get CWM to reboot to bootloader) flashing with CWM (which you will need to upgrade to get KitKat) to avoid a bootloop. If that happens, pull the battery, reinsert, then power up into the bootloader (Pwr+Vol-Dn keys).
Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?
SOEBOMB said:
Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?
Click to expand...
Click to collapse
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Well ima gna try to root it with what u posted I feel a bit better knowing I dont have to donwgrade and all that etc. im gna follow the steps.hopefully ill be posting in a rooted device in the near future lol paperweights this rookie dnt need
Any other tips I should know?
SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.
Alandra said:
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.
Click to expand...
Click to collapse
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd
SOEBOMB said:
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd
Click to expand...
Click to collapse
Unlocking the bootloader does, yes, wipe your /data partition, but that should be all (besides /cache). If you are concerned about it wiping your MicroSD as well, can always pull the card before getting to that step.
joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
My H-BOOT is 1.45 as well (1.45.1313 since I went S-OFF) and I had no problem rooting. Probably talking about outdated information, like when everyone rooted their phone with Revolutionary. Rooting is possible, S-OFF is possible (via JuopunutBear). And the last bit about trouble flashing ROMs has to do with having to flash the boot.img file as well because you are still S-ON (please see my earlier post about that).
SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
I am also on H-Boot 1.45.0013 and have had no problems rooting and installing custom roms. I am still S-On, which has caused me no issues, but I simply have to use the method in this post to successfully flash a new rom:
http://forum.xda-developers.com/showpost.php?p=22774848&postcount=1
s off toolkit
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/show....php?t=1696373
SOEBOMB said:
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
Cannot say I have. Mind you I'm a linux user so I avoid windows programs where I can.
The second link was broken. I fixed it in the quote. In regard to version 2.0 (first link), the download links have been pulled and the thread closed. Don't bother asking anyone for it. Version 1.0 appears to be still up, although by the looks of the screenshot and changelog, you would be better off following the guide. It's not that difficult.
SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Superuser link appears dead. Here is a live one...
I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!
MTN927 said:
I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!
Click to expand...
Click to collapse
Flash twrp with fastboot and push/flash SuperSU in twrp.
--beaups
Sent from my XT1254 using Tapatalk
I'm having trouble finding some good directions on that stuff...
I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?
MTN927 said:
I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?
Click to expand...
Click to collapse
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk
beaups said:
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This is where I'm not finding any good directions for these steps, as far as how to do the command prompts.
OK finally got TWRP installed, can I flash SU from the SU app?
You flash SuperSU from within twrp.
Sent from my XT1254 using Tapatalk
MTN, I know this can be frustrating for a newbie. There are plenty of walkthroughs, and I'm sure everyone else will tell you to google, but for the sake of being concise, here's the scoop:
1. Make sure you have ADB installed.
2. Go to your ADB prompt and make sure your device is showing up (need the HTC drivers installed) by doing:
adb devices
3. Reboot into fastboot:
adb reboot bootloader
4. Flash TWRP:
fastboot flash recovery twrp####.zip
5. Once you've got TWRP installed, you reboot INTO TWRP (full recovery) and let it patch your system because if you don't it will be overwritten. As follows:
- Reboot with VolDwn held.
- From bootloader, pick "recovery".
- Wait for TWRP to come up.
6. Once TWRP is in, drop supersu package ZIP (get the latest one, careful here!) into a directory, boot into TWRP, and install it.
Boom, your device is completely rooted.
But I think that the thing that you need to understand is that "rooted" only applies to the current ROM. Rooting isn't a magic thing - it simply means that you have root privilege on the current OS. It is separate from firmware, bootloader, etc. which all also have to be flashed/loaded/updated depending on what you are doing. There probably ought to be a newbie page somewhere that explains to people what each thing is. The ROM is essentially the same as whatever version of windows/linux/etc. you have on your home computer. It has nothing to do with the hardware, the firmware, or the bootloader.
On my phone, I followed the above procedure, but then proceeded to download and install a clean ROM that was pre-rooted. Then later I put back the stock Verizon ROM and had to reapply root. I then later removed root to return the phone to verizon for service. But I didn't uninstall Root, I simply flashed on a non-rooted ROM.
Does that make sense?
Its been ages since my last Android device, it was a galaxy nexus. Anyway I recall running CM, I tried a few different roms but kept going back to CM it was moderately light but packed with tons of settings and the ability to add on what I wanted. So Iv been using the Pixel now for a few days and I am already noticing it lacks some settings I want so what roms should I give a try after rooting? Is linage really just a CM port or whats going on there? I was also looking at the Dirty Unicorn rom, hows that compare to CM?
Honestly right now the only thing Id like to do that pixel does not do is. Get a dark theme going, transparent google assistant icon, maybe even slide it over even further so its less obtrusive or just get ride of that icon all together and just slide from the left to get to the assistant/search. also get ride of the dock background, make the app drawer transparent or dark. Does anyone give an option to make the address bar in the browser work on the bottom rather than the top of the page? Android for as old of an OS as it is hasnt seemed to embrace swiping or one handed control. BB10 works great one handed but BB had to go and kill it and conform.
Thanks, Thomas
Did you but from Google or Verizon/best buy?
If you got it from Google then..
-Unlock bootloader first with fastboot
-Follow instructions from TWRP thread for TWRP installation. Basically you are using fastboot to temporarily boot into TWRP and from there you have to flash the TWRP RC 1 zip file
-I think you have to boot phone once now and then go back to twrp and flash SU 2.79 SR2 zip
Definitely read over the OPs in the TWRP and SU threads first. The only thing you have to be careful with is the SU linked in the OP is outdated. Here is the latest.
http://www.apkmirror.com/apk/chainf...elease/supersu-2-79-sr2-android-apk-download/
aholeinthewor1d said:
Did you but from Google or Verizon/best buy?
If you got it from Google then..
-Unlock bootloader first with fastboot
-Follow instructions from TWRP thread for TWRP installation. Basically you are using fastboot to temporarily boot into TWRP and from there you have to flash the TWRP RC 1 zip file
-I think you have to boot phone once now and then go back to twrp and flash SU 2.79 SR2 zip
Definitely read over the OPs in the TWRP and SU threads first. The only thing you have to be careful with is the SU linked in the OP is outdated. Here is the latest.
http://www.apkmirror.com/apk/chainf...elease/supersu-2-79-sr2-android-apk-download/
Click to expand...
Click to collapse
Sorry I was searching within the forums and got a little confused but once I did a google search I found a decent guide that cleared things up. Iam going to tackle this tomorrow So I am just trying to get all my eggs in one basket to get a running start.
Thanks for the updated SU.
I got the phone from google.
Use pure nexus ROM.
Why exactly? I've seen a review on this ROM and it just looked like stock Android.
That would get me halfway to what I want. I want a none bloated ROM with lots of setting options and maybe even some security improves if possible.
You will need to wait until more options become available. CyanogenMod, as we all know, is no more. The source can now be found under LineageOS but I don't know how soon they are going to start publishing builds and if the Pixel will be a supported device.
Pure Nexus will give you theme support to get a dark theme. TBO has a blacked out and (I think) transparent Pixel Launcher which will give you all the stuff you were wanting with the exception of the hidden assistant icon. Browser bar is another ball game though. Not sure on that one. No promises but I can take a look at the Pixel Launcher and see about removing the assistant icon.
fritzgerald said:
Pure Nexus will give you theme support to get a dark theme. TBO has a blacked out and (I think) transparent Pixel Launcher which will give you all the stuff you were wanting with the exception of the hidden assistant icon. Browser bar is another ball game though. Not sure on that one. No promises but I can take a look at the Pixel Launcher and see about removing the assistant icon.
Click to expand...
Click to collapse
Well I got the bootloader unlocked. It was hard for me as usual because I am running linux and I am not very good with linux. However once I got adb installed and fastboot installed heck one simple command unlocked the bootloader. I still need to root. There are tone of how to's on this but they are all using windows and that actually makes it harder. The one how to for linux I did find worked part of the way and then the commands no longer worked. Once I got the bootloader unlocked I tried to go back to that one.
Anyway back at it.
twilk73 said:
Well I got the bootloader unlocked. It was hard for me as usual because I am running linux and I am not very good with linux. However once I got adb installed and fastboot installed heck one simple command unlocked the bootloader. I still need to root. There are tone of how to's on this but they are all using windows and that actually makes it harder. The one how to for linux I did find worked part of the way and then the commands no longer worked. Once I got the bootloader unlocked I tried to go back to that one.
Anyway back at it.
Click to expand...
Click to collapse
So you got fastboot working.... You are all set.
Copy TWRP RC1 to your fastboot folder. Copy SU 2.79 SR2 to your phone. Fastboot BOOT twrpfilename.img Reboot into TWRP and flash SU.
TonikJDK said:
So you got fastboot working.... You are all set.
Copy TWRP RC1 to your fastboot folder. Copy SU 2.79 SR2 to your phone. Fastboot BOOT twrpfilename.img Reboot into TWRP and flash SU.
Click to expand...
Click to collapse
The bootloader says its unlocked but I never got the boot to root to work? is the "boot to root" is that actually a copy of the sailfish pixel os? I am guessing thats what that is because when I downloaded it it was specifically for the sailfish pixel.
Also which copy of twrp RC1 do I need there is one labled md5, pgp signatur and another one that just twrp. I need the .img and the zip correct?
if I type " fastboot BOOT twrp-3.0.2-0-RC1-fastboot-sailfish.img" into my terminal while in recovery I just get waiting on device message. If I type that same quote into the bootloader menu I get a help menu.
I got it. I had to type type,
cd Downloads
cd fastboot
fastboot boot twrp.img
First I renamed the img to twrp.img to make it easier and than I used the terminal to navigate to the folder it was in and then manually launched it. I imagine this is the same was what you said but I am on linux and I am not the best at linux so it was just harder for me. I should creat a how to I mean heck this was all easy in hind sight but dang it took me hours for something that only needed minutes.
So technically if I want to install a custom rom ill just have to install it onto the phone and boot into recovery and install it? I no longer have to tether the phone and use the terminal, I only have to tether to phone to transfer files?
Sorry for all the questions, thanks for all the help though. I think I got it all done now I just have to wait for a custom rom I like.
For some reason I cant find the super user zip file to flash it. I boot into twrp and go to flash and it must be invisible because the file is just not their for me to click? Is it not compatible with twrp or is there another method for installing su? I seen that you can install super user SU using the boot to root is that the only way?
Ok so I found a super user zip file and just installed it using twrp apparently twrp couldnt see the apk? Well it seemed to have work but i didnt find super user on my phone so i went to the play store to download it and it says i do not have root access and that confuses me.
The phone says the bootloader is unlocked and i have twrp recover installed plus i installed the twrp img file which i was assuming was a rooted version of the pixel os. The next step was to add Super SU but i havnt been able to do that successfully yet. So why do I not have root and what do I need to do yet?
The only thing I did not do was install root to boot, i was going threw so many different methods to unlock the bootloader and install twrp and root and I am assuming that is just a different pixel img so I skipped over that to the twrp.img. Is this what I am missing do I need to go back and flash boot to root?
All problems have been solved at this time so far. I had to delete fstab.sailfish file and then install the supersu.zip.
Thanks all and thanks deez-troy. I am sure ill have more issues down the line lol.