Related
My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
icdeamons said:
My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
Click to expand...
Click to collapse
Hi mate as you can get to the bootloader all is not lost.
Download the following files
The Restore to Factory via nvflash: http://www.adventcomputers.co.uk/download-select/nojs/3255
Recovery Guide: http://www.adventcomputers.co.uk/download-select/nojs/3260
Follow the guide to the letter apart from if you have the drivers already installed for ADB and Fastboot you also have the driver installed for APX.
This should get you booting again hopefully.
I have this problem but im on completely untouched device. No root no recovery all official roms.
What can i do?
LightInDark said:
I have this problem but im on completely untouched device. No root no recovery all official roms.
What can i do?
Click to expand...
Click to collapse
Do the above my friend that is your only hope.
Doing it via NvFlash doesn't require root as your flashing via a special mode called APX.
my problem is I don't think my computer even picks it up because the USB doesn't kick in until after the TEGRA NOTEtm screen as far as I am aware.
Follow the PDF it will place the device into apx mode for flashing via nvflash. The guide shows how to install drivers to flashing the device.
Apx mode is to recover from complete bricks or issues like the op. If you can't boot in to android give apx flashing a go. Trust me on this one. I have already done this myself.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
icdeamons said:
My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
Click to expand...
Click to collapse
When i root my slate 7 extreme i never knew that i need to enable the usb debugging mode but somehow i am able to get root access by unlocking the boot loader and installed the cwm(which is usefull to install stock/custom rom)..heck i only know that option was actually available and hidden by default after rooting the device.
the step i followed is from this link:
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
and watching all rootjunky videos at YouTube might be helpful too..
You can unlock the bootloader, flash recovery the root that way but the aio scripts use adb and fastboot not just fastboot on its own.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
hacktrix2006 said:
Hi mate as you can get to the bootloader all is not lost.
Download the following files
The Restore to Factory via nvflash: http://www.adventcomputers.co.uk/download-select/nojs/3255
Recovery Guide: http://www.adventcomputers.co.uk/download-select/nojs/3260
Follow the guide to the letter apart from if you have the drivers already installed for ADB and Fastboot you also have the driver installed for APX.
This should get you booting again hopefully.
Click to expand...
Click to collapse
Hello.
Does this also work for other brands of Tegra Note, like Homecare?
Cheers,
Jaro
Doesn't work, I tried this and it just gets stuck on the Advent Vega logo instead of the TEGRA Note logo.
Ok have you tried going into the bootloader and getting into recovery?
If you get a android with a red triangle just press Vol-Up and power then clear the cache then do a factory reset and then reboot and see what happens.
If after the reboot your still in the same boats as you was before the apx flash then i think it could be due to a messed up partition somewhere (bad block on emmc) i am still looking for other ways of recovering the devices that have bricked but Nvidia has decided not to reply to my messages (Thats the mobile team support for ya!)
I retried the flash and it got to the spinning nvidia logo for a few secs, then it froze and the screen messed up and jumped around pixelly. Then shut off and started getting incredibly hot and wouldn't stop. Seems like bad manufacturing to me.
Sent from my LG-G2 using XDA Free mobile app
It sure looks like that as my first on did this as well. Seems its a hit and miss. My first one died due to the battery getting way to hot and killing the tablet the second one i stopped at 4.3 and i haven't had any issues. So not sure whats causing the issue out right.
Take its out of warrenty?
I hope advent will replace it even while in another country, I got it while under warranty but I'm currently in Belgium. It didn't even last 1 month before dying.
If no luck you could try Nvidia directly via their support
Posting an update. Whenever I try the fix from the advent flash it finishes, reboots and gets stuck at tegra note again.
LightInDark said:
Posting an update. Whenever I try the fix from the advent flash it finishes, reboots and gets stuck at tegra note again.
Click to expand...
Click to collapse
Hi mate, OK how many times have you flashed via the APX ???
Can you get back into fastboot?
If you can try a fastboot -w and then try booting again.
Well I decided to try a full dead battery then left it to full charge)(charging screen still shows fine) then run the flash and now it still hangs, not sure how to enter fastboot with this tablet.
Sent from my LG-G2 using XDA Free mobile app
Press and hold Volume Up + Power Button till a black menu comes up then go to fastboot protocol.
Then issue the fastboot command!
---------- Post added at 03:18 AM ---------- Previous post was at 02:37 AM ----------
If doing the fastboot -w hasn't fixed it the last thing you can try is the following
Download this: https://mega.co.nz/#!3R1GTAxY!ZeQRTsZdP0xVHP8fl4ImsEQK6Wc0br-8BeeWWuKhd94
Extract this to where fastboot is then type the following.
fastboot flash staging blob
fastboot flash dtb tegra114-tegratab.dtb
then reboot and see what happens!
Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.
So a couple of weeks ago I accidentally let my battery die, which I try not to do because I have trouble getting it to turn back on again and this time it did just that: my tablet wouldn't power on at all. I searched up my symptoms: Power light comes on, Doesn't vibrate, Black screen, and everything pointed to either my motherboard went kaput or APX Mode. A new motherboard for my model is upwards of 50$, so I tried looking into what APX Mode meant. I'm decent with computers but this was beyond me, or more so that I have no idea where to find the files/programs to flash(?) it. Anyway digging through the threads here I looked at a recent one here and on a whim I tried the suggestion, even though it was to another problem they were having with APX Mode. And it worked!
My tablet turned on fine, but I am skeptical of how long that will last. So, some questions that I hope someone can help me with are, what is a "fastboot", and does it hurt the system in any way if used repeatedly? Is there another way (an app or something) that will be able to tell me my UID and SBK other than through a Linux computer? Also, bootloading, does that root the device in any way? When I was looking around it didn't sound like it did, but then sometimes it did and now I'm just confused.
Any help would be greatly appreciated, and thanks for looking!
All files needed for unlocking the bootloader, rooting and unbricking can be found in the root guide in my sig. Along with methods of retrieving the cpuid and also a guide to flash the bootloader using the apxflash tool - I try and keep download links up2date, let me know if you have any probs.
If your tab does have a faulty emmc and I'm not saying it does...it will eventually fail, being stuck at the Acer screen seems to be the most common symptom, followed by the inability to flash.
Fastboot gives the ability to perform wipes and flash via the windows command prompt...
Root is gained (on ics) with icsRoot tool...once done you can then nvflash the unlocked bootloader.
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
All files needed for unlocking the bootloader, rooting and unbricking can be found in the root guide in my sig. Along with methods of retrieving the cpuid and also a guide to flash the bootloader using the apxflash tool - I try and keep download links up2date, let me know if you have any probs.
If your tab does have a faulty emmc and I'm not saying it does...it will eventually fail, being stuck at the Acer screen seems to be the most common symptom, followed by the inability to flash.
Fastboot gives the ability to perform wipes and flash via the windows command prompt...
Root is gained (on ics) with icsRoot tool...once done you can then nvflash the unlocked bootloader.
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Ah, thank you! I will definitely go through those. I checked the cpuid one last night in case it decided to die while I was sleeping, so that's good. Although my sister's tablet doesn't have that file on hers at all? And its the same model ... anyway.
emmc? Forgive me, I am not well versed in these abbreviations. It hasn't gotten stuck at the Acer screen yet since I've had it, but ... its always a possibility.
Hmm, I didn't have it connected to the computer when I tried fasbooting it — is it considered something else when you power the tablet on holding the Power Button + the Volume Up button? Maybe it wasn't in APX Mode at all then, but I don't know if that makes it better or worse. No other way would make it turn on, it was just a dead black screen no matter what I did, and then I tried that and the Acer logo popped up.
And, sorry just to be clear, there's no way to unbrick a tablet without rooting it?
Thanks so much
emmc = memory chip!
Per+vol down = custom recovery
Pwr+vol UP = fastboot
Drivers - From Acer and adb_fastboot drivers from android sdk (or the mini.zip in the guide)
Cpuid/sbk imperative to run most of the unbricking files which are based on nvflash.
Root - unavailable on hc 3.2, not needed to unbrick but usb debugging needs to be enabled in settings. For ics use icsRoot,
skrilax_cz unblocked bootloader - needed to install custom roms. Needs cpuid. Will also flash cwm recovery. Gives fastboot ability. So you can flash a new recovery thru Windows command prompt i.e. enter fastboot
Open command prompt
Type in: fastboot flash recovery "name_of_your_recovery'.img
EUU - Acer upgrade tool which gets you back to stock. PC based, needs cpuid and also used to unbrick.
update.zip - Acer stock updates, some are full os dates some are just incremental updates. Used also to help with softbrick like getting stuck on the Acer screen. Cpuid not required, flashed via ext sd card.
Think that's it in a nutshell...as stated get your cpuid NOW
Which build of Android is the tab running??
Sent from my HTC_PN071 using Tapatalk
Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva
Tsilva80 said:
Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva
Click to expand...
Click to collapse
Hi, Tsilva80...
I hate to be the bearer of bad news, but this has all the hallmarks of a corrupted or erased bootloader, in which case your Nexus 7 is probably irretrievably hardbricked.
The lack of the 'white-on-black' Google logo on boot; the lack of the 'white-on-black' battery charging animation when plugged into a wall socket... and the APX entry on Windows device manager, are all symptomatic of a dead, corrupted or erased bootloader.
And without a working bootloader, not only will the device not boot, but you can't even run fastboot commands in order to fastboot flash a Google factory stock image. The bootloader is critical; without it, nothing happens. It's the 'Achilles Heel' of the Nexus 7.
---
APX mode is the default state the Nexus 7 enters into in the absence of a working bootloader, with the expectation that somebody with the necessary technical skills and equipped with an nvFlash tool, will nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7.
Unless you have, at some point, previously generated unique device dependent 'wheelie blobs' using the flatline procedure (See here and here for more details on this) your only option, is to have the devices motherboard replaced.
Even with the 'wheelie blobs', I haven't read anywhere of anybody successfully using them to revive a hardbricked Nexus 7.
---
Your only glimmer of hope, is that you may have inadvertantly ('deliberately') entered APX mode, by mistake... by pressing VOL-UP (holding) + POWER ON when the device was powered down.
If this is the case, then you **might** be able to break out of APX mode by LONG PRESSING the POWER BUTTON for 15-20 seconds... But this will only work if there is a working bootloader for the device to boot into. If it's erased or somehow corrupted, the Nexus 7 is hardbricked.
See this post, for a list of Nexus 7 button combinations, and more details about entering and exiting APX mode.
---
I really hope you can get your Nexus 7 working again, but based on your post, I can't say I'm optimistic. I suspect you will need a new motherboard.
For what's it's worth... Good Luck.
Rgrds,
Ged.
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.
bluescreened803 said:
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.
Click to expand...
Click to collapse
Hi again, bluescreened803...
Apologies with my delay in responding - been busy with family.
------
Regarding reflashing the bootloader...
You're in a catch-22 situation. You need a bootloader in order to flash a bootloader. Without a working bootloader, you cannot 'send' fastboot flash commands to the Nexus 7, and thus cannot flash a bootloader
------
Regarding nvFlash...
I suspect you're alluding to the 'flatline' procedure from 2013...
https://forum.xda-developers.com/showthread.php?t=2455927
This is a procedure which generates device specific 'wheelie blobs' - these 'blobs' are then stored away (eg., on your PC) in preparation for a rainy day, in the event that the Nexus 7's bootloader ever becomes corrupted or overwritten.
Theoretically, these 'blobs' can then be latterly used to rebuild/reconstitute the bootloader, and make the Nexus 7 bootable again, via nvFlash in APX mode.
Unfortunately however, these 'blobs' need to be created BEFORE the bootloader is damaged. And for the sake of emphasis...
Wheelie blobs are device specific.
Wheelie blobs are NOT cross-transferable.
In other words, 'blobs' generated on a specific Nexus 7 will ONLY work for that specific Nexus 7, and not for any other Nexus 7.
-------------------------------------------------
Some thoughts...
I always thought that 'flatline' was somewhat experimental, with a fairly low chance of success, but nonetheless, back in 2013, I generated my own Nexus 7 wheelie blobs - it was a nerve wracking experience, 'cos it involved (if I remember correctly) fastboot flashing a special custom modified version of Clockwork Mod Recovery, which in turn, flashed a special modified version of the bootloader, with special API 'hooks' in it, which allowed the creation of the 'blobs'. It seemed to have gone quite well, with the 'blobs' and associated files successfully created.
However, I never had the opportunity to actually test my 'blobs' out, because it would have entailed deliberately 'bricking' my Nexus 7 in order to actually test them and see if I could resurrect it from hardbrick...
...which wasn't something I was wildly enthusiastic about doing, for tolerably obvious reasons
Anyhow, my Nexus 7 is no longer in use, and last year, to free up space on my laptop, I deleted a lot of stuff, including all my Nexus 7 related files, including my wheelie 'blobs'.
-------------------------------------------------
If your Nexus 7 is bootloader hard bricked, and it certainly sounds like it probably is, then your only realistic recourse is to replace the motherboard.
Rgrds,
Ged.
bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
There is a guide on how to unbrick your Nexus. I have post it on XDA, go check it out.