on an advent vega running honeycomb 3.2 v7 (viewcomb based on vega) on reboot crashes to starting fastboot USB download protocol and freezes every time requiring a reinstall.
any suggestions ?
exact thing happened to me. powered on the tablet one day and it has self bricked itself. iv gona back to stock 2.2 firmware since honeycomb is just problems and self bricking is just pointless, it takes too long to install apps again and its just adding to the nand wear.
Related
Hello everyone,
I have an opportunity to get a transformer for pretty cheap. Issue is seller says that often the tablet freezes or reboots while in sleep mode. He is running stock ics, no root. You think it is just software and rooting it and loading a custom rom would fix the issue or is it hardware related?
Thanks for your help.
Mike
Both these problems are known to be present in the asus rom. If its really cheap go for it root and flash [ROM][ICS] Codename Android v1.5.0 it stopped my tablet freezing and boot looping at night.
Snatch it up. Some users fixed it with a factory data reset. If not, ASUS should have a new firmware to help with most reboots within a week or two (according to their UK facebook page)
My A500 hasn't been acting quite right. Since I upgraded a while back to a FLEXREAPER rom from Taboonay (HC) I've had numerous SOD issues, but even more so worse and worse crashing and hanging.
Things I've done:
Full wipe/install of latest FLEXREAPER, Lightspeed, Taboonay (3.1). My A500 would hang even during initial setup (google account, etc). Eventually I'd get through the setup and it would still crash (screen freezes) or SOD. Oddly enough, I can't seem to format my internal sdcard .. but I have wiped everything else several times, and absolutely before installing any of the ROMs.
It would also, many times, not even boot. The white power light would come on, the vibrator would spin, but nothing would happen on the screen. It would boot about one in five times.
I then tried going back to a reinstall of old HC Taboonay 2.2 .. it worked for quite some time before, but now it's hanging and crashing just as it did with the ICS ROMs.
Up to this point I didn't touch the bootloader, which meant I was on the old HC bootloader. But in doing a lot of reading it seemed that many SOD issues were fixed with the new ICS bootloader (unlocked and patched).. so I used nvflash to flash a the ICS bootloader.
Well, this solved my only-would-boot-one-in-five problem and it boots everytime. But it still crashes. I even had it crash in CWM 1.7 just like everywhere else ... frozen screen. I've never seen that before in any of my Android devices.
I really don't know what's happened at this point. I'd be happy just to go back to a version of HC that works. I'm downloading timmyDean's V4 3.2 package (the depositfiles link is the only one that works .. and it'll be done in ELEVEN hours.) to attempt a shot at going back to full stock. But considering that's 11 hours or more away, without knowing it'll work .. I thought I'd ask.
Is there any way to downgrade from the ICS unlocked/patched bootloader?
Is there another bare-metal restore for HC out there besides the hellishly slow timmyDean V4 on depositfiles? Another location to download it from?
Is there anything else I can do?
Thanks ...
Found EUUs_SBK_Acer_A501_0.017.01_PA_ATT on some russian site.
I was able to reinstall everything back to 3.01 from the EUU loader. However my A500 still has serious problems.
- During loading the EUU, getting it in AXP mode worked every time, but bouncing it to Download mode worked rarely.
- Most of the time when attempting to power on it will turn on the power light and vibrate, but nothing shows on the screen.
- Sometimes if it makes it past the above, it will display "ACER" but go no further.
- Once actually loaded into an OS (doesn't seem to matter which one) it will lock up after a short while with the screen frozen. Only a hard power off (hold power for 5 sec) will shut it off.
- It will simply die if soft powered off .. not right away, but after some time.
So, is my A500's hardware broken? I can't seem to get any part of it stable.
Many reinstalls later, all options expired. Returned to Acer for warranty repair.
Hi guys
Im having a nightmare with my vega, I have been running vegacomb for a while without issue and decided I fancied upgrading to an ICS ROM instead, but have hit major problems. I went into rom manager to do a nandroid before I flashed anything, when I opened the app it told me to confirm the device type. it came up saying viewsonic 10 so I confirmed it. Then it decided to re-flash the recovery from within the app, I let it do that too. Then I told it to do a backup of the current ROM, so it reboots and then I get nothing. It does the same thing that normally happens when you go into NVflash (screen backlight comes on, nothing else). I have plugged it into the PC and its not in this mode, its also not letting me get into nvflash using the 2 second hold method. Im really stummped now, I have been messing round with android for a while so im pretty familiar with flashing etc, but without being able to get into recovery im lost. Do you have any suggestions?
Hi All,
I hope I'm posting in the right place, apologies if not.
I have been running Cyanogenmod on my S4 i9505 since Christmas. A couple of weeks ago, for no apparent reason, the phone started switching itself off so I decided to try and flash back to a stock ROM using Odin and the most recent firmware (5.0.1) from sammobile.com. I'm pretty new to this and don't have much in depth knowledge at all - hence opting for the apparently easy Cyanogenmod rooting option in the first place. The Odin flash 'passed' yet on reboot I got stuck at the Samsung logo and the phone then gets stuck in a boot loop if I switch it off using the power button. I then tried to flash an older firmware (4.2.2) but it has failed twice, leaving me with a 'brick'.
As I said, my technicial knowledge here is very limited but any step by step help to trying to get the phone back up and running would be greatly appreciated. Have I completely ruined the phone past repair, or is there a way round this?
Many thanks in advance
Whenever you upgrade to Android 5.0.1 from an earlier version it takes up to twenty minutes before it fully boots. This is because of the internal change from the Dalvik app compiler to the new ART compiler Android now uses. Android apps come in multiple parts, and on old versions of Android these parts were assembled into a single running image every time you ran the app. This is called "Just In Time" (JIT) compiling. The new ART compiler uses "Ahead Of Time" (AOT) compiling. It assembles all the apps once, rather than repeatedly assembling an app when you run it.
When you upgrade to Android 5.x and future versions of Android, Android will need to spend time compiling every single app on the device before it fully boots. This can take quite a while if you have a lot of apps, and an unfortunate side effect of this is that the device looks like it's stuck in a bootloop.
If you're able to get into Download Mode, your S4 isn't bricked. Install 5.0.1 again, but this time don't touch the device for a while.
Many thanks, a little patience was all that was needed. Re-flashed 5.0.1 and waited for first boot - all sorted!
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).