So i m one of the ones that used the root for 4.4.4 on at&t. It worked but write protection is still on so you have to flash the system.IMG with it already added for apps that require to write to it. So how can I make one of these?
bobglaus said:
So i m one of the ones that used the root for 4.4.4 on at&t. It worked but write protection is still on so you have to flash the system.IMG with it already added for apps that require to write to it. So how can I make one of these?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595
JulesJam said:
http://forum.xda-developers.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595
Click to expand...
Click to collapse
Didn't you want help with the mofo root for these devices? I can help to also thanks. I'll look into it later
bobglaus said:
Didn't you want help with the mofo root for these devices? I can help to also thanks. I'll look into it later
Click to expand...
Click to collapse
My MX13 XT1060's are both unlocked - 1 is a dev ed the other I bought a code for. I was offering to help those with locked XT1060's if they wanted MoFo but no one seems interested. I will see if I can make a pre-rooted image if someone is interested in MoFo for the XT1060 but if no one is interested, I won't waste my time.
JulesJam said:
My MX13 XT1060's are both unlocked - 1 is a dev ed the other I bought a code for. I was offering to help those with locked XT1060's if they wanted MoFo but no one seems interested. I will see if I can make a pre-rooted image if someone is interested in MoFo for the XT1060 but if no one is interested, I won't waste my time.
Click to expand...
Click to collapse
I have the at&t version so I guess I can't really help but maybe you can help me get busybox baked in since you've done it before. Is it the same process as making a mofo root one? Ive never used mofo
bobglaus said:
I have the at&t version so I guess I can't really help but maybe you can help me get busybox baked in since you've done it before.
Click to expand...
Click to collapse
I haven't done it before - another poster did it. I don't have the linux knowledge to do it.
Do you have any friends who have the Moto X GSM Dev Ed? If so, I could tell you what to have them do. They would have to make a nandroid of their system first, then factory reset, then root, set up their system with all of the apps you want on your device and then pull the ext4 image from their device through ADB. Then it should be flashable by MoFo. They could then restore their system using their nandroid backup.
Oh I see. Couldn't I just take one of mine?
JulesJam said:
I haven't done it before - another poster did it. I don't have the linux knowledge to do it.
Do you have any friends who have the Moto X GSM Dev Ed? If so, I could tell you what to have them do. They would have to make a nandroid of their system first, then factory reset, then root, set up their system with all of the apps you want on your device and then pull the ext4 image from their device through ADB. Then it should be flashable by MoFo. They could then restore their system using their nandroid backup.
Click to expand...
Click to collapse
Oh I see. Couldn't I take one of mine?
bobglaus said:
Oh I see. Couldn't I take one of mine?
Click to expand...
Click to collapse
Take what of yours?
bobglaus said:
Oh I see. Couldn't I take one of mine?
Click to expand...
Click to collapse
A nandroid and pull the ext4? That's the part I can't figure out. How do I get the ext4
bobglaus said:
A nandroid
Click to expand...
Click to collapse
You can only make a nandroid if you have an unlocked bootloader and a custom recovery. Do you? Because if so, you don't need MoFo.
---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------
bobglaus said:
pull the ext4?
Click to expand...
Click to collapse
You can't pull the ext4 unless you are rooted. Are you rooted? Because if you are then you don't need MoFo.
JulesJam said:
You can only make a nandroid if you have an unlocked bootloader and a custom recovery. Do you? Because if so, you don't need MoFo.
---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------
You can't pull the ext4 unless you are rooted. Are you rooted? Because if you are then you don't need MoFo.
Click to expand...
Click to collapse
I am Rooted with the root that was similar to mofo except mofo is a exploit and the one by crashxxl isn't. Its the same idea as mofo I think that's why I asked. Write protection is still on just like mofo so you have to flash modified system.img so I need one with busybox built in. I was gonna just use a mofo one with it built in for my device but apparently there is none or I can't find it
bobglaus said:
I am Rooted with the root that was similar to mofo except mofo is a exploit and the one by crashxxl isn't.
Click to expand...
Click to collapse
OK since write protection is still enabled, then would need to use linux to install busybox in the system image. You would have to read up on how to do that if you don't already know how. I don't know how to do that but I know it can be done b/c another poster who is knowledgeable about linux did it for the XT1096 image.
Or if you know someone with a GSM Dev Ed, you can follow the directions I gave above.
bobglaus said:
so I need one with busybox built in.
Click to expand...
Click to collapse
Someone has to create it using linux. Or if you know someone with the GSM Dev Ed and an unlocked bootloader, they can do what I said earlier.
I have an XT1060 Dev Ed so I can only make images with modifications for the XT1060.
bobglaus said:
I was gonna just use a mofo one with it built in for my device
Click to expand...
Click to collapse
MoFo is not available for your device. In order for it to be available, someone has to create a rooted ext4 system image for your device. Then once they do, they can ask maiko1 to open MoFo for your device to test it.
I am able to make an ext4 rooted image for the XT1058 but only b/c another poster came up with a way to do that through TWRP. But that is all I can do for the XT1058. Someone else who knows linux would have to add busy box to it. Or if you know someone with a GSM Dev Ed, you can follow my instructions above.
JulesJam said:
OK since write protection is still enabled, then would need to use linux to install busybox in the system image. You would have to read up on how to do that if you don't already know how. I don't know how to do that but I know it can be done b/c another poster who is knowledgeable about linux did it for the XT1096 image.
Or if you know someone with a GSM Dev Ed, you can follow the directions I gave above.
Someone has to create it using linux. Or if you know someone with the GSM Dev Ed and an unlocked bootloader, they can do what I said earlier.
I have an XT1060 Dev Ed so I can only make images with modifications for the XT1060.
MoFo is not available for your device. In order for it to be available, someone has to create a rooted ext4 system image for your device. Then once they do, they can ask maiko1 to open MoFo for your device to test it.
I am able to make an ext4 rooted image for the XT1058 but only b/c another poster came up with a way to do that through TWRP. But that is all I can do for the XT1058. Someone else who knows linux would have to add busy box to it. Or if you know someone with a GSM Dev Ed, you can follow my instructions above.
Click to expand...
Click to collapse
Yea I was thinking of making the busy box part except all the guides I found were kinda outdated I think. Also if you make the rooted ext4 then give it to maiko1 will he open mofo for it or is there something else he needs? I'd be willing to test for him
bobglaus said:
Yea I was thinking of making the busy box part except all the guides I found were kinda outdated I think. Also if you make the rooted ext4 then give it to maiko1 will he open mofo for it or is there something else he needs? I'd be willing to test for him
Click to expand...
Click to collapse
But opening up MoFo for the XT1058 doesn't do anything for you if you or someone else doesn't create the images for your device. The images are device specific so you would still need to make the images - either using linux or if someone you know has a GSM dev ed then you could follow the instructions I gave you.
Well I know that. Are the images for mofo the same as the ones I need? And if he opens mofo I could try to make them but the thing is it's really hard to flash them so if mofo is easier it would help with this process
bobglaus said:
Are the images for mofo the same as the ones I need?
Click to expand...
Click to collapse
The ones you need for what?
Well i meant do you have to make them the same way you make mofo ones but nvm I'll do it myslef
bobglaus said:
Well i meant do you have to make them the same way you make mofo ones but nvm I'll do it myslef
Click to expand...
Click to collapse
OK I re-read your post and maybe I misunderstood but you don't write very clearly. If you are asking me what you need for the root method you used, I don't know what you need for the root method you used. I have never used it so I have no idea what it entails. Ask on the thread where the guy is trying to make them. He would know.
For MoFo, that I know what you need - ext4 files. And there are none for your device. Again, I can make you a rooted one, but that is all I know how to do. Or I know the instructions for pulling an image with all of the things you want in it if you know someone who has a GSM Dev Ed. Anything else has to be done in linux and I don't know how to do that. You would have to read up on it or ask people who know how to modify these images in linux.
JulesJam said:
OK I re-read your post and maybe I misunderstood but you don't write very clearly. If you are asking me what you need for the root method you used, I don't know what you need for the root method you used. I have never used it so I have no idea what it entails. Ask on the thread where the guy is trying to make them. He would know.
For MoFo, that I know what you need - ext4 files. And there are none for your device. Again, I can make you a rooted one, but that is all I know how to do. Or I know the instructions for pulling an image with all of the things you want in it if you know someone who has a GSM Dev Ed. Anything else has to be done in linux and I don't know how to do that. You would have to read up on it or ask people who know how to modify these images in linux.
Click to expand...
Click to collapse
Sorry I didn't write it clear enough. I know about all this and I know Linux. What I'm asking is because mofo root and this root use the same concept(flashing modified system images) if I could use the guide for mofo root on this. But if you can can you please make a rooted one for me? I need ext4 files too. I think there made the same way as mofo
Related
Like the title says im after the system dump for this device, it has already been leaked as a few sites are reporting having it so if anyone has it or knows where to find it please share so i can extract wallpapers sounds apps etc to share
Any advice on how to do a system dump? I should have my First in a few days.
fungflex said:
Any advice on how to do a system dump? I should have my First in a few days.
Click to expand...
Click to collapse
I have mine right now but I don't know how to go about dumping the system.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Do you have the Android SDK installed and are familiar with using adb?
dstaley said:
Do you have the Android SDK installed and are familiar with using adb?
Click to expand...
Click to collapse
Absolutely to both.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Could you check to see if it's possible to disable LTE? or did AT&T do something to prevent that as it does on every phone but the iPhone?
Sent from my SAMSUNG-SGH-I747
rooobbbbb said:
Absolutely to both.
Click to expand...
Click to collapse
IIRC, you should just be able to `adb pull /system` to get the important bits. It's not a full dump, but I think you need root level access for that. And the only way I know how to get root access is to flash a zip through recovery, and TWRP/CWM hasn't yet been released for the First.
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
rooobbbbb said:
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
Well, considering that it doesn't come out until tomorrow, I'd be willing to say yes.
I was wondering why no one was posting anything about it. Lol
Sent from my HTC first using xda premium
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Do you have a retail AT&T First? Can you confirm that retail AT&T First is unlockable via htcdev?
Sent from my SAMSUNG-SGH-I747
Yes, this is a retail model, and yes, the bootloader was unlocked via htcdev.com.
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
dstaley said:
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
Click to expand...
Click to collapse
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
nuclear_eclipse said:
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
Click to expand...
Click to collapse
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
dstaley said:
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
Click to expand...
Click to collapse
No good, but thanks for providing the link. The only shot we have left is waiting for the RUU to be leaked so we can pull recovery out of it, and get a CWM/TWRP made from it.
What is RUU and how does that help us? Sorry, just coming from a Nexus-only world, so I'm not familiar with modern HTC/Samsung devices.
Sent from my HTC first using xda premium
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
TRF-Inferno said:
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
Click to expand...
Click to collapse
RUUs for the HTC One were first available on March 26, just about a month after its announcement (and, oddly, a few weeks before it's general release). Since these have to be leaked by HTC, there's no telling when we will see those. Is there any chance another root exploit exists in stock Android 4.1.2 that we could exploit in order to get root?
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
lsl73 said:
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
Click to expand...
Click to collapse
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
superaj13 said:
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
Click to expand...
Click to collapse
Thanks i hope you can get yours going as well
fabriciosr said:
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
The rsd lite cant see my moto x i can only access it thru the fastboot but when i try the rsd way it doesnt see the phone.
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
gokart2 said:
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
Click to expand...
Click to collapse
Gokart i have tried that i dont think i am doing it wrong i got the system.img and the boot.img from here but just incase i ride the small yellow bus with a helmet on can you please point me to the direction i need to go AGAIN.
try to
fastboot flash system system.img
The obvious thing is make sure you have fastboot set up correctly... Drivers as well.
Make sure all drivers are installed, trust me redlite works with a soft bricked moto x, I found out today, my phone was bootlooping, nandroids failed soi wiped the sdcard and realized at that point I did the noob thing, well it worked like a charm rsdlite
Sent on my Moto X
this is the error i keep getting
lsl73 said:
this is the error i keep getting
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249
i would like to thank all you guys for all the advise that was given to help me bring my moto x back to life i finally got it up and running again using the moto x toolkit it seemed like the only thing that would of work in my situation again thank yall so much :victory::victory::victory:
Who unlocks their bootloader but doesn't know what to do when stuff goes bad, like this?
If you read enough to unlock the bootloader, you should have read enough to know what to do here. Coming here frantic without even checking the eleven billion threads already is silly. We have about 12 threads about the new update and similar high number threads about restoring your phone.
Too many repetitive threads for the Moto X on xda. Some people just need to take 5 minutes and look through general or Q&A before they blindly post. Clutter everywhere.
And finally, dude! I do not have any pity for you. I'm on Verizon and cannot unlock my bootloader maybe that's why I just ranted. Nothing personal, just a general consensus of this section as of late...
Sent from my XT1060 using Tapatalk
oh brother i am not mad at you but as a by the way i DID try different ways of trying to load the os back using this site as a guidance before i made this post this post was a last ditch effort before i smash the moto x and use the insurance claim on it i have been a member of this site since 2010 i just didnt create this account
So I picked up a Dev Edition XT1060 on swappa so I can get ARUnchained running on it, and was wondering what's the easiest way to clone my current locked, stock, unrooted XT1060 to the new one? I've had varying levels of success in the past with the Moto "Migrate" app, ADB backup/restore from the command line, and Helium, but was wondering if there is anything better out there now.
Don't think so, not on an unrooted device. Best you can do is helium for user apps and data.
And in my opinion....that's as far as you want to go. Restoring anything system related to a new device is asking for problems. ?
Wade-0 said:
So I picked up a Dev Edition XT1060 on swappa so I can get ARUnchained running on it, and was wondering what's the easiest way to clone my current locked, stock, unrooted XT1060 to the new one? I've had varying levels of success in the past with the Moto "Migrate" app, ADB backup/restore from the command line, and Helium, but was wondering if there is anything better out there now.
Click to expand...
Click to collapse
KJ is right if you are going to a different phone.
But if rooted only & going to the same phone, as in a boot unlock which wipes data. You can (I have not tested) use "Online back up" apk with root only. At least on paper it should work .
See my links below.
aviwdoowks said:
KJ is right if you are going to a different phone.
But if rooted only & going to the same phone, as in a boot unlock which wipes data. You can (I have not tested) use "Online back up" apk with root only. At least on paper it should work .
See my links below.
Click to expand...
Click to collapse
They are identical system images, AFAIK, so there shouldn't be anything different in the system files, and the DevEd has already been unlocked by the previous owner. So I don't think I need any of that stuff transferred anyway, which should cut down on the time involved. I haven't played around with trying to restore an ADB backup from a different device, so I'm not sure if there's going to be any issues there. The only time I've used that method was to backup my device before using RSD to flash a different factory image, and even then it wasn't a very smooth operation. I guess I'll just have to try it and find out
Wade-0 said:
They are identical system images, AFAIK, so there shouldn't be anything different in the system files, and the DevEd has already been unlocked by the previous owner. So I don't think I need any of that stuff transferred anyway, which should cut down on the time involved. I haven't played around with trying to restore an ADB backup from a different device, so I'm not sure if there's going to be any issues there. The only time I've used that method was to backup my device before using RSD to flash a different factory image, and even then it wasn't a very smooth operation. I guess I'll just have to try it and find out
Click to expand...
Click to collapse
You cannot nandroid data from one phone to another!! See my post in the x Philz thread.
aviwdoowks said:
You cannot nandroid data from one phone to another!! See my post in the x Philz thread.
Click to expand...
Click to collapse
Wasn't aware I could even nandroid an unrooted phone.
Edit: I'm wondering if maybe you misunderstood what I was talking about with the ADB backup/restore. Here's more information: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
From my early experience with Carbon (which is now called Helium) it was basically the same thing as the ADB backup/restore function, Carbon was just a user friendly wrapper for it. But I could be way off on that point, it just seemed like it was doing exactly the same thing in the background.
Wade-0 said:
Wasn't aware I could even nandroid an unrooted phone.
Click to expand...
Click to collapse
I only figure that on "paper" the online BACKUP should work with root only. Not restore, mind you, that needs custom recovery. Which one would have after the obligatory data wipe which moto enforces to unlock.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
OP is not rooted. So why confuse the matter. ?
aviwdoowks said:
I only figure that on "paper" the online BACKUP should work with root only. Not restore, mind you, that needs custom recovery. Which one would have after the obligatory data wipe which moto enforces to unlock.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
Click to expand...
Click to collapse
See my edited reply above. Also, the phone is already unlocked by the previous owner (bought it used on Swappa) so I only need to put custom recovery on it and root it, and whatever data transfer method I decide to use.
I thought I would post this also for those wanting a way to backup, while rooted, and then restore their nandroid when unlocked.
I still haven't received the OTA and Marshmallow update, and am starting to wonder if something is wrong with my device.
I'm in England, my N6 is unlocked, my SIM is "3".
Is anyone else here still waiting for Marshmallow? Or can anyone offer any advice, please?
Unlocked and 100% stock?
danarama said:
Unlocked and 100% stock?
Click to expand...
Click to collapse
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.
danarama said:
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.
Click to expand...
Click to collapse
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.
AidanBell said:
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.
Click to expand...
Click to collapse
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build
danarama said:
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build
Click to expand...
Click to collapse
Oh, I never knew that. Thank you very much.
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
The same way you got the dev preview on there I guess.
See the first post at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 In step 5, use Method 2
AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Did you actually buy your phone with M Preview?
AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Just fastboot flash the system and boot images.
Go to Nexus 6 General > Sticky roll-up thread > adb and fastboot. What is it?
This will tell you how to set up fastboot and what it is (and how to use it.). Then flash the system.img and boot.img
AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
Nah, that's his big sig, The message is one line, the sig is many lines and huge font
aiiee said:
Nah, that's his big sig, The message is one line, the sig is many lines and huge font
Click to expand...
Click to collapse
Huge for a good reason
danarama said:
Huge for a good reason
Click to expand...
Click to collapse
Many thanks for the help and comments, guys.
Yes, I bought the phone from the Phones Show Chat forum. So it was the previous owner who flashed the first preview build, not me.
I guess I have no choice, then, but to have a go at flashing the official build.
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.
AidanBell said:
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.
Click to expand...
Click to collapse
You can find the factory images here: https://developers.google.com/android/nexus/images?hl=en#shamu
There are the instructions how to flash it, but ignore the last step of locking the bootloader. If something goes wrong, and can't boot it, you can have a nice brick in your hands.
Save all your data! The flashing process will wipe it completely.
There's not magic needed, just fastboot. Turn your phone off, press down and power, until the "Fastboot flash mode" screen comes up. Then follow the instructions.
A couple of things explained:
1. The bootloader for the M preview and MRA58K were the same, but the MRA58N one might be new. I didn't try it.
2. if you unpack the "flash all" zip file, you can do the flashing by hand yourself, you can skip userdata if you don't want your device fully wiped, but then you must do a factory reset.
And if something is not clear, please feel free to ask anything. It's better to be sure than being modest and have a nice brick.
Edit: The bootloaders are the same bit for bit as the preview.
And the three official packages 58k, 58n, and 58r have the same radios.
58n is the security patch it is noted in the AOSP source too, and nobody knows what 58r is, but it can be for Verizon. But I'm not sure.
Continued thanks.
Still very nervous and somewhat out of my depth, but here goes nothing.
And ... fell at the first hurdle!
Can someone please tell me which version I need; "MRA58K", "MRA58N" or "MRA58R"?
Always the newest. MRA58K was the first Marshmallow factory image. MRA58N is the 1st November securty update, and so far nobody knows what 58R is. People are guessing here:
http://forum.xda-developers.com/nexus-6/help/mra58r-build-t3242328
I found this excellent step-by-step guide, and followed it carefully. Result ... I now have official Marshmallow.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image
So, I recommend that page to anyone else who, like me, needs a guiding hand. And I thank very much everyone in this thread for your help and encouragement.
Cheers,
Aidan
I'm stuck on LVY48I ( 5.1.1 )
don't know why it's too long to get the update !!
My Nexus totally stock.
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
lukemovement1 said:
Not long go the pixel 5 and its been a while since I've played with flashing device partitions. Can anyone give me some pointers on the below?
Is the recovery now the boot partition and the boot partition boot_a?
Is their a way of rooting lineage os without having to modify the boot.img? (idk about amazon)
Do I need to re-root with magisk after each update?
Click to expand...
Click to collapse
Unfortunately you might have asked this in the wrong forum, thus no replies. Look here in Guides https://forum.xda-developers.com/t/guide-root-pixel-5-android-11-r.4187609/
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
Fastboot says that the recovery doesn't exists?
lukemovement1 said:
Fastboot says that the recovery doesn't exists?
Click to expand...
Click to collapse
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
Ay, Ay, Ay,,,
To be fair, he was only trying to help, a simple this isn't helpful goes a long way. Being sour though, gets everyone absolutely nowhere.
And you did ask "Is their a way of rooting lineage os without having to modify the boot.img" -- I believe he was guiding you to that thread to possibly ask there as you may get a faster response. I think the question was just taken incorrectly is simply all. No harm, no foul.
bobby janow said:
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
Click to expand...
Click to collapse
You make more friends with lemonade, or something like that, you were trying to help, so good job in my eyes.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
I'll help.
"Is their a way of rooting lineage os without having to modify the boot.img"
xunholyx said:
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
Click to expand...
Click to collapse
I believe he was propbly doing a list of the partition table, and I haven't looked myself, but recovry is missing and instead of doing some research into this, he was simply asking for a simple answer, I feel this is the point of the Q & A forum, so good job to OP.. Personaly I feel this needed a simple answer, as someone coming from like a htc one m8 or htc 10 (like myself) what the hell happened to recovery.img -- a fair question in my eyes, everyone.
AsItLies said:
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Click to expand...
Click to collapse
Appreciate the info, thank you.
fadedave said:
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
Click to expand...
Click to collapse
Thank you!
Guys, this is how it should work. This is the point of the Q&A thread, ask a question, get an answer, no need for anyone to get upset or to be sour. A question was asked, an answer was kindly given.
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info, asking a question is a battle and half the ROMs and images don't work
lukemovement1 said:
asking a question is a battle
Click to expand...
Click to collapse
That's because you're making it a battle. As mentioned above, you were partly to blame for the initial misunderstanding. If people don't fully understand your question, instead of being upright rude, maybe rephrase or add more clarification as @andybones said.
lukemovement1 said:
half the ROMs and images don't work
Click to expand...
Click to collapse
There are 3 roms in this forum for Pixel 5. They all work and all are regularly updated. You are complaining about the time, sweat and money that developers put in to bring custom roms to us for free. If you don't like something about it, post a feedback or don't use it rather than be disrespectful.
lukemovement1 said:
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info
Click to expand...
Click to collapse
Then leave, or contribute to providing the correct and missing info, rather than, again, complain about free info people bring together in their spare time. None of us here are paid to bring info and provide code. We all do it in our spare time and share our knowledge because we want to make a positive community.
Your total disrespect, negativity and entitlement is not welcome here.
Touché
If you post was removed, it's because I decided to do some house-cleaning -- no one did anything wrong.
And I fixed the title to the thread, so that it's easier on those seeing it and understand what the "simple question" actually is.
Not sure why people get all salty over a simple question...
There is no /recovery partition on Pixel devices. Recovery coresides with the kernel in /boot. Previously, with Android 10, it was possible to install a custom recovery alongside a rooted kernel (such as using Magisk) but Android 11 broke this.
The best and most foolproof option in my opinion is to only temporarily boot a custom recovery to perform modifications. This is what I do every time I get an update on my Pixel 5 - I download the OTA, boot TWRP, install the OTA, reboot to system, let the update finish, boot TWRP again, and flash Magisk.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
agree , the people don't want to help,