I have a MXIII 4k 2g android tv box running 5.1.1, which all of a sudden boots to the launcher, then shows android logo, then launcher and so on, i've done a hard reset (pin in av) and factory reset but still does it, any help appreciated. Thanks
well, my first box was a MXIII-G 4k, and this is what is left from that "chinese" box , i haved the same problem, reboot loop, until android logo, stuck or reboot, first i thought it's from the power supply, i changed it, still this problem, then i found out that memory chip is damaged and i can't do nothing about it so, i throw him from a wall
try to flash the firmware again, if the problem persists, try to change the power supply, if problem persists well you can't do nothing , don't buy cheap boxes
I've managed to fix it, i used twrp on an sdcard on another box to make a backup, then restored from twrp on faulty box, shame you broke yours
Related
My Rooted Nexus 7 was working perfectly. Now I am not sure If it is Soft Bricked or something else is wrong with it, It was charging one day and I took it off one micro usb charger and put it on another Nexus 7 charger. I went back and turned it on, Now it was stuck in bootloop, I have seen bootloops before, but not like this. It turns on and goes to the lock screen, then after a few second it freezes then restarts. I have been able to quickly log in boot into safe mode but it still freezes and restarts, I made it to the app menu once and then it sad , Unfortunately Launcher has stopped, I have cleared the cache and dalvik cache and nothing works, I have bootloader version 4.1.3 and CWM version 6.0.1.9, I have tried to format tablet and factory reset with cwm recovery but when I turn it back on I still see my stuff and I still reboots, I have tried to restore from a backup from a while ago with cwm but it fails. I tried to use nexus toolkit but I dont remember my version and I cant check, I gave it a guess but It can not find my device when plugged in, even in recovery mode, It said something about fastboot but i think i did that but I am not 100% sure what it is, I need to get this workig again fast.
Hi, first of, this is my first post on this forum, so sorry if this is by chance in the wrong place...
Right, now the issue;
I got a Lenovo Tab A10 (model: Lenovo A7600-F. There is another set of code that goes like Lenovo A7600-F TAB A16GBE-DE)
and I have a serious feeling its bricked.
I turned it on today (at time of writing) and it gave the "Lenovo FOR THOSE WHO DO" logo like normal, and stayed like that...
forever...
So after I pushed the little white reset button besides the micro-sim slot I boot up in recovery mode by holding the volume up and power button till the black screen with the white letters pop up, and I select [Recovery Mode].
Then the Lenovo logo pops up again, and after a second or two an Android looking like he's playing very dead comes on screen with a "!" exclamation mark
above and the text "No command" under it.
I tried a reboot with the same splash screen hangning as before.
I looked up on the internet and found that clearing the cache helped a person, so I did that by pushing the power button with the dead Android and scrolled to "clear chache" with the volume buttons.
I did that, tried a reboot, but nothing happened, same result as the previous reboot.
I went as far as restoring the factory settings and rebooting but to no avail.
I go digging.
I found it could b the rom, the os or both that is totally f%#@ed up somehow and that it is in fact repairable.
Some more digging about and I find this: forum.frandroid.com/topic/203630-clockworkmod-recoveryroot-pour-lenovo-a10-70-a7600f/
Those links are very useful, because they bring me to a bunch of downloads that contain the flashing tool I need and recovery images along with a link to
Lenovo Smart Assistant. Also I can read French, so following the instructions wouldn't be a problem.
The first thing I do is connect the tab and start up Lenovo Smart Assistant (with the tab off). The computer (win8.1 Packard Bell Easynote LE) makes the chime of something
being connected, but I cannot see the device between My Computer like I normally do.
Neither does the Lenovo Smart Assistant recognise anything plugged in after a scan.
Following the instructions on how to recover with the Flash Tool also is fruitless because the Flash Tool doesn't recognise anything plugged in either.
I've now completely run out of options and don't know what to do.
Is there any way at all to save the tab and get it back up and running?
I have a Himedia Q10Pro Android box that has been bricked by a firmware update. I followed the instructions (FAT32 drive, only update on root of drive) I was performing the firmware upgrade from 1.0.8 (Android 5.1) to 2.0.1 (Android 7) very carefully as instructed by the post in the forum, box is in a cool equipment area, fed from a clean UPS for power. Got the Android upgrade screen, progress bar was moving. Stepped away to help my daughter, and when I came back I was at the HIMEDIA boot screen. Left it to boot.. and waited.. and waited. Wouldn't go past that boot screen, left it a couple of hours. Then powered off and then back on, still stuck on the boot screen (says boot on the LCD display too).. left it an hour again, no go. Tried leaving it unplugged overnight (clutching at straws!).. no change.
I've tried the upgrade again, when pressing the upgrade button, the LCD changes to 0000, but still displays the HIMEDIA logo and no activity light on my USB thumb drive. Tried several thumb drives, all 3 USB ports, several firmware versions (including the 1.0.7 as suggested), and every combination.. no dice. Stuck on 0000 on the LCD and Himedia logo on TV if I've used the upgrade button.. stuck on boot on the LCD screen and Himedia logo on the TV if I haven't. There is a guy in youtube (can't post links yet, search 'Himedia Q10 pro bricked after upgrade to hmd2.0.1') who seems to have the exact same problem.
Any suggestions gratefully received.
Thanks
Does the power button blink red and white?
The same problem
The USB does not respond to a any USB flash disk
The same problems.. Guess it is bricked.
Bleh_KR said:
The same problems.. Guess it is bricked.
Click to expand...
Click to collapse
Solution..Open box -contact with rs232 an try with puty...Are work - stop elec. when open driver usb..
So mom dropped off her old Xperia Tablet Z SGP311 as a "gift". It did not work for her anymore, so if I wanted it and could fix it then I would have another tablet in the pile.
Her description of what did not work was what you would expect from a non-techie aka "some error turned up but I cannot remember what the screen said, so can you fix it?".
In the beginning I thought the problem was the common USB/charging problem, however I feel anything about this tablet seems different than other Android tablets, so after finally managing how volume buttons along with power buttons work, I could rule out it was a charging issue.
Getting the Tablet to boot it seemed that it had been updated and was booting into OS doing the "optimising applications 1 out of 258". However going to the step "starting applications", then tablet would just reboot a few times and then start over with optimising applications, starting applications, reboot and repeat all over. So some sort of bootloop.
I then used Sony's Xperia Companion to repair the tablet from fastboot (volume up + power) which succeded until it should reboot the tablet, then I was stuck in the same loop as above.
After a few tries I then managed to unlock bootloader and get TWRP 3.2.2 booted onto the tablet (booted NOT installed since I have no root).
With TWRP I tried deleting Dalvik cache etc., which did not help the situation, same bootloop.
With TWRP I then gave LineageOS a shot, but LineageOS experience kinda the same bootloop (both LineageOS 14.1 and 15.1).
LineageOS boots fine and proceeds with the fresh install questions (region, timezone, Internet access) but as soon as I hit next on the "Location Services" page the tablet will reboot.
Since this tablet has no value to me, I have tried deleting all data on all partitions from TWRP, I have checked the filesystem with e2fsck on the tablet which shows no errors, but in any attempts it simply reboots at the same stage every time.
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
bjoeg said:
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
Click to expand...
Click to collapse
probably memory problem either RAM or ROM.
Hello guys,
I really need your help on how to restore Samsung Galaxy Tab S6 Lite (SM-P615), to factory reset after Odin flash failure.
The Odin flashing started, but accidentally my PC ran into blue screen error and restarted. I lunched Odin again and
connected the tablet to the PC again and on the tablet's says; "An error occurred while updating device software". It further
recommended Samsung Smart Switch, which I tried yet it can't even detect the tablet. Odin too can't detect the device,
since the tablet is not able to enter "Download Mode"
Moreover, when I disconnect the tablet USB cable from the PC, the screen goes dark and nothing shows. As soon as I connect
back the USB cable the "An error occurred while updating device software comes on the screen. I used Power button+Volume-
buttons to restart and try Volume+ and Volume- buttons to enter recovery mode but still nothing changes on the screen.
Again on the tablet's screen, there this red writing at upper left corner saying "Voltage Level [2526]. I changed the USB cable
hoping it could have done something but it is still the same issue and same error message on the screen of the tablet.
Please any advice is welcomed, and thank you all.
I would say maybe try to hard reset the motherboard. You can do that by unplugging the battery then plugging it back in internally, but don't take my advice for granted because this worked for me in the past but I am not a tablet or phone guru so I don't know much.
keep in mind I'm very adventurous and that's why I tried the battery thing in the first place.
DefinitelyNotAngel said:
I would say maybe try to hard reset the motherboard. You can do that by unplugging the battery then plugging it back in internally, but don't take my advice for granted because this worked for me in the past but I am not a tablet or phone guru so I don't know much.
keep in mind I'm very adventurous and that's why I tried the battery thing in the first place.
Click to expand...
Click to collapse
Okay, I'll try that. However, for mean time before I heed to any hardware possible solution, I want to try with the software base first.
Very much appreciated.