yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] rome3ro:
Problem booting up

Hello guys!

Thanks for the post it would be very useful to everybody that own an amlogic box, my problem is that I just updated with a firmware (5.1.1) with the thootpick method, the firmware has installed just fine but after that just shows a black screen and doesn't boot!, after that I have inserted an sd card that contains a firmware with the original firmware (I make this sd card with the burning tool) and the box starts booting fine!! with new firmware!!, so my question is what can I do to fix the boot without have the sd card inserted all the time!
[Android Stick & Console AMLogic based Computers] muncheno:
Looking for help / advises

Many great thanks to Team DevDigitel.

Long story in short, finally I m able to unbrick my m8s (I believe is n200) but now it is K200 for build.prop.

I still left some problem here, hoping expert here could advise on this:-

I check my PCB here is with ap6330 and I know my is S812.

1st problem I found is 5.8ghz wi-fi actually run at linking speed of 65mbps(it should be 433mbps before brick). Current with

Team DevDigitel ROM, the file transfer speed from nas 2.4ghz wi-fi (~1.3MB/S) actually faster than 5.8ghz (~300kb/S).

2nd issue, I can't get LAN working even I have key in all the static IP details. It shown internet connected but internet still not working.

3rd, the Kodi can't browser the smb or NFS from network. With solidexplorer I can transfer files from the NAS, but with firmware still an issue.
[Android Stick & Console AMLogic based Computers] graphdarnell:
I remember from a thread on Freaktab.com, someone mentioned all roms for S812 should work on S802 (which I have). I also remember you mentioning people can try the Universal rom. Well, I tried 5.1. in hope of going to 5.1.1 Universal with TWRP. No luck. Is there a specific procedure to follow when doing this, or is it already known that this can't be done? The box works fine as it is now, but I'd like to know the possibility of going LP on it. Thanx in advance for any response.
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
I think that your chances of success should be fairly high by just following the guide I posted earlier. I did indeed use the Universal S8xx ROM for that repackaging.
[Android Stick & Console AMLogic based Computers] graphdarnell:
No go. Tried to flash the first rom with both TWRP and stock recovery. Stopped half-way through and system aborted it. Needless to say, no next steps. Wonder if there's anything else I can try since new Kodi requires LP or higher. Oh, well...

Thanx for the tips anyway.
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
Right, and what happens if you really follow the guide and use the toothpick method instead? :p
[Android Stick & Console AMLogic based Computers] graphdarnell:
I didn't know one could get into stock recovery and get the rom to flash any other way. So I did that too, obviously with little luck. BTW, on my unit, which is an MXIII S802, pushing and holding the reset button while plugging the power jack does nothing. One has to hold down the power button while pushing the reset to get to the stock recovery mode. Am I missing anything?
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
The toothpick method involves pushing in something fairly long in the AV port until you hear a "click", holding it steady there, followed by plugging in the power and wait 10-15s until the recovery from the

SDCard

is booted. Did you or didn't you try this way? What brand is your box? How does it look on both the inside and outside? What firmware are you running now?

Extra info: The Acemax ROM will wipe your flash clean, and then re-write the bootloader if done correctly. See the file "aml_autoscript" for more information.
[Android Stick & Console AMLogic based Computers] pnin:
If anyone has tried this with a Beelink IOne s826 (AML 812) please post about results. Thanks.
[Android Stick & Console AMLogic based Computers] graphdarnell:
I've attached the thumb so you can see what went on. If I leave the aml_autoscript on, it gets to recovery only half of the time, whereas if it's out, it goes to recovery everytime. The n200 OTA file wouldn't flash. Thinking it might be corrupt, I tried to download it again from your link, and it wouldn't. You might want to check the file integrity again.
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
The file in the first step is just the official Acemax firmware, the link is taken from their official page. The file is fine, you can verify the zip integrity if in doubt.

Anything interesting if you go to "view recovery logs"?

I think that the only way forward here would be to modify the updater script (META-INF\com\google\android\updater-script) to give you more debug info on what step that actually fails, and then try flashing with TWRP. For example:
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
Here is an example for how you can modify the updater script:

