Related
powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hello guys,before with the rom hidro ponic 4.4 all was well.After i want change my rom and i've brick my asus after flash rom unofficial cm10..because the camera apk not found, and dispay is total green..I suppose the problem is the rom but after another flash rom the problem is same.On again the display is lock on the logo Asus and upstar on the little: the device unlock..stop.My asus there's no way to get it to recognize at pc and the driver installed not found..are't fastboot logo in Controll Pannel.I've not possilìbility to choce android--usb--wipe data.Help me please thank you sorry for my English
What about booting into recovery? Or fastboot?
As far as I understand your post Android isn't booting, but what if you hold volume-down when you turn on the tab?
I have almost the same problem. I flashed a bad boot blob (vanilla linux, not android) and now I'm stuck at the first Asus logo if I boot normally. But I still have fastboot and CWM recovery so I'm confident I can get it back into shape (even though a restore in CWM didn't help)
I think there's no way to unbrick the device,because I have the same problem.
I flash my device to official 4.1 and I found I lost root of my device
So I try to downgrade my device,but I failed...
Then I try to enter recovery and I failed again...
At last I try to wipe data of my device but it had no respond...
Of course,I had to reboot my device...
The result is:It bricked...
The symptom is just like the thread starter
What should I do???
I tried to contact the customer service of ASUS,but they said the device which unlocked by yourself couldn't get any warranty,even I willing to pay for it
(I think the customer service of ASUS is too bad,especially their attitude)
(I'm also sorry for my poor English...)
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
e...Thanks anyway
But my problem(the same as the thread starter) is:I couldn't enter either fastboot nor recovery
If I could enter one of it,I think I can fix it...
(Maybe I misunderstand what you mean?)
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
Thanks guys Today i can try the guide..we ope in God:angel:
I try twrp jb recovery but not function because the teerminal it's impossible go in download mode (down+power)....The Jig Usb forf Asus exist?
Hello guys, but for this type of brick no one has an answer? Method with nvflash can 'operate according to you ..? But I'm trying to appear APX and install the drivers as a guide is a company because it makes them install it
As far as I can see nvflash is coming to TF300T, it has been developed for T201 (http://androidroot.mobi/t3_nvflash/). But at least for TF201 they have to have fastboot first, so that may not help you.
If I understand you correctly nothing is booting and you have neither ADB nor fastboot access. In that case I don't think there's anything to do except wait and hope for a working nvflash or to try to have Asus fix it, but since the tab is unlocked they probably won't do so for free.
It seems this tab bricks easily.
I have the same problem, and I hope nvflash too. But I don't know nvflash in dev or no. This my best device which die first. Cry
Having the same problem here also. Only had the tf300t for less than a week.
Here is a sticky to a thread I made. I'm just waiting for people to put in a bunch of ideas. Hopefully NVFLASH doesn't need fastboot.
http://forum.xda-developers.com/showthread.php?p=31465583#post31465583
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
surdu_petru said:
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
Click to expand...
Click to collapse
...Tried it about 1000 times, not possible, but thanks anyway. No fastboot possible, NVFLASH won't be working either...
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck!
Same problem. Stucked at Asus Logo but i can go into recovery. What can I do? Help me please
My PC finds it as Fastboot.
Seem I'm no alone...
Seem I'm not the only one.
This morning I bricked my tablet, 5 minutes after I bought a wall charger on EBay... :crying:
As for now the only answers seem to be from people that don't read post good.
We can't get to use the recovery...
Again, if someone knows how reset the tablet prior booting...
I beleive that its the only other way.
The last possibility, buy a new one...
I believe the problem started before.
- I unlocked my tablet more that a month ago, at the Jelly Bean release.
- Rooted
- Installed the official release
- Everything went well, up to this morning
- I noticed that my Rom Manager Premium start to show adds
- Goo manager refused to install recovery script
- Then I tried to go in recovery, it fails.
- I said to myself that it was better to start from scratch
- I tried a Factory reset using setting menu.
- After this step the tablet started to show This device is unlocked
-After the last step the device wouldn't boot no other way...
I don't know what happened but it seem a bit strange that everything worked fine before this morning.
For sure I'll keep exploring ways to get out of this mess.
But if I have to buy another tablet, there's a chance that I'll go to a Nexus 7...
Good luck to all the other unfortunate that that are in the same boat.
Alain
Hi back,
After I bricked my device i sended back my tablet to canadian customer service.
At first the didn't wanna fix the proble and the service told me that he needed to change the motherboard.
I argue a while and after an email discussion whit the customer service agent, they told me that they would fix the problem for me THIS TIME.
This morning I received my tablet and everything seem to work fine, as it was reset to factory.
BUT, after I started to investigate, seem that in no time the cover removed.
And maybe the motherboard change is a trick to suck more money from the users.
In fact I can't understand why you'de have to change the motherboard after the tablet is bricked.
Maybe I'm wrong, but I find this way of doing thing awefull, and I consider lucker that I got outa this mess...
Good luck to the others unfortunates
Alain
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Bricked TF300GT (please help)
Hello developers,
I have a bricked Transformer the goes in a loop flashing ASUS every 5 seconds or so. That was after having unlocked and then reset to factory default.
I have been reading a lot of articles at various forum for a solution. I have never seen something so confusing. Please is someone can point to me a page where the un-bricking is described step by step for that aparticular model?
Many thanks in advance
Yves
NB: I have tried the -volume and power button trick or the +volume power button that just make a USB connection on my PC
---------- Post added at 11:01 AM ---------- Previous post was at 10:53 AM ----------
tobdaryl said:
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Click to expand...
Click to collapse
I have the same problem and done what you described without success. What must I flash with fastboot and where will I get fastboot. I believe my machine is in JB 4.0.. Many thanks,
Yves
i got my tf300t bricked to.
got my tablet this weekend wanted to install cyanogenmod.
just did a week early'er a other one (the one for my mother)
that went well
my tablet installed de orginal 4.2.1 from asus.
Today wanted to install cyanogenmod.
run first de unlocker v8
the installed fastboot twrp421.blob
when i went to the twrp menu the cyanogenmod wont install, but the orginal wont start also not, it want nothing to start.
tryed with external sd.
ok i thought i want cmw so i run the recovery-clockwork-5.5.0.4-tf300t.img
went wel also.
i can only go to cwm but they are no file rights and still can install a zip or mount a sd internal or external.
now fastboot is not working
when i turn the tablet on it is going to cwm
wat i can do?
edit:
cmw version = v6.0.2.3
Me too! asus ask 230$ for replace new mainboard. I think they want eat money, because they already have nvfash to fix. 230$ can buy new item from amazon. I hate asus and never buy any thing of asus. Very bad support.
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.