Related
Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!
Saweet
Sent from my Nexus 7 using xda premium
Just trying to make it easy
im on 4.2 already ,can i use this to root?
Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...
Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.
Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?
Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited
trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.
trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP
Nevermind, I wiped cache and dalvik cache and it worked for me too.
Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
When i powered it on, the bootloader was missing so it just froze with the Android logo on the screen and after a few seconds it shut down.
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have. no adb, fastboot. So it's pretty much useless.
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless.
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it.
The phone is still covered by warranty, but I'm not sure if they are going to do it for free, because I messed with it.
I can try that story: "I was taking an OTA Update and the phone never powered on." maybe they are going to buy it.
So is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ?
RO.maniac said:
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
Logically, when i powered it on, the bootloader was missing (I've erased it earlier and the phone Powered Off just before writing the bootloader from backup) it just freoze with the Android logo on the screen and after a few seconds it shut down. Because it has no bootloader and it doesn't know how and what to boot...
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have... no adb, fastboot, odin. So it's pretty much useless...
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless...
I have no fastboot, adb, odin (that I'm not sure if works on this phone) access... :crying:
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it...
The phone is still covered by the warranty, but I'm not sure if they are going to do it for free, because I messed with it. Basically, I can try that story: "I was doing an On The Air Update and the phone never powered on..." maybe they are going to take it... anyways...
So, I'm asking you, is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ???
Click to expand...
Click to collapse
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Bigkiler5 said:
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Click to expand...
Click to collapse
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
RO.maniac said:
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
Click to expand...
Click to collapse
Like i said i have xperia x10 so i have knowledge about my device. You should ask this question in your mobile's forum. That will really help..... I think the solution they will give may be similar but in a different way.
Greets
i cant power on phone vodafone smart 2
my Vodafone won't turned on after trying to make recovery from alberto. and even did not vibrate after pressing power button to turn it on.
also it does not work at all like there are no battery attached to it. almost dead phone. and my computer not detect it anymore. and can't access fastboot or recovery screen.
do anyone fix this problem??
same problem bricked Vodafone smart ii
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
mixeristu said:
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
Click to expand...
Click to collapse
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
vodacrap II bricked
Bigkiler5 said:
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
Click to expand...
Click to collapse
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
mixeristu said:
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
Click to expand...
Click to collapse
It could be a hard brick and your info seems to confirm this but don't take my word for it. Search on google for issues with your device I seem to remember reply to a thread similar to this a while back.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
The I think.this is because when some phones are bricked they show the manufactures name such as on a hard bricked htc device it sometimes shows qhsusb_dload (don't quote me on that if my spelling is wrong) and it connects under a Qualcomm USB device driver. That is because sometimes on devices the chipset is made by Qualcomm but on your device the chipset is made by Broadcom and that why it shows a Broadcom named device driver.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Hi!
Someone has news about this topic?
bad news
cfjrocha said:
Hi!
Someone has news about this topic?
Click to expand...
Click to collapse
Yes, the bad news is that even JTAG could not repair my hard-bricked vodacrap II. My advice is to be really carefull when installing the custom android version, especially when using another sim than vodafone, some of the mods won't let you insert the network cod (eight of 1), mine didn't work with any version of the mods, sometimes I wasn't able to receive calls, sometimes to make calls, depending. Take it and keep it using vodafone or in any other case don't buy is not worthy.
i accidentally erased boot and bootloader.nor download mode nor recovery work and my pc recognize it like Broadcom USB wireless modem.Any solution?
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.
By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol
shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.
Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Wow, been buying new phones every year (sometimes more frequently) since the Galaxy Skyrocket and ROM'd every single one.
This is my first ever hard brick!!!!
Not getting any display at all.
Charge was ~30% at the time if I remember correct.
Can't get to fastboot or any display output at all.
Just a dead black screen. ugh
This isn't a questions thread, since there is no recovering from hard-brick like you can from soft-brick.
So I'm not here to ask for help, because there is no help.
This thread is just to let you see what I did wrong that caused a hard brick.
TWRP Booted to slot B.
Wiped cache/dalvik & system & data.
Flashed Bootleggers ROM zip (unofficial, not available to public, I kinda wasn't supposed to flash it but hey, it's not at fault here, so don't think that).
Rebooted to recovery.
But it rebooted to stock recovery, so TWRP got lost.
Booted up to Bootleggers.
Let it settle.
Looked around and it's neat.
Rebooted to Bootloader.
Fastboot booted TWRP.
Installed TWRP zip.
Noted that I'm on slot A again.
Rebooted to slot B to verify nothing was installed there.
It never actually booted, of course. Just got a black screen.
Held power button/volume-up buttons down forever and got nothing.
Waited 5 seconds and tried holding power button down forever and got nothing.
Waited five minutes.
Tried holding power button for a long while. Nada.
Let it charge for 10 minutes (never got charging symbol).
Held down power button 60 seconds. Nada
I wish there was something I could offer - I have thought I was hard bricked on other devices I have owned but thru the help of others was able to eventually get to a point where I could flash a stock image. I don't know if you are really past that point or not but I wish you luck and hope you find a solution.
Might be worth contacting GOOGLE for a warranty repair - worst case, they will charge you something to bring the phone back from the dead .....
Good luck my friend, hope you figure something out.
Google Fi "support"
lol
Google Support
You are number 97 in the queue.
Click to expand...
Click to collapse
Yeah, I'm usually the guy helping others recover from soft brick.
This one is just dead-dead.
Even tried checking if my PC recognized it for ADB or fastboot after various key press combos.
CZ Eddie said:
Google Fi "support"
lol
Yeah, I'm usually the guy helping others recover from soft brick.
This one is just dead-dead.
Even tried checking if my PC recognized it for ADB or fastboot after various key press combos.
Click to expand...
Click to collapse
Don't feel too bad. I did pretty much the same thing. You don't want to try and boot to the inactive partition with twrp. It's like there is no system there and voila, your hard bricked. I did rma the device.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Don't feel too bad. I did pretty much the same thing. You don't want to try and boot to the inactive partition with twrp. It's like there is no system there and voila, you're hard bricked. I did rma the device.
Click to expand...
Click to collapse
You know, I suspected this was the issue.
Me booting to an unused, inactive partition.
We didn't have this issue on Pixel 1 though.
At least not when I was still flashing my P1.
I never had a Pixel gen 2.
I just did some Googling and see there are warnings out there not to do what I did because it could cause a non-recoverable brick.
So I edited my thread title for any other fools like me. :good:
This might sound strange, but I once thought I hard bricked my original Pixel. Tried for 2 days to get it to boot. Then finally I got it to boot by holding down the Power Button & Volume Down Button, then plugging in the charger cable while still holding the buttons down. It booted up bootloader screen and I was able to fastboot twrp and bring the phone back to life. Not sure if you tried that or not.
wtyler2505 said:
This might sound strange, but I once thought I hard bricked my original Pixel. Tried for 2 days to get it to boot. Then finally I got it to boot by holding down the Power Button & Volume Down Button, then plugging in the charger cable while still holding the buttons down. It booted up bootloader screen and I was able to fastboot twrp and bring the phone back to life. Not sure if you tried that or not.
Click to expand...
Click to collapse
Yep, I tried that but thanks.
Let it charge a while.
Let it sit a while.
Then pressed vol+ & power and plugged in charger.
Also did vol- & power and plugged in charger.
And power and plugged in charger.
And vol- and plugged in charger.
And vol+ and plugged in charger.
Also did this by pressing the buttons and waiting a second before plugging in charger.
lol I did it all.
****ty!
I wonder if there's is a way for twrp to warn that that partition is empty and not to boot. Or something twrp can do to prevent booting in that?
Anyone able to talk to the twrp team about this?
I noticed that when you wipe system it goes to black screen. It happen to me twice. I was able to get back to bootloader by pressing volume down and power button at the same time.
Sent from my SM-G955U using Tapatalk
---------- Post added at 07:55 PM ---------- Previous post was at 07:51 PM ----------
c_86 said:
****ty!
I wonder if there's is a way for twrp to warn that that partition is empty and not to boot. Or something twrp can do to prevent booting in that?
Anyone able to talk to the twrp team about this?
Click to expand...
Click to collapse
When I wiped system and flashed a rom system image which flashed ok, I press reboot. TWRP said there is no system OS to boot.
Sent from my SM-G955U using Tapatalk
rimgarciag said:
[/COLOR]When I wiped system and flashed a rom system image which flashed ok, I press reboot. TWRP said there is no system OS to boot.
Click to expand...
Click to collapse
Yep, it does this!
I should have known better but as an Android tinkerer, I always do things I shouldn't do.
Anyhow, I'm sort of back up and running.
I kept trying and trying and trying to get to bootloader.
And finally got it!!
At first, it started by an occasional white line that would briefly show up on the screen for 1/4 of a second.
A kept trying and trying, and eventually I would get fastboot briefly flash on the screen for one second and then go away.
After four or five times of getting fastboot to flash up on the screen like that, on the sixth try (?) it finally stuck!!
So I ran flash-all.bat and the OS booted up just fine. :good:
I then encountered nothing but issues with trying to get TWRP installed again.
It was failing to decrypt anything even after installing it three times.
And before that, my PC kept refusing to recognize the phone after booting TWRP, so I had a heck of a time just trying to transfer the TWRP.zip to the phone to install.
I gave up on all that.
And I did the following:
fastboot erase partition (A & B individual partitions for everything below)
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
Now I'm gonna flash-all.bat again and hope things go better this time around. :good:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
CZ Eddie said:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
Click to expand...
Click to collapse
Great that you're up and running. Maybe I should have kept trying on my device. But after a number of attempts and it not charging at all I gave up. You just kept trying to boot into the bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Timing is the key here to get into bootloader, you've got release the key combo super quick. It's a really stupid behavior, but I had the same situation and that's what happens.
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Paradoxxx said:
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Timing is the key here to get into bootloader, you've got release the key combo super quick. It's a really stupid behavior, but I had the same situation and that's what happens.
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Click to expand...
Click to collapse
I'm not sure I understand the timing to do a hard reset. When I boot into the bootloader I typically press and hold power and volume down until it boots into the bootloader. I do notice the first time I do that it doesn't seem to do anything but if I do it again it boots. If I do a quick press and release of the keys it didn't seem to do anything.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure I understand the timing to do a hard reset. When I boot into the bootloader I typically press and hold power and volume down until it boots into the bootloader. I do notice the first time I do that it doesn't seem to do anything but if I do it again it boots. If I do a quick press and release of the keys it didn't seem to do anything.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's simple really.
If you hold the key combo too long, you'll end up hard resetting instead of going into fastboot. You have like half a second to react to release the keys and not hard reset and stay into bootloader.
Press both buttons->Hold till bootloader screen appears->Release immediately->If not released HardReboot.
Paradoxxx said:
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Click to expand...
Click to collapse
Yep, I'm familiar with this behavior.
But I don't think it's what was happening for me.
Well, maybe it was, but the timing was off.
Because I've done this hard reset before.
As well as booted to Bootloader thousands of times.
I'm pretty good with the timing when they're working properly.
Paradoxxx said:
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Click to expand...
Click to collapse
I actually did try this!
And nope, it didn't work for me but maybe it would for others.
Because when I finally got bootloader to stick, it wasn't recognized by my PC.
I had to reboot my PC.
All in all, I'm happy it wasn't a hard brick after all.
Just a unusually bad soft-brick. :good:
Continue to hold volume down key when you release the power button.
CZ Eddie said:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
Click to expand...
Click to collapse
WOW, so glad you got it back. Gave me severe indigestion before seeing that you're OK.
HI Guys, just curious, as I've not worked on A/B partitions before (my P3xl will be the first time), but how does one boot TWRP to an inactive partition? My guess is inactive means there is nothing in there since an erase was done on system, and perhaps a fastboot set_active_<the inactive partition> was issued?
Just a thought so that I know what not to do. Thanks in advance everyone!
CZ Eddie said:
Yep, it does this!
I should have known better but as an Android tinkerer, I always do things I shouldn't do.
Anyhow, I'm sort of back up and running.
I kept trying and trying and trying to get to bootloader.
And finally got it!!
At first, it started by an occasional white line that would briefly show up on the screen for 1/4 of a second.
A kept trying and trying, and eventually I would get fastboot briefly flash on the screen for one second and then go away.
After four or five times of getting fastboot to flash up on the screen like that, on the sixth try (?) it finally stuck!!
So I ran flash-all.bat and the OS booted up just fine. :good:
I then encountered nothing but issues with trying to get TWRP installed again.
It was failing to decrypt anything even after installing it three times.
And before that, my PC kept refusing to recognize the phone after booting TWRP, so I had a heck of a time just trying to transfer the TWRP.zip to the phone to install.
I gave up on all that.
And I did the following:
fastboot erase partition (A & B individual partitions for everything below)
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
Now I'm gonna flash-all.bat again and hope things go better this time around. :good:
Click to expand...
Click to collapse
I think i may be fully bricked
https://forum.xda-developers.com/pi...reen-fastboot-one-catch-t3875953#post78351724
The phone is now completely blank, and it’s useless to press any button, and you can’t enter fastboot. Use 9008 to perform steps 5 and 6 (5. Power off your phone by pressing Voice Down + Power Buttons) (6. Start update_image_EDL.bat script-it will recreate all of the partitions) The script window flashed and exited without any prompts, how can I solve it?
Same here...
I was trying to flash BlissRom 12.8 on a clean Q stock rom and when it finished flashing, I wanted to reboot recovery to slot B. Then it went black.
No button or combination works, no charging, no recognition by Windows, adb, fastboot.
The QDLoader 9008 fix (update_image_EDL.bat) returns that variable _COM is not defined.
Can anyone help?
Edit: So I can see the screen flashing very faintly every second, there seems to be some logo but I cannot identify it...
Edit2: was able to fix it with the QDLoader, but only by bridging two contacts inside the device...
got exact same situation. Booted into twrp (twrp-3.4.0-1-I01WD, no install)
installed asus rom from there (UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user) from sdcard
rebooted to bootloader (adb reboot bootloader)
I can see a faint powered by android logo every second
Maybe it's a bad idea to install stock rom from twrp.
abprie said:
Same here...
I was trying to flash BlissRom 12.8 on a clean Q stock rom and when it finished flashing, I wanted to reboot recovery to slot B. Then it went black.
No button or combination works, no charging, no recognition by Windows, adb, fastboot.
The QDLoader 9008 fix (update_image_EDL.bat) returns that variable _COM is not defined.
Can anyone help?
Edit: So I can see the screen flashing very faintly every second, there seems to be some logo but I cannot identify it...
Edit2: was able to fix it with the QDLoader, but only by bridging two contacts inside the device...
Click to expand...
Click to collapse
how did you do the bridging also is there any alternate way unless opening the device and did you wiped the vendor??
23598685 said:
got exact same situation. Booted into twrp (twrp-3.4.0-1-I01WD, no install)
installed asus rom from there (UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user) from sdcard
rebooted to bootloader (adb reboot bootloader)
I can see a faint powered by android logo every second
Maybe it's a bad idea to install stock rom from twrp.
Click to expand...
Click to collapse
I flash stock roms via unofficial TWRP regularly and so far I've never had any problem. My steps:
-flash new ROM
-flash TWRP Installer
*Reboot to recovery, slot changes
-flash kernel
-flash twrp (it may not be necessary, I do it though)
-flash magisk
And then I'm good to go.
ronak123456 said:
how did you do the bridging also is there any alternate way unless opening the device and did you wiped the vendor??
Click to expand...
Click to collapse
Bridging was easily done with a metal paper clip, but any thing similar out of conductive metal will do.
If you get your device registered as a COM device, you probably can run the script without bridging.
I don't remember wiping vendor, probably not. I had several custom ROMs installed before, but have to admit that I never really got the hang of it with those two slots and getting it finally to work felt like I did something by chance that made it work.
Maybe one additional hint: when I had the device opened, I restored the stock ROM, updated to 10, rooted, installed TWRP 3.4, and flashed BlissRom once again to see if 3.4 was the culprid and it was indeed!
abprie said:
Bridging was easily done with a metal paper clip, but any thing similar out of conductive metal will do.
If you get your device registered as a COM device, you probably can run the script without bridging.
I don't remember wiping vendor, probably not. I had several custom ROMs installed before, but have to admit that I never really got the hang of it with those two slots and getting it finally to work felt like I did something by chance that made it work.
Maybe one additional hint: when I had the device opened, I restored the stock ROM, updated to 10, rooted, installed TWRP 3.4, and flashed BlissRom once again to see if 3.4 was the culprid and it was indeed!
Click to expand...
Click to collapse
bridging with a metal paper clip without opening the phone?
my device is not recognized by the device manager no matter what i do.
any complete solution for this issue yet?
i made huge mistake that wipe vendor this time
it was been too long time to forgot about flashing from last try
ronak123456 said:
bridging with a metal paper clip without opening the phone?
my device is not recognized by the device manager no matter what i do.
Click to expand...
Click to collapse
No, of course not without opening the phone.
If you don't get the phone recognized and see a faint flickering of something like a boot image every second (I could only see this in complete darkness), then you might have the same problem as I had.
---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------
chocosobo said:
any complete solution for this issue yet?
i made huge mistake that wipe vendor this time
it was been too long time to forgot about flashing from last try
Click to expand...
Click to collapse
I did what was explained here and got it working again: https://piunikaweb.com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/
abprie said:
I did what was explained here and got it working again: https://piunikaweb.com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/
Click to expand...
Click to collapse
is that means short that 2 pin make my phone to 9008 state from issue?
my issue is only displaying 'powered by android' at lowest brightness (barely see) for 1 sec and looping until battery out
chocosobo said:
is that means short that 2 pin make my phone to 9008 state from issue?
my issue is only displaying 'powered by android' at lowest brightness (barely see) for 1 sec and looping until battery out
Click to expand...
Click to collapse
As far as I can judge it from the distance, it sounds like the issue I had. Shorting the two pins solved it for me. But if you have warranty on the device, you may want to try returning it. Don't blame me if something goes wrong when you open your phone... If you do: take good care about the cable for the buttons not to cut it (happened to me). See this video for someone who already warned about this:
Edit: by "solved it for me" I meant that the phone was then recognized by Windows and I could run the script to reset it to stock.
Stupid me replied twice to the post...