ui_print("Debug output line 1");
(!less_than_int(1469088646, getprop("ro.build.date.utc"))) || abort("Can't install this package (Thu Jul 21 16:10:46 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
ui_print("Debug output line 2");
getprop("ro.product.device") == "n200C" || abort("This package is for \"n200C\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Debug output line 3");
set_bootloader_env("upgrade_step", "3");
ui_print("Debug output line 4");
show_progress(0.750000, 0);
ui_print("Debug output line 5");
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Debug output line 6");
write_raw_image(package_extract_file("logo.img"), "logo");
ui_print("Debug output line 7");
show_progress(0.050000, 5);
ui_print("Debug output line 8");
write_raw_image(package_extract_file("boot.img"), "boot");
ui_print("Debug output line 9");
show_progress(0.200000, 10);
ui_print("Debug output line 10");
write_raw_image(package_extract_file("bootloader.img"), "bootloader");
ui_print("Debug output line 11");
set_bootloader_env("upgrade_step", "1");
ui_print("Debug output line 12");
set_bootloader_env("force_auto_update", "false");
ui_print("Debug output line 13");
[Android Stick & Console AMLogic based Computers] graphdarnell:
I've tried different roms for different S812-based boxes. Some Kitkat roms do work on mine, but not one Lollipop would flash. This one here is an example. The one you referred to in your guide is for the N200C, and people mention the difference in roms for N200 and N200C.

I have to keep digging. This is just for fun, but if you happen across something of interest, please post it. Thank you.
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
The Acemax ROM is indeed for a N200C, but by repacking the Team DevDigitel Universal S8xx ROM I managed to get it running on my box that identifies itself as a N200 (S812 based).

After looking at the updater script, I think that the most likely culprit is the "getprop" checks. Therefore I have created a new updater script for you to try. Just replace existing file with this one. Be aware that the normal safety checks are removed, but I have also added debug information to facilitate further understanding.

You need to use TWRP, and you can try either the official Acemax firmware (new step 2) or the repackaged firmware (new step 4).

My overall feeling is that updating your box should be fully possible, lets crack this nut together! :)
[Android Stick & Console AMLogic based Computers] graphdarnell:
I apologize for the late response. Been tied up for the last few days. A bit confused though: official Acemax would flash with TWRP? Also, the guide states step 2 should precede step 4, and both are necessary. Acemax firmware is packed for stock recovery. Should I re-install stock before doing Acemax?
[Android Stick & Console AMLogic based Computers] graphdarnell:
I tried them all with your updater-script: Acemax, N200 folder inside, Universal rom. None would flash (see attached thumb).
[Android Stick & Console AMLogic based Computers] MyM8SFinallyWorks:
General answer to what should be flashed, and why: The official Acemax ROM should be flashed with the toothpick method, because that way the boot loader is also re-written. However if we modify the .zip file the checksum will not be correct, so in that case TWRP is needed instead of stock recovery. By firstly flashing the offical Acemax ROM, we setup the necessary structure. The second flash is just a matter of re-writing the /system partition.

-Flash attempt #1: This file can never ever be flashed. It in turn contains a flashable .zip file and some other necessary files for the toothpick method. I think that we are finally getting to the core of why you are not having any luck flashing.

-Flash attempt #2: An updater script is clearly executed, and your box identifies as a k200 instead of n200C. Fine, then we know what do modify in order to flash successfully.

-Flash attempt #3: Since the output is identical to attempt #1, I can only assume that there is something very fundamentally wrong. When you downloaded from Mega.nz, did you selected "Normal download" or "Download as zip"? I am going to assume that you selected "Download as zip", and therefore you once again end up in a situation where you have a file that cannot be flashed.

Recommendation on how to proceed:

-Unzip the files from attempt #1 to the root of your SDcard, and use the toothpick method.

-If that fails, make a copy of the file used in attempt #2, extract the updater-script, search&replace "n200C" with "k200", copy the modified updater-script back in to the .zip file, and finally use TWRP to flash.

-If that in turn fails, check that you don't have a "double zip" in attempt #3, just as in attempt #1.

Good luck! :)
[Android Stick & Console AMLogic based Computers] graphdarnell:
No go. I tried all possible combinations including the ones you suggested, each time it returned with flash....aborted. I guess it's more than just the updater script. It doesn't matter now, but I thought I should let you know. Thanks again for your response.
[Android Stick & Console AMLogic based Computers] AMGPowered:
Team DevDigitel I have the identical box you have in your pics. By any chance you have the remote.conf file for this remote? I tried several .zip on freaktab for the S812 however the volume controls don't function but everything else works.

