Related
Found the zip file for the new leak. Didn't see posted here other than by using the blackhat app.
Haven't tried it, so use it at your own risk. I'm not liable for any damage to your phone or you
http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip
Instructions:
Bootstrap Recovery, Mount, Mount System, Apply Update.zip
I don't know how to do the first 3, so if anyone could elaborate for those noobs like me would be awesome
You can follow the original thread on another forum
http://androidforums.com/droid-x-all-things-root/179646-new-froyo-2-3-15-a.html
Hopefully I'm not breaking any rules. If I am let me know, and I'll take the link out
You can find the Droid X bootstrap app in the market. Just download it and run, then select boot into recovery, scroll down to Mount & Storage, mount system, apply zip. This is all assuming your already rooted.
Gimpeh said:
You can find the Droid X bootstrap app in the market. Just download it and run, then select boot into recovery, scroll down to Mount & Storage, mount system, apply zip. This is all assuming your already rooted.
Click to expand...
Click to collapse
Rom manager doesn't work on my droid for some reason. It reboots the phone but nothing else. My phone is rooted. I don't know if I should buy this and it doesn't work
But thank you for explaining what to do very helpful
Rom Manager and the Bootstrap tool are two seperate utilities. Search under koush to find it if your having trouble. You don't need rom manager in order to install roms.
Gimpeh said:
Rom Manager and the Bootstrap tool are two seperate utilities. Search under koush to find it if your having trouble. You don't need rom manager in order to install roms.
Click to expand...
Click to collapse
Hey
I downloaded it. I hit bootstrap recovery and then the second link. It rebooted and got to the "green screen". I went to back up and restore and hit it. Now my screen is black. Did I messed up my phone, is it normal and takes a while, or can I just pull out the battery and start fresh??
EDIT: Forget it got it, it was empty, I just hit the power button and it went back to normal....
Actually I'm supposed to hit the camera button not the home button, I just saw that :/
Venc said:
Found the zip file for the new leak. Didn't see posted here other than by using the blackhat app.
Haven't tried it, so use it at your own risk. I'm not liable for any damage to your phone or you
http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip
Instructions:
Bootstrap Recovery, Mount, Mount System, Apply Update.zip
I don't know how to do the first 3, so if anyone could elaborate for those noobs like me would be awesome
You can follow the original thread on another forum
http://androidforums.com/droid-x-all-things-root/179646-new-froyo-2-3-15-a.html
Hopefully I'm not breaking any rules. If I am let me know, and I'll take the link out
Click to expand...
Click to collapse
You are definitely NOT breaking any rules.
The leak is just that, a leak of a Verizon test ROM, or perhaps Moto, but leaked software nonetheless.
It is not anyones original work other that Google, Verizon, Moto.
If it was a ROM Developers personally modded tweaked themed built ROM, then it would be inappropriate.
I feel that leaks should always be given to the community for free if someone gets ahold of one, its better for the community.
Anyways...I have installed and works fine...no significant changes from. 13 I have seen.
Cheers!
acidbath5546 said:
You are definitely NOT breaking any rules.
The leak is just that, a leak of a Verizon test ROM, or perhaps Moto, but leaked software nonetheless.
It is not anyones original work other that Google, Verizon, Moto.
If it was a ROM Developers personally modded tweaked themed built ROM, then it would be inappropriate.
I feel that leaks should always be given to the community for free if someone gets ahold of one, its better for the community.
Anyways...I have installed and works fine...no significant changes from. 13 I have seen.
Cheers!
Click to expand...
Click to collapse
amen - paying for a leak is just wrong pfft nice community we have here
yourfriendwayned said:
amen - paying for a leak is just wrong pfft nice community we have here
Click to expand...
Click to collapse
The market speed on this leak SUCKS. If you're happy with what you have, stay there. You gain absolutely NOTHING from updating to this.
If you want, I can make you a build.prop that says your running 2.3.15 and it'd be the same thing. You'd never notice.
LexusBrian400 said:
The market speed on this leak SUCKS. If you're happy with what you have, stay there. You gain absolutely NOTHING from updating to this.
If you want, I can make you a build.prop that says your running 2.3.15 and it'd be the same thing. You'd never notice.
Click to expand...
Click to collapse
I had a similar issuing going from the first leak to the second. What I did is simply restored the original market that I had backed up via Titanium backup. I suspect just clearing the cache and resetting defaults will have the same result.
Gimpeh said:
I had a similar issuing going from the first leak to the second. What I did is simply restored the original market that I had backed up via Titanium backup. I suspect just clearing the cache and resetting defaults will have the same result.
Click to expand...
Click to collapse
No, I tried everything. Clearing cache/data did nothing. I did a checkin, a *228, and replaced build.props, everything. Only thing i didnt do was restoring a market from Titanium. Glad it worked for you, but I really dont notice a difference or see any need whatsoever to make this "upgrade".
Look at the thread on MyDroidWorld.com about it lol It seems more like a bug reporting thread than a "thanks for the good work" thread.
Thanks venc.
LexusBrian400 said:
The market speed on this leak SUCKS. If you're happy with what you have, stay there. You gain absolutely NOTHING from updating to this.
If you want, I can make you a build.prop that says your running 2.3.15 and it'd be the same thing. You'd never notice.
Click to expand...
Click to collapse
What is that build.prop I saw the thread and it speeds up the phone and other stuff, not sure. You just install it over the ROM or does it have to come with the ROM?
Here is the beastly build promp version (free of DATA(?))
http://www.megaupload.com/?d=FPK85Y52
Here is another mirror for the leak:
http://db.tt/KS7Sk6u
Can confirm that clearing data and cache for market solved the does issue and problem with some installs not going through on first try
Sent from my DROIDX using XDA App
gunkle said:
Can confirm that clearing data and cache for market solved the does issue and problem with some installs not going through on first try
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I can confirm the same thing.
AdFree doesn't work on this release. Neither if you had the host files from before. Still have root
Im running rooted 2.1 update1, can I apply this lick without needing to have the past leak versions? If yes, I just have to boot on kush recovery, mount sys. And load from zip? Thanks.
Sent from my DROIDX
Prob best to do the first 2.2 root and then proceed. I have not seen one person make it from 2.1 to the new leaks successfuly.
Froyo 2.3.13.MB810 FTW
jaskru said:
Prob best to do the first 2.2 root and then proceed. I have not seen one person make it from 2.1 to the new leaks successfuly.
Froyo 2.3.13.MB810 FTW
Click to expand...
Click to collapse
Does adfree work on 2.3.13??? I tried installing it first but wouldnt work
EDIT Yahoo is not working for me in this build. Cannot connect to yahoo
jaskru said:
Thanks venc.
Click to expand...
Click to collapse
No problem
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work and we've got another one in America running an older build.
It was running 1.27, now it is running 1.28.
I cannot access the data partition, obviously, not even for read (it is not rooted), however using the pm command I managed to discover which packages are located in the preload directory (excluding the carrier specific apps from my variant):
com.android.calculator2
com.htc.flashlight
com.htc.pdfviewer
com.htc.ringtonetrimmer
com.htc.soundrecorder
Initially I thought ODEX files might be needed, but these are located in the data partition and as far as I know there are no ODEX files there (correct me if I'm wrong).
Using Carbon I've backed them up (see attached here), only thing left is to check whether they can be restored and work properly on unlocked Ones. It might not fit every variant, testing required. Perhaps it might even allow using OTA updates.
If you haven't unlocked your bootloader yet, I suggest trying this beforehand instead of the attached files:
Through ADB, use:
adb shell pm list packages -f | find "preload"
Backup these apps using Carbon.
Unlock bootloader.
Restore using Carbon.
Please let me know if this works.
Thank you so much. Flashlight and calculator is working. The Sound Recorder gives me a force close. But it is a beginning. :cyclops:
Re: [WIP] Restoring Missing Apps Post Unlock: Your Help is Needed
MasterOfDesasters said:
Thank you so much. Flashlight and calculator is working. The Sound Recorder gives me a force close. But it is a beginning. :cyclops:
Click to expand...
Click to collapse
If you keep getting a force close then pmease try settings-application manager-sound recorder-clear data.
This should help clear up any force closures.
Also fixing permissions will help but quicker to just go through settings
Sent from my GT-I9300 using xda premium
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Trekest said:
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work (running version 1.27), and we've got another one in America running an older build.
I cannot access the data partition, obviously, not even for read (it is not rooted), however I did spot some of the missing apps in the system partition. I think that if we pull these files from a locked One and push them after unlocking we might not have to rely on flashing a custom rom to get them back.
Edit: or not... I've seen the Camera and have mistaken it for the Calculator... Idiot...
However, and here's the catch, I'm not sure the files remain unaltered between builds. So, here's the to do list:
Identifying the exact list of missing files post-unlocking - there'd probably be odex files missing as well as APKs, which is why we can't just pull these from a custom rom.
Pulling them from locked Ones (assuming they are in the system partition).
Comparing MD5 changes between different builds.
Testing testing testing.
Update: Stupid... this could be even simpler. These are in the data partition, and ES File Explorer can backup the APKs. I'm grabbing them now. We'll still need to figure out how to get the odex files back.
Update 2: OK, I've got 3/4 of the missing apps, the trimmer could not be backed up (attached them). Will have to continue with it tomorrow.
Maybe this tool can help us:
http://forum.xda-developers.com/showthread.php?t=1844032
Click to expand...
Click to collapse
Hi if you want the .odex files back then you could try just taking them out of the system dump or official firmware.
Just an idea mate
Sent from my GT-I9300 using xda premium
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
OP updated, please try.
ste1164 said:
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
Click to expand...
Click to collapse
Anyone who unlocks their phone would not take an ota. I have never taken an ota on the six unlocked htc phones I have had. They almost always have a new bootloader.
Sent from my HTC6435LVW using xda premium
wow that sucks.
i'm planning on getting the phone unlocked without modifying the bootloader or anything...
will just unlocking to use different sims have missing apps?
predation said:
wow that sucks.
i'm planning on getting the phone unlocked without modifying the bootloader or anything...
will just unlocking to use different sims have missing apps?
Click to expand...
Click to collapse
No, completely different, unlocking sim and unlocking Bootloader are worlds apart.
fernando sor said:
Anyone who unlocks their phone would not take an ota. I have never taken an ota on the six unlocked htc phones I have had. They almost always have a new bootloader.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Well, I have current an HTC Sensation, and up until the first ICS update I was stock and rooted, getting OTAs as usual.
Sure, I had to keep a backup of the original recovery and flash it through hboot each time before installing an OTA, however they did work.
I'm not planning on flashing a recovery this time around, I plan on just booting it to install Koush's Superuser and keep the stock one. And if it wouldn't work, just to root and go back to the stock recovery. Until I've had enough of stock :silly:
ste1164 said:
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
Click to expand...
Click to collapse
Its not a bug, HTC has done this purposely so that you cannot update.
And for everyone who says that you wouldnt want to take OTAs anyway, just wait till a nice update rolls around and then you'll be saying different
CNexus said:
Its not a bug, HTC has done this purposely so that you cannot update.
And for everyone who says that you wouldnt want to take OTAs anyway, just wait till a nice update rolls around and then you'll be saying different
Click to expand...
Click to collapse
If your unlocked you would flash that update as a rom. I'm having a hard time accepting that you wouldn't know that
Sent from my HTC6435LVW using xda premium
fernando sor said:
If your unlocked you would flash that update as a rom. I'm having a hard time accepting that you wouldn't know that
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
CNexus said:
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
Click to expand...
Click to collapse
And the same people that aren't patient enough and want instant gratification are also the ones that have the greatest tendency to hard-brick devices, who would've thought...
CNexus said:
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
Click to expand...
Click to collapse
Generally updates are anticipated and usually a stock version will be posted soon after the ota. Actually the fact that you can't receive an ota after unlocking will save a lot of noobs from installing a new locked down bootloader.
OTAs can easily be pulled from your cache. Someone would pull it and upload it.
Sent from my HTC6435LVW using xda premium
fernando sor said:
Generally updates are anticipated and usually a stock version will be posted soon after the ota. Actually the fact that you can't receive an ota after unlocking will save a lot of noobs from installing a new locked down bootloader.
OTAs can easily be pulled from your cache. Someone would pull it and upload it.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I know, I'm not trying to say that it would be there thing to do or the right thing to do, I am only saying in general.
But yes, that is how you pull an OTA, and it definitely is helpful to not accidentally (or purposely) unroot your phone.
So, did anyone restore apps? If so, can someone attach the calculator.apk?
Sent from my awesome fridge
MaartenXDA said:
So, did anyone restore apps? If so, can someone attach the calculator.apk?
Sent from my awesome fridge
Click to expand...
Click to collapse
See my OP - it has a carbon backup of all the missing apps. Just get Carbon from the play store (free) and restore them.
If you could also later tell me where it pushed them? (data/app or data/preload)
Trekest said:
See my OP - it has a carbon backup of all the missing apps. Just get Carbon from the play store (free) and restore them.
If you could also later tell me where it pushed them? (data/app or data/preload)
Click to expand...
Click to collapse
Yeah saw it, and found the apps in TrickDroid ROM zip. Thanks for the work here, but I can't test it cause I don't have the one.
Sent from my awesome fridge
I just installed the apks within the zip file and all seems fine
Trekest said:
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work and we've got another one in America running an older build.
It was running 1.27, now it is running 1.28.
I cannot access the data partition, obviously, not even for read (it is not rooted), however using the pm command I managed to discover which packages are located in the preload directory (excluding the carrier specific apps from my variant):
com.android.calculator2
com.htc.flashlight
com.htc.pdfviewer
com.htc.ringtonetrimmer
com.htc.soundrecorder
Initially I thought ODEX files might be needed, but these are located in the data partition and as far as I know there are no ODEX files there (correct me if I'm wrong).
Using Carbon I've backed them up (see attached here), only thing left is to check whether they can be restored and work properly on unlocked Ones. It might not fit every variant, testing required. Perhaps it might even allow using OTA updates.
If you haven't unlocked your bootloader yet, I suggest trying this beforehand instead of the attached files:
Through ADB, use:
adb shell pm list packages -f | find "preload"
Backup these apps using Carbon.
Unlock bootloader.
Restore using Carbon.
Please let me know if this works.
Click to expand...
Click to collapse
It works with a relocked bootloader
I've been looking for a way to do a clean reinstall of the os like I can with Odin on the galaxy phones and on iTunes on the iPhone but there seems to be no way to do this for the one.
My phone's untouched and I'm not planning on rooting it or nothing, not interested anymore but I do like to do a clean reinstall every so and so. Especially after updating.
neswii said:
I've been looking for a way to do a clean reinstall of the os like I can with Odin on the galaxy phones and on iTunes on the iPhone but there seems to be no way to do this for the one.
My phone's untouched and I'm not planning on rooting it or nothing, not interested anymore but I do like to do a clean reinstall every so and so. Especially after updating.
Click to expand...
Click to collapse
good luck with that!
There's really no way? I thought I hadn't searched hard enough.
Do you mean a factory reset?
Sent from my HTCONE using Tapatalk 4 Beta
He means RUU. I have no clue if one is available.
Read into this and try it if you understand it. It should work but I can not and will not provide support for it.
http://forum.xda-developers.com/showthread.php?t=2250904&highlight=ruu
Here's a video of wwjoshdew unrooting and bringing his htc one back to stock with step by step instructions.
Tried it once and worked great. Hope this is what you was looking for.
https://www.youtube.com/watch?v=0WWNZpaQBh8&feature=youtube_gdata_player
Sent from my HTC One using xda premium
I see now. I thought that ruu stuff was for rooted phones but I believe it's the official updater from HTC. ROM update utility is what it stands for. Saw the video and it is a stock restoring process. Thanks for the responses guys, will restore my phone during the weekend. Hopefully we'll have 4.2.2 by then!
neswii said:
I see now. I thought that ruu stuff was for rooted phones but I believe it's the official updater from HTC. ROM update utility is what it stands for. Saw the video and it is a stock restoring process. Thanks for the responses guys, will restore my phone during the weekend. Hopefully we'll have 4.2.2 by then!
Click to expand...
Click to collapse
There's nothing from your use-case that a standard factory reset (Settings -> Storage) shouldn't do, though, so do be somewhat wary.
Rirere said:
There's nothing from your use-case that a standard factory reset (Settings -> Storage) shouldn't do, though, so do be somewhat wary.
Click to expand...
Click to collapse
Thing is, I believe some apps may be corrupted when doing incremental updates, or some data may be corrupted or give problems as well. So, a full system restore eliminates this problem. I still get force closes on some stock apps and the browser after a factory reset.
I've considered flashing a custom rom, but I'm just not into tinkling with my devices anymore.
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?
simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?
csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?
csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery
|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.
|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.
Hey guys! So I just saw that the 7.1 preview is coming to our Shamu next month, and it includes the seamless updates the Pixel and Pixel XL are getting! What does this mean as far as our phones partitions? Are they going to be changed from what we're used to? And does this mean it could update itself and potentially brick because of mods we may have? Thanks!
Will i think that you wont get an update if you were in mod as you cant get it now if you rooted or on a customized rom anyway are you sure that we will get it can you show me your sources
My understanding is that the update partition functionality is tied to the hardware, so it won't work on the N6 - I have no specific reference on that (you can look for it as well as I can), it's just what I remember from what I've read. And I'm not worried about the risk of bricking my N6 - it would be unrealistically reckless of Google to issue an update which would break our phones.
But I'll keep my TWRP backups safely on my laptop just in case...
Edit: "are you sure that we will get it can you show me your sources"
Ah, untrusting junior members. He sounds almost like me...
http://forum.xda-developers.com/nexus-6/general/nexus-6-nougat-7-1-preview-t3483997
It may be possible to implement seamless updates through repartitioning of internal storage, but to do it would leave about 11GB left for user files after all is said and done. Not a pretty picture, thus we're not getting seamless updates. Not only that, on a site full of tinkerers and developers, seamless updates would be useless because of our penchant for customizing Android.
My only comment would be is why would we even need it,and why would they waste time implementing it since our device is eol?? And yes I know we will get security updates for awhile but those won't be that big in size.
If there is indeed code for the seamless partition in the N6 build (I wouldn't recognise it if it bit me on the ankle...) isn't it just because Google are trying to keep the code as standard across devices as possible? In my programming life I've seen many programs with code which is active for some purposes and just ignored when non-applicable. It may be a bit of an overhead in the code size, but a few KB here or there don't matter much these days.
So your question "why would they waste time implementing it" - I would say "For the N6, they aren't".
dahawthorne said:
If there is indeed code for the seamless partition in the N6 build (I wouldn't recognise it if it bit me on the ankle...) isn't it just because Google are trying to keep the code as standard across devices as possible? In my programming life I've seen many programs with code which is active for some purposes and just ignored when non-applicable. It may be a bit of an overhead in the code size, but a few KB here or there don't matter much these days.
So your question "why would they waste time implementing it" - I would say "For the N6, they aren't".
Click to expand...
Click to collapse
Correct I've said this already in another thread, but I still don't think we will get it because our major updates are done, and Google has already said only pixel devices + would be getting it
holeindalip said:
Correct I've said this already in another thread, but I still don't think we will get it because our major updates are done, and Google has already said only pixel devices + would be getting it
Click to expand...
Click to collapse
Yea it's definitely all too hazy at this point, I saw a video of I think it was a 5x or a 6p running the new beta, and in the software update area, it said something about seamless updates, like, the developer preview allowed seamless updates on the older Nexus. That's about the time last night I decided to make this thread! lol honestly, my thoughts on this are what's in the op as well as this....... is this going to make manual fastboot flashing more of a pain? like, a crap load of new partitions to worry about on top of the like, 7 partitions Nexus devices already have? And also, mods would be so much harder to use knowing that when the system chooses to update and swaps your system, all your mods would be completely gone!
It was already mentioned that it won't update when modded much like they don't know with root and a non stock system, BUT if your second system partition is unmodified, then it could potentially update that and swap you to that one ._.
Confusing I know, too early to say for sure, but I thought this thread would get interesting.
EDIT: I just downloaded the 7.1 beta for the 6p and looked inside it, the img files all look normal, nothing out of the ordinary. bootloader,boot, radio, system, recovery, userdata, cache, and vendor.
H4X0R46 said:
Yea it's definitely all too hazy at this point, I saw a video of I think it was a 5x or a 6p running the new beta, and in the software update area, it said something about seamless updates, like, the developer preview allowed seamless updates on the older Nexus. That's about the time last night I decided to make this thread! lol honestly, my thoughts on this are what's in the op as well as this....... is this going to make manual fastboot flashing more of a pain? like, a crap load of new partitions to worry about on top of the like, 7 partitions Nexus devices already have? And also, mods would be so much harder to use knowing that when the system chooses to update and swaps your system, all your mods would be completely gone!
It was already mentioned that it won't update when modded much like they don't know with root and a non stock system, BUT if your second system partition is unmodified, then it could potentially update that and swap you to that one ._.
Confusing I know, too early to say for sure, but I thought this thread would get interesting.
EDIT: I just downloaded the 7.1 beta for the 6p and looked inside it, the img files all look normal, nothing out of the ordinary. bootloader,boot, radio, system, recovery, userdata, cache, and vendor.
Click to expand...
Click to collapse
Copy that, yea the factory images won't change much because you are still only flashing one set of partitions
I can only see this as a positive though for people who don't know wth they are doing and like 10 unsuccessful boots will auto boot the other set of partitions,and the seamless update part
Edit: here's the other thread
http://forum.xda-developers.com/nexus-6/general/update-signs-t3455461/post68963916
holeindalip said:
Copy that, yea the factory images won't change much because you are still only flashing one set of partitions
I can only see this as a positive though for people who don't know wth they are doing and like 10 unsuccessful boots will auto boot the other set of partitions,and the seamless update part
Edit: here's the other thread
http://forum.xda-developers.com/nexus-6/general/update-signs-t3455461/post68963916
Click to expand...
Click to collapse
Oh I remember that thread! When the Pixel and Pixel XL factory images are released, I'm gonna download them and check em out. I wonder how much more complicated that makes flashing.
H4X0R46 said:
Oh I remember that thread! When the Pixel and Pixel XL factory images are released, I'm gonna download them and check em out. I wonder how much more complicated that makes flashing.
Click to expand...
Click to collapse
Just edit the flash-all.bat it will tell all
holeindalip said:
Just edit the flash-all.bat it will tell all
Click to expand...
Click to collapse
Oh yea! I forget that that is even a thing, I never once used it lol
H4X0R46 said:
Oh yea! I forget that that is even a thing, I never once used it lol
Click to expand...
Click to collapse
Lol i don't think it's ever worked for the 6, but it tells all for when you get old and don't feel like looking it up on Google or XDA if you forget the commands
holeindalip said:
Lol i don't think it's ever worked for the 6, but it tells all for when you get old and don't feel like looking it up on Google or XDA if you forget the commands
Click to expand...
Click to collapse
It's supposed to work if you have a relatively recent version of Fastboot from the Android SDK but I have also never tried it and prefer to manually flash each image file separately.
alryder said:
It's supposed to work if you have a relatively recent version of Fastboot from the Android SDK but I have also never tried it and prefer to manually flash each image file separately.
Click to expand...
Click to collapse
Mine flashes bootloader and radio then errors out, never tried it again. I always flash individual after that
holeindalip said:
Mine flashes bootloader and radio then errors out, never tried it again. I always flash individual after that
Click to expand...
Click to collapse
I used wugfresh toolkit one time and it gave me that error like, 3 times in a row! Being the noob I was at the time, I FREAKED! Haha no clue what to do! I since started flashing all my partitions manually!
holeindalip said:
Just edit the flash-all.bat it will tell all
Click to expand...
Click to collapse
Just downloaded an image for marlin, and HOLY CRAP! This is a mess o.o Also, the flash-all.bat file just runs the -w update command, doesn't really say which commands are entered other than that! But this looks like a headache to flash manually!
Have a look!
http://imgur.com/a/yJaFq
Also, a pic of the batch file contents! http://imgur.com/a/Fx9Co
H4X0R46 said:
Just downloaded an image for marlin, and HOLY CRAP! This is a mess o.o Also, the flash-all.bat file just runs the -w update command, doesn't really say which commands are entered other than that! But this looks like a headache to flash manually!
Have a look!
http://imgur.com/a/yJaFq
Also, a pic of the batch file contents! http://imgur.com/a/Fx9Co
Click to expand...
Click to collapse
Interesting, the flash-all.bat is the same as ours for the 6
total lack of friday night drinking humor here.......
Pkt_Lnt said:
You *really* want to try flashing 64 bit firmware on a 32 bit phone?
"Cleanup on aisle N6 please". :cyclops:
Click to expand...
Click to collapse
Wth are you talking about about?? If you would of read anything in this thread you would've seen nobody in this thread said anything about flashing a 64bit os on a 32 bit processor