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.
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.
This is ZE551ML Z00A
First view ? Never used XFSTK downloader ?
(fast forward to 18:30 mins in for settings to be modified in XFSTK re... changing GP over ride to 0x80000807 ) Then follow process from the beginning of the video.
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
isoc driver( install this first on its own )
http://www.mediafire.com/file/qhss2kw3vw8uq19/iSocUSB-Driver_v1.2.0.exe
Files for downloader 551 ONLY !!!
http://www.mediafire.com/file/xd8vll7ep644hyo/droidboot_dnx.img.POS_sign.zip
Downloader (isoc driver needs installing before this, if opens up blank - isoc driver isnt installed correctly)
http://www.mediafire.com/file/qalvtzrm7n2fchp/xfstk-downloader_v1.7.0.exe
Flashtool(install this once you get success at temp bootloader screen after 4 colours)
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Raw files to be flashed in flashtool can be found here on XDA thanks go to RealYoti here >
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
**********EDIT**********
AS YOU MAYBE AWARE , RAW FILES FOR 551 Z00A M ARE NOW AVAILABLE BY REALYOTI ABOVE.
So >
If you bricked in M somehow , extract .184 M stock fw from ASUS itself .
Extract IFWI file and in put the IFWI into xFSTK ...leave dnx fwr and posignbin the same:good:
When you get to bootloader after flashing in xFSTK . Your IFWI version should be >
0094.0183 for M
Then flash 4.21.40.184 M raw file in AFT Provided above .
Note. , if serial number is incorrect , you have to 2 part flash raw in AFT like the video.
If serial is correct , flash raw ONCE only in AFT.
[Deleted
Deleted
Deleted
Ive tried this method coupe times. But SN still 123456789ABCDEF please help me. Tired from this problem for 3 days ?? my device ze550ml
Deleted
timbernot said:
Did you use xfstk flash first or just the raw ?
Can you explain why you needed to use this too? come from 6.0 and bricked?
Click to expand...
Click to collapse
Yes I use on xfstk first then continue to use AFT. But serial number won't recover.
yes I'm bricked when Trying downgrade to lollipop. Now my phone flash successfully but imei and SN not recover.
Fyi, i trin oem partition, then erase etc includes factory on fastboot then my SN are 0123456789ABCDEF. please help me
Deleted
timbernot said:
I'm taking a wild guess here
That you didn't really get success in xfstk but your phone booted to fastboot and you think you had success but have boot loader for 6.0 and are trying to flash raw for. 5.0
What is the boot loader version 0094 ? ? ? ?
Click to expand...
Click to collapse
here my fastboot info :
fastboot mode (red colour)
Product_Name - Z008
Variant - ASUS_Z008
HW_VERSION -
BOOTLOADER VERSION - unknow
IFWI VERSION - 0088.016B
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
continue the fastboot process (blue colour)
any something wrong on that?
beforely, i flash ifwi, dnx, boot, droidboot MM to get my phone bricked. then i used XFSTK too repair it, firmware + OS download success, then show a raibow bar on my phone then my fastboot show, then i use AFT. my SN and My Imei wont recover. i ve tried for couple times and stuck for 3 days for this. please help me
Deleted
People struggling still with this method-- yet i have used it over a hundred times without fail.
Please dont send pm`s because i dont think you get my replies for some reason !
If you are still having probs ....re-download your files required.
Use a good quality usb data cable(one i used which worked perfectly all the time, wouldnt work in xfstk)
Do - extract all files offline with A/V disabled.
People with flat batts --
leave your fone alone and off ,let battery build a bit to kickstart enough to get thru the next phase...
Flash xfstk with(4x0`s) 0x80000807 in CRC box ... get your bootloader fastboot quick then power off via bootloader and charge fone for a few hrs....then let cool before reflashing in XFSTK with settings(5x0`s) 0x800000807
Doesnt matter if it says fails operating system ,aslong as success in ifwi and fwr dnx--- you will be back in bootloader by then
Then let fone stay connected to pc for 10mins atleast before closing XFSTK.
Close Xfstk after 10 mins and flash raw.
Follow vid re.. correcting serial number when fone pauses for approx 3 mins after flashing some cmds, when it stays on result=ok for 3 mins.
Unbrick my ZF2 with thousand of lines...lol
hi timbernot....i hv a problem probly u know of.
resently i bricked my ZF2 at usb mode that is after i upgrade to new software by asus.but forgoten that i've rooted my ZF2 with king root apps.then i found yr method from youtube..well i give it a try with xFSTK.somehow after fullfill the requirement needed i almost score the goal..but!my ZF2 end up with line's on my ZF2 screen.i did saw the bootloader screen for 2 second that everything became shattered.
Xfstk gives you bootloader
Once in bootloader you flash raw
You dont try to boot into system-- you let raw finish and boot into system on its own ,like the vid
The grey screen if thats what you mean with black lines (shattered look) is splashscreen in wrong format of 6.0 /on 5.0
Flash in Xfstk again(correctly)
Follow the vid !
my phone is z008
i use xfstk with 550 file =====> my phone no vibrate . no anything.
and with 551 file =====> my phone virate and blank screen @@
how howwwwwwwwww
Could you mirror the raw file in google drive? the original source is very slow to download
nuzulist said:
Ive tried this method coupe times. But SN still 123456789ABCDEF please help me. Tired from this problem for 3 days ?? my device ze550ml
Click to expand...
Click to collapse
It could be as simple as removing the cable from computer and putting in another usb port.
Mine was at 123456789ABCDEF (and then the Asus Flash Tool does not work) and I did this and the correct serial was shown allowing me to use Asus Flash Tool and unbrick my phone.
its perfectly normal for the first part to have 0-9 serial - restore it by pressing Vol + , when commands on phone stays on `RESULT=OK` for approx 3mins -- Then you force close asus flash tool and restart it and serial will be corrected.
The title of the thread gives us the clue that this will correc t serial number
The vid shows exactly when to initiate.
pay atention in the video from -14.00
dude, please help.
in your video i dit it right at minute 3:18, after never show me the bootloader. The phone restart and the 4 colour appear again.
t00lshed said:
dude, please help.
in your video i dit it right at minute 3:18, after never show me the bootloader. The phone restart and the 4 colour appear again.
Click to expand...
Click to collapse
at -3.18 its on boot screen entering set up
if staying on four colours and not entering bootloader - reflash immediately again xfstk till success:good:
press download in xfstk -- press vol+ and power for 10 seconds and release , might have to do this a couple of times
timbernot said:
at -3.18 its on boot screen entering set up
if staying on four colours and not entering bootloader - reflash immediately again xfstk till success:good:
press download in xfstk -- press vol+ and power for 10 seconds and release , might have to do this a couple of times
Click to expand...
Click to collapse
ok! i will do and let you know.. thanks!
Noob so sorry for the stupid mistake.
Have a 551ML, on bliss w/ TWRP and was supposedly rooted already(can't remember which method I used, but the start screen was white background/black words). Have been using the phone for a year without issue.
One day some kind of stupid just came over me, and I followed this thread:
http://forum.xda-developers.com/zenfone2/general/unlock-zenfone2-android-6-0-beta-unlock-t3411264
without even sure what was I suppose to be doing...(not blaming OP, I am the dumba** here)
everything went through just like suggested, but now the phone start screen shows un-rooted(black background, white words), and the phone is stuck on fastboot... Can't get into recovery or normal boot.
Can anyone advise what am I suppose to do now? I am thinking I need to unbrick the device using this guide:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But I am stuck at:
1.2 Connect with computer IntelSoc Zenfone 2:
Can't seems to get the computer to register my 551ML as a 'MOOREFIELD device'?
Can anybody gives me some pointers or maybe there are some easier way for my situation?
p.s. here are the fastboot info, in case it might help:
HW_VERSION - UNKNOWN
IFWI VERSION - 0094.0183
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
continue the fastboot process
Thx in advance!
nexusroad said:
Noob so sorry for the stupid mistake.
Have a 551ML, on bliss w/ TWRP and was supposedly rooted already(can't remember which method I used, but the start screen was white background/black words). Have been using the phone for a year without issue.
One day some kind of stupid just came over me, and I followed this thread:
http://forum.xda-developers.com/zenfone2/general/unlock-zenfone2-android-6-0-beta-unlock-t3411264
without even sure what was I suppose to be doing...(not blaming OP, I am the dumba** here)
everything went through just like suggested, but now the phone start screen shows un-rooted(black background, white words), and the phone is stuck on fastboot... Can't get into recovery or normal boot.
Can anyone advise what am I suppose to do now? I am thinking I need to unbrick the device using this guide:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But I am stuck at:
1.2 Connect with computer IntelSoc Zenfone 2:
Can't seems to get the computer to register my 551ML as a 'MOOREFIELD device'?
Can anybody gives me some pointers or maybe there are some easier way for my situation?
p.s. here are the fastboot info, in case it might help:
HW_VERSION - UNKNOWN
IFWI VERSION - 0094.0183
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
continue the fastboot process
Thx in advance!
Click to expand...
Click to collapse
flash boot image
then flash recovery image
then any rom you want
Thank you for replying so quickly!!
Can you be more specific on how to 'flash boot image'? I have tried to put the asus OTA image on the SD card, but it didn't triggered....
small update:
I have extracted boot image(boot.img) from ASUS Z00A firmware, and download the correct twrp recovery(twrp.img), and tried the following commands:
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot erase cache
and the result is still the same. Only able to reboot to bootloader no matter what, with the 'continue the fastboot process'.
Can anybody share some thought? really miss using my Z00A......:crying:
nexusroad said:
Can anybody share some thought? really miss using my Z00A......:crying:
Click to expand...
Click to collapse
Here is your rescue: http://forum.xda-developers.com/zenfone2/general/wwze551ml2-20-40-19420160713-raw-t3437416
Thank you so much!! The ASUS Flash tool works, and I have my Z00DA back to life!
For people with similar issue and want to use the tool, please noted that it takes a while(~15 min for the flash) + the tools does not shows any progress %, and afterward it will takes another 10 mins for the phone to start, so be very patient.....
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.