Related
I don't know how that's happened.. I am using my nexus on liquit smooth latest version and the phone's not booting up while i am gaming on PC.
I tried to go into recovery and reinstall the ROM ( liquid ). but when in installing progress, the phone failed to be installed the rom somehow and automatically going to google icon screen at the very start. I am pretty sure download mode is available at that time. then I sent my phone to my local phone shop to get it repair. 3 days later the shop technician gave up with my phone's problem. When I tested my phone after that .. my nexus gotten into even worse condition ! even google icon's colors are not right ! I can't go into the download mode ! I can't call recover mode either !!!! .. WTF .. Did my phone bircked? All i can see now is ruined Google screen , Ruined fastboot screen and Ruined Download mode screen. all of them are with wrong graphic placements and wrong colors.. can't go anywhere beyond them. SOMEBODY HELP ME !!!! PLEASE !! :crying:
Ok ur in quite a fix. U tried flashing using adb.
«««««««CYANOGENMOD 10.1 and FRANCO KERNEL»»»»»»»»»
If you can get into the bootloader, regardless of what the screen looks like, and the PC recognises the unit in fastboot then you can flash the factory image. Download it from Google and see if this fixes things. If not, you can then send it back under warranty (assuming it's still covered)
What about the riff box with gnx file ? someone told me that.. i don't know where to find it. pls let me know?
I would try OMAPflash before that. Also, that's what you get for taking your baby to the "local phone shop".
Sent from my Nexus
My LG G3 (T-Mobile) got hard bricked i don't really know y but i did mess with some tweaking apps to boost the phones performance and after that the phone started to glitch BADLY i couldnt even unlock the screen it was so gitchy and errors kept poping up it woudlt let me click the screen so i tried formatting it and the problem persisted, now after trying that i attempted to flash stock ROM again and now its now ****ed ithe screen is all black the screen DOESNT turn on cant use it just a paper weight but when plugged in to the computer this pops up QHSUSB__BULK please help i can pay 175$ for the insurance to replace but i rather try to do it my self
RESTORE
NoMurrcy said:
My LG G3 (T-Mobile) got hard bricked i don't really know y but i did mess with some tweaking apps to boost the phones performance and after that the phone started to glitch BADLY i couldnt even unlock the screen it was so gitchy and errors kept poping up it woudlt let me click the screen so i tried formatting it and the problem persisted, now after trying that i attempted to flash stock ROM again and now its now ****ed ithe screen is all black the screen DOESNT turn on cant use it just a paper weight but when plugged in to the computer this pops up QHSUSB__BULK please help i can pay 175$ for the insurance to replace but i rather try to do it my self
Click to expand...
Click to collapse
Try restoring with stock rom.
1. download the latest firmware (http://lg-firmware-rom.com/)
2. Follow the below thread for the steps to install it.
http://forum.xda-developers.com/showthread.php?t=2772199
NoMurrcy said:
My LG G3 (T-Mobile) got hard bricked i don't really know y but i did mess with some tweaking apps to boost the phones performance and after that the phone started to glitch BADLY i couldnt even unlock the screen it was so gitchy and errors kept poping up it woudlt let me click the screen so i tried formatting it and the problem persisted, now after trying that i attempted to flash stock ROM again and now its now ****ed ithe screen is all black the screen DOESNT turn on cant use it just a paper weight but when plugged in to the computer this pops up QHSUSB__BULK please help i can pay 175$ for the insurance to replace but i rather try to do it my self
Click to expand...
Click to collapse
Had the same problem too, but every method I tried didn't work. So I used the warranty for LG and they're repairing/replacing the phone. You need to email or talk to a LG representative.
The only thing you have to pay is shipping and the rest are free.
xmagiicsx said:
Had the same problem too, but every method I tried didn't work. So I used the warranty for LG and they're repairing/replacing the phone. You need to email or talk to a LG representative.
The only thing you have to pay is shipping and the rest are free.
Click to expand...
Click to collapse
I have the same issue (hard bricked g3) but this definitely isn't under warranty, I got it from a friend cause I figured it'd be soft bricked, but nope it's completely unresponsive, besides QHSUSB__BULK
Ummm, tried formatting what? There is factory reset, restore, but formatting?
Did you try KDZ flash or TOT flash?
If one fails, try the other.
KDZ wouldn't work for me, but the TOT flash method worked like a charm to flash my D852.
If you can see ANYTHING at all on your screen, recovery menu, download mode screen, anything at all, then it's very likely your device can be fixed.
But if you can't see anything whatsoever on your screen, like no recovery screen, no download mode screen ect then it's hard bricked and must be repaired by the hardware vendor.
EDIT: Here are a few other common reasons for failed flashing:
1. Make sure you're using the LGUnitedMobileDriver
2. Try a different usb port (front and rear usb ports can act dramatically different from eachother).
3. Try a different usb cable.
4. Try a different computer to flash.
I just got my phone repaired from LG and I recieved it two weeks after I sent it the phone to LG. They repaired my phone but they deleted everything
Well, my GF's G4 started bootlooping a few days ago, the local store she bought it from doesn't honor the warrenty and says it may be something we did. I didn't like hearing that and decided to take legal action.
In the meanwhile, she asked if the data can be restored, I started playing with it and reading online. The phone bootlooped anytime I took the battery out and reinserted it, then go off. I decided to put it in the freezer after reading about many successful attempts to boot the device. The first time I put it in a plastic bag for 5-10 minutes (when I took it out it had humidity on it which I wiped), it turned on! and went into Android app optimization and we were thrilled, It went off after 2 minutes so I decided to put it in again for 30-40 minutes in a sealed plastic bag (as many recommended), when I took it out it didn't turn on at all no matter how many tries I tried switching batteries, connecting to the charger etc. (it had humidity on it again when taken out of the freezer).
From then on, the phone won't turn on at all, I put it in a bag of rice in get rid of humidity/water but that didn't help and the device won't bootloop at all.
Now, I have no case as it doesn't bootloop and the store can claim there's damage not governed by warrenty, I can't claim it bootloops as it is a brick.
I'm worried the water caused corrosion which totally cancels her warrenty.
Hope someone can help me fix this out, cant believe I hope it will bootloop again.
Thanks.
What version of G4 have you ? H815 ? or other ?
you can try to flash official firmware with LG UP with .kdz file or if you have another G4 with .tot file
You must have computer with drivers installed and LG UP installed
Watch tutorial
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
1. volume up and connect to pc
2. flash the "core disable" kdz/tot (whatever it is)
3. it should boot but it won´t be as fast as i has been
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
To be honest with you pal i very much doubt you'll get it back working as the serial is a 505 which means it's included in the bad batch of faulty motherboards on the phone and its that which is causing the bootlooping , you need to tell the place where you got it that the hardware has failed out of your control if they don't help try contacting LG directly you could be lucky....
YSAndroid said:
Now, I have no case as it doesn't bootl
Thanks.
Click to expand...
Click to collapse
When I did the following steps, I was able to get back into the phone with all my apps and internal data right where it was. It only fixed the corrupt system files. It seemed to work like startup recovery on Windows. But as a warning, I've only done this once so cannot guarantee you the same.
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGM..._4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product...reinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
I was lucky and this didn't remove any of my data.
If you have problems with LG Bridge detecting your device:
i) Make sure you have the drivers installed and are using a reliable cable and USB port.
ii) Open up device manager and look for your phone. It should be named [...... COM#].
iii) Right click and go to the ports tab and click advanced. Select COM41. This seemed to work for me.
hallo, I have now another problem, i have bricked my phone because i failed click install not this zip as i wanna. and i must use xfstk for install (because i have black screen brick) and now i have black screen or flag 4 colors like this https://zapodaj.net/e808ee12dba6a.jpg.html sorry for this link
and i don't know what do now, asus flash tool don't see phone, on my windows 10 and my friend windows 7 (xfstk see my phone on my friend windows 7 but not on asus flash tools ) the same problem. What can i do to revive my phone !?
I don't know if this will work on Win10 because I use Win7x64.
Power off the phone, open xFSTK, begin download, connect the phone, press and hold power button to power off the phone if the phone tries to power up. It took me a few tries but I finally got xFSTK to load a fastboot screen so I could flash a raw file with the Asus Flash Tool.
Stuck on 4 colour screen .
Some devices have reported to stay on 4 colours and battery discon and recon brings back bootloader for some.
Although , the few times mine has stayed on 4 colours , mine went to bootloader everytime by ;-
1 at 4 colours if staying on 4 colours for more than 20 secs , press and keep pressed power .
2 at the first of the two vibes , be ready and hit download again in xFSTK.....
3 do not discon phone from pc at 4 colours while attempting 1 & 2
Hi . Open back cover. And unscrew middle cover. Deattach sim card holder flex cable from motherboard . It must enter to bootloader. After it attach again sim card flex cable to mainboard. I fix 4 color mode in this way. It works 100%.
pavlogs1920 said:
hallo, I have now another problem, i have bricked my phone because i failed click install not this zip as i wanna. and i must use xfstk for install (because i have black screen brick) and now i have black screen or flag 4 colors like this https://zapodaj.net/e808ee12dba6a.jpg.html sorry for this link
and i don't know what do now, asus flash tool don't see phone, on my windows 10 and my friend windows 7 (xfstk see my phone on my friend windows 7 but not on asus flash tools ) the same problem. What can i do to revive my phone !?
Click to expand...
Click to collapse
LOL oml13 dude! Its work ! haha now i flashing raw file i have now flash imego on asus tool and on my device is write RESULT : OKAY
@ops now i have again flags. flash tool bootlop.... ;/ 15 min later phone reset and back to colours ;/
Try it again. and flash this Raw file http://4pda.ru/pages/go/?u=https://...5xzF4dFKPU2tSDtLwXzvtJK_YpA0LwUht4&e=53383245 by clicking "6_сток_рекавери.bat" in the rar archive. Before you must install asus , intel and adb drivers. Its flash Raw firmware without ASUS flash tool.
pavlogs1920 said:
LOL oml13 dude! Its work ! haha now i flashing raw file i have now flash imego on asus tool and on my device is write RESULT : OKAY
@ops now i have again flags. flash tool bootlop.... ;/ 15 min later phone reset and back to colours ;/
Click to expand...
Click to collapse
Downloading... And have one question. In asus flash tool i must wipe data Yes or NO ?
Asus flash tool don't work. But this bat file in fastboot it works. Now system starting up. Thank you very very much bro! U have virtual beers from me!!! Thank again! meybe i can say problem is solved!
?. Congratulations ,bro! I'm happy for you!
pavlogs1920 said:
Downloading... And have one question. In asus flash tool i must wipe data Yes or NO ?
Asus flash tool don't work. But this bat file in fastboot it works. Now system starting up. Thank you very very much bro! U have virtual beers from me!!! Thank again! meybe i can say problem is solved!
Click to expand...
Click to collapse
Hey again. I have now one more problem. When i 3 days ago testing android 7 its very goo but i have problem with auto awake screen. now i have the same problem on this system and i see my touch screen breaks the line when i write on test app. I test it and when i draw straight line, touch screen break the line and draw again and its breaks randomly. This break is maybe for 0.2-0.4 sec and work again. Sometimes is good for hmm 2 minus without awake screen on my table. This can be a hardware problem or maybe something in software inside? I open back cover and check all tapes and wires. All ok i think. i push to be sure. Any sugestions ?
Hi. I think its not hardware issue. Its software bug. Can you screenshot it. Or record as video ?
pavlogs1920 said:
Hey again. I have now one more problem. When i 3 days ago testing android 7 its very goo but i have problem with auto awake screen. now i have the same problem on this system and i see my touch screen breaks the line when i write on test app. I test it and when i draw straight line, touch screen break the line and draw again and its breaks randomly. This break is maybe for 0.2-0.4 sec and work again. Sometimes is good for hmm 2 minus without awake screen on my table. This can be a hardware problem or maybe something in software inside? I open back cover and check all tapes and wires. All ok i think. i push to be sure. Any sugestions ?
Click to expand...
Click to collapse
Ok, when I back to home I record this with draw touch line setting. And update this on what server?
https://youtu.be/LbhiWk3F0zU
Here is video. Waiting for help ;/
@edit i see in battery usage process 99003 wtf
Refresh
Refresh Again
I have see, when i unplug usb panel, phone doesn't auto awake. i think this problem is becouse flip cover magnetic sensor is broken ;/
Hi Guys
please help me fix a few problem which are driving me crazy.
here's the story
my zenfone is z00ad 4ram 64gb version, everything was fine until recently, i tried upgrade to Android M using asus flash tool with the latest raw file provided by realyoti, as a result got it hard bricked, black screen no vibration and pc could not detect the device too
took it to a repair center (there is no official asus service center in my country), they were successful doing a boot repair but couldn't flash any roms ,they told me that they had to replace the hard drive of the device, did so but still took them more than a week to call me saying the phone is ready
they somehow changed my phone to a "Z00ADA" variant with a rooted CN rom, the serail number was 111111111 in the settings, but in the bootloader the serial number was 0123456789..G, and my imei was different from what the box said but since they were both in the back of my phone i assumed it is ok. there were too many Chinese apps and no gapps, so i decided to change to ww version, but there were no recovery and when i tired to boot into recovery phone just booted into the bootloader instead, let the repair technician know asked him why there is no recovery told me that he had to replace the motherboard to do that and that i should use the device as is or give him yet more time to solve the recovery and Z00ADA version, it was nearly a month so i told him no thanks
found the guide on how to do it myself , using fastboot comands and upgraded straight to the latest android M, by the time i finished the typing fastboot reboot that i noticed the op had written its best to flash a L rom before flashing M rom ( which i didnt, and since there was no APD.IMG in the MM rom i skipped flashing it) phone booted up perfectly though
upon connecting the phone pc still recognized the device as Z00ADA when the bootloader was Z00AD, strange!
phone was working fine except for the fast-charge which was working sometimes and not the other times and the com process.phone.stopped working error
then one morning when i restarted the phone it didn't turn back on, thought it is because of the come.phone .process so wiped cache did a factory reset but ran out of battery when booting up. recharged it when i got home and phone booted up but those two problems i mentioned was persistent, then fastcharging stopped working and it was taking me 8 hours to recharge, decided to flash again but pc was not recognizing the device, used sd card to flash the update zip and did a factory reset, phone was ok with those same problems
found a guide deleted every intel driver using a tool and got the pc to recognize my device as Z00AD, since fastcharging was ok in android LP tried to downgrade , used fastboot comands flashed everything but got error in
fastboot oem partition /tmp/partition.tbl
fastboot flash /tmp/partition.tbl partition.tbl
phone was stuck in boot screen , used asus flash tool flashed the LP raw and phone booted up
but the screen was acting up and was doing things on its own, used asus flash tool to upgrade to MM raw , phone booted up screen was fine except when i tried the one layer mode in asus zenui launcher, changed back to two layer mode and it is fine til now, fast charging is working too
but now i have this strange problem, i have to plug the charger in and switch the phone on otherwise after loading the home screen phone will shut down though i have like 70 in the battery , and sometimes the phone shuts down when im using it
please tell me what to do , had i messed the phone changing from Z00ADA to Z00ad , it was working fine on that cn rom
too long didn't read, my phone got bricked , had it repaired and upgraded to android MM, but the phone either shuts down automatically or doesn't stay in home screen if it is not plugged
please help me solve it and change my serial number to the original one
thanks in advance for your replies:angel:
Edit: so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue, it didn't turn off, used it for a whole day like that for testing purposes and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and rebooted the system, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
Edit 2: i took out the sim cards and phone was ok . it was not turning off, tested all apps installed and i noticed every app is working fine except for camera, the second i clicked to take a picture the phone shut down and was not switching back on unplugged, how ever i can take pictures and have both sims installed and phone is functioning properly when it is plugged to power supply. can somebody help me fix it?
here are two scenarios, 1 battery is bad. second if they really changed storage chip, there is a pretty good chance it came with pre flashed firmware. which might be causing the issue. very first of all open your phone and post high resolution images of the motherboard from both sided. i will try to look into it then only i will tell you what to follow. serial is not an issue though. it should not cause any issue in booting or rebooting. we can get it back first you need to resolve reboot issue!
don't forget to remove heat spreading plated before clicking images
sukhwant717 said:
here are two scenarios, 1 battery is bad. second if they really changed storage chip, there is a pretty good chance it came with pre flashed firmware. which might be causing the issue. very first of all open your phone and post high resolution images of the motherboard from both sided. i will try to look into it then only i will tell you what to follow. serial is not an issue though. it should not cause any issue in booting or rebooting. we can get it back first you need to resolve reboot issue!
don't forget to remove heat spreading plated before clicking images
Click to expand...
Click to collapse
hi there buddy thanks for the quick reply, it was working fine without me updating it from cn build straight into MM but ok ill take your advice , will have to watch a video on how to disassemble it, will post pictures and what do you mean by "don't forget to remove heat spreading plated before clicking images" .are there any instructions to follow when taking pictures?
cjdandy said:
hi there buddy thanks for the quick reply, it was working fine without me updating it from cn build straight into MM but ok ill take your advice , will have to watch a video on how to disassemble it, will post pictures and what do you mean by "don't forget to remove heat spreading plated before clicking images" .are there any instructions to follow when taking pictures?
Click to expand...
Click to collapse
i meant about plates covering the components. If you are inexperienced, Better do not take out the mother board. Just one thing, remove the back panel and click pic without removing anything. also disconnect battery connector and reconnect it.
sukhwant717 said:
i meant about plates covering the components. If you are inexperienced, Better do not take out the mother board. Just one thing, remove the back panel and click pic without removing anything. also disconnect battery connector and reconnect it.
Click to expand...
Click to collapse
yeah you guessed right i am a toatal noob when it comes to taking it apart,lol ill do that and just remove the back cover as a last resort since i am a noob
and i kinda felt it is somehow software related, cause i used to be able to change my network type using *#*#4636#*#* code to lte only but now no matter how hard i push on that it reverts back to lte/gsm auto
so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue it didn't turn off used it like that for testing and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and booted the system it, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
i booted into recovery and there they were these logs which alright i had no idea what they were most of the times but at 96% percent of the log file i saw something, it said the kernel header is different from the kernel built kernel must be built with correct footer, do you guys see that too?
edit: i noticed that simcards are causing the problem turned the airplane mode on and phone switched back on unplugged, camera app is also making the phone shut down. what do you think it is, is there a fix?
cjdandy said:
yeah you guessed right i am a toatal noob when it comes to taking it apart,lol ill do that and just remove the back cover as a last resort since i am a noob
and i kinda felt it is somehow software related, cause i used to be able to change my network type using *#*#4636#*#* code to lte only but now no matter how hard i push on that it reverts back to lte/gsm auto
so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue it didn't turn off used it like that for testing and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and booted the system it, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
i booted into recovery and there they were these logs which alright i had no idea what they were most of the times but at 96% percent of the log file i saw something, it said the kernel header is different from the kernel built kernel must be built with correct footer, do you guys see that too?
edit: i noticed that simcards are causing the problem turned the airplane mode on and phone switched back on unplugged, camera app is also making the phone shut down. what do you think it is, is there a fix?
Click to expand...
Click to collapse
i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
sukhwant717 said:
i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
Click to expand...
Click to collapse
i sure hope so thanks, i will remove the back cover and reconnect the battery connector under the volume down button when i get home and will snap some photos for you to see, i have it turned off but i assume it will, will test it and get back to you on that
IMEI1:3577980....
IMEI2:3577980....
the Last 3 digits are different , would imei s change if they changed storage chip? what do they need to replace for that to happen ?
but serial number is changed to 01234....F can i change the serial number using the whatchamacallit sofamia tool?
thanks for bearing with me
QUOTE=sukhwant717;78780989]i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei[/QUOTE]
attached the pics buddy, will you take a look
reconnected the battery connector but didnt solve it
cjdandy said:
QUOTE=sukhwant717;78780989]i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
Click to expand...
Click to collapse
attached the pics buddy, will you take a look
reconnected the battery connector but didnt solve it[/QUOTE]
which firmware version you are currently on?
are your imeis correct?
put your phone on charge overnight only with a genuine or good charger. we will solve it other day. which time zone you live in?
sukhwant717 said:
which firmware version you are currently on?
are your imeis correct?
put your phone on charge overnight only with a genuine or good charger. we will solve it other day. which time zone you live in?
Click to expand...
Click to collapse
yes IMEIs are correct sir
I am on the latest marshmellow build (WW_ZE551ML_4.21.40.352_20170623)
IFWI version: 0094.0183
serial number-0123456789ABCDEF ( dunno why asus flash tool doesn't detect the correct SN!)
ok i will put it on charge overnight, +3:30 time zone iran
phone was on a CN z00ADA version and was rooted and had no recovery when i got it back from the repair center and was ok (used it like that for two days). using your Guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785) , i directly flashed WW_ZE551ML_4.21.40.352_20170623.raw
sukhwant717 said:
Flashing Firmware Without AFT:
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. don't worry, first boot gonna take a little longer time. so have patience and watch some funny video till phone boots up.
Now you can install any firmware version via adb sideload. make sure to install latest lollipop firmware before flashing Marshmallow. follow the guide to sideload.
Click to expand...
Click to collapse
there was no APD.img, ifwi-prod.bin, token MFG_BOM_Full.bin, in the extracted raw file so i skipped flashing APD.IMG and flashed R60_BOM_FULL.bin, ifwi.bin. then i noticed this line "make sure to install latest lollipop firmware before flashing Marshmallow" and though i had killed my phone, but luckily phone booted up and i sighed in relief. phone was still OK except for the "unfortunately the process com.android phone has stopped" error which i wiped the cache for but didn't go away , so thought heck who cares it a minor error and i am gonna use it as it is, used the phone like that for almost a week, then one morning out of the blue when i tapped restart the phone the phone didn't load the zenui. and was shuting down, booted to recovery reseted to factory settings and now i ran out of battery, got back home plugged it in and phone booted up normally, the "unfortunately the process com.android phone has stopped" was still there and sometimes as i was playing games it would pop up and make the phone shut down, flashed the raw this time using asus flash tool no error message bu phone started this shutting down pattern.
trying to fix it i bricked my phone and using your guide and xfstk-downloader, phone was alive again and i was on your mentioned WW_ZE551ML_2.20.40.194_20160713 rom. and even i was getting ota updates , and phone was not shutting down but when i downloaded the ota update the phone did not restart and when i switched it on no update installing process was shown and phone booted up but was shutting down so flashed the rom using asus flash tool again and was OK used for a whole day to test if it is not shutting down and it was OK , updated to marhmellow and phone started shutting down automatically again, and even sometimes the touch screen acts up and press things on its own and starts programs and whatnot's
I am counting on your help to solve it, thanks a lot man
cjdandy said:
yes IMEIs are correct sir
I am on the latest marshmellow build (WW_ZE551ML_4.21.40.352_20170623)
IFWI version: 0094.0183
serial number-0123456789ABCDEF ( dunno why asus flash tool doesn't detect the correct SN!)
ok i will put it on charge overnight, +3:30 time zone iran
phone was on a CN z00ADA version and was rooted and had no recovery when i got it back from the repair center and was ok (used it like that for two days). using your Guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785) , i directly flashed WW_ZE551ML_4.21.40.352_20170623.raw
there was no APD.img, ifwi-prod.bin, token MFG_BOM_Full.bin, in the extracted raw file so i skipped flashing APD.IMG and flashed R60_BOM_FULL.bin, ifwi.bin. then i noticed this line "make sure to install latest lollipop firmware before flashing Marshmallow" and though i had killed my phone, but luckily phone booted up and i sighed in relief. phone was still OK except for the "unfortunately the process com.android phone has stopped" error which i wiped the cache for but didn't go away , so thought heck who cares it a minor error and i am gonna use it as it is, used the phone like that for almost a week, then one morning out of the blue when i tapped restart the phone the phone didn't load the zenui. and was shuting down, booted to recovery reseted to factory settings and now i ran out of battery, got back home plugged it in and phone booted up normally, the "unfortunately the process com.android phone has stopped" was still there and sometimes as i was playing games it would pop up and make the phone shut down, flashed the raw this time using asus flash tool no error message bu phone started this shutting down pattern.
trying to fix it i bricked my phone and using your guide and xfstk-downloader, phone was alive again and i was on your mentioned WW_ZE551ML_2.20.40.194_20160713 rom. and even i was getting ota updates , and phone was not shutting down but when i downloaded the ota update the phone did not restart and when i switched it on no update installing process was shown and phone booted up but was shutting down so flashed the rom using asus flash tool again and was OK used for a whole day to test if it is not shutting down and it was OK , updated to marhmellow and phone started shutting down automatically again, and even sometimes the touch screen acts up and press things on its own and starts programs and whatnot's
I am counting on your help to solve it, thanks a lot man
Click to expand...
Click to collapse
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
yes i did download it and have that rom and im gonna download the ze550 files too and charge my phone overnight ,thanks
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
ready when you are sir
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
I still have the issue and dunno why my SN doesn't get restored to the original one
could you please help me
Edit: i rooted the phone and using this guide https://forum.xda-developers.com/sho...6&postcount=28 i was able to restore my SN but my BT address and mac remained unchanged, and i noticed there is also a config folder that contains this information and in its locale config it is stated that my phone model is 550ml when its 551ml, can you please share the contents of the config and factory folder , change your SN and mac address to zero so i can replace them with mine, i would really much appreciate your help