So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
Related
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
Hi all!
Just a quick synopsis. I've held off for a while. I've read just about everything related as it's come across here over the past few weeks.
I've been perfectly happy with where I sat:
VZW Dev Ed, Rooted, TWRP, xPosed, Tehter & Gravity Box modules.
I'm not fond of ADB commands, etc. but can work my way through them.
Today, I decided to to take a quick stab at things (a little differently).
So, here's what I did:
1) Unfroze some bloat
2) Unistalled xposed Framework
3) USED Flashify to backup my TWRP
4) USED Flashify to install stock recovery
5) Downloaded OTA
6) Installed 4.4.2 update
7) It FAILED
So, I restored my TWRP recovery through Flashify; re-installed xPosed Framework; refroze the bloat and I'm back to where I was before.
The only thing that I really think might have caused the update to fail was the fact that I had AOSP Browser installed. (with its related installer)
So, that's my question here....opinions...would that cause the update to fail?
I've since tried to uninstall that browser with the related installer but it keeps getting hung and force closes when trying.
Opinions? (other than..."please, use ADB commands")
I'm assuming flashing my system ui might take care of that?
Thanks for ideas. I know I'll take the time to get it done "proper". Just haven't been pressed to do it yet.
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
hlaalu said:
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
Click to expand...
Click to collapse
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Dburgessme2 said:
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Click to expand...
Click to collapse
Hmm double check that it checks for subscription when tethering to make sure it changed the files back?
I'm a little rusty with fastboot, but it doesn't wipe your data unless you ask it to:
Code:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
[B]$ fastboot erase userdata[/B]
$ fastboot erase cache
$ fastboot oem lock
So I think if you just don't do the fastboot erase userdata command your data is safe. I'll wait for someone with more experience to confirm that.
But even if that's not the case, I'll still wait because we have to fastboot for root and recovery anyways, might as well just do everything in one go.
Schaweet said:
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Roland Stone said:
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Click to expand...
Click to collapse
Nope, I didn't extract it myself. I'll have to do that to make sure I've got the "real deal".
Thanks!
DB's Nexus 7
Dburgessme2 said:
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Click to expand...
Click to collapse
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Schaweet said:
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Just flash it through recovery I assume?
DB's Nexus 7
Yes
Flashing the system and recovery images is still the most fail safe method. It doesn't erase your settings or data.
Sent from my Dev Edition Moto X
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
awerner68 said:
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
So, fxz the 4.4.2 image for vzw 1060 through rsd lite? But remove "erase data" line from the xml file first. Then, TWRP recovery back (root). That about right?
I think the last thing I used rsd lite for was on old Droid X.
Any quick refresher would be appreciated.
Thanks!
DB's Moto X
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
OK. And now I have to ask... What is HoM? (googled with no good results)
DB's Nexus 7
Dburgessme2 said:
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Click to expand...
Click to collapse
I downloaded the .ZIP file and flashed it with TWRP. Using TWRP to replace itself.
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
bigv5150 said:
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
And, this HoM should work with the Vzw 1060 Dev Ed?
DB's Moto X
I updated to 4.4.2 on att with root but now I want factory reset to make sure its fresh so I can get maximum battery life. Anyway I can do that with going all the way back to stock through rsd? Since the stock recovery is not there from rooting.
Sent from my XT1058 using XDA Premium 4 mobile app
Why can't you factory reset with a custom recovery?
I have a locked bootloader. The stock recovery isn't there because the way I rooted my phone it removed it I believe.
Sent from my XT1058 using XDA Premium 4 mobile app
If I'm not mistaken, by taking the OTA, it flashed the stock recovery, which is why it re-enables write protection.
Why can't I factory reset through the settings then? The phone just reboots on any option I select.
Sent from my XT1058 using XDA Premium 4 mobile app
Well, I must be mistaken lol.
You could fastboot and erase userdata, davlik, and cache I think.
JJHunterx said:
Well, I must be mistaken lol.
You could fastboot and erase userdata, davlik, and cache I think.
Click to expand...
Click to collapse
So you don't have any recovery at all? Have you tried booting into recovery?
adb reboot recovery doesn't bring you to your recovery?
This is the message I get doing that:
Partition (recovery) security version downgraded
Fastboot reason: boot failure
Then I have the option to normal reboot, recovery, and factory, and two other options. Selecting the second or third does nothing and ends up just rebooting the phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Bump
Sent from my XT1058 using XDA Premium 4 mobile app
Same problem here
Hopefully somebody can help. I rooted a while back but didn't use rsdlite because it didn't recognize my phone, couldn't get the drivers installed correctly. So I used the method with mfastboot I believe where I manually flashed all the files and had to change one file to att from Verizon for the radio I think. Its been a while and I don't remember the whole process so hopefully somebody can shine a light on a much simpler method of going back.
Sent from my XT1058 using XDA Premium 4 mobile app
If you rooted via the exploits here on xda (slap my Moto, etc) then it replaced your stock recovery with write protection disabled version of Android. You need to download an sbf and extract the recovery image and flash it via fastboot
-Eclipsed Moto X-
rocketsaucev2 said:
If you rooted via the exploits here on xda (slap my Moto, etc) then it replaced your stock recovery with write protection disabled version of Android. You need to download an sbf and extract the recovery image and flash it via fastboot
-Eclipsed Moto X-
Click to expand...
Click to collapse
Will I be able to do that even if my bootloader is locked? If so, I just find the correct 4.4.2 recovery.img and then flash via fastboot?
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
Will I be able to do that even if my bootloader is locked? If so, I just find the correct 4.4.2 recovery.img and then flash via fastboot?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, you can fastboot commands with a locked bootloader. It shouldn't NEED to be your carriers sbf that you take the recovery from but it wouldn't hurt. If you know how to fastboot, you know to put the recovery image in the same directory as your fastboot
-Eclipsed Moto X-
rocketsaucev2 said:
Yes, you can fastboot commands with a locked bootloader. It shouldn't NEED to be your carriers sbf that you take the recovery from but it wouldn't hurt. If you know how to fastboot, you know to put the recovery image in the same directory as your fastboot
-Eclipsed Moto X-
Click to expand...
Click to collapse
Thank you so much I will try doing that.
Edit: well I downloaded the t mobile sbf and extracted it and took the recovery out since the att sbf is not out. When trying to flash it in fastboot I get a preflash validation error and it doesn't go through. Tried it multiple times.
Sent from my XT1058 using XDA Premium 4 mobile app
Well this is frustrating. Tried using mfastboot command instead of fastboot and still get the preflash validation error.
Edit: I feel like I messed up. After reading up on the internet I think I should have flashed the stock recovery before taking the ota update to 4.4.2 because now I am very limited on what I can do aside from unlocking my bootloader I guess.. if that's even still possible through the guy in China although I would rather prefer not to do that.
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
I updated to 4.4.2 on att with root but now I want factory reset to make sure its fresh so I can get maximum battery life. Anyway I can do that with going all the way back to stock through rsd? Since the stock recovery is not there from rooting.
Click to expand...
Click to collapse
The full SBF for ATT 4.4.2 hasn't leaked yet. When it does it will be put up on -> http://sbf.droid-developers.org/phone.php?device=0
Until then, an alternate way to reboot the phone in bootloader/fastboot mode, and issue the following commands...
mfastboot erase cache
mfastboot erase data
mfastboot reboot
If you are struggling to get into bootloader/fastboot mode... with your phone booted normally, usb debugging enabled, and ADB and its drivers properly installed and added to your PC's path... connect the phone to the PC via USB cable, open a command prompt and issue the following...
adb reboot bootloader
However, the OTA will only install if you have a stock recovery on your phone. The message about "Partition (recovery) security version downgraded" tells me you may have the Stock Recovery from 4.4 or 4.2.2 on your phone, rather than 4.4.2.
Since the ATT 4.4.2 SBF isn't out yet, try downloading the Verizon or T-Mobile 4.4.2 rom from -> http://sbf.droid-developers.org/phone.php?device=0 unzip it... and use fastboot to flash that recovery.img to your phone..
fastboot flash recovery recovery.img
---------- Post added at 06:18 AM ---------- Previous post was at 06:14 AM ----------
dimasp6 said:
Edit: I feel like I messed up. After reading up on the internet I think I should have flashed the stock recovery before taking the ota update to 4.4.2 because now I am very limited on what I can do aside from unlocking my bootloader I guess.. if that's even still possible through the guy in China although I would rather prefer not to do that.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct. If you have a locked bootloader, and took the 4.4.2 update, you might retain root. but you lose the "Write Protection Disable" that MotoWpNoMo gave you.
On 4.4.2, there is no way to disable write protection unless you can unlock your bootloader. If you lose root, on 4.4.2 there is no way to root.
If you flash the 4.4.2 SBF you wont be able to root and disable write protection if you can't unlock your bootloader. And don't try to downgrade to 4.4 or lower.
If you have ATT, the Chinese web site was the only option to unlock your bootloader, however that seems to have ended.
KidJoe said:
The full SBF for ATT 4.4.2 hasn't leaked yet. When it does it will be put up on -> http://sbf.droid-developers.org/phone.php?device=0
Until then, an alternate way to reboot the phone in bootloader/fastboot mode, and issue the following commands...
mfastboot erase cache
mfastboot erase data
mfastboot reboot
If you are struggling to get into bootloader/fastboot mode... with your phone booted normally, usb debugging enabled, and ADB and its drivers properly installed and added to your PC's path... connect the phone to the PC via USB cable, open a command prompt and issue the following...
adb reboot bootloader
However, the OTA will only install if you have a stock recovery on your phone. The message about "Partition (recovery) security version downgraded" tells me you may have the Stock Recovery from 4.4 or 4.2.2 on your phone, rather than 4.4.2.
Since the ATT 4.4.2 SBF isn't out yet, try downloading the Verizon or T-Mobile 4.4.2 rom from -> http://sbf.droid-developers.org/phone.php?device=0 unzip it... and use fastboot to flash that recovery.img to your phone..
fastboot flash recovery recovery.img
---------- Post added at 06:18 AM ---------- Previous post was at 06:14 AM ----------
Correct. If you have a locked bootloader, and took the 4.4.2 update, you might retain root. but you lose the "Write Protection Disable" that MotoWpNoMo gave you.
On 4.4.2, there is no way to disable write protection unless you can unlock your bootloader. If you lose root, on 4.4.2 there is no way to root.
If you flash the 4.4.2 SBF you wont be able to root and disable write protection if you can't unlock your bootloader. And don't try to downgrade to 4.4 or lower.
If you have ATT, the Chinese web site was the only option to unlock your bootloader, however that seems to have ended.
Click to expand...
Click to collapse
Thanks I will try that. Weird thing is I was able to upgrade to 4.4.2 without the stock recovery.
Edit: mfastboot erase cache worked but erase data did not. I got a message saying invalid partition name data, FAILED (remote failure) and then finished with a total time. The problem with simply flashing the stock recovery from a 4.4.2 T-Mobile sbf through fastboot is that I get the security version downgraded message. I'm not sure what else I could try.
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
Thanks I will try that. Weird thing is I was able to upgrade to 4.4.2 without the stock recovery.
Click to expand...
Click to collapse
You had to have some sort of stock recovery on there.. The OTA will only install via stock recovery. If you don't have stock recovery on the phone, you'll get stuck in a boot loop of it trying to install.
Now, its possible to modify the OTA file to install from say TWRP or CWM recoveries, but with a locked bootloader, you can't flash them onto the phone, and you can't flash a modified OTA file..
So that is why I'm thinking you have the stock recovery from an older rom than what is on your phone... especially with the "security version downgraded" message. Its very likely you have mismatched file/partition versions on your phone. If that is the case, its a very dangerous place to be, as doing the wrong thing could cause your phone to brick.
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.