Database Develop

[Q] N00b has done his best to kill Three HTC one (the n00b is me)

This is a great example of how to make a mess of things with a combination of a little knowledge and not paying attention. Here's the background:
UK 1.28 One Stock + Root. No other mods. I needed to install Busybox so I could install Screen Standby # Root. Apparently, the marketplace apps are unable to install due to the System folder protection. I found a .zip to install using TWRP (Sprint_One_Root_Disable_System_Write_Protection_1.29.651.10.zip) and you can already see where I've gone wrong. I looked for a generic/EU version of this zip but this was the only one I could find so off I went. Naturally this didn't work and my phone now won't boot. At least I can get to TWRP still so I presume all is not lost. Looking at my /system directory, there's nothing in it apart from the /bin folder (also empty). From further reading I guess I need to find a stock kernel and use ADB push to push boot.img and then fastboot to install. So my questions are:
1) Is this the correct way to fix this problem? I'd rather rescue this system as I've got everything the way I like it. No, I hadn't done a backup. Yes, I'll sort that as soon as I've fixed it.
2) Can somebody point me in the direction of the stock kernel for my device?
3) How was I supposed to install BusyBox? (I still need to get Screen Standby # Root installed!)
Many thanks for your help in advance.

ShadowTD said:
This is a great example of how to make a mess of things with a combination of a little knowledge and not paying attention. Here's the background:
UK 1.28 One Stock + Root. No other mods. I needed to install Busybox so I could install Screen Standby # Root. Apparently, the marketplace apps are unable to install due to the System folder protection. I found a .zip to install using TWRP (Sprint_One_Root_Disable_System_Write_Protection_1.29.651.10.zip) and you can already see where I've gone wrong. I looked for a generic/EU version of this zip but this was the only one I could find so off I went. Naturally this didn't work and my phone now won't boot. At least I can get to TWRP still so I presume all is not lost. Looking at my /system directory, there's nothing in it apart from the /bin folder (also empty). From further reading I guess I need to find a stock kernel and use ADB push to push boot.img and then fastboot to install. So my questions are:
1) Is this the correct way to fix this problem? I'd rather rescue this system as I've got everything the way I like it. No, I hadn't done a backup. Yes, I'll sort that as soon as I've fixed it.
2) Can somebody point me in the direction of the stock kernel for my device?
3) How was I supposed to install BusyBox? (I still need to get Screen Standby # Root installed!)
Many thanks for your help in advance.
Click to expand...
Click to collapse
Flash a kernel form here. http://forum.xda-developers.com/showthread.php?t=2255160

SmiLey497 said:
Flash a kernel form here. http://forum.xda-developers.com/showthread.php?t=2255160
Click to expand...
Click to collapse
That's brilliant. Given I can only get to my bootloader or TWRP and don't have a USB OTG cable, will that work with TWRP's 'sideload' functionality? If not, how would I install it using fastboot?
<edit> Just tried it using TWRP sideload and I get a 'No MD5 file found' and 'Zip signature verification failed. Any suggestions?
<edit2> Changed to CWM and that seemed to install correctly but the phone still refuses to boot. There's a few errors in CWM that seem to indicate it can't mount System - could this be the problem? I never S-OFF'd before I got in to this mess.
Thanks!

Anyone else? I've got a USB OTG cable on its way and what I hope is the correct Nandroid backup to restore, but I've not given up hope on bringing the current build back to life.

Right, well, things are certainly brighter than yesterday. USB OTG cable arrived, restored Nandroid backup for UK Three 1.28. Phone comes back to life. Brilliant. Set about getting back to where I was and sorting out the Busybox problem. I installed:
HTC Preloaded apps via CWM
Team Seven Sense Kernel v4 stable
Installed Busybox via a market app and things are looking excellent. Apart from the camera app not working. Oh hell. 'Unable to start camera' after about 10-20 seconds of a black screen with camera controls.
Figured this might be a cache or permissions issue so I went back to recovery and cleared cache, dalvik cache and repaired permissions. Clear the app data as well from Settings. No dice. The only thing I didn't delete is the user data as I was hoping to not lose the pictures I've got on there. Everything else is brilliant so I hope somebody can help me fix this!
Thanks again.

Trying to get back to Stock - Rogers M7_ul

I could really use your help guys. I'm trying to get back to stock so I can get the updates being pushed by HTC/Rogers. There are a couple bugs that are really annoying me. So, before i tell you what I need, here's what I have.
M7_ul
Locked Bootloader - was relocked after unlocking a while ago
Rooted
CWM recovery
Stock HTC ROM
S-OFF
Baseband 4a.14.3250.14
Main 1.29.631.4
Modelid: PN0712000
CID: Roger001
Now, what I need is either the RUU or the stock recovery files and some sort of guide on how to install them. I've tried downloading from here: http://www.htcdev.com/devcenter/downloads/P60 but i can't flash it via CWM. I've also tried downloading and RUU from here: http://bugsylawson.com/files/file/1...5013-1033115001-release-312087-signed-2-4zip/ but when i unzip i get corrupt files and i can't move it to the phone.
I'm at a complete loss here. I would really appreciate any guidance you guys can provide. Any idea where I can get the proper RUU and how I can install it? Or if it's easier to just get the stock recovery, any idea where I can get it and how to install it using CWM or another method such as terminal emulator?

no need to relock bootloader is s-off'd
easiest way, IF there is an ruu or ruu zip for the rogers variant (you would need the ruu files that match 1.29.631.4) floating around i suggest this...back up sd card contents,boot into recovery...wipe the system,reboot into bootloader connect device via fastboot,run the ruu..one it boots except the ota
done

but how do i run the RUU and how do I know which exactly is the right RUU for me? I've heard RUUs are exe files but i haven't found any that are. The one I think is right for me is a zip and it seems to be corrupt though I dled the 1gb file twice. So i'm a bit confused.

vijn said:
but how do i run the RUU and how do I know which exactly is the right RUU for me? I've heard RUUs are exe files but i haven't found any that are. The one I think is right for me is a zip and it seems to be corrupt though I dled the 1gb file twice. So i'm a bit confused.
Click to expand...
Click to collapse
You can find the RUU you need here: http://forum.xda-developers.com/showthread.php?t=2207874
Hope to has been usefull

Thanks so much. But I'm still not sure which version to get. I tried the RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed.exe but no go. I get an error. Says it's the wrong ROM. Ugh. I've had no luck with this. So frustrating.
ImJacky said:
You can find the RUU you need here: http://forum.xda-developers.com/showthread.php?t=2207874
Hope to has been usefull
Click to expand...
Click to collapse

So, I've tried Rogers 1.29.631.4.zip which is an nandroid backup but no go on that either, using CWM. At a total loss here.

vijn said:
So, I've tried Rogers 1.29.631.4.zip which is an nandroid backup but no go on that either, using CWM. At a total loss here.
Click to expand...
Click to collapse
This is what I did and it worked like a charm... minus of course the issue after the software update which got fixed anyway.
http://forum.xda-developers.com/showthread.php?t=2357881

Ugh. Thanks cue_32. I had just downloaded that file when I saw your post, so I was very hopeful this would work. Pushed it to my phone, tried installing via CWM but almost immediately it said installation aborted. I have no idea what's going on. Nothing seems to be installable. WTF? And the link you posted for the stock recovery doesn't seem to lead to anywhere that has a recovery file for DL. So, I'm totally stuck now. UGH. Been on this for almost 2 days now. Haven't run into this much trouble with any of my previous phones, despite trying out almost a dozen different ROMs. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.

vijn said:
Ugh. Thanks cue_32. I had just downloaded that file when I saw your post, so I was very hopeful this would work. Pushed it to my phone, tried installing via CWM but almost immediately it said installation aborted. I have no idea what's going on. Nothing seems to be installable. WTF? And the link you posted for the stock recovery doesn't seem to lead to anywhere that has a recovery file for DL. So, I'm totally stuck now. UGH. Been on this for almost 2 days now. Haven't run into this much trouble with any of my previous phones, despite trying out almost a dozen different ROMs. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.
Click to expand...
Click to collapse
There's no RUU available yet for Rogers so I personally wouldn't try any other RUU.
So you downloaded the Nandroid backup from Whamboush (or whatever the name was), you extracted and moved the EXTRACTED FOLDER to the proper location (Clockwork>Backup) and updated the permissions correct? I used Root Browser to do this, the permission should be exactly like your other CWM backups. If I recall correctly there are 3 columns with 3 rows, all are X'd except for the last box on the 2nd column\3rd Row. (middle\bottom)
example:
X X X
X X X
X _ X
From there I just did the restore using the original clock work mod (non-touch cause I'm old skool)
After it successfully flashes, before it prompts you to reboot you'll be prompted to re-root from within CWM itself. Select No.
After it reboots, test to make sure everything is ok.
Then enter fastboot mode (adb reboot bootloader), from fastboot mode you can then flash the recovery.
You're welcome
---------- Post added at 11:29 PM ---------- Previous post was at 11:14 PM ----------
vijn said:
Ugh. Thanks cue_32. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.
Click to expand...
Click to collapse
here's your stock recovery...I know how frustrating it can get so don't mind the step by step procedure.
http://d-h.st/dyr
You're welcome

well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....

mathrania said:
well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....
Click to expand...
Click to collapse
If I had the original nandroid, of the original Rom for example, would all that one needs to do is flash it and unroot and that's it?
Sent from my HTC One

chc31 said:
If I had the original nandroid, of the original Rom for example, would all that one needs to do is flash it and unroot and that's it?
Sent from my HTC One
Click to expand...
Click to collapse
Flash, unroot (if necessary) and flash stock recovery, which is what the instructions I provided, and optional lock the boot loader

So, I tried changing the permissions, which I hadn't done before, using Root Explorer but it says that some files can't be modified. So I can't set the permissions and CWM won't see those files at all, so that's not an option it seems. So I decided to just flash the recovery but when i do i get an error in adb Failed (remote: not allowed). So, that's not working either. Hehe. Every time I think i got it, something stands in the way. Will definitely feel like an accomplishment when i get this thing done finally, just not sure how or when it'll happen.
cue_32 said:
There's no RUU available yet for Rogers so I personally wouldn't try any other RUU.
So you downloaded the Nandroid backup from Whamboush (or whatever the name was), you extracted and moved the EXTRACTED FOLDER to the proper location (Clockwork>Backup) and updated the permissions correct? I used Root Browser to do this, the permission should be exactly like your other CWM backups. If I recall correctly there are 3 columns with 3 rows, all are X'd except for the last box on the 2nd column\3rd Row. (middle\bottom)
example:
X X X
X X X
X _ X
From there I just did the restore using the original clock work mod (non-touch cause I'm old skool)
After it successfully flashes, before it prompts you to reboot you'll be prompted to re-root from within CWM itself. Select No.
After it reboots, test to make sure everything is ok.
Then enter fastboot mode (adb reboot bootloader), from fastboot mode you can then flash the recovery.
You're welcome
---------- Post added at 11:29 PM ---------- Previous post was at 11:14 PM ----------
here's your stock recovery...I know how frustrating it can get so don't mind the step by step procedure.
http://d-h.st/dyr
You're welcome
Click to expand...
Click to collapse

Ya, I tried flashing the recovery, no go. No go on the nandroid backup either. The good thing is, i'm getting much more familiar with adb. Hehe.
mathrania said:
well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....
Click to expand...
Click to collapse

vijn said:
Ya, I tried flashing the recovery, no go. No go on the nandroid backup either. The good thing is, i'm getting much more familiar with adb. Hehe.
Click to expand...
Click to collapse
well, interested in another option.....i havent done this, but some people do...
change you CID to some device which has rcvd OTA, like mine is HTC_J15....just an example... now your mobile would be WWE internation blah blah... now grab the RUU.exe for it....backup all your data...and run it.....and then go for the OTA's ...in short the region of your device would be changed... you will have to find it in the forum itself... there are tutorials out there to do it...

Well, I'm leaving for the weekend, so I'll have to put this aside for now. In my research I had come across what you are suggesting but it seemed like more trouble and a little confusing so I opted against it, but maybe I'll have to revisit it when i get back. Hopefully you guys will still be around to provide some guidance. I do appreciate all your help. THanks again.
mathrania said:
well, interested in another option.....i havent done this, but some people do...
change you CID to some device which has rcvd OTA, like mine is HTC_J15....just an example... now your mobile would be WWE internation blah blah... now grab the RUU.exe for it....backup all your data...and run it.....and then go for the OTA's ...in short the region of your device would be changed... you will have to find it in the forum itself... there are tutorials out there to do it...
Click to expand...
Click to collapse

cue_32 said:
Flash, unroot (if necessary) and flash stock recovery, which is what the instructions I provided, and optional lock the boot loader
Click to expand...
Click to collapse
alrighty! ill keep that in mind, thinking of rooting! i had a htc sensation i bought online, if anything would happen to it i couldnt do anything about it, so i rooted and kept it like that. Now a Rogers One.. different lol. Thanks!

vijn said:
So, I tried changing the permissions, which I hadn't done before, using Root Explorer but it says that some files can't be modified. So I can't set the permissions and CWM won't see those files at all, so that's not an option it seems.
Click to expand...
Click to collapse
Just to be sure, the EXTRACTED FOLDER I'm referring to is the last folder before you see ALL the files of the 'ROM' like boot.img, cache.ext4.tar, recovery.img, etc...This folder is the one you want to make the permission changes to.
I had the exact same problem before and tried on ES File explorer, Astro File explorer, and Root browser (not root explorer although Im sure it works too). (I've never had to have this many installed at once) but basically this was the problem because after I extracted and updated the permission using Root browser, it worked on 1st try.
What I had done as well is make sure I was moving the extracted folder to the proper location by doing a nandroid back up first. From there I located the backup I just created and moved the extracted folder there. Once the extracted folder is in the right place, I went and used root browser and updated the permissions.

This totally worked Cue. Thank you so much. Finally managed to get the nandroid back up flashed, but then when I went to flash the recovery, i got an error: Failed (remote: not allowed). Ugh. So baby steps, but still in the right direction. So now my status is, Locked bootloader, s-off, flashed nandroid backup, but still have CWM recovery which I apparently can't seem to shake. Anyone know where I can maybe find a .zip recovery that I can try flashing via CWM? Not sure whether that's even possible, as CWM would essentially be overwriting itself but not sure what other options i have. From the research I've done so far though, it seems i can't flash a recovery with a locked bootloader. It does feel like i'm going around in circles here.
cue_32 said:
Just to be sure, the EXTRACTED FOLDER I'm referring to is the last folder before you see ALL the files of the 'ROM' like boot.img, cache.ext4.tar, recovery.img, etc...This folder is the one you want to make the permission changes to.
I had the exact same problem before and tried on ES File explorer, Astro File explorer, and Root browser (not root explorer although Im sure it works too). (I've never had to have this many installed at once) but basically this was the problem because after I extracted and updated the permission using Root browser, it worked on 1st try.
What I had done as well is make sure I was moving the extracted folder to the proper location by doing a nandroid back up first. From there I located the backup I just created and moved the extracted folder there. Once the extracted folder is in the right place, I went and used root browser and updated the permissions.
Click to expand...
Click to collapse

Do i really have to go through the entire unlock bootloader process to flash stock recovery? Ugh. I honestly don't get why this is so complicated. My previous phones were SOOO much simpler in comparison. This just feels like way too much trouble. I originally just wanted a rooted phone to get rid of bloatware and other small tweaks. I had no idea it would have such annoying consequences. Now, I'm just trying to get the stock ROM updated with HTC's latest bug fixes and software upgrade before i try and custom roms. I suspect it's not going to get easier though. I think once i get this finally done, i'm just going to leave the phone as is, completely stock at least until the 4.2.2 upgrade. Then after that I'll root it again. I used to love this process of rooting, installing custom roms, etc. Was fun, but this is just tedious as all hell. Hehe. Anyway, enough ranting. Ya, if anyone can tell me what my next step is, I'd be grateful.

backing up / restoring original firmware

i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.

gcbxda said:
i'm about to root my moto x dev.
i want to keep a backup of the original firmware in case i want to go back.
does it make any difference that it is encrypted? i'm guessing no...
also, any good dumb proof steps? the main info thread only mentions restoring stock by downloading a firmware not using a backed up one.
Click to expand...
Click to collapse
Rooting how? What version of android are you on? These are very important considerations to be able to make a recommendation.
Assuming you intend to unlock your bootloader, you can make a backup with TWRP Custom Recovery BEFORE you root.
If you are using the PIE exploit (only current root method for 4.4.2+), you cannot flash custom recovery. If this is the case, your only option to return to stock will be to flash the official SBF file for your carrier as listed in the "Return to Stock" thread. Not really important since the changes are lost upon reboot anyways.
Regardless, we need more details.
EDIT: Just saw you are using DEV edition.
Very easy!
FIRST: When you unlock your bootloader, it ERASES EVERYTHING. Save anything important first. You cannot make a backup until after you flash twrp, which you can only do AFTER you unlock the BL.
Additionally, according to this thread, it is impossible to backup an encrypted device. So after unlock, you are advised to not choose to encrypt, otherwise no backup can be made: http://forum.xda-developers.com/moto-x/moto-x-qa/twrp-device-encryption-t2711700
Once Unlocked, flash TWRP custom recovery with mfastboot:
mfastboot flash recovery twrpfilename.img
link to download twrp here: http://forum.xda-developers.com/moto-x/development/recovery-twrp-official-support-moto-x-t2779637
then use fastboot to reboot into bootloader:
fastboot reboot-bootloader
now VOL DOWN to "recovery" and VOL UP to open it.
There is a BIG backup button. Use it.
Afterwards, click exit. When you do, it will tell you that you are not rooted and ask if you want to flash SuperSU Installer.
Say yes! Once rebooted, run SuperSU installer and it will root & install SuperSU for you. It will give you 2 options: Choose Play Store Option.
Good Luck

@gcbxda
Keep in mind, since unlocking the bootloader also does a factory reset and puts you back to "fresh out box" the backup you do once you flash TWRP on your phone, will be no different than "Stock Rom" (except TWRP recovery). So why not use the factory firmware to flash the phone back instead of restoring such a backup?
Oh, and keep in mind, if you do backup while in TWRP, you'll want to copy that back up file from the phone to the PC for storage. Future Factory Resets and such will likely wipe the X's internal /SDcard so the backup file would be lost.
Now if your intent is to unlock the bootloader, setup your phone the way you like it before rooting, back up, and then root.... I can see the value in that.

You can also use 'adb pull /sdcard c:\' to backup any files you have

Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore

Stock
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Also, what if I do a backup of the partitions with ADB? ...man sometimes the android community pisses me off. everything must be packaged in a app or some GUI that hides all the information. ...just wasted 2 days reading xposed source to learn that all i had to do, instead of even installing xposed, was to edit a single sql value from 1 to 0... i'm all for the nice guis, but don't hide the actual steps like it is some black magic.
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0

MikeNaples said:
Hello,
You can find all the stock roms here - - > http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy

gcbxda said:
thanks. i also saw that motorola offer it themselves.. is this their own repository?
but regardless, it is always nice to already have your own handy
Click to expand...
Click to collapse
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
SBF.Droid-Developers.org is neither owned, operated nor sponsored by Moto. They keep every version full stock roms (SBF files) they find. I'm not going to speculate how they come across them, but they have many SBF files that Moto hasn't officially released to the public too. i.e. Sprint, ATT, and other carriers.
---------- Post added at 07:27 AM ---------- Previous post was at 07:01 AM ----------
gcbxda said:
Thanks everyone!
Backing up my stuff is good, but my main concern is going back to stock if I need (what if they release a kick ass moto watch and i need the OTA stock upgrade to use it?
Click to expand...
Click to collapse
There are ways to get back to stock to be able to take an OTA -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
gcbxda said:
Also, what if I do a backup of the partitions with ADB? ...
When i started this thread i was thinking of a backup more on the lines of: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
You can certainly back up that way. But I haven't tried backing up that way and restoring, so I don't know.
gcbxda said:
anyway, if adb pull is not an option, my plan of action:
1. backup everything i want on the fake sdcard
2. copy the files out (either adb pull or rootbrowser to move sd files to a external pendrive on the USB OTG)
3. factory reset and/or root bootloader
4. install TWRP (this will be new, always liked classic no-touch CWM on my nexus)
5. backup stock roms
6. root/flash/etc
anyone can expand on item 5 with personal experiences? ideally if you ever did a successful back-to-stock restore
Click to expand...
Click to collapse
With my HTC Incredible and HTC Thunderbolt and Moto Droid, I did backups in CWM, and restores. It was mainly for when a new upgrade came out. I would backup my current device setup, apps, etc. Apply the update, and if I didn't like the update or had problems, I could revert to my pre-update backup, rather than flash a stock rom and have to set it up all over again, install all my apps, etc. But the HTC devices had S-OFF, so downgrading wasn't an issue.
With my Droid Bionic, the bootloader wasn't unlocked, so it wasn't an option. And there were issues with GPT.Bin and other items preventing downgrading roms, even when flashing official full SBF files.
I haven't really done this with my VZW Dev X, mostly due to the fact that while the bootloader is unlocked, its not unlocked as much as a Nexus device, or an HTC with S-Off, where you can downgrade and flash any parts no matter what. Security issues, things like GPT.BIN, MotoBoot, etc can still get in the way when trying to downgrade. So I never felt it worth the risk. Not to mention the limited space on the X, and time/effort to make the back up and move the file to the PC, and then getting it back on the phone should I ever need to restore it since there is no real SD card.
If your intent of backing up stock roms is so you can revert to stock, having the Moto SBF files available elevates most users concerns. When flashing the same version, there are ways to do it without losing your Apps/Data (like in the case of running 4.4.2 rooted and modded, but wanting to get back to stock to take the 4.4.3 OTA).
If you want to do a backup/restore inside TWRP, you can. I have read many posts from users who were successful. I just advise that you keep track of the version you back up, and only restore if the same Android version is still on your phone (i.e. only restore a 4.4.2 back up if 4.4.2 is on your phone, only restore a 4.4 back up if 4.4 is still on your phone, etc)

wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app

gcbxda said:
wait, what are the limitations i will have with a unlocked Dev device?
with my nexus and touchpad i often tried 4.3 roms and went back to 4 or 2.3 even...
i tried searching the terms you mentioned but it spawn all sort of threads with OP having some flashing problem and then pages of comments starting with "i think..."
I'm extremely confused now
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Unlocked or Locked Moto X... you have to be concerned when flashing backwards. The Security features on the X prevent downgrading certain components. Attempting to do so will brick or set you up to brick in the future.
Please see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm
Short version... once you have 4.4.2 on your phone, do NOT attempt to downgrade.

KidJoe said:
Moto officially offers recovery images (full stock rom) for the GSM Dev/GSM Unlocked XT1053 and Verizon XT1060 by request on their web site here -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images They are the most currently released rom only. You wont find older versions there.
Click to expand...
Click to collapse
Lol. looking back at that thread i whish i had went ahead and did all the backups on all OTA updates before each twrp/root and did not trust motorola to have my back.
I'm a moron. Bumping this as a lesson to others

[Q] First Nexus

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.

How To Flash MetroPCS MM 6.0.1 Official ROM Without PC (already rooted 626s only)

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