Hey guys,
Recently I've tried to port CWM to my device following this tutorial and it bricked...
It did not boot in any mode (Recovery, Fastboot or Normal) after doing this (stuck on motorola logo/boot menu).
@diego-ch helped me and he managed to flash the XT920_2_290_2014 back on my device and unbrick it, but I want to install XT920_2_310_2014 back.
There are some Stock ROMs available on the internet, but these ROMs are outdated compared to my original ROM...
The ROMs available are: XT920_2_290_2014_A01_MP (Tim Brazil) and XT920_2_290_2009_A01_MP (Retail), and my original ROM was XT920_2_310_2014_A01_MP.
The backup script in this tutorial created a few files files: recovery.img, system.img, boot.img...
What I want to know is...
Is there any way to "reflash" these backups to my device?
Here is a printscreen from my original ROM:
https://dl.dropboxusercontent.com/u/82392755/OriginalROM.jpg
And a printscreen from the "new" ROM:
https://dl.dropboxusercontent.com/u/82392755/NewROM.png
Thank you!
In this link you can get the up-to-date firmware for the D3,
and for now you can't flash those img in the device.
Regardless it's a MTK6577 chipset (the same of some generic chinese devices), Motorola used some security measures that we couldn't avoid yet. In this thread you can follow the discussion about it.
My theory is that the ROM make some validation on each partition in every boot. If one doesn't pass, then the phone stuck in a bootloop, as happened to you. Also, we can't flash any partition as we do in similar devices because the phone requires an authorization file, a signature. The only way to generate it is with a private key, that we don't have.
Maybe you can recover some data from the data.img if you root your phone and use some specific software to extract the files and put it in the data partition, but you'll need to research about how to do it. Also... maybe there some apk in the Play Store that provides this options to you, idk... but I think the most important is to recover you system, the data you can just reinstall your apps.
About the root, you can find good tutorials researching in Google
@farenheith, thank you for your answer!
My device is already rooted, thanks for advice!
Can I help you with something right now?
I'm studying how Android works (ROMs, APPs, Drivers, etc), and I've downloaded the source code found on SourceForge (Razr D Files) and I'm studing it (applying to my Razr D3).
If I have something new, I'll post it here!
I have some driver conflict problem with the motorola drivers in my machine... I take hours to successfully flash the firmware again... it's very annoying...
And well, I want to do more tests right now, but I can't. If you want to help, you can do some tests too:
What I did:
* I got an image from the recovery and then I flashed it again without any changes. The phone boots successfully. This tests was to make sure that the writing operation was not screwing something
* I tried to edit myself the ramdisk of the image I got before and then I flashed it. I got a bootloop again...
What I need now:
FIRST TEST
* Get an Image from recovery with these adb commands
Code:
adb shell su -c "dd if=/dev/recovery of=/storage/sdcard1/recovery.img bs=6291456c count=1"
adb pull /storage/sdcard1/recovery.img
* Unpack and repack the image without any change and try to flash again (to do the repack you can use this app). Commands:
Code:
adb push new_image.img /storage/sdcard1/recovery2.img
adb shell su -c "dd if=/storage/sdcard1/recovery2.img of=/dev/recovery bs=6291456c count=1"
reboot
* Look if the phone will boot normally. If not, re install the firmware with RSD
The idea of this test is to check if the phone needs a padded recovery, ie, with exact 6291456 bytes, to boot properly.
SECOND TEST
Do exact as the test above, but, before repack the recovery, add the following parameters in the default.prop in the ramdisk:
Code:
ro.testtest=1
This test is to check if the phone will do a validation, like a checksum, in the partition to make sure it can boot. If the phone doesn't boot with this change, then we know that any recovery we put there will not work. If it boot, then the problem is something inside the recovery.
Update: I did the tests I talked about... I'm quite sure that we do have a checksum validation of some internal partitions (like bootimg and recovery) during the boot.
I'll start to analyse the source code to see if I find some clue. Maybe we can edit some partition manually or even recompile some and write it using adb, we just need to find where this supposed validation is happening and study the best workaround for it.
Can you help me with it? Do you have some programming knowledge?
farenheith said:
Update: I did the tests I talked about... I'm quite sure that we do have a checksum validation of some internal partitions (like bootimg and recovery) during the boot.
I'll start to analyse the source code to see if I find some clue. Maybe we can edit some partition manually or even recompile some and write it using adb, we just need to find where this supposed validation is happening and study the best workaround for it.
Can you help me with it? Do you have some programming knowledge?
Click to expand...
Click to collapse
I can help you @farenheith!
I know a bit of programming (I'm already conversant with some source codes)... I've downloaded the code and I'm studying it.
If I have some news, I'll post it here!
naroku said:
I can help you @farenheith!
I know a bit of programming (I'm already conversant with some source codes)... I've downloaded the code and I'm studying it.
If I have some news, I'll post it here!
Click to expand...
Click to collapse
Hello guys, I am from brazil also. Yesterday I was trying to convert my 32gb SD to exFat or NTFS and to do so I had to install Multi mount SD card and I believe it was this **** that brick it. One of the signal meters of the sim cards is gone, the other is normal, also I don't have the slide to disable one of the sims, they are gone... I've tested and both sims are still working, to make calls and receive. Also my Google Play Store is gone, every time I open it it forces closed with "unfortunately google play store has stopped". ja tentei de tudo, qnd faço clear dos dados do app ele ate abre, mas é so mandar iniciar o download de alguma coisa que ja ferra (I've tried everything including deleting app data, when I do that it does open, but after the first download start it forces closes with that error). And the worse of all is that i've been reading that if you hard reset or flash a rom you get the 2nd chip disabled forever. is that true?
one more info... my xt920 is being recognized as xt919! I believe this is what is causing all the problems... the strange thing is that there was no factory reset, hard reset, or firmware flash... just this **** app which might have caused this. How can an APP make your phone be recognized as another model? how could I fix it?
fscussel said:
Hello guys, I am from brazil also. Yesterday I was trying to convert my 32gb SD to exFat or NTFS and to do so I had to install Multi mount SD card and I believe it was this **** that brick it. One of the signal meters of the sim cards is gone, the other is normal, also I don't have the slide to disable one of the sims, they are gone... I've tested and both sims are still working, to make calls and receive. Also my Google Play Store is gone, every time I open it it forces closed with "unfortunately google play store has stopped". ja tentei de tudo, qnd faço clear dos dados do app ele ate abre, mas é so mandar iniciar o download de alguma coisa que ja ferra (I've tried everything including deleting app data, when I do that it does open, but after the first download start it forces closes with that error). And the worse of all is that i've been reading that if you hard reset or flash a rom you get the 2nd chip disabled forever. is that true?
one more info... my xt920 is being recognized as xt919! I believe this is what is causing all the problems... the strange thing is that there was no factory reset, hard reset, or firmware flash... just this **** app which might have caused this. How can an APP make your phone be recognized as another model? how could I fix it?
Click to expand...
Click to collapse
Hey man, don't panic!
When you run "getprop" command, what model you get on [ro.product.model]?
Run this tutorial and you get your XT920 back.
Don't use your SD in exFAT or NTFS, it may cause some trouble, use um FAT32 yet.
Cya!
ROM XT920 32D working!!! Follow this instructions:
Instalando a ROM v 2_32D_2009 no RAZR D3 (XT920).pdf (322 KB)
https://mega.co.nz/#!olhn2QQa!fU1KmU9Mp2rRp671bSpI0iB_Vo0_YsFMgZZf8CfnlnA
Is anyone needs it english translated please contact me. I believe it solves sim locked problems!
Unfortunately It don't solve the sim locked problem...
Just a good new... I did a question for Motorola in the razr d sourceforge about the HID support, and they answered me that is possible to implement it. HID is the common protocol for keyboards, gamepads, mouse, etc...
http://sourceforge.net/motorola/razrd/discussion/general/thread/0eaeef02/
Anyone discovered a solution for the locked SIM Slot problem?
I'm in panic here for not being able to use 2 sims on my phone...
And motorola doesn't give any answers about it..
Take it easy, you're not alone.
Motorola released a official update for D3, idk if it'll solve this problem. Last week a guy robbed me, so I don't have a D3 anymore. Look for this update and how to put it in your phone.
Good luck
farenheith said:
Unfortunately It don't solve the sim locked problem...
Click to expand...
Click to collapse
Late reply but... The SIM locked problem, is due to User Data files, when you restore a good one, the problems are gone....
farenheith said:
Unfortunately It don't solve the sim locked problem...
Just a good new... I did a question for Motorola in the razr d sourceforge about the HID support, and they answered me that is possible to implement it. HID is the common protocol for keyboards, gamepads, mouse, etc...
http://sourceforge.net/motorola/razrd/discussion/general/thread/0eaeef02/
Click to expand...
Click to collapse
Hello,
There's any news about the sim lock problem?
silverfoxbrazil said:
Hello,
There's any news about the sim lock problem?
Click to expand...
Click to collapse
Unfortunately a thief robbed my D3, so I'm not looking into this theme anymore, sorry :/
seems i'll have my phone fixed.
in contact with motorola they authorized send the phone to service, even without warranty.
they send me a code from "correios", to ship it without any charge
they called it "special warranty", i will send it today by "correios", let's see what's gonna happen
Related
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
TimothyGaray said:
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
Click to expand...
Click to collapse
Yeah i just got mine yesterday and im having the same issue. I get a Root user account error with Root Checker Pro. Ive tried clearing data in the SU app but nothing. There is an update for SU in the Play Store but i read on Freaktab where someone said not to update SU app or it will give you a bootloop. I havent updated it yet cuz i wanted to do some more investigating but i really dont see the harm in just updating the app itself. I know updating the su binary will result in a bootloop because i updated the binary on my T95Z and got the bootloop. Ive been googling all day trying to find a TWRP.img file for the MX10 but have found nothing yet. Ive also been looking for a root method for this box as well but not sure what i should use. It would be nice if these each box had it own sub forum like the phones have.. would make life so much easier. lol
If you figure anything out i would appreciate if you would pass that info on.. will do likewise.
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Android 7.01 said:
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Click to expand...
Click to collapse
Have you updated the SU app? Not the su binary but the app from play store itself?
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Hi, I received my MX10, a few days ago and have the same problem (SuperSU issue).
I purchased it from GeekBuying, and posted on their blog, for the latest firmware update I could find: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Really want to root it, so I can edit the keyboard/remote control files to map keys on the H18+ remote I bought at the same time as the MX10.
I haven't tried flashing different firmware (or booting into recovery). If/when I receive a reply to my post on the GeekBuying blog, I'll post here - but no idea if they'll reply.
supergiulio said:
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Click to expand...
Click to collapse
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
TimothyGaray said:
...I downloaded updated firmware for this box and the SuperSU zip file...-TimG
Click to expand...
Click to collapse
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
RADiuMOz said:
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Click to expand...
Click to collapse
Yeah i agree.. odd it ships with su installed but no root. Theres some fw's on this page.... ive downloaded just in case i ever need it... dont see why i would since there is no root though. lol
http://freaktab.com/forum/tv-player...3328-4-32gb-tv-box-2-4ghz-wifi-fast-lan/page2
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Thanks for the tip
Thanks Freak69! It was so easy ... but still it would be good to root the MX10
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Click to expand...
Click to collapse
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine - out of the box - on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
RADiuMOz said:
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Ok so ive been on Samsung for the last 5-6 years and never had to backup things like boot.img, recovery.img cuz we have have odin, so there was never any need to...... so i just did a google search on how to do this but it only brings up ways to do it with root. Can you explain how to do this or link to a tut?
Also could i get a more in depth of using Magisk? I have it on my HTC M7 but i rarely ever play around with it... actually im root with SU on it. So i have to run Magisk on my MX10.. search for boot.img.. patch it.. flash some zip in twrp.. and how do i get twrp on the box.. through adb? I should know this as long as ive been rooting but root on U.S. snapdragon samsung phones is totally different since the bootloader cant be unlocked. Thanks for your info so far bro
Post redundant.
flipmode_11 said:
Did you see my questions?
Where did you source your device from? Ebay? Online? Retail?
What software and steps above did you try?
Did you try the Paragon app with Total Commander?
Did you try downloading the recovery.img linked in the Media TV Box category? https://forum.xda-developers.com/showthread.php?p=75644464
Using Magisk is even more important these days as developers attempt to detect SU/Root, plus Magisk does not make modifications to your /System partition which makes life MUCH easier upgrading / troubleshooting / debugging and allows you to mask Root/SuperUser to then use all apps (Spotify, Play, Netflix, Stan, et al.)
Click to expand...
Click to collapse
I got my box from Amazon. Ive not tried anything with it yet. I dont use Total Commander.. that was another guy saying something about it and wanting to be able to write to external sd... i could care less for that. I want root for adaway and a few other things. Im using Blockada right now to block ads but i cant use it and Expressvpn at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
You are funny! I was talking to @RADiuMOz - I had quoted him.
No wonder your reply made no sense. Then my reply made no sense.
Please see my topic on AMLogic devices "AMLogic S905 S912 FAQ ✰ Fix Root, Switch SU, Backup/Restore etc ✩ Media Player TV Box" here: https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
I would suggest you follow the steps to Backup first as it does not make any changes to your system.
Then follow steps to Root (download 3 files) and proceed with the FAQ I have written on how to root and which of the 3 methods suit you (probably the one similar to Part 1 of the backup, plus flashing the ZIP.
I had similar corrupt Root issue where SU and SUD were present, but didn't appear to have permissions. Some apps reported Root OK, and others No Root.
Anyway, let me know how you go. I have documented how to un-root / clean-up and then to re-root your system (i.e. Corrupt Root). Reply there.
Cheers!
p.s. May I suggest you check out AdGuard instead of AdAway? It lets you subscribe to block lists, plus you can set-up DUAL VPN's with it (read their KB/FAQ's). AdGuard's menu's allows you to accomodate both being able to VPN and run adblocking at the same time - ROOT Free. So you can probably ignore everything I have even said! LOL (AdGuard > Left Menu > Settings > Proxy Settings)
VyprVPN is far better and I suggest you try them when they have a promo. You can enable an option to block malicious servers, etc. But no way of managing this and adding adverts. Anyway, I switched and tried various VPN providers and found VyprVPN far better, plus offer a higher level of OpenVPN encryption which is not blocked or detected by 3rd parties called "Chameleon".
freak69ize said:
I got my box from Amazon. I want root for AdAway and a few other things. Im using Blockada right now to block ads but i cant use it and ExpressVPN at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
Click to expand...
Click to collapse
EXPERIMENT: Has anyone tried an OTG adapter in the USB-C slot for a Galaxy S8? Then connect a small USB drive with a recovery.img only, formatted in FAT32? You could even try placing the recovery.img on your Micro SD inside your phone...? Perhaps while holding down menu + up or menu + down, switch on your phone, and it might read the recovery.img on the external memory and boot into that?
*Anyway*, try the same thing in your MX10 and report back add success. Use a compatible S905 TWRP recovery.img (see my type here with download attached and tested with S905x Devices.
Hmm... So many ideas... so many things I have not tried!
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart. Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
First up - sorry mate - I actually thought I'd replied to your post, but clearly either didn't submit it, or just dreamed the whole thing.
I have to wait for free time at the weekends (I have kids), but I'll go back to your topic and give that a go.
As for NTFS, etc. I ended up buying a Synology DS218J NAS box as I want my daughter to be able to back up her MacBook to it, as well as probably back up some of my stuff to it as well - and of course then use for the MX10. I bought it from GeekBuying, and they're not that particularly helpful. Not intentionally unhelpful, though.
My MXIII-G was great for just working straight out of the box, with the external NTFS drive (exact same drive).
So now, as for rooting, my only reason will be so I can remap some of the keys on my remote - but don't absolutely have to do that. But I'll do backups anyway, so that I'm ready for if/when any firmware updates come out.
I'll certainly know to have a MUCH better look round, before buying my next Android TV box, though - that's for sure. I did a quick search, but didn't find anything on a user level - but also didn't search XDA: just did a regular Google search.
Thanks for your detailed reply, as I know it takes time and thought on your part - it's much appreciated. As soon as I've got something to report, I'll post in the same thread, so other people can perhaps benefit from my findings.
Cheers,
Richard.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Apologies! I thought I'd replied, here, but clearly didn't submit it, or just dreamed I had. I've replied to your PM, but also for anyone/everyone else's benefit (and in brief), I bought my MX10 from GeekBuying. I just bought a NAS box, so I'm going to use that instead of trying to get NTFS working, although the people at GeekBuying said, "Our factory tests show that the MX10 can read and write ntfs hard drives. So please try again." I'd be interested to hear whether anyone else is able to write to NTFS.
I'm going to go back to your topic, and give that a go - and will then post back here, to let everyone know (hopefully might benefit someone).
Cheers,
Richard.
i have mx10 and it suddenly stuck in start logo when i open,i dont have any idea please help.
i try to factory reset using toothpick and hit the factory reset no command coming out to delete all files and quick return to booth the system.
whwn i try to reboot again stuck in start logo i'll wait for 30 min but still just rounding the startup logo.Please help me...
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download