I have ROM Manager on my phone but as we all know, it does not have many of the ROMS available out there including some of the newer Z roms. I have a new iMac at home and am unsure as to how to push roms to the phone, so I have been relying on qr codes or what is available on rom manager. Is there a way to download a rom, theme or mod file and then somehow create a qr code so that rom manager can upload?
Download them from the phones browser, then in ROM Manager hit Install ROM from SD Card and go to Downloads. Wipe Cache and Data and back up current ROM. DONE! Also there are apps on the Market that make QR Codes.
will try this out...been using SR3.5 and for some reason in rom manager when I select a rom I have to manually reboot the phone into recovery, unlike in other roms the application automatically throws the phone into recovery...seems strange that this happens. I guess as long as I have everything backed up I should be good to go...thanks!
jdaniels31 said:
will try this out...been using SR3.5 and for some reason in rom manager when I select a rom I have to manually reboot the phone into recovery, unlike in other roms the application automatically throws the phone into recovery...seems strange that this happens. I guess as long as I have everything backed up I should be good to go...thanks!
Click to expand...
Click to collapse
What version of ClockWorkMod Recovery are you running. The newer one is giving people problems with Rom Manager.
2.5.1.2 Also, when I try and flash an older or even a newer version an error message is coming up that says "an error occurred while flashing your recovery". Not too big of a deal though...just one extra step
Just stay on the newest one and manually apply the ROM's until they fix it.
Maybe I do this the long way or something, but I was just mounting the SD card to my laptop then opening the file under My Computer and drag & drop the zip file onto the sd card. Then sometimes when I'm at work and I get the itch, I'll just go to this site on the phone browser and download the link. Another handy way is using Chrome to Phone. Just shoot the download link right over to the phone wirelessly.
^^^^^^
This is what I do as well. Chrome to phone is nice though. To eliminate as many variables as possible I often manually go into Recovery and do it.
Does anyone know if ROM manager wipes the Dalvik cache when clearing cache is selected?
Hey, I have searched the internet for many days, and have yet to find a Rom made for the metro pcs wildfire s. Does anyone know if there are any? mostly directing towards a cyanogenmod7 ported onto this phone.
id05dav said:
Hey, I have searched the internet for many days, and have yet to find a Rom made for the metro pcs wildfire s. Does anyone know if there are any? mostly directing towards a cyanogenmod7 ported onto this phone.
Click to expand...
Click to collapse
Look in the Wildfire S Android Development Sub Forum, you will find ROMs such as cyanogenmod 7.2 there.
Don't flash anything on that phone the only thing that works right now is insinks stock ROM flashing anything else will make you lose data
Sent from my HTC_A510c using Tapatalk
Shoulda read this before flashing. i made a nandroid backup and it didn't even work.
kagevazquez said:
Don't flash anything on that phone the only thing that works right now is insinks stock ROM flashing anything else will make you lose data
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
This is basically true, unless you have advanced Android modification knowldege. I can get a few Virgin Mobile ROMS working, as well as just about any MarvelC stock ROM.
Before you go custom ROM, I would recommend (if you haven't) unlocking your bootloader through HTCDev.com. (You kind of have to do this, unless you opt to unlock a different way.) Download HTCSync and install it, then download the RUU through the "unlock bootloader" option. (You'll have to create an account.) The RUU option has to be performed in Windows.
Once you unlock your bootloader, go here:
http://forum.xda-developers.com/showthread.php?t=1074445
and download the new MetroPCS RUU to update your bootloader to 1.10.0000. This will ensure that the MetroPCS ROM you are running is built from the Marvelc hboot instead of the Marvelct hboot that originally came with your phone. This is an excellent update, and should be performed by all MetroPCS users. It really does help out a LOT of anomolies on our phones
After that, go here:
http://forum.xda-developers.com/showthread.php?t=1213229
And follow the instructions to install ClockWork Mod recovery. You'll need it for installing custom ROM's, as well as setup custom partitions on your SD card. You MUST remove this file from your SD card after it has been installed. Otherwise you will always attempt to install CWM recovery. Once you get this installed, reboot to the RUU by rebooting the phone. Shut down normally, then pull the battery and replace it. Hold Volume Down+Power until you boot into hboot. After it does the update checks, select "recovery" and boot to CWM. Go through the menu and find "Wipe user data/factory reset" and use that. Then go to "Advanced" and format "Dalvik-cache". Then, in the "Advanced" menu, select "Partition SD Card" and use this as the following values:
EXT Partition: 1024MB/1Gb
SWAP: 256 (This is not necessary, but CWM insists you use it...)
Let it do its thing. Once its done, back out until you get to the main menu in CWM. Go to "Mounts and Storage" and connect your phone to your computer with HTCSync installed. On the phone, select "Mount USB Storage" so that the phone picks up as external storage.
insink71 came up with a stock MetroPCS ROM that works pretty good. Its stock with root and a2sd capabilities. This ROM is here:
http://www.mediafire.com/download.php?832o9otiu6713m8
Download this to your SD card on your phone. After you get this downloaded, unmount the phone from the computer through CWM. Back in the main menu of CWM, find "Install zip from SD card" and select that. Find "Choose zip from SD card" after this, and then find the MPCS ROM and flash this.
After you get this up and booted once, log into Google and access the Market to download "Terminal Emulator". Fire this up and accept Superuser rights. Once Terminal Emulator starts, type the following (Without quotes!!):
"su"
"a2sd zipalign"
"a2sd cachepartreset"
"su" grants Terminal Emulator Android super user permissions. "a2sd zipalign" will zipalign your apps to the EXT partition, and take MUCH longer to boot the next time you reboot. "a2sd cachepartreset" will flush Dalvik-Cache and move it to the SD-EXT partition, removing a bunch of extra space that could be on the SD card.
This basically allows you to install a LOT of apps without having to worry about running out of app space.
There are overclock kernels, but I don't recommend any currently. I can get one to work for me, but others dont. Currently, I don't overclock my phone.
bobdamnit said:
This is basically true, unless you have advanced Android modification knowldege. I can get a few Virgin Mobile ROMS working, as well as just about any MarvelC stock ROM.
Before you go custom ROM, I would recommend (if you haven't) unlocking your bootloader through HTCDev.com. (You kind of have to do this, unless you opt to unlock a different way.) Download HTCSync and install it, then download the RUU through the "unlock bootloader" option. (You'll have to create an account.) The RUU option has to be performed in Windows.
Once you unlock your bootloader, go here:
http://forum.xda-developers.com/showthread.php?t=1074445
and download the new MetroPCS RUU to update your bootloader to 1.10.0000. This will ensure that the MetroPCS ROM you are running is built from the Marvelc hboot instead of the Marvelct hboot that originally came with your phone. This is an excellent update, and should be performed by all MetroPCS users. It really does help out a LOT of anomolies on our phones
After that, go here:
http://forum.xda-developers.com/showthread.php?t=1213229
And follow the instructions to install ClockWork Mod recovery. You'll need it for installing custom ROM's, as well as setup custom partitions on your SD card. You MUST remove this file from your SD card after it has been installed. Otherwise you will always attempt to install CWM recovery. Once you get this installed, reboot to the RUU by rebooting the phone. Shut down normally, then pull the battery and replace it. Hold Volume Down+Power until you boot into hboot. After it does the update checks, select "recovery" and boot to CWM. Go through the menu and find "Wipe user data/factory reset" and use that. Then go to "Advanced" and format "Dalvik-cache". Then, in the "Advanced" menu, select "Partition SD Card" and use this as the following values:
EXT Partition: 1024MB/1Gb
SWAP: 256 (This is not necessary, but CWM insists you use it...)
Let it do its thing. Once its done, back out until you get to the main menu in CWM. Go to "Mounts and Storage" and connect your phone to your computer with HTCSync installed. On the phone, select "Mount USB Storage" so that the phone picks up as external storage.
insink71 came up with a stock MetroPCS ROM that works pretty good. Its stock with root and a2sd capabilities. This ROM is here:
http://www.mediafire.com/download.php?832o9otiu6713m8
Download this to your SD card on your phone. After you get this downloaded, unmount the phone from the computer through CWM. Back in the main menu of CWM, find "Install zip from SD card" and select that. Find "Choose zip from SD card" after this, and then find the MPCS ROM and flash this.
After you get this up and booted once, log into Google and access the Market to download "Terminal Emulator". Fire this up and accept Superuser rights. Once Terminal Emulator starts, type the following (Without quotes!!):
"su"
"a2sd zipalign"
"a2sd cachepartreset"
"su" grants Terminal Emulator Android super user permissions. "a2sd zipalign" will zipalign your apps to the EXT partition, and take MUCH longer to boot the next time you reboot. "a2sd cachepartreset" will flush Dalvik-Cache and move it to the SD-EXT partition, removing a bunch of extra space that could be on the SD card.
This basically allows you to install a LOT of apps without having to worry about running out of app space.
There are overclock kernels, but I don't recommend any currently. I can get one to work for me, but others dont. Currently, I don't overclock my phone.
Click to expand...
Click to collapse
Excellent post! Should be required reading for all metropcs users.
insink71's Rom is the only one I can get to work. Even though some will boot, all, including kernels, come up with non-working touch-screen. Inksink's Rom is pretty much stock. It works great on my phone. If you want to get rid of some of the bloatware, use titanium backup to delete. Make sure you make a nandroid, just in case.
What should i do if the ROM keeps boot-looping?
Seems to work great on my WFS form metro, Have wifi hotspot now..but cant configure! Settings force closes every time i try and set it up. Any solutions?
Bradlee69 said:
Seems to work great on my WFS form metro, Have wifi hotspot now..but cant configure! Settings force closes every time i try and set it up. Any solutions?
Click to expand...
Click to collapse
If you haven't done so already, try rebooting.
Hopefully you have a good backup.....
If the rebooting didn't work, do a wipe /delete factory reset, wipe dalvik cache and install the rom again. I'm assuming that you're flashing insink71's metro rom. As far as I know, it's the only one working on MetroPCS phones. Make sure you follow the directions, it's working great for me.
Agree with above
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well wiped all data and followed all directions...still cant setup the wifi hotspot. Ok well i figured out the default password for the hotspot...but im still restricted somehow. This is what i get- Per the Terms and Conditions of Service, Tethering / Mobile Hotspot is not currently supported.
Please visit www .metropcs. com/ terms for terms and conditions of service. Is there anyway to remove this restriction from the phone?
The only rom that worked without problems for my MetroPCS Version of WFS is the HenseMod7 at the moment. Works awesome with minor problems like the Proximity sensor not working and some reason MMS isn't either. I'm still trying to figure out why the MMS won't work. Will look into that if I find a fix for it I will let you guys know.
-Edit I figured out why the Home buttons don't light up. When you set the Auto-Brightness checkmark, and go into a dark room (i.e. if it's night time) it turns on the home button LED's . Awesomeness!!! I'm so happy that it works now, cause it was crappy looking at it at night lol.
-Update , Fixed Proximity Sensor with an app Called Proximity Screen Off, you can find it in Google Play Market by typing Proximity Sensor and get the screen off version. Just need to set up the Settings correctly for it to only work on calls, because it has a settings to be able to turn off the screen by tapping the sensor a couple times. Also the MMS problem is now fixed too with GoSMS from Market. Awesome ROM now that works perfectly all around for the WFS from MetroPCS.
bobdamnit said:
This is basically true, unless you have advanced Android modification knowldege. I can get a few Virgin Mobile ROMS working, as well as just about any MarvelC stock ROM.
Before you go custom ROM, I would recommend (if you haven't) unlocking your bootloader through HTCDev.com. (You kind of have to do this, unless you opt to unlock a different way.) Download HTCSync and install it, then download the RUU through the "unlock bootloader" option. (You'll have to create an account.) The RUU option has to be performed in Windows.
Once you unlock your bootloader, go here:
http://forum.xda-developers.com/showthread.php?t=1074445
and download the new MetroPCS RUU to update your bootloader to 1.10.0000. This will ensure that the MetroPCS ROM you are running is built from the Marvelc hboot instead of the Marvelct hboot that originally came with your phone. This is an excellent update, and should be performed by all MetroPCS users. It really does help out a LOT of anomolies on our phones
After that, go here:
http://forum.xda-developers.com/showthread.php?t=1213229
And follow the instructions to install ClockWork Mod recovery. You'll need it for installing custom ROM's, as well as setup custom partitions on your SD card. You MUST remove this file from your SD card after it has been installed. Otherwise you will always attempt to install CWM recovery. Once you get this installed, reboot to the RUU by rebooting the phone. Shut down normally, then pull the battery and replace it. Hold Volume Down+Power until you boot into hboot. After it does the update checks, select "recovery" and boot to CWM. Go through the menu and find "Wipe user data/factory reset" and use that. Then go to "Advanced" and format "Dalvik-cache". Then, in the "Advanced" menu, select "Partition SD Card" and use this as the following values:
EXT Partition: 1024MB/1Gb
SWAP: 256 (This is not necessary, but CWM insists you use it...)
Let it do its thing. Once its done, back out until you get to the main menu in CWM. Go to "Mounts and Storage" and connect your phone to your computer with HTCSync installed. On the phone, select "Mount USB Storage" so that the phone picks up as external storage.
insink71 came up with a stock MetroPCS ROM that works pretty good. Its stock with root and a2sd capabilities. This ROM is here:
http://www.mediafire.com/download.php?832o9otiu6713m8
Download this to your SD card on your phone. After you get this downloaded, unmount the phone from the computer through CWM. Back in the main menu of CWM, find "Install zip from SD card" and select that. Find "Choose zip from SD card" after this, and then find the MPCS ROM and flash this.
After you get this up and booted once, log into Google and access the Market to download "Terminal Emulator". Fire this up and accept Superuser rights. Once Terminal Emulator starts, type the following (Without quotes!!):
"su"
"a2sd zipalign"
"a2sd cachepartreset"
"su" grants Terminal Emulator Android super user permissions. "a2sd zipalign" will zipalign your apps to the EXT partition, and take MUCH longer to boot the next time you reboot. "a2sd cachepartreset" will flush Dalvik-Cache and move it to the SD-EXT partition, removing a bunch of extra space that could be on the SD card.
This basically allows you to install a LOT of apps without having to worry about running out of app space.
There are overclock kernels, but I don't recommend any currently. I can get one to work for me, but others dont. Currently, I don't overclock my phone.
Click to expand...
Click to collapse
How can I run the RUU?? Is there any tutorial? I am totally lost
---------- Post added 12th May 2012 at 12:27 AM ---------- Previous post was 11th May 2012 at 11:40 PM ----------
KyCut1 said:
What should i do if the ROM keeps boot-looping?
Click to expand...
Click to collapse
I am having the same scenario. Any exit?
Is there any way to turn 3g on? It shows that i have 3g in my area but i stuck with 1xrtt Is there a prl hack ? I have tried to use the qpst services...but wont find my phone. It would be wonderful if i could get 3g to work!
The RUU is an .exe file... You just hook your phone up to computer via usb cable, download and double click [considering your cpu is running some version of windows]... No real tutorial needed for that.
Rob
The rom bootlooping is due to kernel challenges with some metro users [its odd; some experience it; some don't] You will be constrained to the stock kernel until someone figures that mystery out; The oc kernel is causing the bootloop on your device. You are more than welcome to try my rom on AndroidForums and speak with a user named Chicle. He has had/is having same challenges. I've been trying to assist but I have VM phone; so, its touch and go.
Regards,
Rob
Sent from my HTC_A510c using Tapatalk 2
I have rooted and modded a few devices.. but all of them where GSM phones... I dont understand why flashing a different rom messes anything up.. Care to explain?
I ask because my cousin just got this phone and asked me to look into it for him.
boot loop
Hey, I'm having the same bootlooping problem, it loaded fine but then when I ran the commands in the terminal emulator it wont reboot. I'm not sure what to do now, should I just try and load my old stock rom or can I do something else? and if the backup I made doesn't work what shoudl i do? I don't really know but i'm guessing this is because of the zipalign...
Actually when I did it all with a2sd gui it seems to work fine, but another question is how big does my ext3 partition have to be because my sd card is only 2GB and I'd like more space to play with. I guess I have a Fat32 partition and Ext3 partition and a Swap Partition.do I need all those?
I have followed all instructions on your post, am htcdev bootloader unlocked, rooted and got the rom from insink71 image in, but once I run the commands below and reboot - it sets off an endless reboot loop
Are the below a2sd commands required?
I'm attempting to make my wife's phone usable (the memory issues were driving her up the wall). She just wants to be able to download a few apps and see the pictures she took.
bobdamnit said:
...
After you get this up and booted once, log into Google and access the Market to download "Terminal Emulator". Fire this up and accept Superuser rights. Once Terminal Emulator starts, type the following (Without quotes!!):
"su"
"a2sd zipalign"
"a2sd cachepartreset"
"su" grants Terminal Emulator Android super user permissions. "a2sd zipalign" will zipalign your apps to the EXT partition, and take MUCH longer to boot the next time you reboot. "a2sd cachepartreset" will flush Dalvik-Cache and move it to the SD-EXT partition, removing a bunch of extra space that could be on the SD card.
This basically allows you to install a LOT of apps without having to worry about running out of app space.
There are overclock kernels, but I don't recommend any currently. I can get one to work for me, but others dont. Currently, I don't overclock my phone.
Click to expand...
Click to collapse
I tried installing insink71s rom for metro but never boots. Only thing ever worked was HenseMOD7 and now after using cm9 I dunno if I want to go back. Just sucks it says data roaming instead of MetroPCS carrier .
Sent from my Wildfire S MetroPCS running CM9(Alpha7)
KyCut1 said:
What should i do if the ROM keeps boot-looping?
Click to expand...
Click to collapse
Having the same issue unless what was meant by taking "MUCH" longer is this continual loop at metropcs screen.
A lot of people have helped me during my time on the forum, so I felt obligated to do something to help someone else.... (and yes I know this is really easy to most of you, but I was lost and figured this could help other android noobs)
Note:I have an AT&T LG Nitro (P930) this is what I did, if you screw up your phone doing this I am not liable. If you have any corrections feel free to let me know
1. Root P930 and enable USB debugging
Thread:
http://forum.xda-developers.com/showthread.php?t=1376857
2. Install ROM manager (available in Play store)
3. Install Clockwork Mod (option in ROM manager) and backup current rom
4. Download CM9 nightly from here (on computer)
http://get.cm/?device=p930
5. Download latest g-apps from here (on computer)
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
6. Cut/Paste CM9 and gapps into root of micro sd card (not in any folders, just the first screen that comes up when you go to the card)
7. Go back to ROM manager and go to install rom from sd card and select CM9 (it should give you the option to backup and clear, I checked all three boxes)
8. It should boot into CM9, but you will not see basic apps, so go back to ROM manager and click "boot into recovery mode"
9. Select install zip from sd card and click g-apps
10. Click reboot
11. Success!
Article I followed:
http://androidbeast.com/1399/lg-optimus-lte-p930-cyanogenmod-9-ics-rom/
mgoblueno1 said:
A lot of people have helped me during my time on the forum, so I felt obligated to do something to help someone else.... (and yes I know this is really easy to most of you, but I was lost and figured this could help other android noobs)
Note:I have an AT&T LG Nitro (P930) this is what I did, if you screw up your phone doing this I am not liable. If you have any corrections feel free to let me know
1. Root P930 and enable USB debugging
Thread:
http://forum.xda-developers.com/showthread.php?t=1376857
2. Install ROM manager (available in Play store)
3. Install Clockwork Mod (option in ROM manager) and backup current rom
4. Download CM9 nightly from here (on computer)
http://get.cm/?device=p930
5. Download latest g-apps from here (on computer)
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
6. Cut/Paste CM9 and gapps into root of micro sd card (not in any folders, just the first screen that comes up when you go to the card)
7. Go back to ROM manager and go to install rom from sd card and select CM9 (it should give you the option to backup and clear, I checked all three boxes)
8. It should boot into CM9, but you will not see basic apps, so go back to ROM manager and click "boot into recovery mode"
9. Select install zip from sd card and click g-apps
10. Click reboot
11. Success!
Article I followed:
http://androidbeast.com/1399/lg-optimus-lte-p930-cyanogenmod-9-ics-rom/
Click to expand...
Click to collapse
i think everyone with a nitro knows how to do this !
and there are couple of more threads stating this ! so i think the purpose of this thread is unnecessary !
-peace !
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?
xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!
dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!
dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.