Hi all,
before starting to read my thread you can directly start by watching a video of how the device is acting.
Link to the video: Video
++++++++++++++++++++++
I own a Eonon GA6150 device with Android 5.1.1, RK3188, MTCD.
On the stock ROM the device randomly rebooted so I decided to install a custom rom made by Malaysk (Malaysk Custom ROM).
I followed the installation guide and everything worked fine. After booting up and landing on home screen, the device ‚crashed‘ and tried to reboot. Sadly only the car logo appeared and it couldn’t boot up properly (boot loop).
After that I booted into recovery mode and tried every step again. Since then the device is bricked(?). After starting the machine, all of the LEDs are working but the screen remains black. I also can‘t enter recovery mode, at least it doesn’t show up on screen.
Things I‘ve tried until now:
-Creating a bootable SD Card
-Open the case and check all wire connections
Is the device bricked or what exactly is the issue? And how can I fix this issue?
Look at the attachments for additional head unit information! Thank you in advance.
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.
help needed !!
I have a KFHD7(tate) and had been running CM12.1 for a while with only an occasional update using the nightly builds, I only updated occasionally as the unit would not always turn on at the first attempt and would stick at the CM boot logo, after switching it off and back on the unit would run quite smoothly, however none of the updates seemed to cure the problem.
I noticed that there was a new release 'cm-13.0-20160218-UNOFFICIAL-tate' which I flashed via TWRP along with 'open_gapps-arm-6.0-stock-20160301', these were flashed at the same time.
after a reboot the KFHD7 worked fine with no apparent problems, I then downloaded one of the dark themes,(not sure exact one) and this seemed ok at first, I entered the settings screen and only a few words and graphics were visible!
I rebooted back into TWRP recovery and performed a factory reset from within TWRP ... big mistake, now the unit only boots to the blue TWRP boot screen and blinks off after a few seconds it is stuck in a loop and I dont know how to recover it, I have tried the usual combinations of holding the power and vol buttons but still comes on the same .. any suggestions would be appreciated (dumbed down solutions please as not that techy, but can muddle through if step by step instructions)
Hello,
Welcome to XDA.
Try posting your issue in the thread linked below that you got your ROM from.
http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-marshmallow-t3315075
The experts there may be able to help. Good luck.
Hello!
Around a month ago I installed a custom rom on my Samsung Galaxy Note Pro 12.2 (SM-P905), which ran smoothly until a week ago, when my tablet suddenly wouldn't leave the Samsung Galaxy Logo screen when booting. I was also unable to access recovery (I had TWRP installed), however I was able to access download mode. Then I decided to try to install the stock firmware using Odin. It seemed fine until it was about halfway through the installation, when it seemed to disconnect and the installation failed. After several attempts this still happened. I also tried installing both TWRP and CWM, both of which passed in Odin, however I am still unable to access recovery mode. I also tried installing the custom rom, with the same results as I mentioned earlier. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
I also have to mention that this is my first post here and my first attempt at installing a custom rom or doing anything of this nature to my devices. Any help would really be appreciated!
mbrau said:
. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
Click to expand...
Click to collapse
Your battery connector needs to be re soldered first before trying to flash firmware.
Read the threat " Flickering Screen " for more information. Cracked battery connector will cause flickering screen, reboot, hang on samsung logo at boot..etc...
Hi - my Nvidia shield K1 was suffering from battery drain issues after the latest updates to the point where it only showed as having an hour or so of run time from 100%. I followed a video guide and managed to successfully unlock the boot loader and downloaded earlier official recovery images from the nvidia site. I used various programs and successfully flashed the image over to the tablet. However, when the tablet reboots and goes to initialize and run for the first time after flashing i encounter the following problem; the screen turns on and a grey box appears with 'Android is starting' in and proceeds to 'optimising apps (number) of 114' (or whatever the number of apps is). This completes then the tablet goes to the android, Nvidia logo screen and stays on it for a few minutes before returning to the 'Android is starting' box again and re-optimising all the apps again before going again onto the logo screen. I tried with the 1.5.0 and 1.4.0 images but had the same result from both.
Can anyone help me with any suggestions of how to stop this boot loop and which recovery image to use that will take my tablet back to a time when the battery life was high again. Thanks in advance
Hello,
I'm a long time browser of this forum and have had a lot of luck with ROMs in the past, however, in the spring I bricked my N8013 like something horrible. Long story short, I zeroed the internal SD card and had to rebuild the partition table from scratch as I couldn't find a working PIT at the time. FUN!
Anyway, once it was fixed I was able to get Lineage 14.1-20170305-unofficial-n8013 installed and working....mostly What a relief! MTP didn't work, but WiFi did. One thing I noticed right away was that the Boot Logo, when you first turned the tablet on seems to be referencing some trash space on the internal SD card as there is no logo, only noise or maybe a previous screen (i.e. if I go into download mode and reboot, then the download mode screen is now my boot logo). After the initial POST, the lineage boot screen shows fine, but that's some 10s later.
Regardless, the N8013 hardware does not run lineage very smoothly and Lineage is not optimized for the N8013 - aka **** battery life.
So, I decided to give Android HD Revolution 21 a shot. I used Odin and flashed "High On Android" recovery and installed Android HD Revolution 21 from my external SD card. Easy! Still doesn't resolve the boot image issue, but whatever.
Boot up and I discover that not only does MTP still not work, but neither does WiFi! Bluetooth works for some reason though. So, I took to the forums and tried to resolve the issue.
I tried flashing both sets of stock kernels from here and repeating the install process. Nothing. Additionally, I noticed in the Android Settings inside Android HD Rev. that it shows N8000, however, my tablet is the WiFi only model (N8013EA as stated on the back of the device).
So, TL;DR
-Welcome suggestions on how to resolve MTP and WiFi issues. Currently working in Android HD Revolution but I don't think it's limited to that ROM
-Welcome thoughts on how to fix the Boot Logo issue. I feel like this should be a simple fix, I just don't know where files like this would/should be stored since it exists somewhere in the partition table and now in the ROM.
Well, was able to resolve the WiFi issue by install the Boeffla Kernal from: https://www.boeffla.de/index.php/downloads/eol-kernel-versions
Still looking for help with MTP and the boot logo if anyone has ideas!