Develop Bugs

Black screen, no fastboot

I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..

If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59

Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.

The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/

freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...

Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.

freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...

familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone

freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^

familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.

freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^

[Q] flashed tmo on att d850 HELP!

I just flashed a rom on my d850 and now the screen wont turn on the phone is completely unresponsive I don't know what to do I can't even get the phone to boot some one help me im sure I just bricked the phone..

sriv2102 said:
I just flashed a rom on my d850 and now the screen wont turn on the phone is completely unresponsive I don't know what to do I can't even get the phone to boot some one help me im sure I just bricked the phone..
Click to expand...
Click to collapse
First, what rom did you flash and how did you flash it?
Try this as well:
Pull the battery, press the power button for a few seconds. Put the battery back in and press the power button again. Pop the battery out a 2nd time and then put it back in. See if it turns on.
If that doesn't work, pull the battery and hook the phone up (without the battery) to a computer and again see if it turns on and shows up in device manager.
Flashing the wrong rom should only result in a non-booting situation. If you have a custom recovery installed, you should be able to still get into that. The d850 has some serious issues with successfully rebooting in general (which can be resolved by the two suggested procedures above), so I would suspect that before worrying about a brick.
Lastly, the d850 requires bumped ROMs to get by the locked bootloader. The d851 (T-Mobile version) does not have a locked bootloader, so the roms are not bumped and will of course fail to boot.
Once you get back into recovery, just wipe all partitions except for internal storage/sd card and install a correct rom.

nicknc said:
First, what rom did you flash and how did you flash it?
Try this as well:
Pull the battery, press the power button for a few seconds. Put the battery back in and press the power button again. Pop the battery out a 2nd time and then put it back in. See if it turns on.
If that doesn't work, pull the battery and hook the phone up (without the battery) to a computer and again see if it turns on and shows up in device manager.
Flashing the wrong rom should only result in a non-booting situation. If you have a custom recovery installed, you should be able to still get into that. The d850 has some serious issues with successfully rebooting in general (which can be resolved by the two suggested procedures above), so I would suspect that before worrying about a brick.
Lastly, the d850 requires bumped ROMs to get by the locked bootloader. The d851 (T-Mobile version) does not have a locked bootloader, so the roms are not bumped and will of course fail to boot.
Once you get back into recovery, just wipe all partitions except for internal storage/sd card and install a correct rom.
Click to expand...
Click to collapse
hey so i flashed the new port of the g4 on my phone and i believe i bricked the device i am not able to reach my recovery the method you mentioned did not work but plugging the phone in with out the battery did get the screen on. I'm not sure what else to do at this point I do greatly appreciate your help dude!..

sriv2102 said:
hey so i flashed the new port of the g4 on my phone and i believe i bricked the device i am not able to reach my recovery the method you mentioned did not work but plugging the phone in with out the battery did get the screen on. I'm not sure what else to do at this point I do greatly appreciate your help dude!..
Click to expand...
Click to collapse
When you say you got the phone on, what do you mean?
If it is on and showing up as a phone in Windows, why not just use the LG recovery tool and flash back to stock, then start over?

nicknc said:
When you say you got the phone on, what do you mean?
If it is on and showing up as a phone in Windows, why not just use the LG recovery tool and flash back to stock, then start over?
Click to expand...
Click to collapse
it jus shows that the battery is missing nothing else as soon as i replace the battery the screen stays black im not able to boot into download or recovery

sriv2102 said:
it jus shows that the battery is missing nothing else as soon as i replace the battery the screen stays black im not able to boot into download or recovery
Click to expand...
Click to collapse
Does it show up in windows at all?

it does under device manager i can find it .

nicknc said:
Does it show up in windows at all?
Click to expand...
Click to collapse
it does show up in windows and i have the drivers installed still.

sriv2102 said:
it does show up in windows and i have the drivers installed still.
Click to expand...
Click to collapse
Give the lg firmware flash and recovery tools a go then. There are several threads on here dealing with unbricking phones that detail what you need to do.

nicknc said:
Give the lg firmware flash and recovery tools a go then. There are several threads on here dealing with unbricking phones that detail what you need to do.
Click to expand...
Click to collapse
I did use the lg flash tool but it was not successful im not sure what else to try..

sriv2102 said:
I did use the lg flash tool but it was not successful im not sure what else to try..
Click to expand...
Click to collapse
Did you solved it? I have the same problem, the screen only turns on when i charge the phone

G4 Freezes & Bootloops

Hi!
So earlier today I was using the phone as usual and I decided to update some apps because I had wifi available for once.
I go to the Xposed installer and updated a youtube addon and Gravitybox, about 20 seconds later the phone freezes and turns off (before I even get to reboot myself).
Since then it continues to bootloop - I try to access TWRP and the phone just freezes on the kernel bootscreen, or restarts.
My computer won't recognize the phone and there's nothing I can do.
Sometimes my phone actually goes further than just the kernel bootscreen, it acctually boots the system, but it always freezes before I get to do anything (but the time is random)
Although the phone doesn't freeze when I'm in the recovery menu (the white one, but as soon as i click yes for twrp, it gets stuck)
I have a regular H815, BL is unlocked and im using the Genysis Rom. (Marshmallow)
What I've tried:
Access TWRP through ADB
Access TWRP through the phone ( vol down etc)
Access Download Mode, computer won't recognize the device.
Boot normally.
Remove SD/Sim and do the above.
I'm stumped guys. So I came here. Any help would be apprecieted.

Deciding to bump this popular thread by updating my progress.
I managed to make download mode work, I flashed a KDZ matching my current rom, it was successfull according to the LGUP program, but the phone is still rebooting, I cleared data, but it's still not booting up.
I later tried downgrading and wiping the whole phone. Flashed the original rom i had when I bought the device... The screen with Lg and (Bootloader is unlocked) is still the only screen I get, anything I do doesn't seem to work and I'm starting to lose hope.
Although I've noticed, that everytime I flash KDZ, it still shows the same rom of origin, even if i just flashed another, meaning the flash wasn't effective. Is there any other programs than LGup? the LG flashtool won't find it, although Up will
It seems like the phone broke completely, yet it's still actually starting up. After googling I found that there was a common flaw with it actually bootlooping because of hardware issues - which I'm starting to think is the issue.

What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck

innocence07 said:
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
Click to expand...
Click to collapse
It's definetly a 505... lol.
y bootloaders been unlocked, meaning warranty is void. How would you reccomend hiding the fact its UBL?
Perhaps I could dirtyflash it with the wrong kernel, making it completely bricked. And just cluelessly leave it for warranty, but although I feel like that's a risk.

As far as I know there is no going back once you Unlock your bootloader and no warranty will be given whatever you do as IMEI of your phone is sent to LG when you unlock the device thru their site so when you do claim your warranty they will check to see if yours are unlock/lock. If you still push for a warranty they will charge you 200-250 dollars(estimated cost in our country) for the mobo replacement. Friendly advice, since its a paperweight now you could just sell it on ebay for 80-100 so dollars and buy a new phone.

zenfone 2 serial number and shutting down PROBLEM, HELP ME!

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

Question Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.

PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image

DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

Read this thread if you haven't...

blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.

PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.

DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.