Related
To make things easier here is a link to BRD's update to 3.1 I suggest you check it out for an easy upgrade to 3.1.
http://forum.xda-developers.com/showthread.php?t=1074609
If you are already on 3.1 just flash the stock HRI66 system image and Tiamats boot image to get sd card support back from there you should be able to run BRDs update from the SD card in clockwork
I did this using CWR on a rooted Xoom
1. Copy the update to your sdcard and name it update.zip
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
4. Then back to fastboot and flash the root31.img to your boot partion (link below)
5. Then reboot your xoom and push su using koush's original root instructions and you are rooted running 3.1
6. You can then use rom manager to reflash CWR.
Link to post with root31.img
http://forum.xda-developers.com/showthread.php?t=1073298
Other files easily found on xda
Just have to wait for an updated kernel to has sdcard support back.
All credit goes to the people that did the actual work I'm just listing instructions. And of course you assume all risk in flashing and modding your device.
Sent from my Xoom using my Xoom
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
dch921 said:
6. You can then use rom manager to reflash CWR.
Click to expand...
Click to collapse
Just use fastboot. That's what it's there for.
JFMFT said:
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Haven't tried it but worse case scenario just reflash root31.img
Sent from my Xoom using my Xoom
Nice! It worked perfectly!
I tried flashing Tiamat 1.4.1, wouldn't recommend it, you'll have to go right back to stock.
I am doing this right now on my XOOM. I will update this post when I am done.
Thank you for the instructions
EDIT: works perfectly!!
Got confused at first and followed the whole guide to originally root...but then realized that you do not flash rootboot.img.
Only do the following code:
1. adb remount
2. adb push su /system/bin
3. adb shell
4. ln –s /system/bin/su /system/xbin/su
5. chmod 4755 /system/bin/su
6. exit
7. adb push Superuser.apk /system/app
Click to expand...
Click to collapse
props worked great
Cansay that this worked great. I love the update and I love keeping my root. The device is running smoothly with the stock 3.1. Good post indeed.
Sent from my Xoom using Tapatalk
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
Click to expand...
Click to collapse
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
This instruction is very unclear...
Blades said:
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
Click to expand...
Click to collapse
Of course not. You can have a ramdisk with ro.secure 0 and the stock kernel, or you can use any kernel you like that will run.
(IMO, it's better to root with as small a change as needed, and if you want to use a different kernel, you can do so if you want separate to the decision of wanting root)
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
Again, just use fastboot (because it's unlocked), then reboot into recovery. Does that not work?
ljwnow said:
This instruction is very unclear...
Click to expand...
Click to collapse
No its pretty simple you must not know what your doing
sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
after you flashing boot.img and HRI66 system.img, type this in cmd, fastboot reboot
xoom will reboot to normal mode, then wait untill it completly settle to home screen, it will take sometime (it seems like bootloop but it does not, HC doing re-dalvik cache, so it takes time)..after it boot to normal mode type this in cmd, adb reboot recovery
you will reboot to cwm recovery (i'm guessing you have flash cmw before on 3.0.1) then follow the OP steps..
i'm on 3.1 now.. with no data loose and rooted ;-)
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
wsuo2006 said:
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
Click to expand...
Click to collapse
No sdcard support until we get a new kernel
Sent from my Xoom using my Xoom
I was wondering if anyone could package the stock 3.0.1 kernel and system.img into an update.zip so this can all be done using rom manager? Thinking about it most likely not cause moto has been pulling system dump images
Sent from my Xoom using XDA Premium App
dch921, would it be possible for you to please add the relevant links to your OP instead of saying to search XDA for them? If you do this, I will gladly sticky this guide.
Thanks!
This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
1. If I root my HTC One M8 with the stock rom, will I still get updates, or will I have to flash a rom everytime there is an update from HTC?
2. How can I manage folders and write to my microSD card once I root?
3. Once I root and unlock my bootloader do I have to flash a rom or will the stock one be automatically flashed? I want to remain stock just like the phone came out of the box, and get all my updates from HTC automatically. I just want to have the H/K audio enhancements and I want to be able to move things to my SD card. Thats the only reason I want to root. Any help in doing this is greatly appreciated. In fact, if someone helps me out greatly with a step-by-step by rooting,keeping stock,getting H/K, being able to write to sd, I will pay them $5 via Paypal if thats allowed here....
Oh, and I have the Unlocked version.
bhags8 said:
1. If I root my HTC One M8 with the stock rom, will I still get updates, or will I have to flash a rom everytime there is an update from HTC?
Click to expand...
Click to collapse
You will get updates.
bhags8 said:
2. How can I manage folders and write to my microSD card once I root?
Click to expand...
Click to collapse
Any root file explorer app should be fine. I use Es file explorer.
bhags8 said:
3. Once I root and unlock my bootloader do I have to flash a rom or will the stock one be automatically flashed? I want to remain stock just like the phone came out of the box, and get all my updates from HTC automatically. I just want to have the H/K audio enhancements and I want to be able to move things to my SD card. Thats the only reason I want to root. Any help in doing this is greatly appreciated. In fact, if someone helps me out greatly with a step-by-step by rooting,keeping stock,getting H/K, being able to write to sd, I will pay them $5 via Paypal if thats allowed here....
Click to expand...
Click to collapse
This question makes me believe you don't have much understanding of what rooting is and that means if something goes wrong, you will not be able to fix it. This is a dangerous. I strongly suggest doing some reading and trying to understand before you mess around (no I don't care to know how many devices you've rooted in the past). This is the only warning I will give you.
Unlock bootloader at HTCdev.com
boot to TWRP or Philz Touch (fastboot boot customrecoveryfilename.img)
Make a nandroid backup and save for just in case.
Install supersu or superuser (custom recovery should offer to install root for you, I know TWRP does, not sure about Philz Touch)
Firewater S-OFF (optional, extra dangerous, HK may not work without it.)
Install HK
Install a file explorer app capable of requesting root.
Good luck. I suggest reading the guide in my signature.
So if I flash twrp or the other one I won't flash a rom after that to keep stock right? Then if HTC pushes an ota update I would still receive it?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
bhags8 said:
So if I flash twrp or the other one I won't flash a rom after that to keep stock right? Then if HTC pushes an ota update I would still receive it?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct. However, after you have everything like you want it, you will need to flash the original recovery back to your device. From what I understand, the OTA updates don't work with a custom recovery.
However, you should also consider that nearly every ROM in this forum will be updated within a few days anytime a new release is pushed. I can speak from personal experience that ARHD 5.5 is nearly identical to stock. It would only then require a weekly visit to his thread to see if a new release is out. Every other Sense based ROM here would be the same. Just mentioning that you do have alternatives.
Don't flash twrp. Just boot to it. Since you're not flashing roms, no point in flashing a custom recovery.
Sent from my HTC One_M8 using XDA Free mobile app
If I never flash a custom recovery do I still have to flash the original recovery?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Oh and do I have to get S-OFF for H/K and write to SD access??
Sent from my HTC One_M8 using XDA Premium 4 mobile app
bhags8 said:
Oh and do I have to get S-OFF for H/K and write to SD access??
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You don't need it for Sd card access
You might need it for HK as I stated earlier. If you don't understand why you might need it. read the thread I linked.
exad said:
Since you're not flashing roms, no point in flashing a custom recovery.
Click to expand...
Click to collapse
Intend to root my M8 but keep it in stock for the time being. So just rooting and booting into recovery to take backup.
I am a newbie so trying out the advantages of rooting and taking it one step at a time. As such Custom Roms are not my priority right now. Flexibility to OTA update is a priority, for which i have learnt that other than installing some basic root apps like titanium, if i decide to flash custom roms/recovery, overclock/undervolting, then i loose that flexibility.
1. Is my understanding correct?
2. I wanted to play around with xposed framework. Will installing xposed framework work against easy OTA updates?
3. Anything else i shouldn't be doing if i want easy OTA? I say easy because i do know that OTA can be achieved in a round about way even after flashing roms and all other customizations.
anjaan said:
Intend to root my M8 but keep it in stock for the time being. So just rooting and booting into recovery to take backup.
I am a newbie so trying out the advantages of rooting and taking it one step at a time. As such Custom Roms are not my priority right now. Flexibility to OTA update is a priority, for which i have learnt that other than installing some basic root apps like titanium, if i decide to flash custom roms/recovery, overclock/undervolting, then i loose that flexibility.
1. Is my understanding correct?
2. I wanted to play around with xposed framework. Will installing xposed framework work against easy OTA updates?
3. Anything else i shouldn't be doing if i want easy OTA? I say easy because i do know that OTA can be achieved in a round about way even after flashing roms and all other customizations.
Click to expand...
Click to collapse
1. yes
2. should still be able to receive OTA
3. Don't remove system apps. Use titanium backup to freeze if you don't want them running so you can unfreeze if needbe.
Tip 1
Make nandroids when you make changes so you can revert back, you can always boot into custom recovery to make and/or restore nandroids.
Tip 2
Always know how to undo what you're doing. If you don't have an undo plan, don't do it.
Hello Exad,
I am new to HTC and want to do all the necessary research before I root my phone. I have read your everything explained guide which was very helpful. As with the other users on this thread I want to gain root access but I do not want to run custom ROMs and I still want to receive OTA updates to my phone. It looks like simply booting into a custom recovery such TWRP and flashing supersu will enable root access without changing the stock recovery.
Can you explain how I boot into TWRP recovery without actually flashing it? It seems like every thread or guide I find online instructs me to flash a custom recovery. Where do I place the TWRP recovery file on my computer in order to boot into recovery?
Thank you for helping out a newbie
SouthBayBruin said:
Can you explain how I boot into TWRP recovery without actually flashing it? It seems like every thread or guide I find online instructs me to flash a custom recovery. Where do I place the TWRP recovery file on my computer in order to boot into recovery?
Click to expand...
Click to collapse
so long as you have fastboot available on your pc, , connect the phone in fastboot mode, then on the pc open a command prompt in teh folder where the recovery is(**), and issue teh command
Fastboot boot custom-recovery-name.img
that should boot you without flashing it.
** browse to the folder where it is in regular explorer, then hold shift and right click, there will be an 'open command prompt here' option in teh menu.
samsamuel said:
so long as you have fastboot available on your pc, , connect the phone in fastboot mode, then on the pc open a command prompt in teh folder where the recovery is(**), and issue teh command
Fastboot boot custom-recovery-name.img
that should boot you without flashing it.
** browse to the folder where it is in regular explorer, then hold shift and right click, there will be an 'open command prompt here' option in teh menu.
Click to expand...
Click to collapse
Thank you for the help.
If I am following correctly here are some basic steps I should follow. In order to get fastboot on my computer should I download the entire Google SDK from the google developer website. This file will then include everything I need on my computer in terms of fastboot. I should also ensure that I have all of the latest HTC one (m8) drivers installed on my computer.
Then I should download the latest version of TWRP and ensure that the file name is matches custom-recovery-name.img
I should enter fastboot mode on my phone and connect it to my computer. Following the command prompt, I will boot into TWRP recovery. Once in TWRP recovery can I disconnect my phone from the computer? I should first create a nandroid backup (as a precaution) then I should install supersu. Once I install supersu I should have root accress.
I just need to reboot my phone and it should still have the stock recovery but now with root access.
Thank you for the help
sorry, can't answer the SDK stuff, I didn't have to install any SDK, BUT it may have still been installed from when I used to flash my HD2 a few yrs ago, , or perhaps the drivers are installed when you first connect the phone in fastboot mode to teh PC?
Whichever, I certainly don't currently have the SDK installed, so it's either leftovers, or it comes with the drivers. (EDIT - i also have myphoneexplorer installed, which installs certain drivers and stuff too,,,)
try it, put the phone in fastboot, , connect it to usb, let windows install whatever drivers it feels, then open a command prompt on teh PC and type
fastboot
if it says unknown command, then its not there, if it gives you lots of lines of help info, then fastboot is installed.
Assuming it works (or once you get it working) change custom-recovery-name to say whatever your recovery is called, and it will boot the phone allowing you to perform all the normal actions. Whether or not it will allow SU to install, I don't know, i've only had the phone 2 days, and all i did was HTC bootloader unlock, flash twrp, install su, flash viperrom and done.
samsamuel said:
sorry, can't answer the SDK stuff, I didn't have to install any SDK, BUT it may have still been installed from when I used to flash my HD2 a few yrs ago, , or perhaps the drivers are installed when you first connect the phone in fastboot mode to teh PC?
Whichever, I certainly don't currently have the SDK installed, so it's either leftovers, or it comes with the drivers. (EDIT - i also have myphoneexplorer installed, which installs certain drivers and stuff too,,,)
try it, put the phone in fastboot, , connect it to usb, let windows install whatever drivers it feels, then open a command prompt on teh PC and type
fastboot
if it says unknown command, then its not there, if it gives you lots of lines of help info, then fastboot is installed.
Assuming it works (or once you get it working) change custom-recovery-name to say whatever your recovery is called, and it will boot the phone allowing you to perform all the normal actions. Whether or not it will allow SU to install, I don't know, i've only had the phone 2 days, and all i did was HTC bootloader unlock, flash twrp, install su, flash viperrom and done.
Click to expand...
Click to collapse
Thank you for the advice. I have rooted one other phone in the past and I remember using adb commands, so my computer may already have fastboot enabled.
Since I do not want to flash the custom recovery and only boot into recovery will I need to keep the phone connected to my computer while in TWRP recovery?
why would you need to unhook it? play it safe and leave it connected.
I have been using this method to boot into TWRP to re-install SuperSU after each HTC ONE M8 update. However, with the update just released (Android 4.4.3), when I issue the command it just has the phone reboot. It does not bring up TWRP. Any ideas?
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Assuming you don't have a custom recovery installed either?? What's the "difficulty with trying to hook to a PC?
No, I don't have a custom recovery installed. There are more people facing this problem: https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4. Solution is not working for me for some reason.
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
I was afraid of that. Maybe i'll go with a factory reset then. Thanks tot the help anyways.
jd1639 said:
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
So..... The bottom line is..... You still need a PC.
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
You're right. You can flash a boot image with fastboot. Is there a boot image that has magisk as party of it?
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
bluesh4rk said:
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
Click to expand...
Click to collapse
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Instead of downloading the entire ROM, you might find what you need here: https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
bluesh4rk said:
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Click to expand...
Click to collapse
Hello there ,
I have same as your issue.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
Hi I'm new to rooting. I have a ZTE n9137 tempo x looking to root .I can't get this done.no recovery no boot.img no custom recovery none what so ever .the olny I keep reading is that I have to have a PC I don't like I said I'm new to root but I'm trying anything to get this done I unlocked the oem but I don't thing that it is enabled.?.?and I don't think that the phone can do this ota so now what ?? If I'm wrong plzz tell me where at I'm wrong and how to gain root thanks for all the help
Update not got root
hi everybody i wanted to root a samsung a3 2018(idk what version it is because it is still my grandma's phone) and as i know there isn't any twrp version for that phone