Develop Bugs

[Q] Nexus 7 (2013) 4.4 KRT16S Touch Screen Dead

Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!

red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk

Help
frarredo said:
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine

red_ferrari007 said:
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
Click to expand...
Click to collapse
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk

frarredo said:
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC

red_ferrari007 said:
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
Click to expand...
Click to collapse
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk

Flashing Help
frarredo said:
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks

red_ferrari007 said:
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
Click to expand...
Click to collapse
I can't say for sure that unlocking the bootloader will solve your issue but it will for sure wipe your device. I would recommend creating a back up, but since you can't enable USB debugging to create a backup using adb, you are most likely going to need to be okay with losing all your data first.
As far as I know, I Dont know of any way to enable USB debugging without going into settings first. =\
Check the forums?
I'm at work right now, and I'm also not familiar with the process on a PC. I know how to do it on a mac, since that's what I use and am familiar with. I know that for windows its a very similar process but there are some device specific drivers that you must download and install on your machine before hand.
Without a computer in front of me right now ( I'm at work ) I can't tell you exactly what to do for a PC
Look online there are tons of guides also check you tube.
I should be free later around 2 or 3pm ( pacific ) and if you can't figure it out and would still like to my help. Id be happy to help you then.
Sent from my Nexus 5 using Tapatalk

red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?

i am ready !!!
sfhub said:
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
Click to expand...
Click to collapse
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!

red_ferrari007 said:
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
Click to expand...
Click to collapse
First step, do you have the USB drivers from google installed? If not download/install from here:
http://developer.android.com/sdk/win-usb.html
Then boot into bootloader (Press/Hold Power+VolDown until bootloader menu comes up)
Then download and unzip this file on your PC
http://forum.xda-developers.com/attachment.php?attachmentid=2405103&d=1384987176
Connect your tablet to the PC via USB cable.
Open up command prompt
Go into the razors-krt16s directory from the unzipping of above file.
type in command line
fastboot oem unlock
follow the directions on the screen. You need to use volup to select yes, and Power to accept.
it will proceed to wipe your user data.
post back when you are done.

i am ready !!!
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset

red_ferrari007 said:
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
Click to expand...
Click to collapse
Have you unlocked the bootloader?
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
If you have unlocked the bootloader, follow the directions in this post to flash JSS15J
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
I am suggesting JSS15J instead of JSS15R because it is the closest factory image to JWR66N that you can get.

DONE !!!
i think its done
the LOCK STATE: UNLOCKED is shown

which u recommend ?
Should I proceed with JSS15J ???

red_ferrari007 said:
Should I proceed with JSS15J ???
Click to expand...
Click to collapse
yes.
Instructions in above post.

ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???

red_ferrari007 said:
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
Click to expand...
Click to collapse
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.

Last doubt
sfhub said:
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Click to expand...
Click to collapse
Just one doubt before proceeding
From ur link i downloaded JSS15J stock image
ur guide also mentions to download an addon zip file correct ? but its name is JSS1Q addon,zip
So is it correct ???

I need to extract that addon file to that extracted ? STOCK image file rite ?

Best method to unlock zenfone 5 bootloader without any freeze/random reboot!

I'm using RR 5.6.9 by @tank0412 for last one week.
http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
So far I didn't face any freezing or random reboot issues. What I did is as below:
1. Flash/downgrade to UL-ASUS_T00F-WW-2.21.40.30-user firmware.
If you know how to flash stock firmware then skip step 2-12 and just flash it by yourself. These steps are for new users.
2. TURN OFF the device. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. Check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. Download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
If you have different SKU, you need to find the right firmware(version-2.21.40.30) here: https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/
5. Extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. Run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Then go to recovery by selecting from the menu, you will an android logo with "!" sign. Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.
8. In the recovery, select wipe data/factory reset
9. Select wipe cache partition
10. Select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. After successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Download this official tool for Unlock Bootloader: http://dlcdnet.asus.com/pub/ASUS/Ze...rel.zip?_ga=1.117083014.1481752799.1464212721
A501cg users should get the tool here: https://www.asus.com/Phone/ZenFone_5_A501CG/HelpDesk_Download/
14. Extract the downloaded file and copy the .apk file into you SDcard. Install that .apk(if it says untrusted app, then go to settings>security>enable Unknown sources).
15. Run the installed app and press unlock. wait and let it reboot. After this, your Asus splash screen will become white & bright.
16. Now do a clean flash for any custom rom.
You guys can try it. :highfive:
Note: Few users are having "No Camera" issue for unlocked bootloader. This method will not fix that. Sorry about it, I'm a victim as well.

a8962383 said:
I'm using RR 5.6.9 by @tank0412 for last one week.
http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
So far I didn't face any freezing or random reboot issues. What I did is as below:
1. Flash/downgrade to UL-ASUS_T00F-WW-2.21.40.30-user firmware.
If you know how to flash stock firmware then skip step 2-12 and just do it.
2. TURN OFF the device. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. Check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. Download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
If you have different SKU, you need to find the right firmware(version-2.21.40.30) here: https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/
5. Extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. Run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Then go to recovery by selecting from the menu, you will an android logo with "!" sign. Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.
8. In the recovery, select wipe data/factory reset
9. Select wipe cache partition
10. Select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. After successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Download this official tool for Unlock Bootloader: http://dlcdnet.asus.com/pub/ASUS/Ze...rel.zip?_ga=1.117083014.1481752799.1464212721
14. Extract the downloaded file and copy the .apk file into you SDcard. Install that .apk(if it says untrusted app, then go to settings>security>enable Unknown sources).
15. Run the installed app and press unlock. wait and let it reboot. After this, your Asus splash screen will become white & bright.
16. Now do a clean flash for any custom rom.
You guys can try it. :highfive:
Note: Few users are having "No Camera" issue for unlocked bootloader. This method will not fix that. Sorry about it, I'm a victim as well.
Click to expand...
Click to collapse
When i run unlock application its saying my device its not supported. My device is zenfone 5 a501cg 1.2 ghZ, 2gb ram and 8 gb rom.
Sent from my ASUS_T00J using XDA-Developers mobile app

Well weather this method would work is debatable since I have used various methods posted on ozanks thread but non have worked I even used a debricking method and it still didn't fix freeze this method would only qualify and a downgrade from roms after this

pintuvirani said:
When i run unlock application its saying my device its not supported. My device is zenfone 5 a501cg 1.2 ghZ, 2gb ram and 8 gb rom.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
First of all, please don't quote the whole OP while you are replying.
Yes, it won't work for your device as you have a501cg. You need to get the official unlock tool from this site: https://www.asus.com/Phone/ZenFone_5_A501CG/HelpDesk_Download/
Before that you have to flash or downgrade to *.30.zip firmware.
Sent from my ASUS_T00F using XDA-Developers mobile app

jiyaad1 said:
Well weather this method would work is debatable since I have used various methods posted on ozanks thread but non have worked I even used a debricking method and it still didn't fix freeze this method would only qualify and a downgrade from roms after this
Click to expand...
Click to collapse
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app

a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Click to expand...
Click to collapse
Actually a501 has the SAME unlocker as a500cg. There's only one app that unlocks a wide variety of Asus devices. (Zen6's different afaik).
And we tried to install 2.21.40.30 for base as well and it changed nothing.
And unlocker application doesn't change the working mechanism of phone (we decompiled it).
So, are you sure that you tried to use heavy applications like Youtube or some games?
If you get any user that reports freezes gone; i will try it again with your method.
Thanks for your contribution. Good luck with your method. :laugh:
Btw assuming you have a500cg, that phone can be fixed imo.

