hi everyone
can somebody tell me or help me to give me information if i did flashing official .img (firmware) from google site (same series, same build number) will it make my google pixel brick?
thank you
xerxess said:
hi everyone
can somebody tell me or help me to give me information if i did flashing official .img (firmware) from google site (same series, same build number) will it make my google pixel brick?
thank you
Click to expand...
Click to collapse
Hi there. Do you mean flashing image with the same built you already installed? If you do, it will wipe your phone completely. So, no brick. Just a fully wiped phone.
Vanschtezla said:
Hi there. Do you mean flashing image with the same built you already installed? If you do, it will wipe your phone completely. So, no brick. Just a fully wiped phone.
Click to expand...
Click to collapse
yes thats what i mean, flashing image with same built that i already installed. so it's safe.
is there any something i need to cautious before do that? as far as i remember , in google site there is 2 kind of image, full ota image and factory image. which image can be used for locked bootloader google pixel?
sorry my english not good
xerxess said:
yes thats what i mean, flashing image with same built that i already installed. so it's safe.
is there any something i need to cautious before do that? as far as i remember , in google site there is 2 kind of image, full ota image and factory image. which image can be used for locked bootloader google pixel?
sorry my english not good
Click to expand...
Click to collapse
I'm sorry but as far as I know, you need to unlock your bootloader before flashing those. If anything you need to be cautious of, is make sure you properly unlock your bootloader before flashing.
OTA can sideload in factory recovery. No need to unlock as far as I know. There is always a risk, anything is possible, but if you look up guides for either factory image or ota update you should be fine. If you want to wipe your userdata, you should use the factory image method.
Related
Hi all I i eeded stock rom samsung M200s??
thank advance
samnang ouch said:
Hi all I i eeded stock rom samsung M200s??
thank advance
Click to expand...
Click to collapse
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Thank for reply but i need M200s not M200 .
Please Help
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
samnang ouch said:
Thank for reply but i need M200s not M200 .
Click to expand...
Click to collapse
No such thing exists. It's m200.
summereyes said:
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
Click to expand...
Click to collapse
Get that. And read the instructions.
hp420 said:
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Get that. And read the instructions.[/QUOTE]
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please
summereyes said:
Get that. And read the instructions.
Click to expand...
Click to collapse
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please[/QUOTE]
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
So, more or less
Have fastboot working
Boot in fastboot mode
Make sure you untar every file from the link above.
wipe data
fastboot -w update image-sojuk-JRO03E.zip
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
Ok so i'm running lollipop 5.0 with twrp 2.8.3.0 rooted with cf auto root and i want to update to 5.0.1. First what i did i tryed to install ota but it did not start to install when the device resets. So i downloaded factory images for 5.0 and flashed factory recovery via fastboot, now when i download ota and device starts to install it on 1/4 % of progress bar it says error. So what else i need to do to install ota? Or there is not any other way exepct to flash factory image for 5.0.1.
Best option is to download factory image 5.0.1 and flash it with no wipe.
zagorteney said:
Best option is to download factory image 5.0.1 and flash it with no wipe.
Click to expand...
Click to collapse
Ok, so i do it with no wipe by editing the bat file right? i need to delete w?
Yeah, why download 5.0 instead of 5.0.1 factory image?
Easiest thing to do would have been flashing the 5.0.1 twrp flashable version of the rom from XDA...
rootSU said:
Yeah, why download 5.0 instead of 5.0.1 factory image?
Easiest thing to do would have been flashing the 5.0.1 twrp flashable version of the rom from XDA...
Click to expand...
Click to collapse
Sorry i did not know that there is a flashable version :/ can you give me the link to it? i will flash back twrp now and flash it like you said.
Its in the resources section of general > sticky roll-up, by vomer
rootSU said:
Its in the resources section of general > sticky roll-up, by vomer
Click to expand...
Click to collapse
I did all as u said and it went without a problem. So thanks a lot
Alexandar92zr said:
I did all as u said and it went without a problem. So thanks a lot
Click to expand...
Click to collapse
Can u give me more information ?
chessjoe said:
Can u give me more information ?
Click to expand...
Click to collapse
What more do you need? If you read my post, all the information is there
rootSU said:
What more do you need? If you read my post, all the information is there
Click to expand...
Click to collapse
someone else asked for more information, but it all went well im on 5.0.1 now rooted with twrp so thanks again
Alexandar92zr said:
someone else asked for more information, but it all went well im on 5.0.1 now rooted with twrp so thanks again
Click to expand...
Click to collapse
I was talking to the guy who asked for more information.
rootSU said:
I was talking to the guy who asked for more information.
Click to expand...
Click to collapse
That's great to hear. By the time, Is there any handy guide just to sideload the 5.0.1 update without actually wiping the data.
A lot of people will be looking the same just like me!
CODENEX said:
That's great to hear. By the time, Is there any handy guide just to sideload the 5.0.1 update without actually wiping the data.
A lot of people will be looking the same just like me!
Click to expand...
Click to collapse
You can only sideload OTA and OTA doesn't wipe data.
rootSU said:
You can only sideload OTA and OTA doesn't wipe data.
Click to expand...
Click to collapse
So it's the same way like we flash the factory image/custom ROM. Since the manual wiping doesn't even require, no need for apps backup?! #n008
CODENEX said:
So it's the same way like we flash the factory image/custom ROM. Since the manual wiping doesn't even require, no need for apps backup?! #n008
Click to expand...
Click to collapse
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
rootSU said:
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
Click to expand...
Click to collapse
I think the Section - B of the guide complies what you said.
Why is there three links, with warning (Original, may not flash for most people and full radio)?
rootSU said:
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
Click to expand...
Click to collapse
This is best explanation as you can get. But for newbies like me, there is also tool, named Wugfresh Root Toolkit. It does exactly what rootSU said above, but for ordinary users in more friendly way.
Regards, Zagor
zagorteney said:
This is best explanation as you can get. But for newbies like me, there is also tool, named Wugfresh Root Toolkit. It does exactly what rootSU said above, but for ordinary users in more friendly way.
Regards, Zagor
Click to expand...
Click to collapse
True but the problem there is that toolkits take away the learning curve for noobs. This means if something goes wrong using the toolkit of even later on, when we try to help, the noob doesnt understand the basic things we're saying.
Sure, it saves noobs time, but it wastes our time later when the noob needs our help (which is unfair and a bit selfish) So we strongly urge noobs to NOT use toolkits.
rootSU said:
True but the problem there is that toolkits take away the learning curve for noobs. This means if something goes wrong using the toolkit of even later on, when we try to help, the noob doesnt understand the basic things we're saying.
Sure, it saves noobs time, but it wastes our time later when the noob needs our help (which is unfair and a bit selfish) So we strongly urge noobs to NOT use toolkits.
Click to expand...
Click to collapse
It makes sense. But there is another truth, too. There aren't so many professionals like you with understanding android enviroment.
For example. I'm steel worker. I know how to weld. But also I know just few basic things about how welding machines works. I do not need exactly know how it works I just need to know how to adjust some of parameters to get better results. Because I have a good welding machine, it is almost impossible to go anything wrong. So for me good Toolkit is like good welding machine.
When I try to install SDK from Google and start with it I just give up after only 10 min. Toolkits works for me since X10. Of course there were many mistakes I've made (and probably will do), but I never bother people for such a situations like "I flash HTC Xspeed kernel on Samsung device - my gosh, please help". There are also unpredictable situations. I hate that with Titanium Backup and its /storage folder most. But the beauty of android system is that you can't do anything wrong. If you have somekind of backups you can allways start fresh. And that is the best school for everybody.
Regards, Zagor
You don't need the SDK. Its worth reading the stickies. The problem is when someone uses a toolkit and doesn't know how to use fastboot and we have to explain everything to them whilst panicking. Its easier to learn fastboot first.
Of course you must feel free to use toolkits yourself but many of us will say what I have said today if you recommend it.
Fastboot is not knowing how it works. Fastboot is the same knowledge you have as your welding machine. Developing would be more than you know than your welding machine.
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
cesarp3791 said:
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
Click to expand...
Click to collapse
Just unlock your bootloader now, the longer you leave it the more difficult it'll be to backup your internal storage beforehand. You should really have it unlocked anyway as insurance against anything going wrong with your phone. Once you have unlocked it you can flash TWRP recovery, then the correct procedure to go back to CM11S would be to perform a full wipe (system, data, cache, dalvik cache) and then just flash the zip. As far as custom ROMs for this device go, there are many excellent options to choose from that offer extra customisation that you won't find on the stock ROM.
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
uansari1 said:
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
Click to expand...
Click to collapse
The firmware is contained in the official zip.
Heisenberg said:
The firmware is contained in the official zip.
Click to expand...
Click to collapse
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
uansari1 said:
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
Click to expand...
Click to collapse
You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thanks!
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
cesarp3791 said:
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
Click to expand...
Click to collapse
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
uansari1 said:
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
Click to expand...
Click to collapse
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Heisenberg said:
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Click to expand...
Click to collapse
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
uansari1 said:
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
Click to expand...
Click to collapse
That modem should be fine.
Hey all I just want to make sure I understand all the steps correctly so I dont end up with a brick.
Before everyone freaks out on me, my friend wanted a Pixel and I want the XL she doesn't want a unlocked bootloader so she ordered the XL and shes taking my Pixel.
So if I understand correctly download vendor img here https://developers.google.com/android/images and run the flash-all.bat then lock bootloader? Do I have to do anything with the different partitions? Appreciate any guidance as I really dont want to brick this. Thanks!
Konfuzion said:
So if I understand correctly download vendor img here https://developers.google.com/android/images and run the flash-all.bat then lock bootloader? Do I have to do anything with the different partitions? Appreciate any guidance as I really dont want to brick this. Thanks!
Click to expand...
Click to collapse
Sounds right to me. Flashing the factory image will wipe everything and flash all the partitions.
roirraW "edor" ehT said:
Sounds right to me. Flashing the factory image will wipe everything and flash all the partitions.
Click to expand...
Click to collapse
Thanks for the help!