Good day, guys!
I've got a problem with my Iconia tab a700. I'm using CyanogenMod 11.0, latest Nightly. Today, suddenly my device just switched off and stuck on the boot screen. Then, I tried to boot to recovery, but failed - device just rebooted. then, using adb (fastboot boot recovery.img) I finally booted to recovery. I tried to restore from my backup, but failed with the "can't mount" problem. afterwards I did "mount/system" and reboot. Device rebooted, started to load cyan, then stuck. so, I tried to boot to cwm again, but had "FAILED (data transfer failure (Too many links))". So, now device can't turn on at all. The strange thing is, when device is plugged in, my computer makes that "found new device" sound, but nothing happens.
don't know what to do... Any help will be greatly appreciated!
in the settings on my PC I see that iconia's been identified as APX
In a service center they told me, that the motherboard is probably dead. So the topic may be closed.
Related
Ok, so I gave my wife my old TF101 when I got the 701. I reflashed it with a fresh install of timduru's KatKiss ROM. It's been running reasonably well aside from random reboots. all of a sudden, yesterday it stopped booting up at all. It shows the normal Asus flash screen, but then when it shows the OS specific one (in this case, the weird little picture of timduru's meerkat thing...) it's just flashing random little bits of tha tpitcure all over different parts of the screen an some sort of random flickering and never going past it. I can still boot to the recovery normally, so I wiped it and tried reflashing the same ROM and ended up with the same thing. Tonight I plan to try to download the newer version of the ROM and try, but I fear I may be SOL. Any other suggestions?
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
*Detection* said:
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
Click to expand...
Click to collapse
Yes, I did that. Still no good. I'm pretty much screwed, aren't I?
If your TF serial number starts B6O or lower, some B7Os too, then it is SBK1, which means you can use NVFLASHable ROMs - they delete and remake every partition on the TF and reinstall stock ROM - you could try that in case the sdcard is corrupt
stuck at TWRP screen, failed to flash bootloader
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of yesterday, it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TWRP logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle. I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a day now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.
Dear guys and girls,
I have a problem. Since 2 days my tf300t is for some reason not starting up anymore. The start screen does not go away. Before it worked like a charm. I have tried almost everything, I can think of. As far as I know the latest firmware is installed. The problem is also that the tablet isn't in developer mode. So my options are limited afaik to fastboot. I have installed the naked drivers version 0.73. But windows is saying that the device is not started. Only fastboot is started as device. I have tried to reinstall the firmware by usb, but to no avail. It sends but doesn't write... I have drained the battery to zero level. Can anyone help me with this? What am I missing?
<>< A Dieu
Jaco Oversluizen
I'm also having this same issue. Tablet was working fine and then froze up. After rebooting we are now stuck on the Asus screen with the circular logo going. Waited over an hour with no change. Tried to boot into recovery and recovery crashes and gives me Error! This is a stock tablet that hasn't been unlocked or anything.
Update: Did a Data Wipe and the device rebooted and came up. Doing all the updates again. Hopefully it wont mess up again.
So you have an unlocked bootloader ?
Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.
Hi so I have a Moto G 4G (XT1039) and I recently tried flashing an Android Lollipop rom onto the phone. The process in TWRP went fine but afterwards my phone started turning on and it showed the boot up screen for a quarter of a second and after I was redirected to the fastboot menu with the error message 'Fastboot Reason: Fall-through from normal boot mode' I tried going on 'Normal Powerup' after that but that resulted in 'Boot up failed' and it does this for every option except 'Recovery' this took me to the stock recovery screen. (not TWRP because when I tried flashing TWRP recovery earlier this came up with 'Boot up failed' for when I went on Recovery so instead I put TWRP in the normal boot mode). Anyway, after this I went to wipe all the data from Recovery and it did this process just fine however when I rebooted the device it still came up with 'Fastboot Reason: Fall-through from normal boot mode' and 'Boot up failed' when I went on 'Normal powerup'. My computer does not let me access the phone either. (it is detected because it made a noise when I plugged it in but its not accessible and doesn't appear in my drivers screen). I think the phone still may be trying to boot from the corrupted/faulty boot image as I put it in the phones internal memory but I cannot delete it from there because as I said I can't access the phones internal memory. If there is a fix for this (I assume there isn't as I am so limited to doing anything on the phone or on the computer now) I would appreciate it a lot. I would also like to ask: when the phone boots does it boot up from the internal memory and files from the hard-drive in the phone or from somewhere else? If so I will probably just take it to a shop and pay for the hard-drive to be replaced. Thanks. And also if there are any developers that skim this post and a similar one that sounds the same don't as there is no one else with this problem and I have a different problem thane the others. And yes I have posted two other posts one is similar but still different and the other has been closed by mistake because of somebody skimming that one and my other one thinking they were the same
Your thread will be moved to the appropriate forum.
So I flashed CM12 on my Galaxy Tab 2 10.1 and then tried to encrypt it. I had full battery and everything but I saw them message that it failed. It asked me to reset the device so I clicked it. It was the only option. When it rebooted, it went straight to TWRP but instead of loading TWRP, it just kept showing the splash/loading screen. Then it would flash black quickly and then show the splash screen again. I left it plugged in over night to see if it would load. It did not. So I let the battery completely die. Once I charged it, it still does the same thing. I've tried using ODIN to flash TWRP again. It says it successful but the same thing happens. I also successfully flashed CWM with ODIN but the screen flashing thing still happens. (I can put the tablet in Download Mode with no problem).
Does this mean I've fried my SD card or is there some other fix I'm not aware of?
I'm not sure why this worked but I was able to boot into CM by leaving the device in the boot loop and running the command `adb reboot bootloader`. After that CM12 loaded up. I decided to try restarting and it restarted just fine too. Everything seems to be back to normal.