ozank said:
Actually a501 has the SAME unlocker as a500cg. There's only one app that unlocks a wide variety of Asus devices. (Zen6's different afaik).
And we tried to install 2.21.40.30 for base as well and it changed nothing.
And unlocker application doesn't change the working mechanism of phone (we decompiled it).
So, are you sure that you tried to use heavy applications like Youtube or some games?
If you get any user that reports freezes gone; i will try it again with your method.
Thanks for your contribution. Good luck with your method.[emoji23]Btw assuming you have a500cg, that phone can be fixed imo.
Click to expand...
Click to collapse
Bro, I'm a heavy user. Many of us had faced forced close for 8 ball pool game. I had it too but after this method no forced close happened again. I'm not sure whether a500cg and a501cg have same app for unlocking. It's a bit confusing to me as they have different sites to download their firmwares and tools. But I'm sure, what ever the phone is a500cg or a501cg, the tool will work if the user has *.30.zip firmware installed.
Sent from my ASUS_T00F using XDA-Developers mobile app

a8962383 said:
Bro, I'm a heavy user. Many of us had faced forced close for 8 ball pool game. I had it too but after this method no forced close happened again. I'm not sure whether a500cg and a501cg have same app for unlocking. It's a bit confusing to me as they have different sites to download their firmwares and tools. But I'm sure, what ever the phone is a500cg or a501cg, the tool will work if the user has *.30.zip firmware installed.
Click to expand...
Click to collapse
Yes because the tool seeks for if.bin on firmware folder and it copies to the sysfs. (You're doing same thing on fastboot when flash ifwi if.bin)
So that's why I don't believe the unlocker tool fixes something.
Anyway, thanks; I will wait for another users that solved the issues with your method and then take a look with my phone.

a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried it. Within the first few minutes, it froze again.
Anyways, thanks for trying.

cnswico said:
I've tried it. Within the first few minutes, it froze again.
Anyways, thanks for trying.
Click to expand...
Click to collapse
Did you downgrade to UL-ASUS_T00F-WW-2.21.40.30-user.zip?

a8962383 said:
Did you downgrade to UL-ASUS_T00F-WW-2.21.40.30-user.zip?
Click to expand...
Click to collapse
Exactly as stated in the instructions. I'll try it a second time.

cnswico said:
Exactly as stated in the instructions. I'll try it a second time.
Click to expand...
Click to collapse
This unlock app its work on first kikat rom 2.19 build. But thing is my device not detecting sim on jelly bean and first kitkat build. I tried many time but not detecting sim. Only start detecting sim from 2.19.40.9 to lollipop rom only.
Sent from my ASUS_T00J using XDA-Developers mobile app

It froze again about 3 hours after I had unlocked with asus tool & flashed RR 5.6.9. And I hate that white & bright splash screen anyways, thanks so much for doing research. I believe we will find out a way to solve this problem some day.

a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
I used a method suggested by @dgadelha and it still didn't help and right now I lost my phone to a freak accident so I'm with out a unit for testing ?

tranxuanthang said:
It froze again about 3 hours after I had unlocked with asus tool & flashed RR 5.6.9. And I hate that white & bright splash screen anyways, thanks so much for doing research. I believe we will find out a way to solve this problem some day.
Click to expand...
Click to collapse
Extract splash.bin from rom:
fastboot flash splash splash.bin
or
fastboot flash splashscreen splash.bin
I don't remember which was doing this, but try these

a8962383 said:
Many of us had faced forced close for 8 ball pool game.
Click to expand...
Click to collapse
this is not due to bootloader
I have no problems with bootloader
8 ball force closed on all custom MM rom's
I have no problems except "freeze on 8 ball"
all custom MM rom's used dgadelha's device tree
I think there is a mistake in this

milano88 said:
this is not due to bootloader
I have no problems with bootloader
8 ball force closed on all custom MM rom's
I have no problems except "freeze on 8 ball"
all custom MM rom's used dgadelha's device tree
I think there is a mistake in this
Click to expand...
Click to collapse
You are right. Most of the cross platform developed apps are crashing. It seems like something is wrong with the JavaScript's render engine. I don't play with ROMs. Hope ppl will come forward to have a fix. But to my utter surprise it's been 10days, I still don't have any freezing.
Sent from my ASUS_T00F using XDA-Developers mobile app

Before, following your method with 2.21.40.30-user.zip was not success, but downgrade to 2.22.40.540-user.zip is ok. Unlocked with black logo, white ground but can not flash TWRP, how can install cooked ROM?

My phone is Asus Zenfone 5 T00j A501CG WW. It has 1.6 GHz CPU, 16 gb internal, 2 gb ram. Can this method work if I get the stock firmware you mentioned?

Hi I am new to Android, I follow the steps as mentioned. But not able to after step 7(Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.), I am not go to recovery mode. The phone goes power off mode and is not starting again. Any help is appreciated.
Regards,
Debasish

Vibe K5 doesn't boot up

hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do

Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
I tried that now, it didn't work, still on bootloop :/

Gabriel337 said:
I tried that now, it didn't work, still on bootloop :/
Click to expand...
Click to collapse
Use Qualcomm Flash tool or QFIL then ..

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP before, is with these roms the frozen lenovo screen happens), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.

Gabriel337 said:
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.
Click to expand...
Click to collapse
Wipe everything except system. It should work

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
soldiersz said:
Wipe everything except system. It should work
Click to expand...
Click to collapse
First of all, thanks for you help!
So, I wiped, and nope, the same error happens. This is a problem that I've never seen before

Gabriel337 said:
First of all, thanks for you help!
So, I wiped, and nope, the same mistake it happens. This is a problem that I've never seen before
Click to expand...
Click to collapse
Yeah me too :crying:

Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
I am facing the same problem :crying: Got any solution? How did u flash stock ROM?

I have flashed using qfil now device works fine

Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?

kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
You can go for Vibe k6 power. Why k5 plus?
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
1) Main problem is Battery backup. It won't last long a day.
2) Stock ROM Really sucks
There is no heating issue though. It has been solved by latest updates

K5 Plus flash recovery
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this

Youzpalang said:
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this
Click to expand...
Click to collapse
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.

walterfuster said:
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.
Click to expand...
Click to collapse
Thanks man , What custom rom would you suggest? Is bootlegger OK?

Youzpalang said:
Thanks man , What custom rom would you suggest? Is bootlegger OK?
Click to expand...
Click to collapse
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.

walterfuster said:
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.
Click to expand...
Click to collapse
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!

Youzpalang said:
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!
Click to expand...
Click to collapse
I figured out , Problem solved!

