Related
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
So, one day ago I was just going through my messages and suddenly my phone's launcher (CM13's launcher as I was on CM13) got an FC and the phone was stuck at it. So, I removed the battery and then booted into recovery just to clear the cache and dalvik. After that, I tried to boot my phone again but it got stuck at the boot logo and I tried flash the CM13 as well as stock rom but none of them worked and then I tried to change the recovery just to take a shot but now when I flash it through ADB it shows 'error: partition table not found'. Yes, I googled it for literally a day but still the problem remains the same. I can't boot into recovery. If I do, the screen hangs at the bootloader menu and restarts. I am only able to access Fastboot but "adb devices" in ADB doesn't show my device either. I guess I need to make partitions for my internal sdcard. So, I have got nothing but I can unlock and relock my bootloader. Nothing much. SP tool doesn't detect my device and the Android One Toolkit works but no change. PLEASE HELP as I have been without my daily device for more than a day now. :crying:
AgentJT said:
So, one day ago I was just going through my messages and suddenly my phone's launcher (CM13's launcher as I was on CM13) got an FC and the phone was stuck at it. So, I removed the battery and then booted into recovery just to clear the cache and dalvik. After that, I tried to boot my phone again but it got stuck at the boot logo and I tried flash the CM13 as well as stock rom but none of them worked and then I tried to change the recovery just to take a shot but now when I flash it through ADB it shows 'error: partition table not found'. Yes, I googled it for literally a day but still the problem remains the same. I can't boot into recovery. If I do, the screen hangs at the bootloader menu and restarts. I am only able to access Fastboot but "adb devices" in ADB doesn't show my device either. I guess I need to make partitions for my internal sdcard. So, I have got nothing but I can unlock and relock my bootloader. Nothing much. SP tool doesn't detect my device and the Android One Toolkit works but no change. PLEASE HELP as I have been without my daily device for more than a day now. :crying:
Click to expand...
Click to collapse
well after installing new stock rom my micromax canvas a1 stopped charging my battery level now dont get above 4 percent so i took it to the customer care they sent it to delhi to fix the issue i got my phone like after 1 month they changed the motherboard of it but problem still remains so i thought i should change the rom but i cant install any new recovery whenever i select fastboot mode in recovery my phone just shuts down my im thinking to update my rom to 6.0 and try flashing rom again ill see if that works
jassi150 said:
well after installing new stock rom my micromax canvas a1 stopped charging my battery level now dont get above 4 percent so i took it to the customer care they sent it to delhi to fix the issue i got my phone like after 1 month they changed the motherboard of it but problem still remains so i thought i should change the rom but i cant install any new recovery whenever i select fastboot mode in recovery my phone just shuts down my im thinking to update my rom to 6.0 and try flashing rom again ill see if that works
Click to expand...
Click to collapse
What was the cost of replacing the motherboard ? I don't have good customer care here in Gandhinagar, Gujarat. So, how do I send my device to the compay ??
AgentJT said:
What was the cost of replacing the motherboard ? I don't have good customer care here in Gandhinagar, Gujarat. So, how do I send my device to the compay ??
Click to expand...
Click to collapse
my phone was under warranty so i dont know about the cost of the motherboard but you should search go to your nearest service center of micromax or call them and get your phone checked they returned mine like after 3 months but now its working fine
jassi150 said:
my phone was under warranty so i dont know about the cost of the motherboard but you should search go to your nearest service center of micromax or call them and get your phone checked they returned mine like after 3 months but now its working fine
Click to expand...
Click to collapse
Okay mate, thanks for your support and sorry for the late reply.
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.
hi
i have realme 8 5g (rmx3241).i flashed a corvus gsi but it comes with bootloop.so,i decided to flash stock rom.but this error comes" status brom cmd send da fail" while trying to solve that error I mistakenly format the phone , now the phone is not coming up again. I was able to solve the that error and decided to flash the firmware now it bringing up verified boot enabled. My major problem about it is the fact that the phone is not even coming up again please help
please reply
i have the same problem we need dump for this model thanks
how to?
awzx_77 said:
i have the same problem we need dump for this model thanks
Click to expand...
Click to collapse
awzx_77 said:
i have the same problem we need dump for this model thanks
Click to expand...
Click to collapse
what have to dumb
Good afternoon, after the ota software update, the display stopped working, just a black screen, but the system sounds are there. I tried to restore the official firmware via flashtool, it didn't help. Rmx3242 . The display is original, not replaceable
rentest said:
Good afternoon, after the ota software update, the display stopped working, just a black screen, but the system sounds are there. I tried to restore the official firmware via flashtool, it didn't help. Rmx3242 . The display is original, not replaceable
Click to expand...
Click to collapse
You have to flash the stock rom including the ocdt.img, I had the same problem.
Did you ever solve your problem ? I'm experiencing something similar, the phone won't boot or charge
I've got something similar. The phone turn on, barely, and immediately turns off again. Gives a tiny vibration and turns off.
Only when on the charger, if it's not on the charger, no boot whatsoever.
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.