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
Related
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.
I'm something of a noob here, so I appreciate your patience and help.
My wife's Nexus 5x applied the latest update for 7.1.1 and her phone then fell victim to the dreaded bootloop. I was able to get through this guide to apply a rescue OTA: https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view (sorry, I can't post the hyperlink to an external site since I'm so new here, lol).
All of the steps completed down to step 21, when I tried reboot after the update - it rebooted then went right back into the boot loop.
The OTA I used was for Bullhead N4F26O (which is the one I should use based on the guide). I also tried N4F26I, but the OTA failed and it went straight to the bootloop.
I ran out the battery, charged it a bit, and tried again, but ran into the same problem (update completes, reboot, bootloop starts again).
Does anyone else have any more ideas on what I can try? At this point all I really care to do is recover any photos I can from the device (my wife forgot to setup image backup on her phone and USB debugging was never turned on). Google Fi already offered to send out a replacement, so I'm not worried about getting the device fully functional again.
Thanks for your help.
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
LeChuck5000 said:
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
Click to expand...
Click to collapse
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Tulsadiver said:
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Click to expand...
Click to collapse
I can get it into fastboot, and can sometimes get it into recovery (but not consistently...it often just goes into the bootloop when I try to launch recovery).
To apply the update I just followed the guide I linked to in my OP. First, installed the adb, fastboot, & usb drivers on my computer. I then put the phone into recovery, and wiped the partition cache. I then connected the phone to my PC, picked Apply update from ADB on the phone, and ran adb sideload c:\MyNexus\bullhead-ota-n4f26i-06953aec.zip from the command line on my PC.
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Arrivale said:
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Click to expand...
Click to collapse
You stick it in the oven? Use a heat gun? How hot/long?
tallgrasshawk said:
You stick it in the oven? Use a heat gun? How hot/long?
Click to expand...
Click to collapse
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
How else?
Arrivale said:
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
Click to expand...
Click to collapse
I don't have a heat gun, how else can I heat it? Also, excuse my ignorance, I'm new to phone thing since my Nexus 5x went into bootloop last week I've learned a lot, fast. Where exactly is the EMMC? How else can I heat it? I'm desperate to get this phone working as I just went overseas and Nexus won't send a replacement here
My attempt at the Rescue OTA fails in step 19, I can't get the device state to be "unlocked" does anyone know how to unlock it when the phone is in bootloop? (So all I really have access to is command prompt, which says I can't unlock the oem) HELP!?!
Zenfone2 ZE550ML Z008 No Sound call &Flash image failure (FAILED (wrong image format)
OK, after some search and trying, i really need more help from xda community, especially asus zenfone 2 ZE550ML user and developer and others too
so, this is whats happen so far:
i got this phone from my sister, asus zenfone 2 ZE550ML Z008 2GB memory with weird problem...
the phone cannot send/receive sound from phone calling.
the call can be made, but not any sound can be heard, in and out...
well, maybe the mic and speaker broken, i found that it is not the case...
why? because any messenger apps (Whatsapp, BBM, IMO, Line) which have voice call, worked just fine, no problem at all
i tried self test (using calulator .12345+= trick) everything working just fine too.
it happen too even when using earphone (which i already tested again worked fine with Whastapp, BBM, Line, IMO, maybe other apps too). the earphone is fine, normal and working OK
i tried doing factory reset, failed, after some search, for anything that can be done, it said disable ok google detection, turn ON dial pad, update asus call screen, etc,
let me know if there is more things to try...
i also already try wipe factory reset and cache from recovery mode, still no luck...
i also find that the SIM2 IMEI is unknown/null, but SIM 1 IMEI still normal...
tried changing to SIM 2, and as expected, it didnt get any signal, so cannot be used
i tried all OTA update to the latest update, and the problem still exist
so i think i should flash using Asus Flash Tools (AFT) using flash raw file so it can fix this problem, to make the phone really like new again...
but, another problem arise...
i already prepare all driver and AFT and raw file...
in device manager, everything fine, no any yellow/red mark to any device...
boot to fastboot mode, connect the usb cable, detected in AFT and status is connected with blue circle.
but i cannot flash when i click start, after a while, yellow circle, then red circle with note "Flash image failure (FAILED (wrong image format))"
it failed and not flash the phone, the phone can still be used normal like nothing
happen (but still with the problem i mention )
OK, maybe, the file i downloaded corrupted, so i download again few times, but it keep showing the same error
"Flash image failure (FAILED (wrong image format))"
i tried download other version, and error still the same
i also tried different version of AFT from 1.0.0.14 until the latest one, 1.0.0.55 , and still same error...
i am sure my phone is ZE550ML since in the back of the phone there is written Model : ASUS_Z008, or am i wrong??
after that, i tried flash using ADB and zip file from asus site, with the most older file, which is "UL-Z008-WW-2.12.40.9-user.zip" but cannot be done, it is said cannot flash with older version than the current firmware
so i download the latest firmware "UL-Z008-WW-4.21.40.191-user.zip" which is marsmellow, hoping my problem can be fix
but, the problem still exist...really exactly the same way...really confusing
tried self test again, yup, 100% still the same problem...
so now, i need advice and any info, how to flash using AFT and raw file...??
or how to fix the "Flash image failure (FAILED (wrong image format))" error.
FYI, this phone still not root or unlock bootloader (i suppose, because my sister just use it as it is)
but i notice in fastboot mode, the "BOOTLOADER VERSION - Unknown" is it mean it already unlock or what??
Please help me, any advice, suggestion or info highly appreciated...
thx, and sorry for the poor english writing
kim7tng said:
OK, after some search and trying, i really need more help from xda community,
especially asus zenfone 2 ZE550ML user and developer and others too
so, this is whats happen so far:
i got this phone from my sister, asus zenfone 2 ZE550ML Z008 2GB memory with weird
problem...
the phone cannot send/receive sound from phone calling.
the call can be made, but not any sound can be heard, in and out...
well, maybe the mic and speaker broken, i found that it is not the case...
why? because any messenger apps (Whatsapp, BBM, IMO, Line) which have voice call,
worked just fine, no problem at all
i tried self test (using calulator .12345+= trick) everything working just fine too.
i tried doing factory reset, failed, after some search, for anything that can be
done, it said disable ok google detection, turn ON dial pad, update asus call screen,
etc,
let me know if there is more things to try...
i also already try wipe factory reset and cache from recovery mode, still no luck...
i also find that the SIM2 IMEI is unknown/null, but SIM 1 IMEI still normal...
tried changing to SIM 2, and as expected, it didnt get any signal, so cannot be used
i tried all OTA update to the latest update, and the problem still exist
so i think i should flash using Asus Flash Tools (AFT) using flash raw file so it can
fix this problem, to make the phone really like new again...
but, another problem arise...
i already prepare all driver and AFT and raw file...
in device manager, everything fine, no any yellow/red mark to any device...
boot to fastboot mode, connect the usb cable, detected in AFT and status is connected
with blue circle.
but i cannot flash when i click start, after a while, yellow circle, then red
circle with note "Flash image failure (FAILED (wrong image format))"
it failed and not flash the phone, the phone can still be used normal like nothing
happen (but still with the problem i mention )
OK, maybe, the file i downloaded corrupted, so i download again few times, but it
keep showing the same error
"Flash image failure (FAILED (wrong image format))"
i tried download other version, and error still the same
i also tried different version of AFT from 1.0.0.14 until the latest one, 1.0.0.55 ,
and still same error...
i am sure my phone is ZE550ML since in the back of the phone there is written Model :
ASUS_Z008, or am i wrong??
after that, i tried flash using ADB and zip file from asus site, with the most older
file, which is "UL-Z008-WW-2.12.40.9-user.zip" but cannot be done, it is said cannot
flash with older version than the current firmware
so i download "UL-Z008-WW-4.21.40.191-user.zip" which is marsmellow, hoping my
problem can be fix
but, the problem still exist...really exactly the same way...really confusing
tried self test again, yup, 100% still the same problem...
so now, i need advice and any info, how to flash using AFT and raw file...??
or how to fix the "Flash image failure (FAILED (wrong image format))" error.
FYI, this phone still not root or unlock bootloader (i suppose, because my sister
just use it as it is)
but i notice in fastboot mode, the "BOOTLOADER VERSION - Unknown" is it mean it
already unlock or what??
Please help me, any advice, suggestion or info highly appreciated...
thx, and sorry for the poor english writing
Click to expand...
Click to collapse
are you on M firmware ?
If yes ,factory reset in settings first
Then search ASUS support for downgrade to LP firmware for Z008(whatever that is)
put on internal sd or dload straight there. Remove ext sd btw before and
Reboot
See if that fixes your probs
edit just seen you cannot factory reset. What does work , lets start with that ?
What firmware are you currently on ?
Date build etc ?
Stock recovery installed ?
timbernot said:
are you on M firmware ?
If yes ,factory reset in settings first
Then search ASUS support for downgrade to LP firmware for Z008(whatever that is)
put on internal sd or dload straight there. Remove ext sd btw before and
Reboot
See if that fixes your probs
edit just seen you cannot factory reset. What does work , lets start with that ?
Click to expand...
Click to collapse
yes, i am on M firmware now
since i cannot flash using AFT, i tried using adb fastboot mode, and now i am on Marshmellow...
i can do factory reset, i do it few times already in backup setting and also in recovery mode...
it just that my problem/issue with No Sound when calling is still happening.
and the IMEI on SIM 2 also still unknown/null, altough this is less priority than the first problem
kim7tng said:
yes, i am on M firmware now
since i cannot flash using AFT, i tried using adb fastboot mode, and now i am on Marshmellow...
i can do factory reset, i do it few times already in backup setting and also in recovery mode...
it just that my problem/issue with No Sound when calling is still happening.
and the IMEI on SIM 2 also still unknown/null, altough this is less priority than the first problem
Click to expand...
Click to collapse
Can you factory reset in settings
Have you got stock recovery ??
You have to bare with me , my pc is upgrading and it has all my links on it
---------- Post added at 11:54 AM ---------- Previous post was at 11:42 AM ----------
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-52.20.40.156-user.zip
If you have stock recovery.
Download this to ext sd .
In file manager , click rename and add an extra .zip on the end ,save and reboot phone
Eg>
UL-WW- bla bla user.zip.zip
timbernot said:
What firmware are you currently on ?
Date build etc ?
Stock recovery installed ?
Click to expand...
Click to collapse
i am on stock rom, android version 6.0.1
security pacth level January 1, 2017
Baseband 1603_5.0.68.9_0810
kernel version 3.10.72-x86_64_moor-gc9c9751
build number MMB29P.WW-ASUS_Z008-4.21.40.191_20161216_7769_user060020736_201603210001
still in stock recovery because i wanna make this still just like new without any mod
kim7tng said:
i am on stock rom, android version 6.0.1
security pacth level January 1, 2017
Baseband 1603_5.0.68.9_0810
kernel version 3.10.72-x86_64_moor-gc9c9751
build number MMB29P.WW-ASUS_Z008-4.21.40.191_20161216_7769_user060020736_201603210001
still in stock recovery because i wanna make this still just like new without any mod
Click to expand...
Click to collapse
Then do as advised earlier , I linked downgrade version for you
timbernot said:
Can you factory reset in settings
Have you got stock recovery ??
You have to bare with me , my pc is upgrading and it has all my links on it
---------- Post added at 11:54 AM ---------- Previous post was at 11:42 AM ----------
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-52.20.40.156-user.zip
If you have stock recovery.
Download this to ext sd .
In file manager , click rename and add an extra .zip on the end ,save and reboot phone
Eg>
UL-WW- bla bla user.zip.zip
Click to expand...
Click to collapse
yes, i think i am on stock recovery, since i never flash anything except file from asus.com named "UL-Z008-WW-4.21.40.191-user.zip"
i am downloading it, using my PC.
isnt it already in .zip files?? do i need add to become "UL-Z008-WW-52.20.40.156-user.zip.zip" ??
kim7tng said:
yes, i think i am on stock recovery, since i never flash anything except file from asus.com named "UL-Z008-WW-4.21.40.191-user.zip"
i am downloading it, using my PC.
isnt it already in .zip files?? do i need add to become "UL-Z008-WW-52.20.40.156-user.zip.zip" ??
Click to expand...
Click to collapse
yes >
UL-Z008-WW-52.20.40.156-user.zip.zip
Is how it should read in file manager , you can add the .zip from pc on sd before inserting in phone too .
Reboot
timbernot said:
yes >
UL-Z008-WW-52.20.40.156-user.zip.zip
Is how it should read in file manager , you can add the .zip from pc on sd before inserting in phone too .
Reboot
Click to expand...
Click to collapse
isnt this firmware files to downgrade to Lollipop again from MM??
after downgrade, what should i do?? because i am guessing it will be the same one too...
but still i was hoping it can fix my problem...so ill do it anyway...
i thinking that flashing using AFT is the things that (maybe) can fix my problem...
kim7tng said:
isnt this firmware files to downgrade to Lollipop again from MM??
after downgrade, what should i do?? because i am guessing it will be the same one too...
but still i was hoping it can fix my problem...so ill do it anyway...
i thinking that flashing using AFT is the things that (maybe) can fix my problem...
Click to expand...
Click to collapse
Hows it going ?
You had probs flashing in AFT according to OP
timbernot said:
Hows it going ?
You had probs flashing in AFT according to OP
Click to expand...
Click to collapse
sorry for late update, have to do other things first...
so after i rename it to "UL-Z008-WW-52.20.40.156-user.zip.zip" and put in SD card,
when i turn it on, it tell me there is update from that file. well, so i OK'ed it and then it is "installing system update"
now it go back to android lollipop...and my problem still exist the exact same way...
still cannot hear sound in and out
SIM 2 IMEI still null/unknown
so, what should i do??
what is OP?? original poster, right?? thats me
btw, after updating back to lollipop, the phone still saying there is update
kim7tng said:
sorry for late update, have to do other things first...
so after i rename it to "UL-Z008-WW-52.20.40.156-user.zip.zip" and put in SD card,
when i turn it on, it tell me there is update from that file. well, so i OK'ed it and then it is "installing system update"
now it go back to android lollipop...and my problem still exist the exact same way...
still cannot hear sound in and out
SIM 2 IMEI still null/unknown
so, what should i do??
what is OP?? original poster, right?? thats me
btw, after updating back to lollipop, the phone still saying there is update
Click to expand...
Click to collapse
I think you can now rule out it being a software problem now
``btw, after updating back to lollipop, the phone still saying there is update``
Yes , is that the same file you just downgraded to or update to M ?
timbernot said:
I think you can now rule out it being a software problem now
``btw, after updating back to lollipop, the phone still saying there is update``
Yes , is that the same file you just downgraded to or update to M ?
Click to expand...
Click to collapse
so it is hardware problem??
but how?? the mic and speaker still can be use in Whatsapp, BBM and other chat apps just fine when voice call...
in selftest, i confirm it can pass, since i hear from speaker and speak through the mic just fine too...
and also i found that, if i record the call, it file cannot be played back, and yet i can record when not calling using sound recording and the file can played to just fine...
it only cannot hear or receive sound when in calling...
now, the things i not done is flashing using AFT, which cannot be done because the wrong image error...
i wonder, why?? there must be something i miss out
kim7tng said:
so it is hardware problem??
but how?? the mic and speaker still can be use in Whatsapp, BBM and other chat apps just fine when voice call...
in selftest, i confirm it can pass, since i hear from speaker and speak through the mic just fine too...
and also i found that, if i record the call, it file cannot be played back, and yet i can record when not calling using sound recording and the file can played to just fine...
it only cannot hear or receive sound when in calling...
now, the things i not done is flashing using AFT, which cannot be done because the wrong image error...
i wonder, why?? there must be something i miss out
Click to expand...
Click to collapse
AFAIK -- you would not be allowed to downgrade if something was a miss with current software(pre-flash) of the downgrade version.
Although , i would try 1.17 AFT in my unbrick thread in my signature below -- and check that you are flashing in AFT correctly by checking unbrick video from 2:17 mins in where AFT flash begins .
I did read in another thread that you stated your serial number is OK .
When you connect in AFT if serial is corrected you flash once.
If serial is 0-F, this is incorrect and you need to do a 2 part flash in AFT to correct it.
Watch the video carefully from 2:17 mins see if you are not doing something right !
Ps , are you flashing a raw file in AFT ?
Out of curiosity, what was the file you tried to flash with the asus flash tool? Was it a raw file?
Sent from my ASUS_Z00A using Tapatalk
timbernot said:
AFAIK -- you would not be allowed to downgrade if something was a miss with current software(pre-flash) of the downgrade version.
Although , i would try 1.17 AFT in my unbrick thread in my signature below -- and check that you are flashing in AFT correctly by checking unbrick video from 2:17 mins in where AFT flash begins .
I did read in another thread that you stated your serial number is OK .
When you connect in AFT if serial is corrected you flash once.
If serial is 0-F, this is incorrect and you need to do a 2 part flash in AFT to correct it.
Watch the video carefully from 2:17 mins see if you are not doing something right !
Ps , are you flashing a raw file in AFT ?
Click to expand...
Click to collapse
sorry, i kinda not understand by that...so if i can downgrade, what does that mean??
is flashing using AFT and adb sideload the same?...i though that AFT flashing flash more deeper than adbsideload or using recovery
(i mean is that AFT do flash more things than adb sideload or OTA update, )
just like XFSTK downloader that looked wayyy more deeper flash using AFT...
i said normal, because it is not "0123456789ABCDF" but "F7AZGF00N937" (which also showed in AFT)
but, after i looked closely, its SN for a brief moment, show "0123456789ABCDF" about 2-3 seconds, i dont know whats that mean...i though just a refresh...
let me show you with a video what i mean here:
https://youtu.be/ksjVDFD2V-A
i record just now, after i press power + vol up to enter fastboot mode
yes, i tried Flash rawfile in AFT...
i download few raw files like
WW_ZE550ML_2.20.40.92_20150918.raw
WW_ZE550ML_2.20.40.156_20160815.raw
WW_ZE550ML_2.20.40.155_20160713.raw
all raw file i get from here
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
kenbo111 said:
Out of curiosity, what was the file you tried to flash with the asus flash tool? Was it a raw file?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i tried flash raw file i get from here
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
the one from "ZF2 5,5" ZE550ML"
or maybe there another raw file i should try??
oh, i rememeber a little details
so, when i tried flash using adb side load,
when i type "adb devices" in CMD directed to specified folder it show like this:
List of devices attached
0123456789ABCDEF sideload
and yet, flashing using adb sideload finish normally without any error...(but still with the same "cant hear calling" problem )
how come it not read my correct serial number??
kim7tng said:
sorry, i kinda not understand by that...so if i can downgrade, what does that mean??
is flashing using AFT and adb sideload the same?...i though that AFT flashing flash more deeper than adbsideload or using recovery
(i mean is that AFT do flash more things than adb sideload or OTA update, )
just like XFSTK downloader that looked wayyy more deeper flash using AFT...
i said normal, because it is not "0123456789ABCDF" but "F7AZGF00N937" (which also showed in AFT)
but, after i looked closely, its SN for a brief moment, show "0123456789ABCDF" about 2-3 seconds, i dont know whats that mean...i though just a refresh...
let me show you with a video what i mean here:
https://youtu.be/ksjVDFD2V-A
i record just now, after i press power + vol up to enter fastboot mode
yes, i tried Flash rawfile in AFT...
i download few raw files like
WW_ZE550ML_2.20.40.92_20150918.raw
WW_ZE550ML_2.20.40.156_20160815.raw
WW_ZE550ML_2.20.40.155_20160713.raw
all raw file i get from here
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Click to expand...
Click to collapse
Check you have driver >
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
When you press vol+ serial is corrected and you only need to flash once in AFT
AFT flash is fastboot mode flash .
Have you checked the video ? highlighted (clicked on ) your serial number, it turns blue ? before flashing
Use the AFT i have in my unbrick thread .
Also , tick erase data in AFT before hitting start :good:
AFT >
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Video of AFT settings and flash procedure from 2;17 mins in
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
Note.....
If this above is done correctly then you should be-able to flash it in AFT
Downgrading from M to LP which you succeeded with checks everything re software is OK before flashing , which you succeeded with.
I notice you were worried IF the bootloader was unlocked previously in the other thread and that this maybe affecting the AFT flash .
You said you got this phone off your sister ? Does she know if she unlocked bootloader ?.
source >
https://forum.xda-developers.com/ze...ool-failed-t3574763/post71516049#post71516049
"...........
in fastboot mode, my serial number is looks normal but "bootloader version - unknown"...
i wonder if the phone bootloader have been unlock, so it cannot be flash using AFT. ..........."
Heres , what i suggest might have happened although NOT too sure.
Someone previous bricked the device.
Didnt flash or succeed to restore serial correctly ... Then used other software to create a serial number which did`nt correspond with the imei .
This is the only thing i can think of .
This doesnt explain how downgrade version succeeded though .
timbernot said:
Check you have driver >
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
When you press vol+ serial is corrected and you only need to flash once in AFT
AFT flash is fastboot mode flash .
Have you checked the video ? highlighted (clicked on ) your serial number, it turns blue ? before flashing
Use the AFT i have in my unbrick thread .
Also , tick erase data in AFT before hitting start :good:
AFT >
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Video of AFT settings and flash procedure from 2;17 mins in
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
Note.....
If this above is done correctly then you should be-able to flash it in AFT
Downgrading from M to LP which you succeeded with checks everything re software is OK before flashing , which you succeeded with.
I notice you were worried IF the bootloader was unlocked previously in the other thread and that this maybe affecting the AFT flash .
You said you got this phone off your sister ? Does she know if she unlocked bootloader ?.
source >
https://forum.xda-developers.com/ze...ool-failed-t3574763/post71516049#post71516049
"...........
in fastboot mode, my serial number is looks normal but "bootloader version - unknown"...
i wonder if the phone bootloader have been unlock, so it cannot be flash using AFT. ..........."
Heres , what i suggest might have happened although NOT too sure.
Someone previous bricked the device.
Didnt flash or succeed to restore serial correctly ... Then used other software to create a serial number which did`nt correspond with the imei .
This is the only thing i can think of .
This doesnt explain how downgrade version succeeded though .
Click to expand...
Click to collapse
Yes, i have watch the video...
and yes, the State is blue circle just like in the video...
the different is that after i click start, it turns yellow for few seconds and afterthat, show red circle with error "Flash image failure (FAILED (wrong image format))"
i will show u the video when i got time to do it...but maybe tommorow, since now i got something to do...
i am not in a hurry after all, and i really thankfull you helping me sharing your knowledge...
i wonder because the the stock bootloader version said unknown...i am guessing, with normal phone everything should have some status or whatever, right?? maybe some number or code...
what is the status with normal phone looked like?? or is it normal for un-mod phone to have bootloader version unknown??
i cannot compare to other phone, because i only got this 1 phone...
can you show me what the normal fastboot mode looked like?? with all other status, so i can get more picture of it
yes, i got this from my sister...and i believe she doesnt know anything like this...she is just pure user type, know what i mean, right...
but i dont know if she ever bring this phone to the service or not, i gonna ask her next time i meet her...she is not in the same house with me...
and she bought this phone brandnew from official store, i believe...
and the serial number detected on AFT is the same as number in the back of the phone, which is "F7AZGF00N937"
and also, as far as i know, this phone never bricked (this bricked mean you cannot enter the OS to use the phone, right? like bootloop or cannot start at all)
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.
steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
redchigh said:
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
Click to expand...
Click to collapse
The LG driver you've installed on your laptop is most likely no longer functional for the phone. If it shows in Device Manager when you're trying to connect it, uninstall it (mine didn't work either after unlocking/using FWUL, or something else, for whatever reason).
Once the current driver is uninstalled, turn off your computer, plug your phone in with the USB cable and then turn on the computer and let Windows install the driver now (It worked on mine).
See the attachment below for a screenshot of the current driver for my LG G4 that is working completely.
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
redchigh said:
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
Click to expand...
Click to collapse
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
sdembiske said:
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Click to expand...
Click to collapse
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
sdembiske said:
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
Click to expand...
Click to collapse
Thanks for the reminder, I'll try to remember.
redchigh said:
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
Thanks for the reminder, I'll try to remember.
Click to expand...
Click to collapse
OK - one last thing to try if you want to try it. Using the power and volume keys, see if you can get into Recovery mode to do a hard factory reset
- refer to this link for the how-to for entering Recovery mode: https://www.androidexplained.com/lg-g4-recovery-mode/