Related
This issue was resolved by Meghd00t's new REPART.IMG file. See this post on that thread: http://forum.xda-developers.com/showpost.php?p=26060323&postcount=151cool:
I have the 8gb model Nook Tablet and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how the internal flash version would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the stock "reset" warnings - or even a flash of light. No matter how I try to boot it (with or without cable, with or without the Nook button) or how long I hold the buttons down, it still remains with a BLACK SCREEN.
However, the SDCard will boot properly.
I followed the instructions on this thread ( http://forum.xda-developers.com/showthread.php?t=1515788) precisely to reset the BootData. I did NOT receive any errors. However, it still will not boot internally.
I then tried sigmabeta's process to flash CM9 (http://forum.xda-developers.com/showthread.php?p=25661314) to the internal emmc (which is supposed to work on NT8). The flash process (via SD/CWM) went properly and I did not receive any errors. However, I still cannot get anything to boot (except my SDCards).
If I put my CM7a (bootable) SDCard (http://forum.xda-developers.com/showthread.php?t=1481826) into the NT8, it boots and runs great! Likewise meghd00t's recovery/CWM sdcard boots and runs properly.
I can do ADB & FASTBOOT and I have even done the dd to download my partitions (for backup) and then dd copies from online onto the device's partitions. Still no joy.
However, even after dd'ing a downloaded copy of p5 to the device, ADB still reports my TRUE serial number? It seems that the dd to part5 did not take?
The only other thing that I have found, that seems significant, is the fact that when I am in CWM, I cannot mount the EMMC. I can ADB/shell into the device but that did not allow me to mount the emmc either.
Any ideas how I can get this thing to boot internally? How can I force the device to mount the emmc?
Click to expand...
Click to collapse
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Final "fix"
lavero.burgos said:
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Click to expand...
Click to collapse
Not sure that I have tried ALL of them, that is why I am still searching. Also, people come up with new ideas that have not previously been published.
Thanks for all YOUR help. Especially the dd to fix bootdata.
Sure wish someone would come up with a solution for this problem. There seems to be quite a few of us who are looking for answers.
Sent from my Nook Tablet using XDA
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Existing solutions
succulent said:
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Click to expand...
Click to collapse
Thanks for the info. I do appreciate it and I will be trying some of your suggestions later today when I get home.
One problem (that seems to be easing up a bit) is the fact that few posters distinguish WHICH version of the NT that they are working with. The NT16 "solutions" became the NT8 "problems." It would be great if everyone posted WHICH version they have.
The other issue is (as you stated) when you follow a guide to fix an issue, it CAN mess up your device even worse that it was. Then, you have TWO issues to deal with - rather than just one as before. I am afraid that is where I am now.
One question: You mention "compiling" CWM. Are you referring to the technical term of compiling code into an executible? Or, are you simply referring to the process of putting a working image onto an SDCard? I can do the latter without issue but I have never compiled code.
I do use Ubuntu Linux so many of the Windows driver issues are moot for me. However, I do have a dual boot with XP in on the other side - just in case I need to do some Windows-only stuff.
I really appreciate the help. I am no novice but I am not a developer either. I can usually search, read, try, and work out the problems that I (and other less technical users) experience. That is what my website is all about - translating the really "tech" jargon into everyday language for non-techies to follow. But this one has stumped me (and at least a few others) for the past couple of months.
succulent said:
I have learned that many people like to format things apparently.
Click to expand...
Click to collapse
Sent from my NookTablet using Tapatalk
I've noticed this as well. People really need to do more reading before randomly selecting/flashing things.
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!!
Hi,
I'm pretty interested in learning a bit about android, but for the moment i have this tablet that i have royally screwed up during my learning curve It's a PORTO 10.1 chinese tablet.
It would freeze up at the boot logo, but after some searchin, a forum member on the internet kindly sent me some .img files that he used to fix the same brand/model of tablet. They are flashed with the Rockchip tool. It's a RK3066 based tablet.
Prior to receiving the files i was trying other ROM's because it was becoming clear that there wasn't a full dump available for this tablet. None of them worked, and the tablet ended up being completely dead as a result. Being completely stupid once more, i formatted the tablet in the Rockchip tool, before realizing and learning that the ROMS don't come with .img files for partitions like userdata or cache etc? So any chances of recovery even if i did find a partial ROM, may have gone. Yes, i am an idiot Well you have to read a lot and make mistakes to learn, right? I've certainly learnt how to backup all of my partitions now in Rockchip tool since then!
Anyway the jist of it is, the tablet is 100%low level erased as far as i know. I've flashed the files that i was given from a guy on gsmforums, and the tablet turns on again, displays the manufacturer logo and then the android boot animation...but thats it. It gets stuck on the android logo animation.
The partitions i know have been flashed and should exist now are:
misc
boot
kernel
recovery
system
backup
The parameters of these partitions do match what they should be for this tablet. The one thing i did do before screwing the thing up was backup the parameter data. It's a shame i didn't backup anything else!
Obviously there are partitions i am missing, such as userdata, cache and maybe some more from what I've read. My main questions are these:
1. Will android hang like this at the logo if it cannot find/mount a userdata partition? or might i see a terminal/errors instead?
2. If i could get into Recovery (which i can't) does a factory reset just quick format the userdata partition, or would it obliterate it and recreate the partition over again and format it?
3. Are there any ways i may be able to recreate my missing partitions, assuming that it the reason why android is now stuck at the logo?
I did attempt to flash a copy of the cache and userdata partitions from another very similar tablet, but it didn't make any difference.
I know a little about what each partition is there for and what they do, i use a linux pc regularly although i am still working my way up from semi-newbie
Knowing how android should react to having no userdata/cache partitions might help me figure out what i need to do to fix this tablet? I am willing to read and learn if someone can tell me where to begin or give me some hints that might answer some of my questions.
Many thanks,
James.
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...
Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.