I tried to use fastboot to install a blob..
It must have frozen or something. It got through sending the blob, then it try to write the system file but it hung overnight and did not finish. I had to try reboot the tablet.
It now does not turn on, go into APX, recovery, or even light up that its charging. The only indication that I get that it has any life left is that when I try turn it on when it is plugged via USB to my PC, my computer makes the noise it does to recognize devices.
Please tell me there's a chance for my tablet.
I don't really think so , if it doesn't show anything i think it's dead, have you tried to acces the bootloader?
(i am not an expert in these things i also didn't brick my tab yet)
Sent from my ASUS Transformer Pad TF300T
I have tried. It did not work.
Are there any tools at all for me to combat this?
Sent from my SAMSUNG-SGH-I317 using xda premium
i think you should send it to asus and see what happens!
Sent from my ASUS Transformer Pad TF300T
I have a warranty from Sams. I am going to attempt a return with them.
What does anyone think my chances of them not figuring out its unlocked if it's hard bricked?
Sent from my SAMSUNG-SGH-I317 using xda premium
sometimes they ask you to pay for a new motherboard (because of unlock) sometimes they just fix it (with an unlocked bootloader) sometimes they fix it and make the bootloader UNunlockable
Sent from my ASUS Transformer Pad TF300T
Thanks for the words. I appreciate it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Liquidmetal6 said:
I tried to use fastboot to install a blob..
It must have frozen or something. It got through sending the blob, then it try to write the system file but it hung overnight and did not finish. I had to try reboot the tablet.
It now does not turn on, go into APX, recovery, or even light up that its charging. The only indication that I get that it has any life left is that when I try turn it on when it is plugged via USB to my PC, my computer makes the noise it does to recognize devices.
Please tell me there's a chance for my tablet.
Click to expand...
Click to collapse
To be honest, it doesn't actually sound like it's off. You shouldn't be getting any response whatsoever if the device is off and dead (on and dead will sometimes net you a malfunctioning device error). If it's still doing that, you can try doing what you would normally do to put the device into fastboot (power + vol. up) "blind." It's worked for me once or twice before, and it's possible it's just your screen that's messed up.
All things considered, given your screen won't come on (so there's no warning about the device being unlocked), so long as Sam's doesn't check with ASUS for your bootloader key status, they won't be able to tell (and likely won't have the know-how to either).
I have had the same thought about sams. However, apparently their warranty does not activate until a year after you purchqse the device, because they pawn if off to Asus. Of course, Asus received the email that I unlocked it and wont do anything about it .
I tried to get it into fast boot and failed but I will mess around with it more since it's not completely dead.
If I flashed a 4.1 blob file and it hung up on writing the system, would the bootloader be 4.2 or 4.1?
It is 4.2 fastboot should have started normally, if it is 4.1 I need to go and do something in the bootloadrr to activate fastboot, correct?
Sent from my GT-N8013 using xda premium
Related
Hey,
Yesterday I rebooted my i9023 and it won't start anymore. I pulled the battery because I forgot to start in bootloader mode, and I think I might've done that while the bootloader was starting up. I assume the bootloader is corrupted, or something. Buttons don't react anymore, nothing is displayed on-screen when charging, can't get into bootloader or download mode. I've tried all the things I could find, including this, but no dice.
I'm gonna make myself a USB JIG tomorrow and try to get it into download mode, but before that,is there something else I could try?
You can't even boot into fastboot mode? Even if its a black screen did you check if the computer detected it?
You can try the typical method of getting into download mode: hold vol+ and - and plug in the usb, not sure if it works that way with the Nexus. I see i9023 odin images available at sammobile.
Sent from my SGH-T959
eksasol said:
You can't even boot into fastboot mode? Even if its a black screen did you check if the computer detected it?
You can try the typical method of getting into download mode: hold vol+ and - and plug in the usb, not sure if it works that way with the Nexus. I see i9023 odin images available at sammobile.
Sent from my SGH-T959
Click to expand...
Click to collapse
Nope, can't boot it into anything and the pc doesn't detect it.
Sadly another confirmation that pulling battery to save seconds is a bad idea, happened some people before. Hope you can save your phone.
Well, I hope the JIT works. Otherwise, it's off to warranty, and hopefully they can fix it....It'd be sad to have to get a new phone...really really like this one.
Don't you worry. Just send it on warranty and they will replace your motherboard. I did exactly the same thing, pulled my battery to save some seconds. I sent my phone to repair, they took care of it in 10 days
Sent from my Nexus S using xda premium
nexususer1 said:
Don't you worry. Just send it on warranty and they will replace your motherboard. I did exactly the same thing, pulled my battery to save some seconds. I sent my phone to repair, they took care of it in 10 days
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Is there a chance to recover the data? I don't have much on it, but I have photos I haven't pulled.
That was my biggest concern. I'm afraid you'll loose all data, just as I have lost mine. Some (or all) of your photos might have been autosent to your gmail account. I managed to restore only some of those photos. Not all of them have been sent to my google account.
Sent from my Nexus S using xda premium
this happened to me twice before ,i fix it by ,using adb cmd and rebuilding recovery image ,it works
james300 said:
this happened to me twice before ,i fix it by ,using adb cmd and rebuilding recovery image ,it works
Click to expand...
Click to collapse
Yes, but your computer was able to detect it, if you could do that. Mine is literally a brick right now. Computer doesn't see it and it doesn't start at all. I'll try the JIG later, and if not, I'll send it to warranty and hope for the best
JIG didn't work. Didn't react at all....I'm sending it to warranty...
Hi guys, I really hope someone can help me.
I accidentally deleted the boot partition on my vodafone smart 2.
I was trying to install the original recovery that came with the phone before the OTA update2 using a tool from roeddie BUT, I forgot to put all the images in the same folder as the tool and the tool ended up deleting the boot partition without having a boot image to flash, and now I have a phone that is stuck in the white screen with the green android in the middle =(
btw, if I "reboot" if and quickly plug the usb cable in I get and unkown device in the device manager with this ID VID_0A5C&PID_2132&REV_0204
:crying::crying::crying:
With the program that you flashed it with can't you just download all the required sectors (boot, recovery, Rom) and just reflash?
Sent from my SGH-T999
No, the computer does not recognize the phone anymore =(
To my knowledge every Android phone has like a "apx or apb mode" or something of that nature(don't quote me on that lol) didn't you have to go on some sort of mode to use the application?
Sent from my SGH-T999
Yes, I had to power the phone holding volume down + power, but that won't work anymore =/
Ok now i had this happen to me with the Asus transformer tf 101 i flashed only the Rom and the tablet wouldn't even return on but it did go to apx mode, where the screen would show nothing, basically off, but with the right drivers my computer was able to recognize it and I flashed the boot.img, recovery.img, and Rom hopefully you should be able to do the same thing.
Sent from my SGH-T999
But the computer does not recognize the phone when I plug it, usually it shows something in the device manager, but now it shows nothing at all, except for when I quickly plug the usb cable right after it powers up, but apparently that hardware id is from some broadcom wireless something.
I don't know i never has experience with that phone , did you try to boot into recovery?
Sent from my SGH-T999
It was the first thing I tried, but I guess before it goes into recovery it needs the boot partition, which is gone.
I found this thread
http://forum.xda-developers.com/showthread.php?t=1144773
ALCATEL OT-980 /OT-981 recovery
On how to recover a bricked phone with "fast boot" hope that helps you good luck mate
Sent from my SGH-T999
Already tried this, does not work with this phone =(
But thanks for the effort.
I guess I'll have to go to the vodafone store in which I bought the phone and try to send it to repair.
Sorry man good luck
Sent from my SGH-T999
Just got home with my phone =)
Took the phone to a vodafone store at lunch, around 4pm got a text saying I could go and get my phone, I guess they have some mojo, voodoo or black magic to bring the dead back to life.
I think you probably messed up a step with the tutorial but at least you got the phone fixed how much did it cost you?
Sent from my SGH-T999
Nothing, it's still under warranty
Nice man congrats and if you try again make sure you have a recovery img available lol
Sent from my SGH-T999
having The same problem!
i'm also having the same problem with my xperia c3
it is bricked due to custom recoery and my boot partition has somehow deleted now i'm unable to boot up my phone any possible waysssssssss?:good:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Not that its much help but if you are bricked like I was, it was quite easy to replace the main board with a used one from Ebay.
No chance you had NV Flash snapshots?
Good luck with it,
Feend
In all honesty it simply sounded at first to be a permissions issue for SystemUI.apk.
But if you can get to fastboot I would try Reformatting your system partition and flashing another ROM. Then factory reset your data partition.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
sbdags said:
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Click to expand...
Click to collapse
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow. Thanks a lot for posting this information. I had no idea. Would using the factory reset within CWM or in the settings be dangerous?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
So doing this completely hard bricks the device? meaning NO bootloader? It almost seems like the bootloader factory reset is touching the block that holds the recovery. Isnt there source code for this bootloader? Couldnt this be solved?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow i am very glad i stumbled across this.. there should be a sticky about this or something!! Thanks for the very helpful post
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have to agree, I'm REALLY glad I came across this. I'd noted that in a few of the "My tablet is bricked" threads that people had bricked after accidentally clicking something in the bootloader screen and had vowed not to touch anything in the original bootloader.
Thanks for the heads up on this.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Game over
sbdags said:
Game over
Click to expand...
Click to collapse
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
sbdags said:
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
Click to expand...
Click to collapse
That's a bummer for them but good to know nvflash can fix it. and f*** Asus for locking the jb boot loader to prevent nvflash... Maybe this is a stupid comment but I think they would sell more devices if they didn't do stuff like this... I know when I look into purchasing a device I come here first to make sure there is android development and unbricking procedures. ( I saw nvflash for tf300t and that's pretty much the reason I picked that tablet). Its a bummer that companies like Asus are much more concerned with making money by repairing bricked devices. (Although I do love Asus hardware. I own a tf300t and a nexus 7...its a love hate thing... Damn you Asus)
Sent from my Nexus 7 using xda app-developers app
D.MADROX said:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
Click to expand...
Click to collapse
I have worked with six or seven who used the wipe data on the bootloader; two recovered.
If you have any chance to recover you have to work at it. First apx mode is useless unless you previously flashed Nvflash.
We need adb, fastboot, or recovery working. Here is a thread for your use to get control of your tablet.
You mention rebooting into recovery. Stock, cwm, or twrp?
As you progress through this list the tablets have a way of evolving. This can happen even if you haven't gotten anything to function as you wish. That means you have to do them again; three times may be the charm.
I would like very much to know about your mention of recovery. Can you still get into recovery and which?
How about a current update before you begin using that link.
my Asus TF300T is blocked on the asus logo, I can't enter into recovery mode but I can enter into apx, mode there is any chance of saving
P.S. sorry for english
IlHawk said:
my Asus TF300T is blocked on the asus logo, I can't enter into recovery mode but I can enter into apx, mode there is any chance of saving
P.S. sorry for english
Click to expand...
Click to collapse
Are you able to boot to the bootloader screen?
If so do you have access to fastboot?
I can't do anything
The only thing I can do is enter to apx mode ,
The computer recognizes it bit if i do "abd devices " The PC don't find it
Sent from my Nexus 4 using xda app-developers app
Can you give me some info on how the devices got to this state?
Did you flash or update anything before this happened?
I was doing a wipe data and ThE tablet closed . when I turn it on it was bricked
Some time ago I user ThE Asus tool forma unlocked ThE device
Sent from my Nexus 4 using xda app-developers app
Was this the wipe data icon in the bootloader screen/menu?
If so this is a know way to cause a bricked device and sorry but I have not seen any solution to this.
Yew is ThE data wipe on bootloader menu....
Sent from my Nexus 4 using xda app-developers app
Sorry I am not able to help you more here and am not familiar with apx commands but think this is only for use with NVFlash files, I could be wrong here.
If you did the NVlash backup on an ICS bootloader prior to the brick then you should be able to recover this way, but if not then with out being able to get to the bootloader screen and fastboot or adb then I'm not sure apart from sending to asus for repair sorry.
So if you hold vol- & power you don't get anything? no bootloader screen?
pjc21 said:
Sorry I am not able to help you more here and am not familiar with apx commands but think this is only for use with NVFlash files, I could be wrong here.
If you did the NVlash backup on an ICS bootloader prior to the brick then you should be able to recover this way, but if not then with out being able to get to the bootloader screen and fastboot or adb then I'm not sure apart from sending to asus for repair sorry.
So if you hold vol- & power you don't get anything? no bootloader screen?
Click to expand...
Click to collapse
$230 to replace motherboard! Buy a new non asus tablet,I did.
ThE facto that i bought ThE docking and i paied the Asus tablet much
Sent from my Nexus 4 using xda app-developers app
I fixed mine this way
Link to my thread! --- > http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to write me if you have doubts.
Hello
As soon as the warranty period expired I tried flashing the CyanogenMod firmware onto my TF300, so I unlocked my device and tried to follow the guide on the CM website,
(wiki[dot]cyanogenmod[dot]org/w/Install_CM_for_tf300t). I've got to point 5 of the "Installing CyanogenMod from recovery" section of the guide. but then when I selected the "wipe" option things screwed up. Now when turned on my TF300 only displays the "The device is unlocked" message in the top right corner and the ASUS and nVidia logo and does nothing else. No response to power + vol up/down. It won't even turn off, I have to wait for the battery to go flat...
Anyone wishing to reply, please do not waste our time by voicing your opinion (e.g. calling me this or that). All I am asking for is SUGGESTIONS and HELP.
Thank you!!!
On a side note: The only "solution" Asus offered was a motherboard replacement for $300. The service centre guy said this is the only way and that I have to "get back" in their system (database), which means that my device has to be locked for them to consider offering any help. Hence their offer to force me back into their flock, by forcing the motherboard replacement onto me. Something to keep in mind...
solvent said:
Hello
As soon as the warranty period expired I tried flashing the CyanogenMod firmware onto my TF300, so I unlocked my device and tried to follow the guide on the CM website,
(wiki[dot]cyanogenmod[dot]org/w/Install_CM_for_tf300t). I've got to point 5 of the "Installing CyanogenMod from recovery" section of the guide. but then when I selected the "wipe" option things screwed up. Now when turned on my TF300 only displays the "The device is unlocked" message in the top right corner and the ASUS and nVidia logo and does nothing else. No response to power + vol up/down. It won't even turn off, I have to wait for the battery to go flat...
Anyone wishing to reply, please do not waste our time by voicing your opinion (e.g. calling me this or that). All I am asking for is SUGGESTIONS and HELP.
Thank you!!!
On a side note: The only "solution" Asus offered was a motherboard replacement for $300. The service centre guy said this is the only way and that I have to "get back" in their system (database), which means that my device has to be locked for them to consider offering any help. Hence their offer to force me back into their flock, by forcing the motherboard replacement onto me. Something to keep in mind...
Click to expand...
Click to collapse
Did you do some reading before posting about all of the other bricks? Also, more information please. You can't get into fast boot or recovery? Have you tried using terminal to enter recovery? What boot loader or firmware were you on? Which recovery did you install?
Sent from my Transformer Pad TF300T using xda app-developers app
andrewnelson23 said:
Did you do some reading before posting about all of the other bricks? Also, more information please. You can't get into fast boot or recovery? Have you tried using terminal to enter recovery? What boot loader or firmware were you on? Which recovery did you install?
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
1. recovery: koush's ClockworkMod Recovery
2. Cannot get into recovery/fast boot
3. firmware: latest Asus firmware (as of 2 weeks ago)
4. when I connect the tablet to my PC nothing happens, I guess this kind of stops me from using the terminal to enter recovery...
5. I have read a few other frustrated post, but found no solutions so far
*** I can get into the APX mode by pressing the Volume Up and the reset with a paper clip and I managed to install the Asus Transformer Prime APX Interface Driver!!!
Where to from here???
Thx!
This has happened before, unfortunately.
http://forum.xda-developers.com/showthread.php?t=2347159
This one might be helpful, too. Someone got it to boot a while back. Not sure if it's the exact same issue, but it's there, just in case.
http://forum.xda-developers.com/showthread.php?t=2323886
I hope you can get it to boot!
Sent from my Transformer Pad using xda app-developers app