Everything works as you said (LED light in reverse and all)

Help will be appreciated
[Android Stick & Console AMLogic based Computers] jritt:
Hi guys,

I have been going thru pretty much the same issues as you guys. I have a Matricom G-box Q2 (CPU: Amlogic S812: GPU: Mali 450 Octo core: Memory: 2GB RAM. The box came from the factory rooted running 5.1.1, it just didn't have a superuser app installed. I installed Supersu and flashed Abdul's TWRP from here: w w w.freak-tab.de/abdul_pt/aml/TWRP_2.8.7.0_T8Plus. Tbh, the box really isn't running too bad. It's running Kodi 17.1 with "Beast" build fairly well. The main issues I'm having now stem from the lack of RAM, and also very slow wifi and pretty bad file system performance. I actually have set it up to dual boot between the Android 5.1.1 and LibreElec. The LibreElec is honestly running much smoother than the Android, it's just missing a number of features. I know there's not really anything I can do regarding the lack of RAM, but I plan to try a wifi dongle to see if I can get better performance from it than the Broadcom chip inside the box has been giving me. I would love to experiment with custom ROMS although up till now I haven't been able to find any. But what I really have been trying to do lately is to change my file system from ext4 to f2fs. I have been led to believe the box will perform much better with f2fs. Unfortunately, my recovery only supports FAT, ext3 and ext4...and I have been unable to determine what the kernel supports. These Kodi boxes are new to me, but I certainly have my share of experience modding Android phones and tablets. I'm more than willing to pitch in and help anyway I can.

And if anyone has any thoughts on how I can switch my box over to f2fs you'd be my new hero. Anyways, that's where I'm currently at.
[Android Stick & Console AMLogic based Computers] w20grippy:
applied this rom from TWRP on Minix X8-H Plus and brought in to this error. I had the Lollipop installed on X8-H Plus before trying. Do I need to flash boot.img given above?

Screenshot Link: https://screenpresso.com/=ZVA8b

Screenshot:
[Android Stick & Console AMLogic based Computers] limesoft:
screen couldn't fit

same here, my tv can't view the rest of the contents, totally out of screen. anyway to adjust ?
[Android Stick & Console AMLogic based Computers] philliedbz:
I would just like a flashable zip for the nav bar and the working notification
[Android Stick & Console AMLogic based Computers] graphdarnell:
Been struggling to install 5.1 on an MXIII S802 box. Finally succeeded with Matricom M8 5.1 firmware, but it was too unstable and finally resulted in a bootloop. Then I dirty-flashed Universal rom without the boot.img. It went through but when rebooting, got stuck at "installing first APPS, do not power off please wait..." forever.

I know DevDigital mentioned using own working boot-img, but I thought the current Matricom firmware already had it on. Yet TWRP always erases "system" before flashing. Does that mean it also erases Matricom boot-img? I did flashed a second time, with boot-img extracted from Matricom 5.1, transferred to Universal Rom, and zipped with standard zip app for linux (I am using Ubuntu). It failed. Was I doing anything improper, or is it something else I'm not aware of?

Should I, as a preventative measure, always flash boot.img from Matricom 5.1 backup right after flashing Universal Rom? The problem is that once it gets stuck a the screen above-mentioned, it's too hard to get back to TWRP from sd card. For some reason the TWRP flashed after Universal Rom just doesn't show up anymore.

Team DevDigital, can you give an opinion about what I related above, PLZ.
[Android Stick & Console AMLogic based Computers] graphdarnell:
deleted
[Android Stick & Console AMLogic based Computers] Dynamic_d:
Hi,

Did you manage tro finally getting it to work?? Im dying to get this also working or abny other lillipo on my mx3.
[Android Stick & Console AMLogic based Computers] graphdarnell:
Sorry for the belated answer. Not sure why Team Digital did not respond at all to my question. But as I said, I was able to flash Matricom Lollipop on MXIII, but it was stock firmware, and consequently not rooted. The trouble begins with rooting with anything other than KingRoot. The reason I need to root it with SuperSu is that KingRoot would mine data and relay it to some server in China, I was told. I think I recounted the process somewhere.
[Android Stick & Console AMLogic based Computers] gorus1:
Hi guys,

I need help becouse my SD card slot is broken,

i need universal ROM Dev Digitel 5.1.1, but for USB Burning Tool method.

(for my M8S/+ box tv).
[Android Stick & Console AMLogic based Computers] smudge100:
Hi

Anyway to upgrade this M8S+ box to marshmallow or nougat ?

I am using this Rom at the moment....

TeamDevDigitel 5.1.1 -

https://www.androidfilehost.com/?fid=24588212152304711

regards James
[Android Stick & Console AMLogic based Computers] Jasono7419@gmail.com:
link

i am downloading gonna give it a try i have a m8s+ stuck on 16.1 firmware needs upgrade i hope this works!!!:)
[Android Stick & Console AMLogic based Computers] philliedbz:
Well extracted the systemui file and settings apk and they work flawless on my ATV rom just need to know how to make recent app switcher to work and im a happy man
[Android Stick & Console AMLogic based Computers] philliedbz:
Anybody know how we can get recent apps to work ??
[Android Stick & Console AMLogic based Computers] wajerle:
S812 M8S plus
[General Questions and Answers] IAmBashingMyHead:
first post here sorry if i am in the wrong section. Well i have a Samsung galaxy s7 edge (EXYNOS) and today it fall of my leg at speeds of mach 5 and hit a chair with the power button. Unfortunetly its broken and i must replace it. I had only rooted it before and because i was afraid that there may be problems with the warranty, i tried unroot it from the settings of supersuser. CONCLUSION: now its stuck in a boot loop and i cant do anything because i have a broken power button. Is there any way to format without pressing the volume up, home button,power up button ? I cant do it from adb because it cant find my device in this state. Oh yeah i forgot to mention that for some reason the download mode is stuck at the warning were i must press the volume buttons. PLEASE HELP I HAD MY FIRST S7 EDGE STOLEN LAST MONTH AND I CANT AFFORD A THIRD ONE (i live up in my name). sorry if i dont anwser fast because i am at my village were i dont have a wifi at my home and i must live with a shi* mini rooter with only 1 gb. ty
[Xperia Z5 Q&A, Help & Troubleshooting] x10Mark:
Hi all,

