Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
I have an unlocked bootloader.
Can anyone upload to a Dropbox, or somewhere else, just the system partition so I can restore via nandroid on TWRP? Otherwise I am stuck waiting for the SBF, since I can no longer downgrade.
Thanks
Sent from my Moto X using Tapatalk
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att: http://www.androidfilehost.com/?fid=23329332407581236
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
cpetersen2791 said:
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Exactly.
I see it was downloaded 9 times before me. I didn't have any luck with both TWRP and Philz's recovery. Flash stalled on "extracting system files" for 5+ minutes.
I would take the entire TWRP backup if you can upload that.
UPDATE: I deleted the boot.img out of the zip file, and it flashed, then manually flashed boot.img.
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
Ctrl-Freak said:
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Click to expand...
Click to collapse
OMG, I think this file will help me to rescue my brick!!!!!
Can I manually flash this firmware on my device using fastboot tool?I have no idea about what safestrap is,please no hate.
It's still a WIP, after flashing, I didn't have radio. Will work on that tomorrow. If we get it going, I'll post something, with Ctrl-Freak's approval.
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
Exactly.
Click to expand...
Click to collapse
I download your zip and find out this is not a firmware...OTZ
I can only wait until the sbf file released.
cpetersen2791 said:
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
...
It's still a WIP, after flashing, I didn't have radio...
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Safestrap Version
-If you are already on 4.4.2 then boot into Safestrap and factory reset, do not wipe the system then install to the STOCK slot.
-If your not on 4.4.2 then go here and follow the instructions from my stock rom thread http://rootzwiki.com/topic/116025-ro...52-kitkat-442/ I don't feel like reposting them in here.
Click to expand...
Click to collapse
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Ctrl-Freak said:
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Click to expand...
Click to collapse
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
cpetersen2791 said:
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
Click to expand...
Click to collapse
Sorry. I wasn't telling you to get that rom or the Verizon radio, I was pointing out that a factory reset in TWRP may help with the radio issue.
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
Click to expand...
Click to collapse
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Ctrl-Freak said:
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Click to expand...
Click to collapse
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
cpetersen2791 said:
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
Click to expand...
Click to collapse
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Another thought. Maybe I have to flash the radio, even though I haven't changed. Kind of like flashing the boot.img. I haven't changed that either, but it had to be flashed to boot.
Do you know where I can grab the radio IMG? Can't seem to find it around.
I supposed I can pull it from Att 4.4 sbf. Which files tho, just the Non-hlos.bin file? I don't have the xml here @ the office so I don't know what to look for.
Thanks again for your help
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Click to expand...
Click to collapse
Found this...
it's OS 4.4 (140.44.5), will that run into the brick issue?
Related
I have a Verizon moto x unlocked currently running 4.4.2 with twrp installed. If I understand correctly I can't take the OTA because I don't have a stock recovery.
Has anyone uploaded a flashable update yet?
Sent from my XT1060 using Tapatalk
A quick look around the forums would've answered your question.
nhizzat said:
A quick look around the forums would've answered your question.
Click to expand...
Click to collapse
No it didn't but thanks for the help.
Sent from my XT1060 using Tapatalk
If you click yourself on over to the Moto X General forum, you'll see this thread titled "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" which has 10k+ views,163 posts, and is at the very top of the first page right below the stickies. The last reply in that thread was posted tonight at 9:29pm. Between 9pm and the time you posted this thread, there were 8 replies posted so the thread has been at the very top of the General forum.
You've been a member here for nearly 4 years and have made nearly 1k posts in that time, there are no excuses. Could I have been more helpful by answering your question? Of course. However, when the answer to your question can be found that easily, why should I bother? It's obvious you didn't bother to look, because there's no way you could've seen "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" and not click on it.
Asks about updating a Verizon Moto X to 4.4.4, skips the thread which has all of the key words in the title.
nhizzat said:
If you click yourself on over to the Moto X General forum, you'll see this thread titled "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" which has 10k+ views,163 posts, and is at the very top of the first page right below the stickies. The last reply in that thread was posted tonight at 9:29pm. Between 9pm and the time you posted this thread, there were 8 replies posted so the thread has been at the very top of the General forum.
You've been a member here for nearly 4 years and have made nearly 1k posts in that time, there are no excuses. Could I have been more helpful by answering your question? Of course. However, when the answer to your question can be found that easily, why should I bother? It's obvious you didn't bother to look, because there's no way you could've seen "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" and not click on it.
Asks about updating a Verizon Moto X to 4.4.4, skips the thread which has all of the key words in the title.
Click to expand...
Click to collapse
And then you waste all that time typing that out, instead of just linking him to what he needs to find? I hate responses like yours. Instead of "did you do a search" why not just not reply at all? Lame.
This is the post with all the info: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
I am in the same boat as OP. I first flashed to stock 4.4.2, but I don't think you need to with the FXZ from that thread.
dhoppy said:
I am in the same boat as OP. I first flashed to stock 4.4.2, but I don't think you need to with the FXZ from that thread.
Click to expand...
Click to collapse
You are correct. With this FXZ, one can flash from *any* version straight to 4.4.4, unlike OTA's which are "incremental" in nature.
No need to flash stock recovery, either. :good:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
T-Keith said:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
RSD Flasher is a java program, should run anywhere, but I don't know about RSD Lite.
I extracted the FXZ file, and then flashed it manually because RSD Lite won't run on USB 3.0, but fastboot will. I don't know if it is supposed to work that way, but seems to be working for me. I'm in the process of rooting right now.
T-Keith said:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
dhoppy said:
RSD Flasher is a java program, should run anywhere, but I don't know about RSD Lite.
I extracted the FXZ file, and then flashed it manually because RSD Lite won't run on USB 3.0, but fastboot will. I don't know if it is supposed to work that way, but seems to be working for me. I'm in the process of rooting right now.
Click to expand...
Click to collapse
I can help you with this....
First, @T-Keith , I came across your post after @dhoppy had just answered your question, pointing you to the fxz thread.
Second, T-Keith, you can absolutely flash this in Linux OR Mac (let me know which you are running, and I'll help with both the tools and commands necessary).
It will take only a couple minutes to complete and your data will be left intact.
Linux
Sent from my Nexus 7 using Tapatalk
T-Keith said:
I have a Verizon moto x unlocked currently running 4.4.2 with twrp installed. If I understand correctly I can't take the OTA because I don't have a stock recovery.
Has anyone uploaded a flashable update yet?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
KidJoe said:
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
Click to expand...
Click to collapse
The new Leaked FXZ is a "KEEP DATA" FXZ - Moto Made it this way (thanks Moto!!). Unless someone explicitly runs "fastboot erase userdata" or uses a different tool to erase userdata, it's just as good (BETTER) than taking the OTA. :good:
T-Keith said:
Linux
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
OK, have you managed to do it already? My response was from last night, so if you have already managed to flash it, I don't want to go finding the tools and spend a few minutes writing up a guide for you. Confirm (quickly) if you still need it, and I'll write it right up for you, if so.
KidJoe said:
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
Click to expand...
Click to collapse
Yeah I have xposed installed, and twrp. So that might be a good option. Is there anyway to test that? It looks like rsdlite and mfastboot are Windows tools, can I just use adb fastboot?
Sent from my XT1060 using Tapatalk
T-Keith said:
Yeah I have xposed installed, and twrp. So that might be a good option. Is there anyway to test that? It looks like rsdlite and mfastboot are Windows tools, can I just use adb fastboot?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
...He's offline. Do you want me to help you? I HAVE all the linux tools, and know how to do this. KidJoe only uses Windows...
EDIT: @T-Keith : Well....here's the info anyways. Use it if you want..
1. Download the FULL FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
2. Extract it
3. Download the attachment that I was so kind as to attach here for you (you MUST use this variant of fastboot - for Linux) Extract THIS fastboot to same folder as the FXZ files (possibly need to change permissions +x)
4. Boot phone into bootloader mode (AP Fastboot Mode): Unplug phone, power off. Hold Down VOL DOWN + POWER
5. Execute the following commands IN ORDER:
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
fastboot 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 customize
fastboot erase clogo
fastboot reboot
DONE! And your data should still be intact....if you would PREFER to wipe your data, add the following command BEFORE "fastboot reboot"
fastboot erase userdata
Thanks. Does this method work with twrp then?
Sent from my XT1060 using Tapatalk
T-Keith said:
Thanks. Does this method work with twrp then?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Definitely! (so long as you are UNLOCKED)
AFTER you complete EVERTHING in my instructions...and you boot into android successfully...and confirm everything works:
Just reboot BACK into the BL, and
fastboot flash recovery twrpfilename.img
(get the latest version here: http://techerrata.com/browse/twrp2/ghost )
then immediately afterwards, type:
fastboot reboot-bootloader
then VOL DOWN to RECOVERY, and VOL UP to select it. (you HAVE do this immediately after flashing TWRP or it won't stick and will revert back to stock recovery...for unknown reasons. As long as you boot into TWRP IMMEDIATELY after flashing it, it sticks forever...)
When you go to exit TWRP, it will ask you if you would like to install SuperSU installer. Tell it YES! Then once rebooted, you will have an icon for SuperSU Installer. Click it, and select "PLAY STORE" method. Done. Rooted. 4.4.4
Any idea if this will work with an encrypted phone? I believe the data partition is the only one encrypted. Mine is throwing an error trying to install the OTA. This looks like a promising second option.
PhilD41 said:
Any idea if this will work with an encrypted phone? I believe the data partition is the only one encrypted. Mine is throwing an error trying to install the OTA. This looks like a promising second option.
Click to expand...
Click to collapse
When installing the OTA via stock recovery (i.e. have OTA.zip on the /SDCard, boot to stock recovery, select install update and pick the OTA.zip) it will tell you exactly why the install is failing.
With the phone being encrypted, I would only consider doing the OTA. Doing an FXZ will over write the system and other partitions, any phone encryption settings will likely be lost.
If you do try FXZ, please copy your data to your PC FIRST!!!! just in case!!
samwathegreat said:
...He's offline. Do you want me to help you? I HAVE all the linux tools, and know how to do this. KidJoe only uses Windows...
DONE! And your data should still be intact....if you would PREFER to wipe your data, add the following command BEFORE "fastboot reboot"
fastboot erase userdata
Click to expand...
Click to collapse
Thanks samwathegreat!!! That worked like a champ. Flashed the set, flashed TWRP, rooted, installed xposed and updated my build.prop. Data and encryption untouched and working as expected. Thanks again for the assistance!!!
PhilD41 said:
Thanks samwathegreat!!! That worked like a champ. Flashed the set, flashed TWRP, rooted, installed xposed and updated my build.prop. Data and encryption untouched and working as expected. Thanks again for the assistance!!!
Click to expand...
Click to collapse
Thanks for the update. I'm very glad it all worked out
TO ANYONE ELSE WHO COMES ACROSS THIS THREAD:
The VZW 4.4.4 FXZ is ****NO LONGER**** A "keep data" FXZ. If you download the FXZ now, you will need to modify the XML file and remove the line containing "erase userdata" if you want to prevent all of your data from being erased.
Just to clear it up: The original leaked FXZ was indeed a keep-data FXZ and did not have the lines for erasing userdata.
NOW that the new official FXZ has leaked, it DOES contain the erase userdata command.
Other than the slightly modified XML (used for flashing), ***ALL OF THE PARTITIONS ARE EXACTLY THE SAME***
So anyone who used the "old" FXZ - Don't worry! You are NOT using a outdated version, and you don't need to flash the new one. They are 100% identical aside from the additional command to erase userdata.
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
rootSU said:
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
Click to expand...
Click to collapse
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
HyperM3 said:
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
Click to expand...
Click to collapse
If you download the image from google there is a zip drive with the files you are looking for inside of them. You can fastboot them individually.
Or you could just flash one of the many roms on here that are using the newer 5.0.2
xxfwmxx said:
Or you could just flash one of the many roms on here that are using the newer 5.0.2
Click to expand...
Click to collapse
That's the thing, I was trying to keep it relatively stock for a while. I don't see any reliable roms out there yet.
Give Sinless rom a try. There is a thread on here for it. It is based off of the office 5.0.1 image and not aosp. Great speed and features and decrypted
HyperM3 said:
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
t2noob said:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
Click to expand...
Click to collapse
Great, thanks for that!
5.02 is out?
cobyman7035 said:
5.02 is out?
Click to expand...
Click to collapse
Only aosp
I made a thread outlining how to update to 5.0.1 after rooting/unlocking yesterday after noticing the same problem:
http://forum.xda-developers.com/nexus-6/help/how-to-flash-ota-updates-rooted-custom-t2996149
Should help
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests
I tried flashing CM13 and messed it up. I decided to go to twrp and wipe everything(which wiped my zips).
I just need stock files to reflash from the beginning, but everything I find is missing something.
I'm trying to fastboot flash it. Can someone send me the link so I can stop wasting my data downloading other missing files?
I would really like to go back to 5.1, so I can flash CM from there, but I'll take 4.4.4 stock if that's all you have.
adb keeps giving me an error
ibphantom said:
I tried flashing CM13 and messed it up. I decided to go to twrp and wipe everything(which wiped my zips).
I just need stock files to reflash from the beginning, but everything I find is missing something.
I'm trying to fastboot flash it. Can someone send me the link so I can stop wasting my data downloading other missing files?
I would really like to go back to 5.1, so I can flash CM from there, but I'll take 4.4.4 stock if that's all you have.
adb keeps giving me an error
Click to expand...
Click to collapse
There are many many firmwares for the phone, but I can't post a link till I know which one you need.
What model is your phone? xt1092, xt1093, xt1094, xt1095, xt1096, or xt1097?
Also helpful would be your carrier and country.
With this info I can post the correct link.
Sent from my XT1095 using Tapatalk
XT1095
ibphantom said:
XT1095
Click to expand...
Click to collapse
http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip
Sent from my XT1095 using Tapatalk
I need the stock recovery image (from 23.16.3.victara_retca.retca.en.CA) so I can flash the 6.0 update since it won't work with TWRP.
Any help? Google isn't providing me with much.
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
I have no clue. I doubt it would have to be the retCA version. I'm sure everything besides radio and system will be the same.
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
Gus.Ottawa said:
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Thank you both! I'll play around with these files and make it work
DonDizzurp said:
Thank you both! I'll play around with these files and make it work
Click to expand...
Click to collapse
Any update on whether this worked for you? I'm in the same boat
jullyfush said:
Any update on whether this worked for you? I'm in the same boat
Click to expand...
Click to collapse
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
DonDizzurp said:
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
Click to expand...
Click to collapse
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
jullyfush said:
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
Click to expand...
Click to collapse
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
DonDizzurp said:
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Click to expand...
Click to collapse
Something odd has happened since upgrading to 6.0.
'adb devices' still sees my phone, but 'fastboot devices' no longer sees anything, and making a desktop back-up with adb now creates a file containing 0 bytes.
Everything else seems fine. Are there some new permissions I need to give before this will work?
Thanks again.
Edit: I managed to get fastboot working, however now I've run into a new problem.
To confirm, when you say flash the cracked boot.img for Marshmallow, I should execute 'fastboot flash boot boot.img' for the cracked boot.img?
I'm getting the error: mismatched partition size (boot)
I can still enter TWRP with fastboot, but it's not permanent without the cracked boot.img
Am I missing a step?
Edit #2: Finally got TWRP to stick another way and have root now. Thanks for everything!