Develop Bugs

[Q] GNex OTA from 4.1.2 to 4.2 failed, phone bricked :(

Hi guys,
I had my GNex 4.1.2 with SuperSU root survival installed, when upgrading from 4.1.1 to 4.1.2 all went fine. But now, upgrade from 4.1.2 to 4.2 via standard OTA failed and I cannot get through the boot screen with Google text and image of opened lock. Any help would be appreciated.
Thanks.

Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!

manumanfred said:
Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!
Click to expand...
Click to collapse
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?

gabriel31337 said:
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?
Click to expand...
Click to collapse
If you don't want to lose data then you may need to flash manually!
I'm not sure does this keep all data but I think it will keep if just not using fastboot -w command..
Download the factory image and extract files from it to fastboot folder then also extract files from the .zip in .tar package to fastboot folder!
then open CMD (Command prompt) and then write cd /your fastbot folderdestination/ Example: cd C:\GalaxyNexusRootNew
and then when those is done then use exactly these commands:
Code:
fastboot flash bootloader bootloader-maguro-primelc03.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-maguro-i9250xxlh1.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
and finally:
Code:
fastboot reboot
and if that does not work then
Code:
fastboot-reboot

manumanfred said:
Code:
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.

easy way
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.

gabriel31337 said:
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.
Click to expand...
Click to collapse
not actually, it may boot well but may cause some issue so later in CWM wipe dalvik cache and cache

themaskofwraith said:
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.
Click to expand...
Click to collapse
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.

gabriel31337 said:
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.
Click to expand...
Click to collapse
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..

manumanfred said:
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..
Click to expand...
Click to collapse
I don't want to mess with CWM or anything else non factory (apart from SuperSU ). I have restored the phone to 4.2.1 and rooted, apps and data have survived so I'm very happy again. Thanks a lot for your guidance. :good:

[Q] Flashing to pure stock 4.3 with the latest bootloader, recovery, etc.?

I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.

you didnt search very well...
there's a return to stock thread in the general section.

Just use this: http://forum.xda-developers.com/showthread.php?t=1766475
Read last 3-4 pages.

AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
search again... and in short if u are flashing your rom with stock image u dont have to install the bootloader and radio img again... search how to flash stock image using adb..
Sent from my Galaxy Nexus using xda premium

AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
Hi, let me try to help you
Galaxy Nexus is my first smartphone. So i'm pretty new at flashing things. I did some research last year to learn how to flash stuff in it and that's how i learned to make a fresh install:
-Make sure you have the SDK platform-tools and the Galaxy Nexus driver properly installed on your PC. Also, make sure you have USB debuging enabled on your device.
-Download the factory image that fits your phone at https://developers.google.com/android/nexus/images
-Open up the tgz file you just downloaded and extract the files:
-boot.img
-bootloader-maguro-primemd04.img
-radio-maguro-i9250xxlj1.img
-recovery.img
-system.img
-userdata.img
Extract the files in the platform-tools folder to make things easier.
-Connect your Nexus to your PC, open the command prompt, go to the platform-tools folder and type
(Do not turn off, disconnect or close the cmd prompt windows until everything is done. Again, make sure you have the nexus driver properly installed on your Windows)
Code:
adb reboot-bootloader
(this command will reboot your device to recovery mode)
With your device on recovery mode, type the following commands to erase your device:
Code:
fastboot erase boot
Hit enter, then:
fastboot erase cache
Hit enter, then:
fastboot erase recovery
Hit enter, then:
fastboot erase system
Hit enter, then:
fastboot erase userdata
-Now you're going to flash the new files you have downloaded and extracted steps before:
Code:
fastboot flash bootloader bootloader-maguro-primemd04.img
(or whatever name your bootloader img file has. In this case the bootloader file is "bootloader-maguro-primemd04.img")
Code:
fastboot reboot-bootloader
(you'll need to reboot after flashing the bootloader)
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Flash the radio
Code:
fastboot reboot-bootloader
Reboot again
Code:
fastboot flash system system.img
Flash system
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
We are almost done!
Code:
fastboot erase cache
Code:
fastboot reboot
Done! Reboot to Android. The first boot may take some more time than the usual. Don't worry!
-
If you want to flash a custom recovery, download it from their website, go into fastboot mode and flash it using the command to flash the recovery.
Code:
fastboot flash recovery [recovery filename].img
The same command used when flashing the recovery on the fresh install above
That's the way i learned how to do it from scratch. In case someone more experienced has any thoughts about it, i'd like to hear as i'm not an expert and learned by researching it on my own...

This is how it's done, PROPER. Well done, mnoguti.
a maguro wrote this.

@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?

AbhishekS said:
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
Click to expand...
Click to collapse
you don't have to go into the recovery mode to flash recovery, just boot into fastboot mode and flash recovery using command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
obviously replace the recovery.img with the name of the custom recovery file you downloaded, make sure the custom recovery file is in the same folder as fastboot/adb otherwise you'll have to do it like:
fastboot flash recovery C:\Downloads\recovery.img
Click to expand...
Click to collapse

Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.

Obviously he meant fastboot mode..
a manta wrote this.

AbhishekS said:
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Click to expand...
Click to collapse
It's "fastboot mode". Sorry for the mistake!
I've updated my post and now it's right

[Q] How to restore back to factory settings after using towel root

I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.

Flash a stock r for your phone
swagg blasted from TMO LG G3

jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?

If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?

fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.

@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.

Doesn't the boot loader have to be unlocked to flash a ROM via adb?

try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img

Thank you very much I will try this today.

I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?

Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).

January security update?

I received the download on my 5x that's rooted. Will this break root for me?

Yes but you can easily re-root after re-installing TWRP

bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?

Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview

This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes

Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!

SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.

gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk

jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.

Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"

ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.

my zen faild google verification to boot up

hey
when my phone boots shows that my device is not verified by google , what to do?

Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around

sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related

Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.

sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.

Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.

sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?

Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?

sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551

Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error

sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .

Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk

sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .

sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/

Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?

sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM

Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question

sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully

Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again

sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro