Related
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
chylos said:
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
Click to expand...
Click to collapse
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
Click to expand...
Click to collapse
yepp exactly the same.
In short, don't update
Sent from my Nexus 7 using XDA Premium 4 mobile app
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Sent from my Nexus 7
datallboy said:
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Click to expand...
Click to collapse
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
Click to expand...
Click to collapse
Damn that sounds awful, and I was nagging for not getting the update, that's way worse. So you can't access bootloader mode at all? Did you try to use fastboot commands or adb when plugged to the pc?
Worth a shot if not already tried:
http://forum.xda-developers.com/showthread.php?t=2404297
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
Click to expand...
Click to collapse
I've actually gotten the QHSUSB_DLOAD before when trying to get into bootloader but pressing the wrong buttons.
I was eventually able to get out of it going through various button sequences.
I believe holding down the power for a long time worked in the end, but I forget now.
nope nothing helped me. it's still bricked. i tried every button combination up to 3 minutes. No sign of power.İt was 32 gb. i think google ****ed up this time.
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 ?
My pixel xl(1st gen) purchased from Google store in Jan 2017, and in bootloop a week ago.
I contact google support, they told me my device out of the 1-yr warranty, and redirect me to UbreakIfix for repair, cost on myself.
I contacted UbreakIfix, get a quote for 300+ to change motherboard.
As of today, the Pixel XL only worth $130 trade-in value, and the condition need to be perfect.
So clearly I won't spend $300 to save a device only worth $130.
About the issue, I had some level of experience with fastboot/adb command:
* tried re-image all latest Google Stock Image of Android 7/8/9 individually with boot-loader unlocked, no luck;
* tried adb sideload ota image of Android 7/8/9 individually, with boot-loader locked/unlocked, no luck;
* tried change active slot to a and b with combination of above two items, no luck;
* checked the recovery logs, the boot-loader did take whatever Android stock image I feed to to it, and I do almost every time can get in to both boot-loader or recovery-mode successfully, and has no limit to run any fastboot/adb commands, but these are all I can do, and still not to get the phone boot into Android OS.
* in a very few times, the static "Google" in the white screen did spinning into a big rainbow "G", but it was frozen right after, and eventually reboot again.
I don't know if it worth spend more time on it, and feel very frustrated about spending my time on this doomed device and dealing with the Giant company as a individual customer.
I am not a picky guy, I accept the device running slow, or buggy sometime, but doesn't accept it dead in 2 years as a premium phone.
What do you think, guys?
By the way, many thanks to XDA forum, I learnt a lot from many brilliant and kind people here.
It's not acceptable, but it's the norm. Look at buying a new tv - Some mfg warranties are like 90 days labor and 6 months to a year on parts...It's a shame you pay all that money for something that could be a paperweight in a year.
Acceptable for a phone, or any gadget worth $800 to die in 21 months? LMAO. If this acceptable to some group of people, please redirect them to the best psychic facility available on this planet.
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
lafester said:
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I used my Pixel as a regular way, never root it, never even boot into bootloader before the bootloop issue, always use ota in os to get update. No water spilt, never get drop or hit. In another word, I never "abuse" the phone, and the phone has no accident.
Yeah, whatever, for the phone issue, I'm just having bad luck, like you said, many people have no issues. What I upset about is a $800 phone became a brick within 2 years with a normal usage, and Google not even give this case as an exception to cover it out of warranty.
You may say, or like Google said, then what the warranty stands for, right? I say, if only a few people got this issue, then as a Giant company, should cover since no fault on customer, and it would be a small cost to Google; if a lot of people got this issue, then still Google need to cover, since it becomes a general issue to this phone, which indicates this is a failed model at all.
Please don't think I'm a cheap guy, and trying to take advantage from Google, just trying to think the logical here. BTW, I'm not just complaining Google without putting in effort to solve the issue by myself, I did a little bit research and pickup learning, regard this issue, I'm not alone, many other users have the same issue as well, some of them get it "resolved" by reimage, but the other just has no luck like me.
You don't have to agree with me, I'm a kind of guy would love to discuss with people no matter they have same point view as mine or not.
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Phalanx7621 said:
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Click to expand...
Click to collapse
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
I'm having the exact same issue and Phalanx7621 tried helping me out but unfortunately it looks like there's no solution for it.. Just like your issue, everything successfully flashes, but I got a little past the Google logo a couple of times, but no more. My phone wasn't dropped, never wet, nothing at all. Yesterday morning I woke up and the screen was just black and it started boot looping.
Funnily enough, 2 weeks after I paid the phone off. 1 week after Verizon called to let me know they had open enrollment on their insurance plans and I turned it down since, yanno, I don't mistreat my phone.. "Coincidence" I guess..
My post btw https://forum.xda-developers.com/pixel-xl/help/possibly-bricked-t3861057#post78033420 if any of that helps you hopefully.
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
Phalanx7621 said:
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Click to expand...
Click to collapse
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
premedicated said:
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
Click to expand...
Click to collapse
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
Sure. Gimme a couple minutes and I'll report back
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
So it loaded up TWRP, then I remembered that I didn't set a pin after the latest reflash. So I went into software and setup a pin and moved the TWRP files over onto the phone as well as the kernal before it restarted. But now I can't get 'fastboot boot twrp.img' to actually load TWRP on the phone.. Command prompt says "downloading boot.img, booting, finished. And then on the phone it loads up the google logo and then just freezes and restarts.. I'll dink with it some more and see if i can make it work
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Phalanx7621 said:
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Click to expand...
Click to collapse
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
premedicated said:
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
Click to expand...
Click to collapse
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Phalanx7621 said:
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Click to expand...
Click to collapse
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
premedicated said:
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
Click to expand...
Click to collapse
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
premedicated said:
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
Click to expand...
Click to collapse
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Phalanx7621 said:
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Click to expand...
Click to collapse
Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.
Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Deleted
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
lil_michelle said:
Did you flash disable dm verity first after unlocking the bootloader before flashing a patched system image?
Click to expand...
Click to collapse
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
thank you! Using the Android Flash Tool resolved my issue.
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Hard to say, for those of us who haven't had any problems...yet. I've flashed the full factory image at least twice so far.
Normally, the USB cable and to a lesser extent, the USB port used on the computer, would be my first suspects as to the problem, but since you said it finished successfully, I have no clue.
Do I need to disable dm verity at least once, or is that just completely obsolete now.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
When using Magisk 23016 for rooting it is not necessary at all.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
The *only* time you *might* still need to disable verity and verification are for some custom kernels - until those kernels are updated the same way Magisk Canary 23016 was, and then they won't need it. If you're not planning on using custom kernels, and just rooting the stock kernel instead, then there's no reason to disable them anymore.
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Did either of you verify the hash of the download before flashing?
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
JW09I4 said:
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
Click to expand...
Click to collapse
^ This. For years now, I've just gotten used to verifying the hash of every important thing that I download that has the hash value made available. Saves a lot of hassle later on since if the downloaded file is corrupted just slightly, everything will go wrong down the road in the process.
I also check for new Platform Tools and Google's USB driver each and every time I flash a new update. It's just habit and again, saves a lot of trouble.
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD and type
Get-FileHash <Drag'n'Drop'le'File'here>
Click to expand...
Click to collapse
Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
It's easy, it's fast, it's reliable. It will only cost you a few seconds. No hassle involved.
Morgrain said:
Windows has a built-in hash checker, you just need to open CMD and type
Click to expand...
Click to collapse
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Morgrain said:
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD... Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
Click to expand...
Click to collapse
roirraW edor ehT said:
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Click to expand...
Click to collapse
It's often better to use a program that will compare the hashes, else a SHA256 or SHA512 hash becomes tedious to manually compare - I'm partial to QuickHash [GitHub] due to its broad functionality (drag and drop file for it to auto-compute hash and you can paste what the hash should be either before or after)
For quick one or two-file comparisons, I prefer Implebits' HashTab, which adds a new configurable tab to the file properties dialog in Windows. I originally got turned onto the program when it was Beeblebrox.org, which being a Douglas Adams fan definitely got my attention back then but I stuck with it after they sold it.
Edit: I see Implebits is going out of business and HashTab will go to GitHub and be open source, so exciting times!
Implbits Software, LLC is going out of business
We will soon release Hashtab as an Open Source project on Github. Until we do... you can download the last build of Hashtab that we made using the link below:
Click to expand...
Click to collapse
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
That's what I had to do and agree to relock bootloader
Joynaruto said:
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
Click to expand...
Click to collapse
Tried that with no joy as future idk. My situation was different after flashing Los the recovery was overwritten and flashing stock said something about timestamp error
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
I think you should of used the full image not the update with flashall.bat
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
I had this before as well after manually flashing the November update. Got the device cannot be trusted. Rebooted, flashed again, and device completely fried. Wouldn't turn on, not recognized by computer, nothing. Complete brick. Suspect system board fried. I'll never try to manually flash an update with a Google device again. Hopefully it ends better for you.
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.