Database Develop

Still no OTA but you want KitKat AND keep your data?

Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!

Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:

random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142

vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong

I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...

fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10

Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot

Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img

opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!

"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!

good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.

what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way

Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4

how is this method different from if i just removed the -w wipe parameter?

maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.

Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'

hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.

[GUIDE][VIDEO] Droid MAXX/Ultra/Mini - Return to stock (RSD Lite OR manual flash)

NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear

Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app

Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app

Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!

allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app

allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app

YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.

will it work if i want to downgrade from 4.4 to 4.2 ?

No

YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!

Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app

First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?

kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.

OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...

kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot

I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.

Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader

akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.

One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?

TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?

help me my razr xt890 is not booting

So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !

doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.

Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me

doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.

Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"

doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.

I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)

i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition

doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back

Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)

+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu

doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:

waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?

doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.

give me the right access (i'm [email protected])

Sorry, forgot to set it to public, should be fixed now.

so now i have to flash the boot.img or what? i'm not really sure what to do with this zip

You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.

i can't make works neither cwm nor twrp

doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Stuck in Fastboot

Hey everyone got my Pixel 5 yesterday and unlock and flash Magisk patched 21005 but after flash i’m stuck in fastboot when i presss start nothing happen, if i try to power off it goes back fastboot . I post in the Tutorial tread but haven’t gotten any answer yet .
What’s the procedure to get out of this . I’ve had pixels before but haven’t for a while , kinda rusty .
Thanks

What method did you use to flash Magisk? You patched the boot.img with the Magisk app?
To get out of your bootloader loop, flashing the stock boot.img should get out of it, then you could try again. Make sure your SDK Platform Tools is up to date.
Also, if you are on the Android 12 Developers Preview, fastboot boot the patched boot.img instead of flashing it.

xunholyx said:
What method did you use to flash Magisk? You patched the boot.img with the Magisk app?
To get out of your bootloader loop, flashing the stock boot.img should get out of it, then you could try again. Make sure your SDK Platform Tools is up to date.
Also, if you are on the Android 12 Developers Preview, fastboot boot the patched boot.img instead of flashing it.
Click to expand...
Click to collapse
No used a patched magisk which was post in one of the guides to unlock and root pixel 5.

Could downloading full factory image and extract the boot.img and flash it in fastboot fix this ?.

jawonder said:
No used a patched magisk which was post in one of the guides to unlock and root pixel 5.
Click to expand...
Click to collapse
The guide might be outdated

jawonder said:
Could downloading full factory image and extract the boot.img and flash it in fastboot fix this ?.
Click to expand...
Click to collapse
Yes, that's exactly what I meant.
Then after you are fixed up, install the new Magisk app. Transfer the boot.img to your phone's download folder. Open up the Magisk app and choose to install. That will give you an option to patch the image. Select that. Navigate to your phone's download folder and select the boot.img . When that's done, transfer the patched image to your PC (in your ADB/fastboot folder makes for the easiest way). After that fastboot flash boot **drag and drop the patched boot.img here**
If you are running the 12 developers preview through, flashing it isn't working yet. You'll have to fastboot boot it for temporary root, and have to do that again every time you reboot. This should be fixed soon though. It might already be. I'm not sure if Magisk v22.0.0 had fixed that yet. I'll know in the next couple of hours when I have time to play with my phone.

Ahh!, that’s straight forward . I had pixels phones before so i remember a little .
I’m on android 11 Fi version, just got my phone yesterday and updated it .
Thanks will do that when i get home .

jawonder said:
Ahh!, that’s straight forward . I had pixels phones before so i remember a little .
I’m on android 11 Fi version, just got my phone yesterday and updated it .
Thanks will do that when i get home .
Click to expand...
Click to collapse
Yeah, the game changed after Android 10 got released. I won't get into specifics of why, but devices released with Android 10 and later don't have twrp anymore mostly