Hey all,
So I bought a cheap 9" tablet off eBay for use as an electronic billboard outside my dorm room door (cool, huh?)
I've been trying to root it for a long time so I could disable the touch screen/buttons on the device. I don't want people powering it off or something weird. I tried a bunch of different rooting methods to no prevail and eventually decided to try installing a custom recovery image using fast boot. Well, I definitely screwed something up as now the tablet just keeps rebooting as shown in the gif below.
[Gif video] i.imgur.com/ZtU4RtG.gifv
The screen will turn on and off and it seems to do it too quickly to be recognized by fast boot.
Should I paint a target on the back and practice my aim or is there any hope here?
Thank you for reading.
I figured it out! For anyone who has a problem in the future, I'll tell you how I did it.
Get PhoenixCard, it allows you to reinstall firmware through a micro sd card.
blogtechtips.com/2015/11/24/phoenixcard/
Then, get the iRulu firmware from the iRulu website. I checked the sticker on the back of my tablet and my model is like an x1924 (first part of whatever that code is.) I downloaded the "X1921 X1922 X1931 X1932 Firmware_YHK" firmware as it was the closest one. There should be instructions on how to use the PhoenixCard software to reinstall your firmware, but I found that I had to remove the card and try burning again if it failed to burn. It'll say "error" at the end if it failed.
Then I tried plugging in the card and booting the tablet a couple of times until a loading bar appeared on the screen. Wait patiently, and eventually it will turn off again. Remove the card and boot up and you're good!
my tablet
hey my model number says x9 and i am kinda confused because i cant find the firmware for it. itsvthe same 9" 4.4 will that firmware work on mine
Jason1077 said:
hey my model number says x9 and i am kinda confused because i cant find the firmware for it. itsvthe same 9" 4.4 will that firmware work on mine
Click to expand...
Click to collapse
I also have an IRULU x9 (boot screen says expro x1) I have a serial # jx944wf1507061e. I found the firmware on the Irulu site as firmware for JX944 & JX945 HERE
xx.irulu.com/download/lists.html
replace xx with www
I rooted my tablet but it is stuck in factory reset boot loop. If there is a power cycle i lose all programs installed and the tablet goes back to factory settings out of the box state. However, I still have root and superuser (Kingoroot) installed.
I will try flashing it with phoenixcard and with the factory firmware and post if it fixed it.
***update** Flashed the firmware with Phoenixcard, used JX944 firmware and it is back to factory specs working as it did when it was stock.
Thanks to you both. I'm going to try this over New Year's. Wish me luck!
Sent from my Nexus 5 using Tapatalk
Related
Basically I ran Livesuit to flash my Chinese Tab, its called a desiretab has an a10 processor. Anyways the first flash was successful, besides the fact that it didn't pick up touch calibration correctly. So, I decided to flash it again with a different firmware image, low and behold it gets about 50% in and just freezes up. Now the Tablet shows no form of screen output, I attempt to flash it repeatedly, nothing works. Help Please.
*Just noting that when I say I attempt to re flash it and nothing works, I'm saying that it just sticks at zero and the flash command does nothing.
Strange, I used to own some of these tabs but its been a while since I used livesuit, if I remember correctly there is an option to reformat as well? Maybe best to try this and then attempt to flash factory firmware to it.
If you've tried all this and still nothing, I used to be active on a different forum that had a large selection of threads on allwinner tabs called flashmyandroid.com , hopefully someone there could be of more assistance, otherwise this may help
http://forum.xda-developers.com/showthread.php?p=23451308
Its an old thread on these allwiners I started back when, probably not a lot of info here and it was for the a7 but best of luck!
Sent from my Nexus 4 using xda premium
Hello everybody,
I would kindly ask someone for assistance how to repair the Amlogic 8726-MX based TV box which is stuck on the boot.
Origin of the problem starts when I rushed to change DPI settings with one application from Play Store and failed to boot after restart. Boot was stuck at endless loop of Android logo with vertical yellow bars due to wrong DPI/ resolution settings. After I tried to make the reset of the system (Safe mode through button reset) and which failed, I tried to prepare and boot from SD Card with some ROMs I found online for very similar model with same chipset, and I am stuck at brand (Corto) logo after the Amlogic logo is displayed. I can not enter recovery mode when following instructions. This model has dedicated reset button, so the "toothpick" method is not needed here. However holding it 5-10 seconds during the boot, does not start the recovery in my case, so I am not sure if:
a) Recovery is damaged?
b) I didn't prepare the SD card in correct way? (I used DD + u_boot.bin)
c) My SD card does not contain correct version of files so it does not start recovery?
I assume I would need to identify the exact model of the board, quite similar to generic 8726-MX player, but board layout is little bit different. Product is sold under brand Corto, model AMPC-200, and it seems to be the same as model CM-Q7 by Coltech Cynmate. Production date is September of 2013. On board there is sign B6_V1.1. Images attached.
I am even considering to buy second unit, if it would be possible to extract recovery from new unit and fix the old one.
I would be thankful if anyone could suggest some solution.
Thanks!
do you resolved the situation
Pleas help
Hello everyone,
I bought Smart TV Stick http://goo.gl/b9ivdd
And i have problems with WiFi.
Device see a lot of AP, but can't connect with my router at all. I'll tryed to changed encryption (WEP/ WPA/ WPA2) and nothing changes. My router is wrt54gh. Maybe devices can't connect cos this router have only G standart?
Any ideas?
Thank you, best regards
Bump. I am also interested. I have the same device, but mine works properly. However I would like to know how to access basic recovery, and install TWRP or CWM recoveries.
mitramix said:
Hello everybody,
I would kindly ask someone for assistance how to repair the Amlogic 8726-MX based TV box which is stuck on the boot.
Origin of the problem starts when I rushed to change DPI settings with one application from Play Store and failed to boot after restart. Boot was stuck at endless loop of Android logo with vertical yellow bars due to wrong DPI/ resolution settings. After I tried to make the reset of the system (Safe mode through button reset) and which failed, I tried to prepare and boot from SD Card with some ROMs I found online for very similar model with same chipset, and I am stuck at brand (Corto) logo after the Amlogic logo is displayed. I can not enter recovery mode when following instructions. This model has dedicated reset button, so the "toothpick" method is not needed here. However holding it 5-10 seconds during the boot, does not start the recovery in my case, so I am not sure if:
a) Recovery is damaged?
b) I didn't prepare the SD card in correct way? (I used DD + u_boot.bin)
c) My SD card does not contain correct version of files so it does not start recovery?
I assume I would need to identify the exact model of the board, quite similar to generic 8726-MX player, but board layout is little bit different. Product is sold under brand Corto, model AMPC-200, and it seems to be the same as model CM-Q7 by Coltech Cynmate. Production date is September of 2013. On board there is sign B6_V1.1. Images attached.
I am even considering to buy second unit, if it would be possible to extract recovery from new unit and fix the old one.
I would be thankful if anyone could suggest some solution.
Thanks!
Click to expand...
Click to collapse
You need to go to the freaktab site, find the device, download the gbox midnight rom, sd flash tool. Use the tool on pc to flash the sd, put the sd in the box, keep the reset button pressed, its accessed via the rear of the device with maybe a cocktail stick if you dont know, then connect power keeping the reset pressed till recovery appears. Apply update on sd card, reboot. Everything you need for this box, roms, how to s etc, even cwm are on freaktab. The gbox rom, flashed correctly fixes bricked devices. Mine included. Hope this helps, it should do.
Sent from my LG-P875 using XDA Forums Pro.
Anlogic 8726 mx v1.1 image
t, I have Amlogic 8726 mx v1.1 tv box that has become stuck on the android logo after I attempted to install an update for the MX2 thinking it was the same thing, how wrong I was. Does anyone still have the V1.1 image available, every link to the V1.1 image have all been taken down.
Thanks in advance
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk
While trying to flash on atvXperience (following the instructions blindly,stupid of me), I have bricked the box. When I was in TWRP, the install part only gave LOGO, RECOVERY and BOOT as the install locations. Should have installed TWRP first before fully wiping the device. The M16 does come rooted. HDMI doesn't output anything and a faint green LED is lit when powered on, originally it was a blue LED on normal operation.
USB Burning Tool comes back with "[0x10303004]Romcode/Switch status/Identify/Error result" basically everytime. Tried different ROMs, I have asked to get the original firmware from the eBay seller (have to wait for them to ask the manufacturer, I guess)
Looking for some ideas. Thanks for help in advance!
Link to the box: https://androidtvbox.eu/the-new-firmware-for-m16-tv-box-with-amlogic-s905x-20171030-release/
Board Images (on Google Drive): Images
So an update to the situation: The first box seems completely bricked. So, I acquired a new box and booted TWRP and took a full backup, then killed the recovery mode while trying to flash TWRP over stock recovery. Rebooting and holding down the AV reset button would normally just factory reset but now just shows the non-animated boot logo and sits there (Since flashing TWRP).
I want to replace the firmware because I have detected the default firmware on the box is talking back to China (at least on the 8GB/1GB RAM version because I ordered it in a hurry). You can thank Watchguard for that info.
I'm also not really up to buying another (or 3rd) box because it takes 3-4 weeks delivery and the amount of money already spent. I might try and use a hot air rework station to remove the eMMC from the bricked unit and directly flash it; also to work out where the ball grid maps out too. God help me on this effort.
Is there a way to convert the TWRP backup in to a flash-able IMG file? This could restore the bricked box, which i like cause it's the 2GB RAM version.