Related
So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.
Xnin47 said:
So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.
Click to expand...
Click to collapse
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?
timbernot said:
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?
Click to expand...
Click to collapse
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?
Xnin47 said:
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?
Click to expand...
Click to collapse
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:
timbernot said:
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:
Click to expand...
Click to collapse
Unfortunately, No it's still not okay.
Xnin47 said:
Unfortunately, No it's still not okay.
Click to expand...
Click to collapse
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
timbernot said:
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?
Xnin47 said:
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?
Click to expand...
Click to collapse
Seems like you didn't need any help.
timbernot said:
Seems like you didn't need any help.
Click to expand...
Click to collapse
The problem just seems very weird to be a hardware problem , So, again, after charging my phone up to 100 percent, booted it up to Android and then unplugged it, and I had about a minute of activity now before it shuts down. Again in recovery or boot loader, it never shuts down.
Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:
timbernot said:
Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:
Click to expand...
Click to collapse
Tried it now, still shuts down.
Xnin47 said:
Tried it now, still shuts down.
Click to expand...
Click to collapse
If its out of warranty , i would first check all connections inside phone ,
it could be battery
it could be main board or usb board.
If it were battery though , it should shut down connected to lower amp pc usb2.
Not much you can do really apart from above, usb boards are cheap`sh to buy, maybe worth the gamble ? Obviously if connections dont fix before ditching if main board. Try a discon of all connections and reconnect before ditching
I have the EXACTLY same problem.
Did you solved?
Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!
neves4 said:
Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!
Click to expand...
Click to collapse
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!
Xnin47 said:
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!
Click to expand...
Click to collapse
Hey dude! I've replaced my battery 3 weeks ago based on a Brazilian forum and it was, indeed, the culprit haha. Now everything is back on track again.
Thanks a lot for the answer
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.
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Zinnz said:
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Click to expand...
Click to collapse
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
fireclouu said:
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
Click to expand...
Click to collapse
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Zinnz said:
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Click to expand...
Click to collapse
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
There are Deep Flash Cables, I don't know if those work on Poco F3..
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
Just wanna ask a few questions to exclude them
Have you tried using a different USB cable /different USB port on your pc?
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
If you do think it's a hardware issue, it couldn't hurt to flash to stock and see what service center / xiaomi can do. I just wouldn't mention anything about the whole flashing business lol. But yeah, they might swap it out for ya best case scenario. But might be without a phone for awhile :/
fireclouu said:
View attachment 5686001
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
Click to expand...
Click to collapse
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Have you tried using a different USB cable /different USB port on your pc?
Click to expand...
Click to collapse
yup i thought my cables are faulty so i borrow other cable thats also come from xiaomi
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Click to expand...
Click to collapse
done that too, I formatted the device before flashing it again, only dirty flash on eu update, after my issue arises ive done clean flash, does also too before reflashing stock rom on fastboot
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
Click to expand...
Click to collapse
done as well, even on stock rom, i also lock my bootloader just to be sure, but still at 100%
one thing I also did was manually flashing persist but it wouldnt let me in, I tried also on recovery terminal, via orangefox, and twrp.
tried flashing persist manually too using
Code:
dd
, output says it pushed successfully but I dont think so. fastboot disabled flashing persist, needs edl mode.
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
oh this is new to me, okay ill try bootloader, wish me luck flash it rn
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
didnt fixed too, i even booted to fastbootd tried flashing there but boot_ab inaccessible, only in normal fastboot
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
cyanGalaxy said:
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
Click to expand...
Click to collapse
xiaomi fked up the system now blackmarket abuse this kind of restrictions
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Rstment ^m^ said:
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Click to expand...
Click to collapse
its true , im just trying to figure this out myself if possible or not, accessing service center here is much more troublesome rather fixing it in such way i think possible
but yeah ill update soon enough, tomorrow will be my only day off for a week, will definitely take a visit, wish me luck!
update: i sent my phone to mi authorized drop points yesterday. expected to get it repaired within 2 weeks and to pick it up next month.
update: today Ill pickup my device, will ask what could be the cause of the issue
fireclouu said:
update: today Ill pickup my device, will ask what could be the cause of the issue
Click to expand...
Click to collapse
Good luck! Let us know
so I got the device, support told me about the issue: battery only replugged, no other service, no replacements needed, seems some wirings got loose.
Ive read similar incident here, s/he only did replug the cable, got it fixed. Same issue on my end
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.