Hi I have a few questions for my nexus 6 that I am getting today
1) I am going to flash a the new marshmallow update, which one should I pick because for root you need a specific build but on the google factory images the latest build is not supported? I really don't know.
2) After I flash 6.0 can I just do the fastboot flash recovery twrp.img without flashing the boot.img
3) When I go to a new rom like Chroma by Zephik do I still need to change the boot.img to flash the beta super user
For now these are all my questions and I would really appreciate if you could answer it.
side note: I cannot use NRT becuase I am on a mac, if you guys have any alternatives I would really appreciate it too.
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
cupfulloflol said:
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
Click to expand...
Click to collapse
Thanks so much, I actually used adb/fastboot when I was rooting my mytouch 4g so this knowledge should come in handy, one other question if I were to root the latest factory image can I use the MRA58K.img that Chainfire posted for 6.0 or do I have to find a modified boot img that matches the latest factory image which is MRA58R, thank you so much again
Related
Got my phone (AT&T Captivate, firmware 2.1-update1 version JH7, kernel 2.6.29, build eclair.UCJH7) on december 28 from a AT&T store (it even came with a pic taken december 20 ) and I've already been able to boot into download mode (power off, hold volume keys then plug usb) and into that menu used to install packages (power off, hold volume keys then power on). Guess my hardware and firmware are ok, so I may be able to recover my phone by myself in case things go south.
I've been doing my homework lately (been reading stickys, tutorials and faqs for 10 days) but I'm still confused about some procedures. I'm not going to list everything I've read here, but I would like someone to correct me if I've learnt wrong. I don't really need the easiest methods, I want to understand the options available and to choose the best ones (aka the hardest path).
First of all, it seems I need to root my phone in order to be able to create backups, carrier-unlock it and flash custom roms. But it doesn't make much sense to me, since rooting it seem to be enough to prevent it from receiving FOTA updates - and I want to make the most comprehensive backup possible, in such a way I could restore my phone to 'factory condition' if needed.
Second, I realize there are many ways, programs and guides to root the phone - the most famous ones, One-Click root/unroot and z4root, seem to be listed in the wiki (http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897), but there is also CLShortFuse's One-Click Root and Allow Non-Market Apps, which sounds interesting but I don't know if it is undo-able. So there are different ways to root the phone, but there is little to none information on what's the difference between these methods, which is 'better' and what difference does it make if I root it permanently or by some reversible method. Does it affect performance? How each of them work? I have no clue.
The mess gets even greater when it comes to creating backups. People mention different programs to make these backups (clockwork recovery, titanium backup) but I don't understand if they back up different parts of the phone. Some even seem to change the bootloader of the phone - shouldn't it be backed up prior to any modification? Do I flash these backups using Odin? Which programs should I use to have a full backup? Is there anything left I should back up manually?
I'll quit talking for now because I've already written a lot and I still have many questions; if I write all of them at once, no one will ever have the patience to read them.
Erk, a long post deserves a long answer
So first off, il tell you about recovering your phone. Since you just got it, you can go back to the store and play dumb to get a new one in case anything goes wrong. You can also use the 3 button combos to get into download mode and use odins back to stock to get back to your original 2.1 eclair firmware . To do that you would need to get into download mode. Now there are a couple ways to do this, and i can only explain two since ive actually used two. (Well 3 actually, but il get to the third after these 2)
The first method is using the 3 button combo which you should already know. The second method is using adb commands such as (adb shell, adb reboot download, adb reboot recovery, adb devices). The third way is building a jig. Thats basically connecting 301k 1/4 watt worth of resistors together and placing them on pin 4 and 5 on your micro usb slot. You can read more about that on the tutorial on how to build a jig for your phone.
To restore to your factory setting, odin's one click back to stock thing should do the job. It simple installs the stock 2.1 eclair all over again (without the root).
To root your phone, any method from the wiki should work. None of them are really "better" :S, they all do the same job and give you super user permissions. None of them root your permanently since you can always go back to stock using Odin's... It does not really affect performance, not to any extent i have noticed :S, and unfortunately, i dont really know how it works.
As for creating backups, Titanium Backup is the best solution. Whether you have the few extra bucks to spend for the premium one or simply want to use the free one, its one of the best tools out there. I personally use it and its one of the best. It backs up all the data (except for my text messages). It creates a folder on your internal memory which you can just copy to your desktop. When the time comes that you need to restore your backup, just copy the folder back into your internal memory, load up titanium backup. Restore it and voila .
I think ive answered everything, if ive missed anything, let me know
Edit : Forgot to mention this . If your truly interested in customization. Custom roms are the best there is a howto in the themes and apps section on how to install it. It comes pre-rooted (if that is the word to use :S) and theyre much better than the stock firmware. Im currently using serendipity v3.0 (flashed it yesterday)
supaphreek, guess I'll have to thank you twice: once for reading my enormous post, and again for you supacompleteanswer.
I'm being paranoid with recovery because I actually bought the phone in the US then came back to my country (Brazil), so I'm a few thousand miles away from the simple lets-return-this-thing solution.
From everything I've read, I believe the most instructive were the wiki at http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897 , the FAQ at http://forum.xda-developers.com/showthread.php?t=858765 , the PDF guide from user nbs11 at http://forum.xda-developers.com/showthread.php?t=761819 and the wiki at http://www.capfaq.com/w/FAQ. These contain most of the info a newbie user would ever need and I'd definitely recommend them to any newbie user who happen to be reading this. And for everyone afraid of bricking, it's a tremendous relief to know pretty much any mess you do can be reverted using download mode and Odin, so the first thing to test is if you can get into download mode using one of the ways described by our buddy supaphreek.
On the rooting matter, I found no discussion at all about which is better, so they should be pretty similar (though I have no idea which is the oldest version, I'd assume the recent ones might be a little improved). There is some discussion on what's the better lagfix and many of the cooked ROMs already come with some lagfix installed, but this is another story...
Once I get my phone rooted, it seems to be trivial to carrier-unlock it. There's even an app on android market for this, so I won't even need sideloading. Since all this procedure does is just give me a number, there's hardly any difference among all the unlocking procedures out there.
For the backup, I'll still do it using both titanium and clockwork, as suggested by nbs11 on the pdf I've linked on this post. Better safe than sorry, right?
And yes, I'm truly interested in customization and I'll go deep down that path, I'm just packing up my head with some knowledge to avoid being desperate if things eventually go fubar.
As a last question, is there somewhere I can get 1-click Odin with my exact firmware version? (2.1-update1, I897UCJH7, Kernel 2.6.29 [email protected] #2, build eclair.ucjh7) And how important is it to get the exact same firmware?
As I've done my research, I found 1-click odin with JF6 here: http://forum.xda-developers.com/showthread.php?t=731989
I've also found the 'standalone' I897UCJH7 on this topic (where this guy even flashed succesfully his phone using old JH2 firmware without problems, so finding the exact firmware version might not be the greatest issue): http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but this process is a bit more complicated and uses regular Odin and clockwork recovery. Nonetheless, from what I've understood, I can still use any old version of odin to flash JF6 then use my own clockwork backup, right?
Hmm, unfortunately, im not sure if there is a specific Odin for that firmware :S. However what you can do is use one that reverts you to any stock version, and then flash the version you want through clockwork mod
I'll do that. Thanks again!
Also if you one click to stock, you can OTA update to the most recent firnware. I suggest titanium premium if you are going to flash a lot of custom roms, it is a lot faster to restore and also syncs with dropbox
Sent from my SAMSUNG-SGH-I897 using XDA App
Be careful trying to flash with odin. Some newer builds get instabrick flashing back to jf6 and must go with jh2 or newer.
So, you may want to invest a few bucks in a jig setup before blindly using odin.
Thanks for the tip, sixstringsg.
Newter55, as my phone is brand new I believe I may have one of these insta-brickable devices. If I happen to try flashing it with a recent rom, does it get recoverably bricked (fixed by flashing an older rom), or I'm left with a $500 paperweight?
You just need to use the correct firmware version of odin if you manage to get in trouble. Many people flash rom over rom, including myself, but it is highly likely that at some point you will need odin if you are flashing roms so it is best to ensure that you have that set up first. Look for the odin thread by c3popl (sp?) in development forum and you should find what you need. Read through that and look for others with your base firmware. Or look through q&a at the "help I bricked" threads . On my phone and posting links is a pita or I would make it easy for you.
If your phone came with JH7, follow this guide:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If you use one of the Odin one-clicks and brick your phone, you'll need a USB jig to recover.
You guys are awesome. Thank you newter55 and GGXtreme for this info! I hope I'll never need it, but I'll buy a cable and make a jig.
The news: I've rooted my phone using One Click Root / Unroot by TGA_Gunnman (for the record: it worked with my JH7 Captivate bought in 28 dec). Once I booted windows, installed dotnet framework 4 and the samsung drivers (easy too, but a pita), rooting was easy and failproof. However, someone using linux might find it easier to just download 1-click root, find the root.zip file in there, rename it as update.zip, put the zip in the internal sdcard, boot the phone holding the volume buttons and then 'install packages'. This way there will be no need to fight Wine nor install anything nor look for a windows computer with admin privileges.
Also unlocked my phone using SGS Unlock Tool, available in the Android Market. The unrooted option won't work, but once rooted it worked like a champ. Next step: I'll do the backups, and then... start messing up my new toy!
Hey all so I currently have an unlocked bootloader, rooted Nexus One still running the Stock Froyo 2.2.2. and I decided to finally upgrade to the OTA Gingerbread update but have a problem.
The OTA update restarts my phone with a triangle with an "!" inside it and an Android next to it, so I decided to try a manual update as described here.
Everything went well until the installation itself, during the install I kept getting some sort of error stating Twitter.apk in the system directory could not be authenticated.
So here's the problem, with Titanium Backup I made the stupid mistake of uninstalling it and not backing it up when I first rooted a while ago. I thought I could just reinstall it from the market but I get the same error. The only solution I can think of is if someone running a Nexus One Stock Froyo could possibly send me the Titanium Backup files of Twitter, hopefully this would make it work, otherwise I don't think I could ever update.
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Thanks for the response, but I'm having trouble figuring some of this stuff, after spending some time with the search option here in XDA:
1. I don't the difference between custom recovery and flashing an image.
2. I can't find a simple stock Gingerbread image (thought its called ROM?) Details in posts tend to be vague for people that are learning this stuff, like me.
3. Many people have written to use Amron_ra 2.2.1 but I don't know the specifics of each ROM are (ex. if its Froyo based, Gingerbread based, etc.)
4. Would using ROM Manager be a good method to use any ROM or is it limited?
I'm essentially looking for an effective method to upgrading to a clean Gingerbread, since doing it the normal way won't work on my phone (as stated in my first post).
1 - Recovery, bootloader, and 'ROM' are two different partitions on you phone. Once you break security on one, you can use it to break the security on the other. In your case, the security on your bootloader is broken (unlocked), so you can use it to install new software on the other partitions.
2 - See bullet 4 on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1005591
3 - For recovery you have 2 choices, Amon Ra or Clockwork, If you go with Clockwork, I recommend you stay away from 3.x versions. Unless the ROM you want to install says otherwise, either of these recoveries will work.
4 - ROM Manger will work. It's an easy way to achieve results, but unless you know what you are doing, it's also an easy way to screw things up.
I suggest you take it a step at at a time, and really understand what you are doing. Reading the wiki is always a good start, then ask specific questions...
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
Thanks Danger, I made the jump to Cyanogen 7, RC-4 via ROM Manager and couldn't be happier! Only problem is the known audio bug for Nexus One (person on other end of a call hears a lot of static sometimes, and have to recall them). The forced apps2sd is by far my most favourite feature, especially since the N1 internal space is pretty horrible, I've moved most of my apps2sd and haven't had any problems thus far.
Thanks for recommending CM7, I just wish their website listed the full features for newbies like me.
Thanks danger-rat http://www.nexusoneforum.net/forum/...lick-doesnt-work-gingerbread-2.html#post93952
I downgraded my gingerbread to froyo
Was pulling my hair out with a lame guide in the general section
Congrats!!
Sent from my Nexus One using XDA Premium App
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.
If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.
Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app
So I have an older version of Viper ROM on 4.4.2, and I want to latest version of Viper ROM. From my understanding, it works better when you have 4.4.3, so I need to upgrade to that first. So, what do I need to do? Revert to stock, update OTA, and then re-root, get TWRP again, and then reflash to the new version of Viper ROM? I really hope that's wrong, but I don't even care what I have to do if I can just get a clear understanding of what it is I need to do.
I'm pretty annoyed that Viper ROM offers no support when it comes to updating, but when you search elsewhere on xda for this information it's very hard to find. I've installed custom firmware on phones about 5 times in the past 5 or so years, and I've never come close to having such a hard time at finding basic instructions. Every time aside from the first I haven't been able to fully remember the process, but had no issues like I'm having now when it comes to finding guides.
jaluke said:
So I have an older version of Viper ROM on 4.4.2, and I want to latest version of Viper ROM. From my understanding, it works better when you have 4.4.3, so I need to upgrade to that first. So, what do I need to do? Revert to stock, update OTA, and then re-root, get TWRP again, and then reflash to the new version of Viper ROM? I really hope that's wrong, but I don't even care what I have to do if I can just get a clear understanding of what it is I need to do.
I'm pretty annoyed that Viper ROM offers no support when it comes to updating, but when you search elsewhere on xda for this information it's very hard to find. I've installed custom firmware on phones about 5 times in the past 5 or so years, and I've never come close to having such a hard time at finding basic instructions. Every time aside from the first I haven't been able to fully remember the process, but had no issues like I'm having now when it comes to finding guides.
Click to expand...
Click to collapse
if you are s-off it's pretty easy: http://forum.xda-developers.com/showthread.php?t=2365506 (in the firmware section), and note that the "fastboot flash zip <firmware>.zip" has to be done twice!!
Is "Copy partitions zip" still needed when prepping for roms with official firmware?
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
we still need it. which video doesn't have this step? pretty sure i did mention it in all the videos. if i did not , then my bad.
Hey man thanks so much for replying! I haven't actually seen it in any of the videos - unless I'm missing something incredibly obvious.
(for context - my ultimate goal is to flash LineageOS 15.1 and get root passing SafetyNet to the point where GPay works)
I started here to get the basics:
https://www.youtube.com/watch?v=bkmczD9tvEQ
This video starts right with flashing the stock firmware:
https://www.youtube.com/watch?v=2-Kcwjyk_Ls
This video I didn't understand at first, but eventually got that you're just explaining A/B slots, not necessarily giving a tutorial:
https://www.youtube.com/watch?v=zVwYxp30dps&t=119s
None of these have that specific zip being flashed.
So if I understand correctly the correct process after buying the phone would be...
1) Unlock bootloader
2) push needed zips to phone storage
3) fastboot into TWRP
4) flash copy-partitions-payton.zip
5) reboot into recovery
6) flash stock firmware (I'll be using PAYTON_FI_8.1.0_OPWS28.46-21-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
6) ...and basically follow the rest of your video to a T from there.
Hey I was wrong sorry - it's totally in the Android P video. So that was super helpful... and I just finished flashing everything successfully! I did not seem to have to flash the stock firmware at all - I simply flashed copy-partitions-payton.zip, did a factory reset, and moved right on to flashing LineageOS.
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
This is also missing from the official Lineage documentation, fyi:
https://wiki.lineageos.org/devices/payton/install
Thanks for your videos, they've been super helpful and so far no problems with my flash.
amirite said:
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
Click to expand...
Click to collapse
What do you mean by flashing a copy of stock firmware? Where is it asking you to flash stock firmware, the guide assumes you are on stock firmware. Also, if you have LOS already running dont bother about it too much. The original instructions explaining all this were in the LOS thread I created, which was transferred to Erfan once LOS was official. Now, the original instructions are no longer there. So, just forget about them and enjoy your custom rom :highfive:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
amirite said:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
Click to expand...
Click to collapse
What I understand is that Moto does not flash both slots by default, but flashing the flash-all does both slots with the stock firmware. If you are on the default stock setup, copy-partions will just copy your the Moto default to the other slot.
Got it. So basically the main goal with that first step is simply to populate the B slot which can be achieved by either method. Thanks guys, I just wanted to make sure I understood the full scope of what had to be done. Always an adventure catching up to the many months of hard work y'all do to get us here. Much appreciated and I'm enjoying my new setup a bunch!
amirite said:
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
Click to expand...
Click to collapse
Well, I did not need it. I just went from stock android 9 to LineageOS 16.