Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.
Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.
Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...
Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.
berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?
sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...
berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.
Related
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hello guys,before with the rom hidro ponic 4.4 all was well.After i want change my rom and i've brick my asus after flash rom unofficial cm10..because the camera apk not found, and dispay is total green..I suppose the problem is the rom but after another flash rom the problem is same.On again the display is lock on the logo Asus and upstar on the little: the device unlock..stop.My asus there's no way to get it to recognize at pc and the driver installed not found..are't fastboot logo in Controll Pannel.I've not possilìbility to choce android--usb--wipe data.Help me please thank you sorry for my English
What about booting into recovery? Or fastboot?
As far as I understand your post Android isn't booting, but what if you hold volume-down when you turn on the tab?
I have almost the same problem. I flashed a bad boot blob (vanilla linux, not android) and now I'm stuck at the first Asus logo if I boot normally. But I still have fastboot and CWM recovery so I'm confident I can get it back into shape (even though a restore in CWM didn't help)
I think there's no way to unbrick the device,because I have the same problem.
I flash my device to official 4.1 and I found I lost root of my device
So I try to downgrade my device,but I failed...
Then I try to enter recovery and I failed again...
At last I try to wipe data of my device but it had no respond...
Of course,I had to reboot my device...
The result is:It bricked...
The symptom is just like the thread starter
What should I do???
I tried to contact the customer service of ASUS,but they said the device which unlocked by yourself couldn't get any warranty,even I willing to pay for it
(I think the customer service of ASUS is too bad,especially their attitude)
(I'm also sorry for my poor English...)
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
e...Thanks anyway
But my problem(the same as the thread starter) is:I couldn't enter either fastboot nor recovery
If I could enter one of it,I think I can fix it...
(Maybe I misunderstand what you mean?)
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
Thanks guys Today i can try the guide..we ope in God:angel:
I try twrp jb recovery but not function because the teerminal it's impossible go in download mode (down+power)....The Jig Usb forf Asus exist?
Hello guys, but for this type of brick no one has an answer? Method with nvflash can 'operate according to you ..? But I'm trying to appear APX and install the drivers as a guide is a company because it makes them install it
As far as I can see nvflash is coming to TF300T, it has been developed for T201 (http://androidroot.mobi/t3_nvflash/). But at least for TF201 they have to have fastboot first, so that may not help you.
If I understand you correctly nothing is booting and you have neither ADB nor fastboot access. In that case I don't think there's anything to do except wait and hope for a working nvflash or to try to have Asus fix it, but since the tab is unlocked they probably won't do so for free.
It seems this tab bricks easily.
I have the same problem, and I hope nvflash too. But I don't know nvflash in dev or no. This my best device which die first. Cry
Having the same problem here also. Only had the tf300t for less than a week.
Here is a sticky to a thread I made. I'm just waiting for people to put in a bunch of ideas. Hopefully NVFLASH doesn't need fastboot.
http://forum.xda-developers.com/showthread.php?p=31465583#post31465583
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
surdu_petru said:
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
Click to expand...
Click to collapse
...Tried it about 1000 times, not possible, but thanks anyway. No fastboot possible, NVFLASH won't be working either...
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck!
Same problem. Stucked at Asus Logo but i can go into recovery. What can I do? Help me please
My PC finds it as Fastboot.
Seem I'm no alone...
Seem I'm not the only one.
This morning I bricked my tablet, 5 minutes after I bought a wall charger on EBay... :crying:
As for now the only answers seem to be from people that don't read post good.
We can't get to use the recovery...
Again, if someone knows how reset the tablet prior booting...
I beleive that its the only other way.
The last possibility, buy a new one...
I believe the problem started before.
- I unlocked my tablet more that a month ago, at the Jelly Bean release.
- Rooted
- Installed the official release
- Everything went well, up to this morning
- I noticed that my Rom Manager Premium start to show adds
- Goo manager refused to install recovery script
- Then I tried to go in recovery, it fails.
- I said to myself that it was better to start from scratch
- I tried a Factory reset using setting menu.
- After this step the tablet started to show This device is unlocked
-After the last step the device wouldn't boot no other way...
I don't know what happened but it seem a bit strange that everything worked fine before this morning.
For sure I'll keep exploring ways to get out of this mess.
But if I have to buy another tablet, there's a chance that I'll go to a Nexus 7...
Good luck to all the other unfortunate that that are in the same boat.
Alain
Hi back,
After I bricked my device i sended back my tablet to canadian customer service.
At first the didn't wanna fix the proble and the service told me that he needed to change the motherboard.
I argue a while and after an email discussion whit the customer service agent, they told me that they would fix the problem for me THIS TIME.
This morning I received my tablet and everything seem to work fine, as it was reset to factory.
BUT, after I started to investigate, seem that in no time the cover removed.
And maybe the motherboard change is a trick to suck more money from the users.
In fact I can't understand why you'de have to change the motherboard after the tablet is bricked.
Maybe I'm wrong, but I find this way of doing thing awefull, and I consider lucker that I got outa this mess...
Good luck to the others unfortunates
Alain
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Bricked TF300GT (please help)
Hello developers,
I have a bricked Transformer the goes in a loop flashing ASUS every 5 seconds or so. That was after having unlocked and then reset to factory default.
I have been reading a lot of articles at various forum for a solution. I have never seen something so confusing. Please is someone can point to me a page where the un-bricking is described step by step for that aparticular model?
Many thanks in advance
Yves
NB: I have tried the -volume and power button trick or the +volume power button that just make a USB connection on my PC
---------- Post added at 11:01 AM ---------- Previous post was at 10:53 AM ----------
tobdaryl said:
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Click to expand...
Click to collapse
I have the same problem and done what you described without success. What must I flash with fastboot and where will I get fastboot. I believe my machine is in JB 4.0.. Many thanks,
Yves
i got my tf300t bricked to.
got my tablet this weekend wanted to install cyanogenmod.
just did a week early'er a other one (the one for my mother)
that went well
my tablet installed de orginal 4.2.1 from asus.
Today wanted to install cyanogenmod.
run first de unlocker v8
the installed fastboot twrp421.blob
when i went to the twrp menu the cyanogenmod wont install, but the orginal wont start also not, it want nothing to start.
tryed with external sd.
ok i thought i want cmw so i run the recovery-clockwork-5.5.0.4-tf300t.img
went wel also.
i can only go to cwm but they are no file rights and still can install a zip or mount a sd internal or external.
now fastboot is not working
when i turn the tablet on it is going to cwm
wat i can do?
edit:
cmw version = v6.0.2.3
Me too! asus ask 230$ for replace new mainboard. I think they want eat money, because they already have nvfash to fix. 230$ can buy new item from amazon. I hate asus and never buy any thing of asus. Very bad support.
signature Mismatch Unrecoverable bootloader error 0x00000008
unlocked & rooted.
had TWRP TeamWin installed
tried to install a new Rom & got the above error
wiped data & now only the following shows.
signature Mismatch
Unrecoverable bootloader error 0x00000008
is this unit dead & not fixable?
I bought from Amazon so maybe returnable? if not fixable, had for a week now.
If you can't get into fastboot or recovery then it is hardbricked.
le rustle face
Keion said:
If you can't get into fastboot or recovery then it is hardbricked.
le rustle face
Click to expand...
Click to collapse
have never used fastboot icon but it dont boot that far for the icons to show anymore.
but no recovery as it can't continue far enough for TWRP TeamWin splash screen to show up
as i guess the bootloader needs to work to get past this stage.
as far as I read there are no fixes for bad bootloader. but this was posted in feb & march of 2012 so I was hoping for new info & maybe a fix.
this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.
Maybe toggle signature verification to disabled? Or if your able to still go into recovery, sideload the latest firmware from asus site and flash it from recovery?
..........
Sorry just read the above comment... Hopefully someone here can help you out. Good luck to you!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
atc3030 said:
Gtalk Me before you send it. I think I had the same problem and if so i can fix it for you. Gtalk: [email protected]
Click to expand...
Click to collapse
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.
lafester said:
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.
Click to expand...
Click to collapse
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.
okantomi said:
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.
Click to expand...
Click to collapse
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
I'm really sorry this happened to you, but you probably knew you were venturing into very untested ground.
Are you posting in the Pre alpha AOSP thread? That might be more productive for you. It seems there have been at least 3 hardbricks from flashing that rom.
polish_pat said:
this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.
Click to expand...
Click to collapse
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
Im not bashing anyone or any product, was my fault, no one elses. I have been modding for 20 years & should have known better & done more research into what I was doing here. We are warned all over these forums that everything we do is a risk. you dont blame anyone but your self.
JTAGing would be the way to repair, I agree, I just haven't found anything for the transformers yet. been looking, but nothing out there that someone has connected & got to work. just talk about jtag & transformer. there are some arm7 jtag programmers im sure some software could be made, but I think we are far from knowing how to talk to the bootloader in a low level, im sure some are trying to reverse engineer to get to the boot loader.
yes, windows loads the drivers when you hold the right vol button + power. you hear it connecting if windows 7 has speakers on. the drivers do have to be installed for this to work, I think the device is called APX in device manager.
I have posted in the other forum about this, but like I said above, not a products fault.
I would like to thank everyone for there input.
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
The Volume Up + Power button combination allows you to put the device in APX mode but it's still useless without a working NVflash solution.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
thanks for the info Pretoriano80
I will keep researching for Jtag & bootloader recovery & waiting for nvflash to be ported to the transformer series Doesn't even seem JTAG would even be needed just a port of nvflash, jtag would be a marketing thing most likely after reseaching other tablets that have unlocked bootloader, they just use nvflash if im correct in my finding here. as if it can be fixed down the road then no worries anyone would have as it could be fixed if a JTAG or nvflash portedwas made, bought & was plug & play install not taking apart tablet, just plug into docking station port & plug usb cable to computer install drivers & JTAG software GUI interface software made for windows 32bit & 64bit plus Linux support also or just nvflash ported. im sure there are people already looking into this.
I sent back the unit to Amazon will get another unit late thursday.
I think I will only root this unit, until I understand & research more on Android devices like I should have from the start my mistake, No one else, as this was my fault & no one else.
everyone should know everything is at risk, if the bootloader is unlocked. my new replacement will only be rooted, till I see a must have for a unlocked bootloader. rooted seems to be a must have. but not a unlocked bootloader at this stage of the transformer. maybe at some point down the road, it would be a must have, but time will tell.
:fingers-crossed: Let me know if any of you are looking into JTAG & or nvflash for the tranformer, im sure nvflash is the way to go & not jtag
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Click to expand...
Click to collapse
Is there a version of cwm yet? Although it has some really great features, I still don't quite trust twrp after causing all of those soft bricks after recovering by not properly restoring /boot
Sent from my Nexus 7 using xda premium
Thread cleaned. Take the fighting out to the parking lot boys....
Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?
musicfreak said:
Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?
Click to expand...
Click to collapse
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Click to expand...
Click to collapse
I thought I couldn't make my Transformer to power down. I hold the power button till it vibrates as you suggests. When I press volume down - power button nothing happens, the screen remains blank...
Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.
musicfreak said:
Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.
Click to expand...
Click to collapse
For this procedure, you must have obtained a blob.bin file by installing the hacked bootloader while you were still on a 9.4.5.26 or older bootloader.
If you don't have this file, and you don't know your tablet's unique SBK (Secure Boot Key), which nobody outside Asus knows, then you can't use nvflash.
Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...
musicfreak said:
Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...
Click to expand...
Click to collapse
If you can't get into recovery and you're using the correct side of the volume rocker (left!) and it really, really doesn't react to holding the power button for eternity - then you're probably bricked
The question is why? And how?
This hardly ever happens on the CleanRoms...
Did you reboot into system after flashing the bootloader and before flashing CromiX?
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I don't know what happened after I flashed the 10.6.1.14.4 WW Bootloader and TWRP 2.5 recovery. After a while the tablet didn't react anymore...
In a Dutch forum I get the suggestion to check Easyflasher (http://www.youtube.com/watch?v=BxNmK6uXfFE&list=PLudvvIZ2s2oHbCK2Gb8aZHIoPpABzwthA). But om http://forum.xda-developers.com/showthread.php?t=1688012 I read WARNING: IF YOU USE THIS ON YOUR TF201/TF300/TF700 YOU WILL BRICK IT so this will be of no use I think.
I wouldn't use this -- it has been reported earlier to brick.
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)
berndblb said:
The question is why? And how?
This hardly ever happens on the CleanRoms...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I strongly suspect the Recovery, I also had issues attempting to flash a later version of Clean
Rom. It took a day of flashing to get the tab back to health. Along the same lines I have also had issues flashing my T'bolt and also my DNA. For the time being I am refraining from changes on the tab and DNA.
I have used both CWM and TWRP
MartyHulskemper said:
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
Click to expand...
Click to collapse
I've done this, but I see no Icons.... For me it's hard to see if my tablet is on or off. But when I hold the power button for a long time it vibrates so I assume it's off then.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)
Click to expand...
Click to collapse
What a great offer! Sometimes I visit Utrecht, and the UMC so this would be nice. When I'm planning to visit Utrecht I will give you a sign.
OK, so I went over and despite musicfreak having good ideas along the way, we haven't been able to revive his 700, and I'm not feeling too optimistic it can be done. However, I don't want to pass up the opportunity for _that to show off his immense skill once more (feel the pressure? ) and help musicfreak out.
In short:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
- the procedure for reflashing stock doesn't work at all, obviously, because there was a custom recovery (TWRP) -- still, grasping every little straw, we tried -- everything -- but the screen stays black.
My own 700 is detected properly in fastboot mode, so it seems unlikely we have a cabling and/or USB port and/or OS error (tried both WinXP 32-bit and 7 64-bit).
After the usual hassle of getting the drivers in place -- musicfreak's saving the day of installing the patched drivers (I though the patch had gone mainline by now) -- we haven't been able to get any further.
Is there a command we can get to the device in APX mode to detect what is causing this?
Is this recoverable? RMA?
Thanks for the help and insights, guys and girls.
MartyHulskemper said:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
Click to expand...
Click to collapse
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
MartyHulskemper said:
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
Click to expand...
Click to collapse
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
MartyHulskemper said:
Is there a command we can get to the device in APX mode to detect what is causing this?
Click to expand...
Click to collapse
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.
_that said:
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.
Click to expand...
Click to collapse
Yup, the two options you call out here were in my head, too. I got over to musicfreaks' thinking that the bootloader was actually working, but it soon turned out to be dead. Since the only mode Windows can detect is APX and neither adb nor fastboot give any reaction or meaningful reply, I guess musicfreak's 700 is deceased.
@OP: given the fact that even our guru knows not how to save your 700, it comes down to either salvaging the parts and selling them on their own, or selling the broken unit and dock together subtracting the repair cost.
Anyone having specific ideas which is better? (I'd veer towards selling it in whole, which at least makes sure you're not going to get stuck with loose parts...)
Yes, there seems no hope for my TF700 anymore....
I also think that selling the whole set (tablet and dock) is the best choice.
Unfortunately looks like a brick to me. Without nvflash the only option is to send it off to Asus if you want it fixed. Otherwise sell it for parts (Screen, digitiser, case etc)
I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.
musicfreak said:
I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.
Click to expand...
Click to collapse
Nope. If it were unencrypted, we could've tackled it ages ago and use it to unlock the bootloader without ASUS knowing. I have no doubt that the processor serial number or some other identifier does figure into the process, but we do not know the rest of the algorithm used.
As to your specific question: there is no use in trying to flash anything from the microSD card since we couldn't get into the bootloader at all, and therefore have never even seen a recovery of whatever description or denomination.
As I said when I was at your place: I was udner the impression you at least had the bootloader and fastboot access. Although it's probably hard working even then, it would not be without hope. Not having a bootloader, and not having Nvflash at hand, well... I fear it is without hope.
It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.
musicfreak said:
It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.
Click to expand...
Click to collapse
No it is no more risky than flashing any ROM. Flashing a ROM is not very risky cos even if you brick you will be soft bricked and usually that is recoverable. Your issue may have been related to the bootloader and recovery flash. Did you interrupt it - it should have rebooted on its own after the blue bar went to full?
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?
So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)
Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......