I've bought an used Xperia Z5 yesterday, but there is no option for fingerprint in security.

I've read that it might be the cause of having US firmware on it, but how can I check if I have US firmware or not? Or if it simply lacks the fingerprint scanner itself as hardware?

Also the guy said the vibration doesn't always work since he dropped it and he had it repaired but the problem remained. It's yet to work for the first time for me it doesn't work in the diagnostics test either, should I be getting it repaired again or just live without the vibration function since the previous repair didn't fix the issue. (haven't had my phones hardware repaired before, so idk if it is no cure no pay)

The phone has been factory reset 3 times and repaired once by the Xperia Companion pc software.

Any help would be appreciated, thanks in advance :good:
[Xperia Z5 Q&A, Help & Troubleshooting] zippy01:
If they can't fix on warranty they usually send you a quote when I refused a quote I had to pay postage and a small fee for looking at it. I'm in the UK mind so different countries may differ. About the US firmware what's the customization number?
[Xperia Z5 Q&A, Help & Troubleshooting] x10Mark:
Interesting, my customization version number is the following: "1298-7632-R3C"

1298-7632	Customized NL	32.2.A.0.224-R3C FTF

Some research on that got me this:

"E6653 Customized_NL 1298-7632" "E6653/Mobile Phone/MH410c/Customized NL (Netherlands)/Graphite Black"

I am from the Netherlands and so was the seller of the phone.
[Xperia Z5 Q&A, Help & Troubleshooting] zippy01:
You don't have US firmware it's probably hardware
[Xperia Z5 Q&A, Help & Troubleshooting] Momoessamoo:
I have the same problem there is no a fingerprint option on my phone and there is no fingerprint working
[Xperia Z5 Q&A, Help & Troubleshooting] CalamitySir:
I think the US variants or at least some carriers variant don't have finger print scanner on them. I remembered reading an article on it. Google it and you should find some info on it
[Xperia Z5 Q&A, Help & Troubleshooting] x10Mark:
That's the point, it appears I have an European phone.
[Xperia Z5 Q&A, Help & Troubleshooting] xasbo:
What makes you think that it's a euro phone? Because it has NL firmware? If so: I run SG firmware on my phone from HK, so firmware means nothing.

What does the service test for fingerprint say? (Phone > *#*#SERVICE#*#* > Service tests > Fingerprint Test)
[Xperia Z5 Q&A, Help & Troubleshooting] iHenryi:
I'm having problems with the scanner too, doesnt show up in security settings or the *# SERVICE thing either. Is completely missing, UK second hand z5.
[Xperia Z5 Q&A, Help & Troubleshooting] x10Mark:
Yeah nothing about finger print scanner shows up in the service test.
[Xperia Z5 Q&A, Help & Troubleshooting] zippy01:
Firmware means everything if the option is in the firmware lol. Obviously if the hardware is present but us firmware is on the phone the option won't be there. Since the option should be in the firmware mentioned then it is most probably hardware issue or not present
[Desire 820 Q&A, Help & Troubleshooting] yassintrancer:
those are my stats

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 01.01.010_U10305041_08.0

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT55EYC05935

(bootloader) imei: 355721061061844

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: a51_ul

(bootloader) platform: hTCBmsm8939

(bootloader) modelid: 0PFJ40000

(bootloader) cidnum: ORANG309

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: da038a09

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

(bootloader) mfg-name: 0001

all: Done!

finished. total time: 0.010s
[G3 Q&A, Help & Troubleshooting] nahsha:
Hi All,

LG G3 Vigor was the first phone that rogers released supporting VolTE, since rogers also owns fido I bought a used fido lg g3 vigor with hopes to use it with volte. However the moment I attempt to make a call I see that LTE is changing to 4g and I don't see an option to select VOLTE either..

Does anyone know how force/select Volte wit this phone?

Thanks
[G3 Q&A, Help & Troubleshooting] virusdunil:
if i can say...Vigor is a real P,O.S...period ! ;)
[Remix Mini General] haeffnkr:
Hello,

I just got my new Remix Mini.

I am starting to load apps on it and it wil not install/setup the FSGO application.

I says it needs "you must allow location services to use Foz Sports Go."

I have location on and other apps are using it.

I have no issues with this application on my Samsung S5 phone running 5.x

Please help

thanks in advance

haeffnkr
[Galaxy S II Q&A, Help & Troubleshooting] ergoschnuffel:
Hello all,

recently i got an i9100xxls8 handed down to me. (Was sold in Germany), no carrier as far as i know.

I tried to flash it with a twrp which seems not to work at all and cwm with which i was able to flash a custom rom.

But that failed miserably between looping of the cyanogenmod screen (12.1 and 13) with the pulsing circle and just being stuck at the SII boot screen.

Is there a way to get it working again with an original rom (cant find the proper version for it).

I am using heimdall on linux.
[Galaxy S II Q&A, Help & Troubleshooting] Droidriven:
There is a re-pit mod and iso-rec recovery that you need to use if you want CM12/CM13. There are threads here for them if you search.
[Honor 7 Q&A, Help & Troubleshooting] bishnu1992:
hi every one i am newbie. i have indian version honor 7 bought from flipkart.com.. i flashed uk firmware b100 and i got dual sim enable on my indian version honor 7 but when i forced update to MM 6.0 ( UK version MM 6.0 firmware B320) by pressing volume up+down+power it succesfully upgarded to marshmallow but i got only one sim enabled..can any one help me out to get again second sim working on android 6

Thank You.
[Honor 7 Q&A, Help & Troubleshooting] DigiGoon:
The UK version that is PLK-L01 is also having dual sim support, but you shouldn't have flashed UK version over Indian version without debranding it, as both will have different modem partition. :)

The solution is to have to go back to the PLK-UL00 builds. :D
[Honor 7 Q&A, Help & Troubleshooting] swapnil.1834:
Make sure u have purchased dual sim because indian version of honor 7 is single sim

Check does u have 2differnt imei no. Or one (*#06#)
[Honor 7 Q&A, Help & Troubleshooting] vsriram92:
Can you try correcting the patch in the below given thread ?

http://xdaforums.com/honor-7/genera...an-version-t3486133/post69268366#post69268366
[Honor 7 Q&A, Help & Troubleshooting] DigiGoon:
I don't own an Indian model. :)
[Honor 7 Q&A, Help & Troubleshooting] muradulislam:
When the second sim was enabled, were you using both sims at the same time?