So, first off... I know this is a BIG no no... wasn't thinking, it was late at night, and I was having some issues getting LG Bridge to recognize my device... made a stupid mistake. Point is... I'm now stuck in a bootloop with the message "Your device is corrupt. It cannot be trusted and will not boot."
Doesn't seem like I can boot into recovery, however I have noted that the default Factory Reset shortcut still lets me through: PWR + Vol Down, but the menus appear to do nothing helpful. I know I'm about as hard-bricked as one can get, but if anyone has a solution... help an idiot out.
Validfire said:
So, first off... I know this is a BIG no no... wasn't thinking, it was late at night, and I was having some issues getting LG Bridge to recognize my device... made a stupid mistake. Point is... I'm now stuck in a bootloop with the message "Your device is corrupt. It cannot be trusted and will not boot."
Doesn't seem like I can boot into recovery, however I have noted that the default Factory Reset shortcut still lets me through: PWR + Vol Down, but the menus appear to do nothing helpful. I know I'm about as hard-bricked as one can get, but if anyone has a solution... help an idiot out.
Click to expand...
Click to collapse
No worries, you're safe i literally did the same thing yesterday and almost had a heart attack, unplug the phone (if it's plugged), and i'm asuming you've already got Fastboot installed.
Hold the Vol+ Button while plugging in the cable, that should send you into the bootloader, on your computer, open up a cmd where fastboot is, and type in "fastboot.exe oem unlock" (If you have windows that is)
Then do "fastboot.exe reboot" and that should be fixed.
Related
Hello guys, I'm new here and I hope you can help me out.
Let me make the story short.
My phone's screen broke and I replaced.
In that processes I lost the rubber that stick
to the panel of the volume. I was fine with that since my phone
in vibrate mode and I really don't use ring tone in my daily basis.
I tried to download Android 5.0 lollipop and flash it.
How did I get there? well since I did not have a volume button,
I downloaded an app that restarted my phone and got me into
fastboot mode without the key (I did got me where I wanted).
Then the problem was that in the middle of writing the .img
the freaking cheap bastard micro usb unplugged!!!
BAMM!! phone now is bricked, I cannot get into recovery/fastboot mode
since I cannot press the volume key and my phone is bricked.
I tried going through fastboot mode via my computer again,
but the computer doesn't recognize the device since it still
looping there forever at the google logo. I try installing USB
DRIVERS to see if I could do some "magic" haha. Got
error "This device cannot start ..." And still at the same problem.
I know I can get back to my recovery if order the part for the volume
key, I ordered the part to replace it, but trust me I was 3 weeks without
my phone and now this problem
Is there any way that I can get to fastboot mode to factory reset my phone
without volume key with a bricked forever looping a "google" logo ? :fingers-crossed: :fingers-crossed:
I appreciate any help.
vadeld said:
Hello guys, I'm new here and I hope you can help me out.
Let me make the story short.
My phone's screen broke and I replaced.
In that processes I lost the rubber that stick
to the panel of the volume. I was fine with that since my phone
in vibrate mode and I really don't use ring tone in my daily basis.
I tried to download Android 5.0 lollipop and flash it.
How did I get there? well since I did not have a volume button,
I downloaded an app that restarted my phone and got me into
fastboot mode without the key (I did got me where I wanted).
Then the problem was that in the middle of writing the .img
the freaking cheap bastard micro usb unplugged!!!
BAMM!! phone now is bricked, I cannot get into recovery/fastboot mode
since I cannot press the volume key and my phone is bricked.
I tried going through fastboot mode via my computer again,
but the computer doesn't recognize the device since it still
looping there forever at the google logo. I try installing USB
DRIVERS to see if I could do some "magic" haha. Got
error "This device cannot start ..." And still at the same problem.
I know I can get back to my recovery if order the part for the volume
key, I ordered the part to replace it, but trust me I was 3 weeks without
my phone and now this problem
Is there any way that I can get to fastboot mode to factory reset my phone
without volume key with a bricked forever looping a "google" logo ? :fingers-crossed: :fingers-crossed:
I appreciate any help.
Click to expand...
Click to collapse
Im not sure why your text is like this? But paraphrasing buddy comes a long way
Just hold the power button, until it dies, or just let it die in general since your volume button (You only need Vol down and Power) to power it off completely. Since your Volume keys are gone, the best solution is to wait for the replacement before doing so, unless you can get the contact keys to trigger the Volume button, you're in a loss atm. No OS or Volume keys means you can't trigger ADB commands or boot into fastboot. Just wait it out I guess?
Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance
I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment
Im sorry if i type bad but im so frustrated and sad right now.
I downloaded "SRKToolHuawei-STABLE-V1.3-20160619"
My phone was already unlocked so i relocked it again.
that went well
But then i unlocked it again and now its stuck on your device is booting now...
So i restarted it many times now and nothing is happening.
I cant fastboot cause it says my phone couldn't be found.
I need help! i just got this phone and im so stressed right now. Any help will be appreciated! Thank you!
Edit:
Just to make it clear. I was trying to install TWRP.
Im new to this and everything was so messy.
I flashed it a bunch of times but it didn't install so i relocked it and unlocked it and this happend.
currently im waiting for it to drain and ill see what happens
Hello. Long press POWER to reboot and then release and quickly long press both VOL+ and VOL- simultaneously. It should appear an update screen with a failed message and –the most important thing– a restart button at the bottom. Press it.
Now the phone should start Android normally...
alesbabnik said:
Im sorry if i type bad but im so frustrated and sad right now.
I downloaded "SRKToolHuawei-STABLE-V1.3-20160619"
My phone was already unlocked so i relocked it again.
that went well
But then i unlocked it again and now its stuck on your device is booting now...
So i restarted it many times now and nothing is happening.
I cant fastboot cause it says my phone couldn't be found.
I need help! i just got this phone and im so stressed right now. Any help will be appreciated! Thank you!
Edit:
Just to make it clear. I was trying to install TWRP.
Im new to this and everything was so messy.
I flashed it a bunch of times but it didn't install so i relocked it and unlocked it and this happend.
currently im waiting for it to drain and ill see what happens
Click to expand...
Click to collapse
ernestoamaya said:
Hello. Long press POWER to reboot and then release and quickly long press both VOL+ and VOL- simultaneously. It should appear an update screen with a failed message and –the most important thing– a restart button at the bottom. Press it.
Now the phone should start Android normally...
Click to expand...
Click to collapse
I think i know what i did wrong.
it was a old version of twrp i think. so it couldn't boot into it. so i had wait for it to drain and then boot it up again. I got trwp working now!
Hi! I have the same problem. The phone was drained but when i charge It again It tries to start normally, but then starts trying ti enter into recovery again.
so who did you solve It exactly?
what buttons did you pushed when the phone starts again?
Thani you
For anyone pretty much, who has ****ed up his Huawei P9:
I got to the state where I could only enter Fastboot mode (Press vol- and connect power cable). When I tried to start the phone / go into recovery it would only display the "Your device has been unlocked and can't be trusted" Message. My mistake was to relock the bootloader in an attempt to get the recovery to work.
I looked for hours for the answer, here is what worked for me:
follow this tutorial (the "update firmware" part)
German
English
But with real precision, every step.
If you have a european unbranded L09 you should be fine using the firmware you can find on this site:
https://thedroidguru.com/download-install-huawei-p9-b394-nougat-update-europe/
if not you gotta find the full firmware (3 files!!) yourself - good luck!
If you only want to go back to stock you should be fine afterwards.
If you want to install twrp for root/custom rom/... follow these steps after installing twrp with the tool:
Upon flashing TWRP, FIRST THING YOU MUST DO is rebooting to TWRP. If you don't do that, stock Recovery will ovewrite TWRP.
Find instructions in the TWRP threads how to enforce immediate booting to TWRP, upon you flashed it:
-Type on the PC: fastboot reboot -but don't press Enter yet.
-Press and keep pressing Vol+ and Power buttons together on the phone
-Press Enter on the PC and then immediately unplug USB cabel.
-When phone shows Booting, release Power but keep pressing Vol+. button
Hope this helps, I don't take responsability for anything, happy flashing!
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Damn, that's a bit unlucky, this March update said it would make recovery from a loop after OTA update easier to recover from, which might just have helped you. Sorry not sure how to help fix at present.
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
harpoon said:
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
Click to expand...
Click to collapse
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
kt-Froggy said:
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
Click to expand...
Click to collapse
Thanks for your response.
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
=============
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
=============
yenkoPR said:
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
Click to expand...
Click to collapse
Will this work even though I cannot see the device via adb? AND the device state is "locked".
harpoon said:
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
Click to expand...
Click to collapse
Dang... :\ Yeah, the last error means you don't have OEM unlock enabled. So, you can't flash the bts image via fastboot. One last thing I could think of is trying to get to recovery by the button combo. Although, if you are correct in saying you don't have USB debug enabled, it won't do much good, i.e. you won't be able to flash an OTA... :\
While device is OFF, press and hold Volume-Up button while pushing Power button to boot.
Your device will now be in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time to see the recovery menu.
can you try this command on bootloader:
fastboot OEM unlock
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Rudter said:
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Click to expand...
Click to collapse
Nothing ! ..
my ph-1 still into the drawer ! .
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight