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....
Reading through different forums I have read problems similar to mine but nothing exactly the same. I followed each fix anyway but I have not been successful.
The last thing I remember I did before the brick, I flashed CWM touch then CyanogenMod 9. I am unsure what occurred but I tried to flash back to my JB backup and the problem started.
Now my tablet comes on and just hangs on the Asus splash screen. If I turn the tablet off, it automatically comes back on.
I have tried to turn the tablet off and boot into recovery but it just boots back up to the splash screen and hangs; I have no option to go into recovery, android or fastboot.
I can get into what I think may be USB mode by pressing power and volume up through a couple of cycles; my computer detects a device but I cannot load drivers.
I have downloaded the Android USBPCdrivers but each time I try to navigate to the folder to install the device manager fails.
If anyone has any thoughts I would appreciate any assistance, thanks for your time!
UPDATE TO ORIGINAL POST
I as able to finally get my computer to recognize the tf300t in device manager by wiping all the usb drivers and installing "Universal Naked Driver 0.7" posted by 1wayjonny from XDA's website http://forum.xda-developers.com/show....php?t=1766220, not sure if it matters my computer "sees it" as a ASUS transformer prime rather than tf300t.
Now I am reviewing an ASUS unbrick called Wheelie http://forum.xda-developers.com/show....php?t=1687285, I believe this is geared towards the tf101. Anyone have any thoughts based on my status at this point? Thanks
If you are on JB stock, there is no way to flash a booting Cyanogen 9 ot 10 Rom.
Only Hydro JB is running!!!! And JB Stock.
1st of all you have to download a special Recovery. I highly recommend TWRP. You have to dl the JB version!!!!!
Flash it through fastboot. Then flash the Stock JB via TWRP recovery
Then flash TWRP again via fastboot.
Than flash The Hydro JB rom
Then reboot
Then go back to recovery
Then flash the latest Hydro update and reboot
You are like me stuck on the f...... new JB Bootloader and Kernel. All other roms are for the ICS Bootloader and Kernel, so no way of getting them running until the Cyanogen devs finding a solution.
Fastboot not an option
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
mfsmith said:
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
Click to expand...
Click to collapse
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
喔喔兒 said:
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
Click to expand...
Click to collapse
Waiting for nvflash won't do you any good since you needed to have it BEFORE bricking your tablet. If your tablet is already bricked, APX/nvflash will not help you.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
He could still try sending it for RMA. Mine got repaired for free for some reason.
An unusual Asus TF300T brick
Yeah, I'm having problems with my TF300T, too. I had CWM installed, but when I tried to flash a new ROM, I bricked it. No problem, I had figured it out before. But when I was in the bootloader, I inadvertantly erased instead of selecting the USB. Now, All I get when I try to boot up is the white ASUS screen with;
The Device is Unlocked
Android cardhu-user bootloader <2.0 e> released by "ww_epad-9.4.3.26-20120416" A03
Checking for android ota recovery
Booting recovery kernel image
My computer sees the tablet. The Device Manager shows: Asus Transformer Prime APX Interface
But it only shows up when I reset. As soon as I try to boot the tablet, it no longer sees it. I can't access the bootloader and Fastboot doesn't do anything except "waiting for device".
SO! If anyone can give me some help, I'd appreciate it. It's a puzzle for ya, anyway.
Thanx
As your last resort, this worked for me
Link to my thread---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to ask anything.
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T
jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.
I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse
jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!
noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.
I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl
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.
Alrighty, I seem to have hardbricked my transformer, after rooting and unlocking it I attempted to install Ubuntu Touch on it. ( Found out that Ubuntu Touch kinda sucks and I prefer Android for now)
During the restoring process some bad stuff happened, long story short i lost my backups. I then tried to restore it to stock firmware with ADB/Fastboot and the firmware from the asus website.
During the restore process the cable got disconnected from the computer, when I tried to start the process again my PC couldn't recognize my tablet and my tablet could not boot at all, not even into recovery.
From what I've read about my tablet I can only assume that it is now currently hardbricked. When I hit the power button nothing happens, when I try power button and vol-down nothing happens, same with vol-up. Reset button doesn't do squat.
I'm gonna try unbricking it even though I'm pretty sure I'm out of luck.
If you guys have any suggestions that can help me out, I'll be refreshing this thread every few minutes to see what you guys have to say.
And if you have any questions about what I'm doing or how I've messed it up so badly I'll try to answer them.
Wish me luck!
Edit: Alright, I can get into APX however I don't have any backups. From what I've read I can't use other people's Flatline backups to fix my own tablet, can anyone confirm or deny that?
Regardless, is there a way that I can use NVFlash to directly flash the system with the stock blob or am I just completely out of luck?
Evercroft said:
Alrighty, I seem to have hardbricked my transformer, after rooting and unlocking it I attempted to install Ubuntu Touch on it. ( Found out that Ubuntu Touch kinda sucks and I prefer Android for now)
During the restoring process some bad stuff happened, long story short i lost my backups. I then tried to restore it to stock firmware with ADB/Fastboot and the firmware from the asus website.
During the restore process the cable got disconnected from the computer, when I tried to start the process again my PC couldn't recognize my tablet and my tablet could not boot at all, not even into recovery.
From what I've read about my tablet I can only assume that it is now currently hardbricked. When I hit the power button nothing happens, when I try power button and vol-down nothing happens, same with vol-up. Reset button doesn't do squat.
I'm gonna try unbricking it even though I'm pretty sure I'm out of luck.
If you guys have any suggestions that can help me out, I'll be refreshing this thread every few minutes to see what you guys have to say.
And if you have any questions about what I'm doing or how I've messed it up so badly I'll try to answer them.
Wish me luck!
Edit: Alright, I can get into APX however I don't have any backups. From what I've read I can't use other people's Flatline backups to fix my own tablet, can anyone confirm or deny that?
Regardless, is there a way that I can use NVFlash to directly flash the system with the stock blob or am I just completely out of luck?
Click to expand...
Click to collapse
Buy a new logic board. It's not too expensive.
With only APX mode and no nvflash files you are hardbricked. Period.
das chaos said:
Buy a new logic board. It's not too expensive.
With only APX mode and no nvflash files you are hardbricked. Period.
Click to expand...
Click to collapse
I had a feeling that was the case, I'll make sure to use Flatline once I get it so it doesn't get this bad again.