So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?
To reflash with fastboot, you'd need an unlocked bootloader. I wouldn't risk that if I were you.
It looks likes a hardware issue. A ROM contains drivers. Drivers control the hardware. When going into airplane mode, the drivers shut down some of the hardware components, like WIFI and Bluetooth. If you'd have a modded ROM, I'd say there's some driver issue which causes the tablet to crash (weird that it's stuck on bootloop, though). Since that's not the case, I'd say there's something wrong with your hardware.
To apply factory settings, did you do the right moves?:
http://forum.xda-developers.com/showthread.php?t=1861092
How did you enter fastboot mode?
Note that there's only a slight difference in going into fastboot or the factory reset mode. It's only a Vol + and -.
I was asking because I already flashed (in November) my 'previous' A700 with a stock ROM (because JB OTA update failed) without unlocking anything (but using Recovery).
You are probably right, it may be an hardware fault as it does exactly the same as first time and that Acer Support replaced complete motherboard. However it was looking at me very strange that I could get two hardware fault in the row.
I will give a try to the factory reset (I did not knew the move), thanks for the tips.
As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here
troun2000 said:
So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?
Click to expand...
Click to collapse
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure. (they claim to have changed the mainboard.
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD
So I tried the following (yes, it is inverted relative to theory);
- Press [vol +] + [power]
- As soon as the tablet vibrates, let go of power and play several times [lock]
=> Fastboot mod, displaying "Bootloader vJB-653b3d3: Starting Fasboot USB download protocol"
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] and play [lock]
=> no effect
And as reminder, Recovery is not reachable.
TomONeill said:
As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
(...)
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here
Click to expand...
Click to collapse
So I guess I can not flash, because I do not have access to recovery, only to fastboot.
TomONeill said:
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Click to expand...
Click to collapse
Yes they re-install OS as the A700 came back with a German Rom where I sent it with a French Rom.
Thanks a lot for your help :good:
Moscow Desire said:
Also, would help to know which OS you were on. ICS or JB?
[...]
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
Click to expand...
Click to collapse
Can you answer both questions MD asked you?
If you're running Jelly Bean, the bootloader has changed. This requires a different way of going in the recovery mode:
DЯΦ[email protected]П said:
With JB there is a change on the A700 (can't test on A701):
Boot into recovery:
- Press [vol-] + [power]
- Once the tablet vibrated, let go [power] and keep [vol-].
- Now the tablet vibrates a second time, let go [vol-] and press [vol+] quick
- Once the text that appears on the screen ("loading recovery kernel image"), let go [vol+].
Click to expand...
Click to collapse
Moscow Desire said:
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure.
Click to expand...
Click to collapse
Not really, first time it happened while playing music with google music player (reboot then loop).
Second time it was after setting the Airplane mode for night (reboot then loop).
Moscow Desire said:
(they claim to have changed the mainboard).
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
Click to expand...
Click to collapse
I though the same but I found a 'technical paper' saying that board and microphone were changed, and both Wifi and Bluetooth Mac adresses have changed. So it seems they really changed motherboard.
Moscow Desire said:
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
Click to expand...
Click to collapse
Rom were 'different' when it happened; first was an FR and second was a DE. It was google stock player (only first time).
JB both times.
Moscow Desire said:
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
Click to expand...
Click to collapse
I do not have access to stock recovery, only fastboot mode
Moscow Desire said:
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
Click to expand...
Click to collapse
I have;
Acer Logo/animation -> Inconia Tab Logo/animation -> reboot -> Acer Logo/animation -> and so on...
Moscow Desire said:
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD
Click to expand...
Click to collapse
OK, that helps a lot, thanks. I guess what I would like to do is to flash a system Image. Where can I get one?
So far, I have Android SDK installed and Acer drivers installed (which bring me a "ADB interface"-"Acer fastboot interface" device in Windows Device manager)
Related
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
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.
First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.
When you install a stock rom, doesnt it install back the stock recovery? I would try reflashing twrp and installing cleanrom, keep it as stock as possible and see if it boots.
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.
missiveusa said:
First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.
Click to expand...
Click to collapse
1. What bootloader are you on currently? (See 4)
2. By flashing the ".30 kernel" I assume you mean flashing the .30 stock ROM, am I right?
Your device went into a hung boot after making the backup, so I'm not really surprised it does exactly the same when you restore that backup. Have you tried flashing .30 stock ROM again?
3. Which recovery do you currently have? As Tylorw1 said, if you flash a full stock ROM, you'll reflash everything, up to and including the bootloader and recovery.
4. If you still have fastboot available (pick the USB symbol instead of RCK after POWER+VOL_DOWNing), you might want to try to reflash either TWRP or CWM (http://forum.xda-developers.com/showthread.php?t=1926286 for the latter; I have VERY limited experience with the former and you may well have more than me ).
Updating your bootloader just to be sure is recommended, as most current ROMs will not boot properly without it.
Has the fiddling brought any new points of view, or new discoveries?
Update
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup? Flash? Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already . Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!! No big deal really: I'm back to STOCK .26, virgin device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!
missiveusa said:
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Click to expand...
Click to collapse
Agreed.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup?
Click to expand...
Click to collapse
No use -- it won't boot.
Flash?
Click to expand...
Click to collapse
CROMI, redownload, hash check.
Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already .
Click to expand...
Click to collapse
I know exactly what you're talking about. Was there once as well, and still it is changing so fast it's hard to keep up.
Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!!
Click to expand...
Click to collapse
I would not take the chance, and just leave it as it is.
No big deal really: I'm back to STOCK .26, virgin
Click to expand...
Click to collapse
<< and still complaining?
device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!
Click to expand...
Click to collapse
Maybe...
J/K!
You've done great, and I am happy to hear you got it up and running. I started out answering before reading your post in full, assuming it wasn;t fixed yet. Left the comments for reference (and fun, or mockery... -- good job, see you around!
same issue
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.
TeTTiweTTi said:
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.
Click to expand...
Click to collapse
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.
buhohitr said:
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.
Click to expand...
Click to collapse
Thanks for your help. I can boot into stock recovery. But I could move to the USB icon or the the Wipe Icon previously. Now I was able to select the Wipe Data Icon and currently I'm at the virgin "Welcome" screen again.
I don't understand why now it's working and previously not. Did I switch the v- and v+ button? If that's the case, I'm even a bigger idiot then I thought :silly:
Anyhow, All well that ends well.
Stuck on spinning wheel as well
sbdags said:
A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.
Click to expand...
Click to collapse
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!
TransformingPad said:
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!
Click to expand...
Click to collapse
Lagfix takes a good 20 mins to complete, even though it says it has finished after 5. I wonder if you rebooted too early. If you have sync off it can cause corruption on the data partition which might be your issue.
The fix is to format data from the twrp wipe menu and reflash. You will lose Everything on internal so back up in twrp first please.
Sigh - all for naught
stuck on spinning cyan screen
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?
tcemle said:
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?
Click to expand...
Click to collapse
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.
sbdags said:
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.
Click to expand...
Click to collapse
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.
tcemle said:
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.
Click to expand...
Click to collapse
Hmm that sounds like apx mode to me. If you didn't save nvflash backups I suspect it has bricked
I just updated to KitKat via this threat: http://forum.xda-developers.com/showthread.php?p=52214068
I noticed that the tablet was running excessively slow and so I decided to do a Factory Reset from within the tablets Setting. Now it's rebooted and it's sitting at the Android and the spinning thing in it's chest for more than 5 mins. Does it normally take this long?
stuck itwrp 2.7.0.0
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me
gothamhill said:
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me
Click to expand...
Click to collapse
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.
stolen
berndblb said:
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.
Click to expand...
Click to collapse
1st of all thank you, unfortunately the nandroid bu was on a laptop that was stolen. Anything else I can do?
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.