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?
Related
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....
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
what boot loader> also you did wipe from recovery not the first menu right?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
bricked tf300
MaMMiTs said:
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
Click to expand...
Click to collapse
Yes it is unlocked Jellybean nothing happens if i keep holding the volume down and power except the screen goes off for a second the right back to the asus screen Fastboot won't work, it just says waiting for device My pc won't see it at all, not in device manager or anyuthing No apx either. If i could get fastboot to work i think i could fix it
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Also same problem. Fastboot 'sees' the TF300 device but does not flash.
I have the same problem. Fastboot 'sees' the TF300 device but does not flash. If somone has come up with a solution for this, could you please share, it would be greatly appreciated. Did Asus finally release NVflash for JB 4.2? It seems it is the only possible way of solving this, or isn't it?
Thanks for your help
aarsyl said:
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Click to expand...
Click to collapse
---------- Post added at 08:44 PM ---------- Previous post was at 08:31 PM ----------
It seems there is no solution yet. See this post:
http://forum.xda-developers.com/showthread.php?t=2179874&page=17
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
What happened in the end? Did you go to ASUS and get it repaired? How much did it cost?
Hi guys,
I solved the problem with the bootloader error (0x0000000) assistance in sending the TF300T. I told him that during the upgrade something must have gone wrong and the OS did not boot anymore. They repaired free of charge. My dealer to whom I entrusted the tablet is Mediaworld (a chain of electronic products Italian). I hope you can serve
Hello,
I loaded the wrong version of TWRP on my TF300T. When it rebooted it loaded CM10.1 just fine. I then rebooted a second time in recovery mode and I have been stuck at the ASUS screen with the "device is unlocked" message. I am able to get into APX mode but my research has shown that mode doesn't do me any good if I haven't ran a nvflash backup. I am stuck and I would appreciate some advice or suggestions. I wonder what the factory reset fee would be from ASUS.
Thank you for your responses!
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
macgyver40 said:
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Thanks for the speedy response =)
Version History: Stock 4.1 -> CM 10.1 Nightly 0503 or 0429. I had CWM on it before trying to load openrecovery-twrp-2.5.0.0-tf300t-ICS.blob using the terminal emulator method. I think I should have loaded the JB blob but the warning on the TWRP site said to use that if you ran the offical OTA update, which I never did so I stuck with the ICS. It installed fine, then rebooted into CM 10.1 just fine. I then rebooted from there into recovery and have been stuck at the ASUS screen since.
The Vol + - button keeps me in the ASUS screen. Reset button keeps me in the asus screen. Vol + + puts me in APX mode.
I try running fastboot in APX mode but it hangs stating "waiting for device" so I don't think it'll work in APX mode.
Thanks.
T
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
c0ded said:
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
Click to expand...
Click to collapse
I bled it last night. I'll try booting it this evening. Thanks!
racet said:
I bled it last night. I'll try booting it this evening. Thanks!
Click to expand...
Click to collapse
No luck. I bled it twice and I'm still stuck at the ASUS logo with "the device is unlocked"
Am I looking at repair here?
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of eBay and replace it with the one in your tablet. Also, to save other people's tablets from bricks, you may want to look into this petition.
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
c0ded said:
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of
Wow 200$ what a load. To what degree of difficulty are we talking with replacing the mobo? Ifixit makes it look doable, yet at the end he messed up his LCD screen.
Click to expand...
Click to collapse
macgyver40 said:
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I would def like to try it if you can find it.
T
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
http://forum.xda-developers.com/showthread.php?t=2041528
found it. Hope this helps you like it helped me out of my broken recovery. once you download and add the files you want its pretty easy. the script in english makes it pretty easy to understand what your doing and hope it works since I know my TWRP was broken I couldn't even sit at the recover,android wipe screen for more then 3 mins without it bootlooping. I put it on that screen while connected to laptop ran the recovery flash and all went well installing TWRP 2.5 which I then recovered my backup and that even restored my 2.4.4 patch TWRP like nothing happened at all. tablet runs great and have made 3 backups that work after all this.
Good luck
macgyver40 said:
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Please take your time. I have no problem waiting especially if the only solution is to drop 75$ on a replacement mobo.
You could send me the file via email or drop box if it's easier. I was going to use the TWRP 2.5 JB with CM 10.1 nightly. I appreciate all the help!
T
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
macgyver40 said:
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I tried running through your tread but none of the commands worked on the script. Probably because I can't get fastboot to work. When it tries to load a recovery it just states: "waiting for device" and sits there. =/
c0ded said:
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I am unable to get fastboot to recognize the device. The only way the PC recognizes it is via APX mode. Download mode just sits there at the ASUS screen and windows doesn't see any devices.
Still no love. Am I bleeding out the battery correctly? I am just running the boot screen until it dies then I try to power it on again.
I popped the back open today to see how difficult it would be to replace the mobo, doesn't look too bad. Just having difficulty finding a good online guide.
Also, just so I have the terminology straight, when the tf300t goes into a "boot loop" does it ever leave the asus screen and go black or does it just hang? Mine never goes black, just sits at the ASUS screen with "the device is unlocked" message. The only time I can get it to leave this screen is when I do a reboot and hold the + sign. then it goes black and APX is detected on windows.
Just wasn't sure if any of that information was useful.
T
One other solution is to unplug the battery for 30 minutes, then plug it back in.
c0ded said:
One other solution is to unplug the battery for 30 minutes, then plug it back in.
Click to expand...
Click to collapse
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
racet said:
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
Click to expand...
Click to collapse
Usually, the volume button does not fail. Remember the volume button connects to, but is NOT part of the mother board. If it feels stuck when you push it, that's because you snapped the back cover in wrong. You need to slide it in at the corner where the buttons (volume & power) are, then pop in the rest of it. Take it out and do it again.
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.
Hello Friends and first I have to say sorry for my english.
OK, I try to tell whats happend.
2 Days ago I would like to flash a new rom on tf700t. For that it was neccessary to change from TeamWinRecovery to ClockworkModRecovery.
To do this at the easiest way, I have done this Job with the Rom Manager App.
That was my first error.
After Installing I reboot my tf700 and was surprised, TeamWin was still there...
Ok I have created a full backup, after that I performed a full wipe.
After that I have rebootet again, but know TeamWin was not there anymore, Clockworkmod was also not not there.
Booting with Power + Vol Down Fastboot mode is starting (I think so) 3 Symbols in the Middle.
Starting RCK Mode, but nothing happens, only a text left above, Recovey Rom is loading (or somthing like that)
Booting with Power + Vol Up APX Mode is running. Black Screen and Pong on my PC. Nvidia Driver installed.
OK later, verry late at night I have by mistake Used The Wipe Button, I dont wont to do that but I have pressed the wrong button.
Now the follow things happend by Booting.
Only Presss Power:
Tab is starting to Asus Logo in the middle, in the left corner abowe The Device Is Unlockes. Nothing else happens.
Press and hold Power and Vol down: The same like above No Pong on PC, the same screen like starting the tab normaly.
Press and hold Power and Vol up: APX Mode ist starting.
I have many Full Backups TWRP.
I have the Stock Asus Rum on SD Card.
I have the nvflash Package for my tf700t.
I have the flatlinetf700t.img
And many other files.
Oh I dont have createt bevor any blop files.
What I will ask you is: Is it possible to repair the Tab by using nvflash?
I think the bootloader is defect...
What is needed for that
wackaman said:
What I will ask you is: Is it possible to repair the Tab by using nvflash?
Click to expand...
Click to collapse
Not without the blobs.
"Wipe data" + broken recovery + no blobs for nvflash = hard brick. There is no known fix.
Is it possible tu use blob files from an other tf700t 64gb??
I have here a original asus tf700 Stock rom, wich I have full extracted twice. So now I have the rom as a blob file wich was in the zip. 800 MB.
What can I do with that file?
Here I found something to use the android toolkit but it cant work, there is no fastboot mode anymore. If I try to use fastboot, power and Vol down, nothing happens, there is no device installed at pc, only in adb mode, but android toolkit could not handle adb mode.
Read
Last hope is to use some other blob files..
Whats about RMA? Prices for that job?
Thanks.
wackaman said:
Is it possible tu use blob files from an other tf700t 64gb??
I have here a original asus tf700 Stock rom, wich I have full extracted twice. So now I have the rom as a blob file wich was in the zip. 800 MB.
What can I do with that file?
Here I found something to use the android toolkit but it cant work, there is no fastboot mode anymore. If I try to use fastboot, power and Vol down, nothing happens, there is no device installed at pc, only in adb mode, but android toolkit could not handle adb mode.
Read
Last hope is to use some other blob files..
Whats about RMA? Prices for that job?
Thanks.
Click to expand...
Click to collapse
You need the blob files from your device. They store keys particular to yours. When you started the nvflash process it sounds like you never completed it. That means you have no means of recovering.
List the files you have.
RMA will set you back between 200 to 300 dollars but ask Asus for a quote. You might be better off selling it for parts and getting something newer.
What I have is all from here, means the nvflash files for my tf700t.
I also have the original asus stock rom for my device and some other roms, twrp backups and so on...
The most is not usable while there is no fastboot / adb mode possible.
I have never read something about some blob files needed for other devices...
I dont understand what for blob files I need to bring recovery back. Thats all I want to have.
I tried to flash via nvflash the stock asus extracted till to a blob file. I remember nvflash wrote than somewhat like, no blob files found...
Maybe its really time to say goodby to this ....
wackaman said:
What I have is all from here, means the nvflash files for my tf700t.
I also have the original asus stock rom for my device and some other roms, twrp backups and so on...
The most is not usable while there is no fastboot / adb mode possible.
I have never read something about some blob files needed for other devices...
I dont understand what for blob files I need to bring recovery back. Thats all I want to have.
I tried to flash via nvflash the stock asus extracted till to a blob file. I remember nvflash wrote than somewhat like, no blob files found...
Maybe its really time to say goodby to this ....
Click to expand...
Click to collapse
If you followed the instructions on that page including the wheelie part to extract and save your blobs then your device is salvageable. The question is did you?
If yes you can use this guide to restore.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
If no, sell the device for parts as it is dead.
Thanks again.
I have asked Asus for Support and I post again after an answer from asus.
**** happens. That with the strongly recommed to do to make this device bricksave has to be placed on every first sites about this Thing.
Are there more devices who needs those files (means blobs)
wackaman said:
Thanks again.
I have asked Asus for Support and I post again after an answer from asus.
**** happens. That with the strongly recommed to do to make this device bricksave has to be placed on every first sites about this Thing.
Are there more devices who needs those files (means blobs)
Click to expand...
Click to collapse
Get a used motherboard on Ebay and replace it yourself. Sure to revive your darn tab for much less. What is it an Asus technician can do that you can't? It ain't rocket science after all. Go to this site and learn how to take it apart.
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
wackaman said:
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
Click to expand...
Click to collapse
Asus will do nothing other than charge you hundreds of dollars to replace the main board.
wackaman said:
I dont know, what asus can do...
I have now looked many days for a mainboard for my device. Only 32GB Version are listet by ebay.
Maybe I have to wait...
Click to expand...
Click to collapse
Since you are giving up and looking for a new mother board, you can PM and we could try a few different things to see if we could wake it up... If you have some spare time to waste then you could give it a shot, hahaha....