boost moto e4 plus (sku xt1776)
I am new to rooting and roms and whatnot, someone help me? i cant for life of me figure out how to flash a custom rom for this phone. Ive rooted it, but what i really need is a step by step guide on how to flash the correct rom. ive found the lineage ones but i dont know which one to flash.
i used twrp, phh superuser to root. now i want to put a custom rom on here so i can use substratum..
ive been at this for about 4 hours now and im frustrated and i figured instead of trying to figure it out i would just ask an expert who knows more about this stuff than me. I recently got into theming and love it. Im trying to learn as much about it as possible. I used to use tlauncher but once i read about substratum i was hooked in. thanks to whoever decides to help me lol. I appreciate it. There's probably a thread answering this already but i cant find it so sorry to the moderators in advance.
[edit]
I also now have N/A coming up when i boot. Idk if i did something wrong when i rooted?
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
stonefabtim said:
boost moto e4 plus (sku xt1776)
I am new to rooting and roms and whatnot, someone help me? i cant for life of me figure out how to flash a custom rom for this phone. Ive rooted it, but what i really need is a step by step guide on how to flash the correct rom. ive found the lineage ones but i dont know which one to flash.
i used twrp, phh superuser to root. now i want to put a custom rom on here so i can use substratum..
ive been at this for about 4 hours now and im frustrated and i figured instead of trying to figure it out i would just ask an expert who knows more about this stuff than me. I recently got into theming and love it. Im trying to learn as much about it as possible. I used to use tlauncher but once i read about substratum i was hooked in. thanks to whoever decides to help me lol. I appreciate it. There's probably a thread answering this already but i cant find it so sorry to the moderators in advance.
[edit]
I also now have N/A coming up when i boot. Idk if i did something wrong when i rooted?
Click to expand...
Click to collapse
The N/A is a good sign, as I means your twrp has been successfully installed. Install all ROMs the same way.
- Boot into recovery
- Format Data ( type yes) the do normal factory reset wipe. Twice. You'll get some red lines and errors, ignore them and keep going.
- Reboot directly into recovery.
- Format data & then do factory reset again.
- Flash ROM
- Flash no-verity_opt-encrypt.zip
- Flash Magisk (or SuperSU.zip)
- Flash Gapps
- Wipe Cache/Dalvik
- reboot
ALWAYS let the device sit for about 10mins after booting to allow the software to finish expanding before ya start messing with it. I'll add this to my Root Guide in Android forums later.
Hope that helps.
---------- Post added at 09:16 AM ---------- Previous post was at 09:11 AM ----------
koop1955 said:
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
Click to expand...
Click to collapse
Well done
koop1955 said:
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
Click to expand...
Click to collapse
Thanks bro. Much appreciated. My next question would be, in your opinion, what would be the best rom to get for my specific device?
stonefabtim said:
Thanks bro. Much appreciated. My next question would be, in your opinion, what would be the best rom to get for my specific device?
Click to expand...
Click to collapse
That depends on whatcha like and how you use it.. There's a few here in XDA and many more here: https://androidforums.com/threads/moto-e-4-plus-owens-all-things-root-guide.1259898/
Aaand another issue...
bcrichster said:
That depends on whatcha like and how you use it.. There's a few here in XDA and many more here: https://androidforums.com/threads/moto-e-4-plus-owens-all-things-root-guide.1259898/
Click to expand...
Click to collapse
Yeah, my sd card just took a dump. Can this be done without one? i found a thread but its from 2011...
https://forum.xda-developers.com/showthread.php?t=911228
stonefabtim said:
Yeah, my sd card just took a dump. Can this be done without one? i found a thread but its from 2011...
https://forum.xda-developers.com/showthread.php?t=911228
Click to expand...
Click to collapse
Yes, you can flash one without an SD card but you'll have to use a PC for side loading or copying the ROM to device (while in recovery) since you have to do a fill wipe of internal storage to remove encryption anyways..
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
Yes, you can flash one without an SD card but you'll have to use a PC for side loading or copying the ROM to device (while in recovery) since you have to do a fill wipe of internal storage to remove encryption anyways..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Ok, would I be doing it the way that it says in that thread just using twrp instead? Or does that method not work anymore? Thanks you guys for all the help.
stonefabtim said:
Ok, would I be doing it the way that it says in that thread just using twrp instead? Or does that method not work anymore? Thanks you guys for all the help.
Click to expand...
Click to collapse
Dude. No adb stuff needed anymore. Just boot into recovery and do all your wiping stuff. Then copy the ROM, no-verity, magisk, gapps zips from PC to device internal storage, I put in downloads folder. Then go back to the device and flash like normal. Internal storage on our owens is just labeled "sdcard". (I have the exact same device, using Boost Mobile)
Ok. Thanks. I'll give it a shot. Last phone I flashed was in like 2011 (I've been in prison for 5 years) so all this is new to me. It's probably frustrating trying to explain it to me. I appreciate the help though.
bcrichster said:
Dude. No adb stuff needed anymore. Just boot into recovery and do all your wiping stuff. Then copy the ROM, no-verity, magisk, gapps zips from PC to device internal storage, I put in downloads folder. Then go back to the device and flash like normal. Internal storage on our owens is just labeled "sdcard". (I have the exact same device, using Boost Mobile)
Click to expand...
Click to collapse
well, i did everything, used the lineage 14.1, now when i boot into system the start up failed. Should i try a different rom? I know I'm probably starting to be a pain.
stonefabtim said:
well, i did everything, used the lineage 14.1, now when i boot into system the start up failed. Should i try a different rom? I know I'm probably starting to be a pain.
Click to expand...
Click to collapse
Remember to format data and factory reset twice. Boot into recovery and do it again. Then flash ROM, no-verity.zip, magisk, gapps. Wipe cache & dalvik, Reboot recovery and flash again. Really. Afterwards ya should be fine..
Sent from my Moto E (4) Plus using Tapatalk
Yeah I think I just 'bricked' my phone.
stonefabtim said:
Ok. Thanks. I'll give it a shot. Last phone I flashed was in like 2011 (I've been in prison for 5 years) so all this is new to me. It's probably frustrating trying to explain it to me. I appreciate the help though.
Click to expand...
Click to collapse
I tryed flashing the lineage 14.1, gapps, no verity, superuser, now the boot fails. Tried going back into twrp and flashing a different rom, now instead of the 'install zip' button i have install image. And i didnt make a back up, I didnt have enough space in the phone to save the image. I dont know what to do lol
You really should use an external microSD card.
Question how did you root your E4 plus from boost I've been having hella time trying to do so
Funisillegal said:
Question how did you root your E4 plus from boost I've been having hella time trying to do so
Click to expand...
Click to collapse
- unlock bootloader
- flash twrp
- flash custom ROM &/or Root.zip
bcrichster said:
- unlock bootloader
- flash twrp
- flash custom ROM &/or Root.zip
Click to expand...
Click to collapse
Sorry I should of been more detailed. I know the process but my issue is the bootloader. My phone is thru boost and I know it can be unlocked but on Motorola's website I've gone thru pulling the sequence from ADB and when entered in I get a message saying it doesn't recognize what was entered and I've also tried using the data scrubber provided by motorola and same outcome. I've called Motorola and the best they could do was email me a link to their forums which was no help. I feel I have tried everything even the sunshine app and no dice. Frustrated as all help and any help would be greatly appreciated and I've been at this for two weeks
Sent from my Moto E (4) Plus using XDA-Developers Legacy app
Sounds like you accidentally left some letters/numbers/spaces that didn't need be there.. Pull that code again and remove all spaces, leave the #'s tho..
Funisillegal said:
Sorry I should of been more detailed. I know the process but my issue is the bootloader. My phone is thru boost and I know it can be unlocked but on Motorola's website I've gone thru pulling the sequence from ADB and when entered in I get a message saying it doesn't recognize what was entered and I've also tried using the data scrubber provided by motorola and same outcome. I've called Motorola and the best they could do was email me a link to their forums which was no help. I feel I have tried everything even the sunshine app and no dice. Frustrated as all help and any help would be greatly appreciated and I've been at this for two weeks
Sent from my Moto E (4) Plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Moto E (4) Plus using Tapatalk
I've done that and gone as far as entering it in manually a couple of times. Just to be sure I even had my wife read it to me and entered it in with the hashes only
Sent from my Moto E (4) Plus using XDA-Developers Legacy app
Related
Hello. I am new to this forum. I did do searching before I came here. I am sort of a noob so sorry for dumb questions. I wanted an MIUI theme on my phone. I tried MiHome but it doesn't change the UI so I want to get the MIUI ROM on my phone but I wasn't sure how. I know you have to root your phone first, but I read somewhere that MIUI isn't compatible with different rooting procedures like CyanogenMod. If thats true, which one is it compatible with? Is it possible for me to get MIUI on my phone? I have an HTC Vivid (of course) with Android ICS 4.0.3. Can anyone provide me with a guide on how to do get MIUI on my phone, preferably a video with a step-by-step description (yes, thats how noobish I am). Also, what are the odds of me rooting my phone if I follow the steps exactly as told? Sorry for a ton of questions. To sum things up, I would like to get MIUI ROM on my phone but have no idea how. Any help would be greatly appreciated! Thanks!
menachemt said:
Hello. I am new to this forum. I did do searching before I came here. I am sort of a noob so sorry for dumb questions. I wanted an MIUI theme on my phone. I tried MiHome but it doesn't change the UI so I want to get the MIUI ROM on my phone but I wasn't sure how. I know you have to root your phone first, but I read somewhere that MIUI isn't compatible with different rooting procedures like CyanogenMod. If thats true, which one is it compatible with? Is it possible for me to get MIUI on my phone? I have an HTC Vivid (of course) with Android ICS 4.0.3. Can anyone provide me with a guide on how to do get MIUI on my phone, preferably a video with a step-by-step description (yes, thats how noobish I am). Also, what are the odds of me rooting my phone if I follow the steps exactly as told? Sorry for a ton of questions. To sum things up, I would like to get MIUI ROM on my phone but have no idea how. Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Alright....you need to do ALOT of reading...I only say that so you don't brick your phone...but here's some info as well as how to get miui
It doesn't matter how you root your phone, you can still flash any Rom...you don't even need to be rooted to flash roms
Cyanogenmod is not a rooting method, it is an aosp rom...you cam flash from cyanogen but our device doeant even have a cyanogenmod Rom (well there is one but it was discontinued...for now)
In order to get miui you will need to do the following:
1) unlock bootloader
2) get recovery
3) download miui onto your phone (can't be any miui...has to be one made for our phone...you can find it on rootzwiki.com)
4) flash miui
More detail:
In order to unlock bootloader and get a recovery I suggest using Hansen vivid toolkit that is stickier in the dev section...its the easiest most newb friendly way to unlock bootloader and get a recovery...for the most part all you do is plug in your phone and click a few buttons...here's the toolkit: http://forum.xda-developers.com/showthread.php?t=1498003
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Alright....you need to do ALOT of reading...I only say that so you don't brick your phone...but here's some info as well as how to get miui
It doesn't matter how you root your phone, you can still flash any Rom...you don't even need to be rooted to flash roms
Cyanogenmod is not a rooting method, it is an aosp rom...you cam flash from cyanogen but our device doeant even have a cyanogenmod Rom (well there is one but it was discontinued...for now)
In order to get miui you will need to do the following:
1) unlock bootloader
2) get recovery
3) download miui onto your phone (can't be any miui...has to be one made for our phone...you can find it on rootzwiki.com)
4) flash miui
More detail:
In order to unlock bootloader and get a recovery I suggest using Hansen vivid toolkit that is stickier in the dev section...its the easiest most newb friendly way to unlock bootloader and get a recovery...for the most part all you do is plug in your phone and click a few buttons...here's the toolkit: http://forum.xda-developers.com/showthread.php?t=1498003
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Well, thank you for replying! I was gonna mention I am using a mac and the file is a rar, then exe files. Is it ok if I use a program to run it in an app file or does this have to be done on windows? Thanks!
menachemt said:
Well, thank you for replying! I was gonna mention I am using a mac and the file is a rar, then exe files. Is it ok if I use a program to run it in an app file or does this have to be done on windows? Thanks!
Click to expand...
Click to collapse
Shoot...idk how to do it on a Mac sorry :/
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Shoot...idk how to do it on a Mac sorry :/
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'm forced to use my slow PC. Hopefully it won't shut down in the process or else I'll be screwed. :/ Thanks again! I'll let you know if it works out if you want.
Just some ideas , if your pc is slow you can download and of the files you need on your phone then transfer them over to the pc , also if you download the tool kit you shouldn't need anything else but the Rom , if you get s off you will need to do a couple of things , but as mg said do some reading on this subject to kinda get an idea as to what your working with , make sure you kinda understand it so you don't brick your ph. Better safe than sorry .
Good luck and if you have questions there is a lot of good people here and would be glad to help.
menachemt said:
Hello. I am new to this forum. I did do searching before I came here. I am sort of a noob so sorry for dumb questions. I wanted an MIUI theme on my phone. I tried MiHome but it doesn't change the UI so I want to get the MIUI ROM on my phone but I wasn't sure how. I know you have to root your phone first, but I read somewhere that MIUI isn't compatible with different rooting procedures like CyanogenMod. If thats true, which one is it compatible with? Is it possible for me to get MIUI on my phone? I have an HTC Vivid (of course) with Android ICS 4.0.3. Can anyone provide me with a guide on how to do get MIUI on my phone, preferably a video with a step-by-step description (yes, thats how noobish I am). Also, what are the odds of me rooting my phone if I follow the steps exactly as told? Sorry for a ton of questions. To sum things up, I would like to get MIUI ROM on my phone but have no idea how. Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
There are several good guides on here to help you root here is one of them:
http://forum.xda-developers.com/showthread.php?t=1416836
ronnie498 said:
There are several good guides on here to help you root here is one of them:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
Help! I managed to root my phone, which is good. I am currently using WCX. I am not sure how to flash the rom. I tried going to my internal sd card and installing the miui zip file from there. After it reboots my phone, an htc logo loads, then it takes me to some chinese. It has like big chinese words on top in red, then in the middle it has white words, and in between the white words, it loads from 0 to 100 but I have no idea what to do now. It just leaves me stuck on this page! Can anyone help me? Do I need to uninstall the rom then follow a correct process of installation or can I just do the correct process? Also, please don't redirect me to some page, because I did a lot of googling and I found one which would help me, but the site is down. I am sure it isn't a long process. This is what I did:
1. Manually put the zip file into my internal sd card.
2. Rebooted my phone to recovery.
3. Installed the zip file, which flashed the rom.
Is that correct? Can someone please help me! Thanks!
menachemt said:
Help! I managed to root my phone, which is good. I am currently using WCX. I am not sure how to flash the rom. I tried going to my internal sd card and installing the miui zip file from there. After it reboots my phone, an htc logo loads, then it takes me to some chinese. It has like big chinese words on top in red, then in the middle it has white words, and in between the white words, it loads from 0 to 100 but I have no idea what to do now. It just leaves me stuck on this page! Can anyone help me? Do I need to uninstall the rom then follow a correct process of installation or can I just do the correct process? Also, please don't redirect me to some page, because I did a lot of googling and I found one which would help me, but the site is down. I am sure it isn't a long process. This is what I did:
1. Manually put the zip file into my internal sd card.
2. Rebooted my phone to recovery.
3. Installed the zip file, which flashed the rom.
Is that correct? Can someone please help me! Thanks!
Click to expand...
Click to collapse
1. Manually put the zip file into my internal sd card.
2. flash boot.img via fastboot (The boot.img should be in the zip of the rom You have to flash the boot.img - aka the kernel)
3. Rebooted my phone to recovery. Wipe data, cache, dalvik cache, factory reset
4. Installed the zip file, which flashed the rom.
ronnie498 said:
1. Manually put the zip file into my internal sd card.
2. flash boot.img via fastboot (The boot.img should be in the zip of the rom You have to flash the boot.img - aka the kernel)
3. Rebooted my phone to recovery.
4. Installed the zip file, which flashed the rom.
Click to expand...
Click to collapse
I tried what you said. I am using the All In One tool kit that someone told me to use so I flashed the kernel (boot.img) through that, assuming it is fastboot. I then rebooted my phone to recovery and selected the zip file, it flashed it. I rebooted my phone and it still takes me to that chinese screen. Is there a different MIUI ROM zip file download? I used this one: androidfilehost.com/main/HTC_Holiday_Developers/rafyvitto/MIUI_ICS_V4/
Maybe a different file would work? Thanks in advance!
menachemt said:
I tried what you said. I am using the All In One tool kit that someone told me to use so I flashed the kernel (boot.img) through that, assuming it is fastboot. I then rebooted my phone to recovery and selected the zip file, it flashed it. I rebooted my phone and it still takes me to that chinese screen. Is there a different MIUI ROM zip file download? I used this one: androidfilehost.com/main/HTC_Holiday_Developers/rafyvitto/MIUI_ICS_V4/
Maybe a different file would work? Thanks in advance!
Click to expand...
Click to collapse
Let me do some checking will let you know shortly
ronnie498 said:
Let me do some checking will let you know shortly
Click to expand...
Click to collapse
I have no clue what I did. I just rebooted and some other stuff but now it works. I think it was the wipe that I did. Thanks for your help!
EDIT: I tried applying the Ultimate Iphone Theme v7.0 but it doesnt work. I go to themes and select it but it doesn't apply. I tried rebooting but it still doesnt work. I have the MIUI ROM on my phone. Why doesn't the Ultimate Iphone Theme apply? I really like it. Can anyone give me a step-by-step on how to install it because there are no good tutorials online. Thanks!
menachemt said:
I have no clue what I did. I just rebooted and some other stuff but now it works. I think it was the wipe that I did. Thanks for your help!
EDIT: I tried applying the Ultimate Iphone Theme v7.0 but it doesnt work. I go to themes and select it but it doesn't apply. I tried rebooting but it still doesnt work. I have the MIUI ROM on my phone. Why doesn't the Ultimate Iphone Theme apply? I really like it. Can anyone give me a step-by-step on how to install it because there are no good tutorials online. Thanks!
Click to expand...
Click to collapse
It's been a while since I used miui, but last I heard the themes in the miui theme chooser/downloader wernt compatible with miui...at least the majority wernt there was still quite a few that worked/partially worked
Sent from my HTC PH39100 using Tapatalk 2
With the ROM I used, since I am S-On (which I assume you are too since you did not do the wire jump thing from what I read) after you initially flash the boot.img file using fastboot, you need to flash the rom, which you said you did. Then go back in and reboot to bootloader, and flash the boot.img again. It may have been just specific to the Rom I used, but that is the instructions I followed for mine. I hope you made a nandroid before you flashed Miui in case you ran into these troubles....
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.
For RUUs, stock recoveries, stock Nandroids (in case you need to return to stock, unrooted), TWRP links, and other important tools, please check this thread by Rydah805. It has the stuff you want.
Note: S-Off link at the bottom of the OP. You'll need the HTCDev unlock method completed first and you'll need root access to make it work. So once you're done with this little guide (or the noob friendly one in the HTC One international forums here), you can hop right on over to Sunshine (linked at the bottom) to get that done if you don't mind the $25 fee.
I can confirm this works on the following:
Android 5.0.2
HTC Sense Version 7.0
Software Number 1.32.531.25 (tested and working with software update 1.32.531.33)
Kernel Version [email protected] #1 SMP PREEMPT
Baseband version 01.01_U11440251_64.04.50312G_2_F
Build Number 1.32.531.25 CL505029 release-keys
As usual, you do this at your own risk. It's not my fault if you mess things up (although I sympathize completely if you do). I cannot confirm this works on any other version than this one, although I've seen this work on the AT&T, Verizon, Sprint, and International variants. Feel free to link there or just copy paste the whole damn thing and post it over in those forums to make it easier for those folks. I really, honestly don't mind.
It took me a while so I figured i'd make a thread on it to make it easier for our fellow T-Mobile M9 peoples. This is essentially a link dump so you can get to the places you need to go faster. Before continuing, please read this advice from Rydah805 because it's invaluable. Thankfully, we won't be using the 2.8.5.0 version of TWRP in this quick tutorial but the important part of the message is that you should make a nandroid of the unmodified stock ROM BEFORE rooting. Otherwise you will have many problems down the line. If you have thanks to give, give them to the posters of all these various threads. I did nothing special, just went through the steps to see how it worked.
Please note, if you're using Mac or Linux, I don't use those things and couldn't try/test/use the root method on those platforms. I assume Linux works pretty much the same way as Windows (you'll have to get ADB/Fastboot a different way of course).
Let's get started
Pre-requisites:
1. You'll need SuperSU by Chainfire. You can download it here. Put this on your device where you can find it later. I've seen people say it needs to be on an external SD card, but I've seen it work from both internal and external.
2. You'll need a modified version of 2.8.6.0 of TWRP. You can download that here. The link is at the bottom of the post where it says "Beta version with system backup fixed...". That's the one you want.
3. You will need ADB and Fastboot. I recommend Minimal ADB and Fastboot. You can find that here. Install it like any other Windows application AND MAKE SURE TO LET IT CREATE A DESKTOP ICON. This will make finding it later much easier. Linux users will need to find a different way to get ADB/Fastboot. Probably just downloading the SDK...although if you're running Linux you know all this already so let's just move on.
4. You'll need the HTC One drivers. I did this by installing HTC Sync Manager and it worked fine for me. You can download the HTC Sync Manager here.
Okay now for the actual root method.
1. First you'll need to unlock the bootloader using HTDdev.com. Follow this tutorial to do that.
2. Once your bootloader is unlocked. You'll want to flash the TWRP recovery to your HTC One M9. Rename the TWRP file you downloaded in the pre-requisits it to "recovery" (no quotes, and the .img shouldn't be visible) and place it in the Minimal ADB and Fastboot folder on your COMPUTER. For windows, this is usually under your C drive > Program Files (x86) > Minimal ADB and Fastboot.
3. On your One M9, turn it off. Press the volume down key and power simultaneously and you'll get a black screen. Using the volume keys to scroll, go to Download Mode and click the power button to confirm.
4. On your computer, open Minimal ADB and Fastboot using the icon I told you make earlier (you listened, right? ). If you renamed the TWRP image you downloaded earlier to "recovery" and put it in the proper folder as I stated earlier, then all you need to do is type the following:
Code:
fastboot flash recovery recovery.img
5. At this point the recovery should flash successfully. HOWEVER, in my experience, you may get some silly errors (unknown error, Fastboot crashed, too many links, etc). If this is the case, don't panic. Turn the device off, re-enter download mode again, close the command window and re-open Minimal ADB and Fastboot and try again. All I did to get it to work was try a couple of times over again. Sometimes it goes, sometimes it doesn't. Silly Windows being silly I presume.
6. Okay, you should now have recovery. Enter recovery by pressing and holding volume up and volume down while pressing power to enter bootloader mode. Scroll using the volume keys to "Recovery" and hit the power button. You should now be in a weird looking TWRP. This is normal.
7. CREATE A FREAKING NANDROID BACKUP RIGHT NOW. According to some recognized members of the community, HTC updates only work on an unmodified system. If you ever want to receive official updates from HTC, you HAVE to create a NANDROID RIGHT NOW. Do it. I'll wait.
8. Did you create a Nandroid yet? No? You naught boy/girl, go do that now please.
9. But no really, create a Nandroid please.
10. Once your Nandroid is complete and you have an unmodified, unrooted system backed up, we can actually root the damn thing. You should have SuperSU on your device (as per the pre-requisites). If not, go download that using the link I provided above and put it on your device. Anywhere should be fine.
11. Okay now here's the tricky part. TWRP boots into recovery as Read Only but ONLY on unmodified systems. The reason for this is because HTC updates can't install if the recovery is read/write enabled. Since you're not yet rooted, your TWRP is booting up to Read Only. That means even if you flash SuperSU right now, it won't actually do anything because TWRP can't write to /system (yes, it will say it flashed successfully, it's a liar liar pants on fire).
12. To overcome this, you'll need to follow the instructions in this post.
13. Once you have manually mounted the system partition using the post I linked above (did you thank him? I think you should've thanked him), you may now flash SuperSU.zip as you normally would.
14. Reboot, and you should now be rooted. Don't forget to install BusyBox (search "busybox" in the Google Play Store, download the one developed by Stephen (Stericson). Once installed, open it, give it Superuser permission, then just hit install). Once busybox is installed, you will have the full root experience and can use apps like Titanium Backup.
And that should do it folks. Again, don't thank me, all I did was gather links and put the steps in order. The other people deserve your praise.
Now as for updating, I don't know how it will work yet, but this is how I believe it'll work in theory.
If you have a system update:
1. Create a titanium backup of all of your apps (trust me).
2. Reboot to recovery, restore your unrooted, unmodified Nandroid that I told you literally 5 times to make.
3. Reboot, then check for updates. Install the system update.
4. Re-root your device using the steps above (by then I'm sure there will be a more stable TWRP, make sure you always have the most updated one!)
5. Restore your apps via Titanium Backup.
Again, that's how I believe it should work in theory but I won't know for sure until I receive a system update.
IF YOU HAVE PROBLEMS, please contact the smarter people in the threads I linked who are actively working on helping people with issues. I suppose you can post them here, but as you can see by my post count, I rarely pay much attention
Enjoy!
*Edit*
Bonus points: Our device is compatible with the S-Off method brought by Sunshine. It's a $25 purchase but it does work (tested) and I've seen people report that it works on the .33 update as well. Click here to check out Sunshine.
great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?
Rydah805 said:
great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?
Click to expand...
Click to collapse
I could, definitely. Maybe create a clean one (without my stuff logged in) and upload here...what would I have to include so people could actually use it? I've never tried restoring a borrowed Nandroid backup before lol.
All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
Boot.emmc.win
Boot.emmc.win.md5
Recovery.log
System.ext4.win000.win
System.ext4.win000.win.md5
System.ext4.win001.win
System.ext4.win001.win.md5
System.ext4.win002.win
System.ext4.win002.win.md5
System.info
Click to expand...
Click to collapse
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)
Rydah805 said:
All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)
Click to expand...
Click to collapse
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.
DunningKrugerEffect said:
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.
Click to expand...
Click to collapse
Must be my setup. Yours should be perfect. Looking forward to downloading a copy. ? thanks in advance.
Sent From My HTC One (M9)
Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.
Prasad said:
Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.
Click to expand...
Click to collapse
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)
Rydah805 said:
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks! I tried to flash TWRP and got this:
$ fastboot flash recovery twrp-2.8.6.0-hima.img
sending 'recovery' (35928 KB)... OKAY
writing 'recovery'... FAILED (remote: cannot flash this partition in s-on state)
Click to expand...
Click to collapse
EDIT: Never mind.. Got it to work!
[Q] Any benefit to unlock bootloader only?
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?
Gravityrat said:
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?
Click to expand...
Click to collapse
Unlocking the bootloader gives you access to installing custom ROMs, kernels and rooting the phone. You only really need to unlock it if and when you're doing any of these.
Figured as much. I wanna run it stock for a bit to see how it runs. I will admit, I am impressed with the battery life so far. I made it 12 hours at work with 17% left when I got home.
Worked for me. Thanks
Am I missing something? While in recovery, after I've already made a backup(It's uploading) I go to advance>terminal and I type in
Code:
mount -t ext4 /dev/block/bootdevice/by-name/system /system
it returns
Code:
mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Device or resource busy
Edit: Apparently it still worked.
Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive
xxquicksh0txx said:
Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive
Click to expand...
Click to collapse
mind if i link that in my thread?
Rydah805 said:
mind if i link that in my thread?
Click to expand...
Click to collapse
That's what it's there for
:good:
does anybody know if this works on mac?
child0fdecadance said:
does anybody know if this works on mac?
Click to expand...
Click to collapse
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.
Prasad said:
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.
Click to expand...
Click to collapse
sweet! did you have to change any of the procedure or did you do it step by step?
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu