How to update from Android 5.1.1 to Android 6.0 without losing root and data - Nexus 6 Q&A, Help & Troubleshooting

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

Related

[Q] Nandroid of 4.4.2 wanted

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?

[HELP] Can not write any custom roms.

I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.

[RESTORE] Factory Restore 24A zip

Here's a fast way to do a full factory restore so you can take an ota without erasing your internal storage.
This will not however remove the rooted message for a warrant claim.
Check MD5's before flashing.
Step 1: Flash Flash KK24a System Restore 1st.
Step 2: Flash KK24a Bootstack Restore 2nd.
Warning: You will loose your custom recovery after reboot.
Download: KK24A System Restore
https://mega.co.nz/#!kEljCSTY!qPS7oSXokZRg3j60FNzgmeA7sbpda8IMB-4uFTJuMxI
MD5: d3926bcb4b2938e33020c1e8b540414b
Download: KK24A Bootstack Restore
https://mega.co.nz/#!0E00kb6K!wH1bJHbFuqTQpZo2QKLeBrpf21slTgnOSMstivVS7Qs
MD5: dce61ff31f060164bb89962ffe8a1b8c
Reserved....
Can't do 27a restore as System.img is too big for a zip to be flashed. Its over 2.2gb. Needs to be under 2.1gb for custom recovery to flash it. I can't get it compressed under 2.1gb.
This is cool thanks!
Way cool !! Thanks!
Can i use this to upgrade from 4.2.2 ?
berz said:
Can i use this to upgrade from 4.2.2 ?
Click to expand...
Click to collapse
Yes.....
@MicroMod777, just to make sure before I proceed, I lose my custom recovery (in op), but I'm assuming I maintain root? I've read from others root is kept through 27a, and that Freedom Tools also restores recovery. Am I correct on all? Thank you!
njstein said:
@MicroMod777, just to make sure before I proceed, I lose my custom recovery (in op), but I'm assuming I maintain root? I've read from others root is kept through 27a, and that Freedom Tools also restores recovery. Am I correct on all? Thank you!
Click to expand...
Click to collapse
You'll loose root, but root detection is still there. You can use my freedom tools to get custom recovery on 27a.
You'll loose root, but root detection is still there. You can use my freedom tools to get custom recovery on 27a
Click to expand...
Click to collapse
Excellent, thank @MicroMod777. One more question; after I flash this, I'm unrooted, no custom recovery. If I root the 24a using ioroot25 (but not a custom recovery), will the root maintain through the updates to 27A? I recall reading somewhere on here that it did. Thanks for your work!!
njstein said:
Excellent, thank @MicroMod777. One more question; after I flash this, I'm unrooted, no custom recovery. If I root the 24a using ioroot25 (but not a custom recovery), will the root maintain through the updates to 27A? I recall reading somewhere on here that it did. Thanks for your work!!
Click to expand...
Click to collapse
Not really sure, but you can always use Stump Root on 27A. Can take up to 10 minutes for it to root through brute force:
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
I am pretty sure root maintains with the OTA 27A.
Awesome. This is great for when I gotta go to stock real quick for some fix or something and will real helpful once lollipop is out
Sent from my VS980 4G
hi... noob question... sry... how can I install this zip... on my custom recovery?!? ... thanks for any answer
kuribox said:
hi... noob question... sry... how can I install this zip... on my custom recovery?!? ... thanks for any answer
Click to expand...
Click to collapse
noob answer.... Read the Original Post other wise known as the OP.
And if that doesnt work then read it 15 times more... [emoji41]
Sent from my VS980 4G
Can i use this to downgrade from lollipop ?
hoangan12 said:
Can i use this to downgrade from lollipop ?
Click to expand...
Click to collapse
Yes, but why?
MicroMod777 said:
Yes, but why?
Click to expand...
Click to collapse
my phone has problems with touch. very difficult to turn the power button, many touch up
to turn on the screen. flash kdz and tot file failed >"<
MicroMod777 said:
Reserved....
Can't do 27a restore as System.img is too big for a zip to be flashed. Its over 2.2gb. Needs to be under 2.1gb for custom recovery to flash it. I can't get it compressed under 2.1gb.
Click to expand...
Click to collapse
Looks like they may have patched that in twrp recently.
https://github.com/omnirom/android_bootable_recovery/commit/78ab0c5807c17e343cc4fa9af86ea2d787e0e047
Though this could also just be for backups over 2gb... But they split those anyway.
Yoinx said:
Looks like they may have patched that in twrp recently.
https://github.com/omnirom/android_bootable_recovery/commit/78ab0c5807c17e343cc4fa9af86ea2d787e0e047
Though this could also just be for backups over 2gb... But they split those anyway.
Click to expand...
Click to collapse
Now using zerofree in linux to fix that problem.
MicroMod777 said:
Now using zerofree in linux to fix that problem.
Click to expand...
Click to collapse
I haven't had to use it on my LP system images. I used 7zip to compress one with zerofree, the other without zerofree, and the difference was around 8MB. I'm assuming LG didn't add too much junk info. this time around.

Looking for stock recovery to flash OTA

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!

flash stock. via twrp?

Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
mrkhigh said:
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Pkt_Lnt said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
mrkhigh said:
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
Click to expand...
Click to collapse
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Pkt_Lnt said:
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Click to expand...
Click to collapse
That's what I thought.
Thanks for the links,
But I'm still looking for TWRP flashable if anyone knows of one?
This should be a relatively easy thing so I'm surprised it doesn't exist
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
leo5111 said:
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
Click to expand...
Click to collapse
TWRP can flash a stock image if someone creates it. Unless there is something odd about the nexus, but I doubt that. The only thing that shouldn't be flashed stock would be recovery.
I don't think I need to use some toolkit... adb and fastboot commands are simple enough.
I was hoping to avoid needing a PC at another persons house, I mean that is kinda the point of twrp.
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
If I owned the device I would make it for you guys. It seems something that is lacking that is really handy.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Google has done that for you already. Just unpack the archive you choose and the four images are in there.
https://developers.google.com/android/images
I thought we've already decided I cannot flash these images with TWRP....
mrkhigh said:
I thought we've already decided I cannot flash these images with TWRP....
Click to expand...
Click to collapse
http://www.droidviews.com/now-flash-image-files-using-twrp-2-8-4-0/
Different Google search gave this. I can find nothing else on TWRP site or G+
Appears you can also use FlashFire.
Thanks for the help.
OP could flash one of the stock lite ROMs in the development forum and get the TWRP-flashable stock ROM he's looking for. Danvdh and tupac4u both offer one that is nothing more a debloated stock ROM.
TWRP is able to flash system images from 3.0.2 and on. Just unpack the archive and select install img. Remember to flash stock kernel and newest radio and bootloader too (bare in mind that flashable bootloader is harder to find. You might have to find older one and update the files inside on your own). Afterwards flash stock recovery and lock bootloader with a zip. Now you can just reboot it. It's not that hard.
Lawstorant said:
....bare in mind that flashable bootloader is harder to find....
Click to expand...
Click to collapse
For Nexus 6 https://forum.xda-developers.com/showthread.php?p=59728002/
Thank you.
I went ahead and simply flashed him 100% stock via flash and fastboot.
This is probably resolved now, just adding info though. I had flashed stock 7.1.1 zip downloaded from google via twrp 3.0.3.0. It removed twrp itself too and I was back on stock.
mrkhigh said:
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Click to expand...
Click to collapse
Try the app FlashFire.

Categories

Resources