Youzpalang said:
I figured out , Problem solved!
Click to expand...
Click to collapse
Glad to hear that! So, you've decided to stay on stock ROM. OK, it has sense. stock firmware is free of bugs, right? Now, do you know being on stock LL you can "update" to MM and thus get doze and adaptive storage?
How?
Follow this guide:
https://forum.xda-developers.com/k5-plus/how-to/guide-a6020l36-official-lenovo-andoid-6-t3596733
and you'll get the most updated official stock ROM available four our device. Actually, it's a backup made by an Brazilian user, where you should restore only system and boot partitions, in order to keep your data.
This update was only released for Brazil region, but, users from other regions in the thread, reported it worked for them.
I've tried it once, and worked like a charm.

Question Unbrick tool for the 6/6 Pro yet?

So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?​

waiting for same thing.... quite sad that i can't use my phone just from an update

Yeah, there is a number of us in the same position. We could start a club. The really expensive paperweight club or something. I've also reached out to support. They asked a couple of questions, I promptly answered, and thin it's been crickets since.

Are you unable to unlock the bootloader?

chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
yes my phone open bootlooder

chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
No I never really got a chance to do it and now since I can't boot, I can't unlock it.

my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file

shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
Are you unlocked? Did you flash anything?

CyberWolf92 said:
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?​
Click to expand...
Click to collapse
could you please tell me your process, how did you try to flash ? my bootloader is unlocked even though I could not flash with .img file, everytime it's showing - FAILED (no such partition)

numbawon said:
Are you unlocked? Did you flash anything?
Click to expand...
Click to collapse
yes ,phone is unlocked, when i go for flashing with miflash, no .img file showing, or /and to install twrp,its showing no such partition

numbawon said:
Are you unlocked? Did you flash anything?i
Click to expand...
Click to collapse
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode

shakhawat1993 said:
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
Click to expand...
Click to collapse
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.

numbawon said:
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
Click to expand...
Click to collapse
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad

shakhawat1993 said:
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
Click to expand...
Click to collapse
You have been very bad. You will be punished. *invites in the scary nurse with the big paddle*

@shakhawat1993 see this other post as it explains some more in it just in case it's helpful.

shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
i was in same situation like you,,start RM6 only on fastboot but thie works ,download you rom from this page https://drive.google.com/drive/mobile/folders/1BE4FSGDcfXavYoJ3Kw3toGMiPHgCGakC?usp=sharing
extract boot.img to your folder with fastboot
start mobile in fastboot
and open cmd.
fastboot device
if you see your device try next command
fastboot flash boot boot.img
restart your phone and you have stock recovery,,wipe data and you have unbricked device
i download latest twrp but not working and after install twrp i was stucked in fast boot like you

I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.

numbawon said:
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
Click to expand...
Click to collapse
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...

Nocturne Seigneur said:
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Click to expand...
Click to collapse
That's what I was hoping for but worried it's going to take more than just that, like the GPT layout and some other things.

For sure you will need the partition table, rawprogram, & a firehose for the SD888; I'd be surprised if the one for the RM5 would work on the RM6.

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.