Hi All,
I have purchased a leagoo lead 1 http://www.leagoo.cc/c51181.html (slick design and under 150$) but now I'm trying to get it rooted.
I've tries Kingo root, V Root, Shuame, Towel root, Framaroot and none of it is working.
The phone operates on 4.4.2 with an MTK 6582 processor..
When holding Vol up + power I get a fastboot option though.
Would extracting boot.img and rework it mean something? or has anyone usefull tips?
Thnks in advance.
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
boyanpa said:
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
Click to expand...
Click to collapse
First of all .. I managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingosoft one click root, (www.kingoapp.com) Mobile uncle tools
Start sony bootloader unlocker and run it with your phone connected.
It will restart your phone to fastboot and then it remains idle.
Keep your phone plugged in, switch it off and boot manually into the fastboot (power + vol up)
From here the unlocker will proceed unlocking.
Step 1 done.
Now open kingosoft root connect the phone and let it do its thing.
At restart of the phone kingosoft will show on screen a message like "checking root status"
Launch mtk uncle and enter engineer mode.
Go to log and debugging tab ans select user2root
Select Root.
Now kingosoft will tell you that root is succesfull and restarts the phone.
That's that. Phone is rooted. For recovery see the posts 22 and 24 from Vampirefo who did the real hard work in creating 2 flavours of recovery. [emoji106][emoji106]
Non linux users can also flash the img through MTK uncle from sdcard if that doesn't work. See post 40 for flashing recovery via SP tools
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
de vetnek said:
First of all ..Looks like I (accidentaly) managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingo soft one click root, Mobile uncle tools
I Downloaded from kingosoft the sony bootloader unlocker.
It puts the phone in fastboot mode and then it hangs. I unplugged my phone, switch it off (keep the unlocker running) and manually booted into fastboot (vol up+power) the bootloader unlocker then proceeded untill finished.
Next I installed this root tool and started it while the phone was still in the fastboot mode. after a couple of restarts it says checking for Root, then I decided to start MTK uncle tools and scroll to "log and debugging" and select User2Root. then clicked Root and all of a sudden the phone was sucessfully rooted.. Smiling Smiling I don't know what exactly sparked the root access but It's rooted and works!
If anyone can reproduce this in a correct order. please feel free to share.
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
Click to expand...
Click to collapse
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
vampirefo said:
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
Click to expand...
Click to collapse
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
de vetnek said:
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
Click to expand...
Click to collapse
Thanks, GPS was working great on my phone out of box.
vampirefo said:
Thanks, GPS was working great on my phone out of box.
Click to expand...
Click to collapse
Mine wasn't but probably due to a factory reset from recovery? OR it wasn't fit yet to see the dutch sky
Managed to root the thing?
Yes mine is rooted also, Similar to the way you rooted yours.
I used Linux and wine to run the bootloader tool from there, I had to use another tool to get temp root, then I pushed su and set permissions.
The bootloader tool you used works via wine but the root tool doesn't.
Sent from my Leagoo Lead1 via taptak.
So we can carefully state that the (accidental) rooting method works.
Btw. I figured out that /system is ro and not rw
Also with adbd insecure it remains ro. Means it has to be scripted to rw at every boot or.... Can try to run framaroot exploit.
System is supposed to be ro this is normal, to get rw add busybox and then remount rw.
Also you can edit the boot.img and make a insecure boot.img and flash, I have done this myself, this enables adb remount, you can add a script to /system/xbin, to force rw or ro.
I wouldn't want rw all this time, as this can cause instability use ro until you need rw, es filemanger with root also allows you to mount system rw as needed.
Added some pics of phone showing it's rooted.
http://postimg.org/gallery/6ol04a9i/
Sent from my Leagoo Lead1 via taptak.
Check
Noticed that the 1GB Rom quickly runs full if you are not keen on the installation location of apps.
Facebook though can't be moved to SD card.
libvc1dec.sa.ca7.so has text relocations . This is wasting memory and is a security risk. please fix
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
vampirefo said:
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
Click to expand...
Click to collapse
Below shows data is now 4GB, as I am running data from sdcard, I can of course make data any size I want, only limited by size of sdcard, I think this phone supports 64GB, so data could be 64GB.
Code:
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 481.6M 128.0K 481.4M 0% /dev
none 481.6M 12.0K 481.5M 0% /sys/fs/cgroup
tmpfs 481.6M 0 481.6M 0% /mnt/secure
tmpfs 481.6M 0 481.6M 0% /mnt/asec
tmpfs 481.6M 0 481.6M 0% /mnt/obb
/[email protected] 885.8M 819.2M 66.6M 92% /system
/dev/block/mmcblk1p3 4.0G 999.8M 2.8G 26% /data
/[email protected] 123.0M 4.1M 119.0M 3% /cache
/[email protected]_f 8.8M 4.1M 4.8M 46% /protect_f
/[email protected]_s 8.8M 4.1M 4.8M 46% /protect_s
/dev/block/loop0 1.5M 1.5M 0 100% /mnt/cd-rom
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
tunglethanh90 said:
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
Click to expand...
Click to collapse
No ideal what you are saying, Have you rooted your leagoo lead1? if so by what? what is VOcano? Post more details, you say you root but not done, what does that mean?
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
de vetnek said:
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
Click to expand...
Click to collapse
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
vampirefo said:
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
Click to expand...
Click to collapse
Things just got worse hehe.. Did the whole link2sd thing and linked a couple of apps and voila. playstore, facebook, whatsapp gone.. and nowhere to be found back........... doubting whether a factory reset would fix the thing? So in short.... nope.. link2SD does not work.
wouldn't posting the repacked recovery and flashing it to another phone be possible?
Yes the recovery can be flashed on another rooted tablet, but there is more to getting data on sdcard that just flashing a recovery.
I just now modified cwm recovery to work on leagoo lead1, cwm recovery is bigger than my packed stock recovery, but I am able to squeeze in it, lol.
In Utopia..... This would be a good solution for the Leagoo too
http://forum.xda-developers.com/showthread.php?t=2020677
Don't know exactly how they fixed it.. but..... there you also went from 1 to 2.5 GB internal...
Related
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!!
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
sirpy said:
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
Click to expand...
Click to collapse
Had any luck?
moding infocus m512 progress report
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
GalaxyWhy said:
Had any luck?
Click to expand...
Click to collapse
sirpy said:
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
Click to expand...
Click to collapse
Sounds good Keep me posted!
EDIT:
Are you running the most updated software? - http://www.infocusphone.com/m512updates.html
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
rooting infocus m512
GalaxyWhy said:
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
Click to expand...
Click to collapse
I bought it on lightinthebox.com anyways it shouldn't be much a problem to root it, since it's possible to flash a boot img to the device using fastboot.
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
{
"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"
}
In this picture it shows the phone having a recents button but on the website I bought it off it has a menu button. Which one does yours have?
You seem to know more about this stuff than me, I've usually bought well supported devices and rooting was a one click process. I just wanna get root access to be able to use Xposed Modules
Sent from my LG-D802
How'd you go?
I just received mine and I want to root it
rooting infocus m512
GalaxyWhy said:
How'd you go?
I just received mine and I want to root it
Click to expand...
Click to collapse
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
sirpy said:
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
Click to expand...
Click to collapse
Yeah 100% mine didn't have root but I figured it out after lots of searching around. I posted my method here http://forum.xda-developers.com/gen...discussion-t2893455/post55787107#post55787107 so others could do it if they wanted to
Similar problem here
sirpy said:
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
Click to expand...
Click to collapse
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
modifying fstab
Beni.Falk said:
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
Click to expand...
Click to collapse
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
sirpy said:
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
Click to expand...
Click to collapse
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Beni.Falk said:
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Click to expand...
Click to collapse
Well, yes you can try to run fsck. you should follow the method i've outlined in previous post on how to boot the device into ftm mode. then you should be able to run fsck on the system partition (/dev/block.../by-name/system). you will need to run fsck with ext4 option, though i'm not sure if fsck is included, so you might need to download the android version of it and copy it to your device in ftm mode to the root directory change its permissions to 755. (remount / partition as rw)
Firmware download link not working
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Tinox said:
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Click to expand...
Click to collapse
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
already upgraded by seller ?
sirpy said:
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
Click to expand...
Click to collapse
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Tinox said:
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Click to expand...
Click to collapse
download any terminal app, and type "su" in the terminal.
Looking for firmware link
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
sirpy said:
download any terminal app, and type "su" in the terminal.
Click to expand...
Click to collapse
Tinox said:
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
Click to expand...
Click to collapse
well as I said, from what you previously described you don't need the upgrade, you already have the latest.
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Sorry I did not see the area for the guides and I apologize about that.
Also I forgot to thank everyone who gave their time on the LG G3 fast-boot project, as without your information I would not have been able to do this.
Also thanks to Google translate lol.... I couldnt have read Korean
great work friend
I delete some system files and now I cannot install anything from Google Play
I follow you method and I have CWM installed on my device can you help me to say how flash recovery to IMG FILES from you google drive all files are IMG not .tar ...
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
djacks222 said:
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
Click to expand...
Click to collapse
when I flashing the file system.img ( 2 GB size) obtain a error from fastboot for the size of system.img over 512 mb my partition system i
/system 1.97G 1.71G 260.18M 4096
/data 3.96G 1011.82M 2.97G 4096
/persist 31.46M 4.03M 27.43M 4096
/cache 884.61M 14.61M 870.00M 4096
/persist-lg 7.83M 4.33M 3.50M 4096
/sns 7.83M 4.03M 3.80M 4096
/firmware 63.95M 56.39M 7.56M 16384
/mpt 31.46M 13.36M 18.10M 4096
/mnt/shell/emulated 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated 677.76M 0.00K 677.76M 4096
/mnt/media_rw/external_SD 3.72G 395.72M 3.33G 32768
/mnt/secure/asec 3.72G 395.72M 3.33G 32768
/storage/external_SD 3.72G 395.72M 3.33G 32768
/storage/emulated/0 3.96G 1011.82M 2.97G 4096
/storage/emulated/0/Android/obb 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy/Android/obb 3.96G 1011.82M 2.97G
4096
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Man dude that would be awesome. I will even help in aid of development. I dont know exactly what to do but im sure that i could figure something out with all the guides here on xda.
I am in need of other devs to help out...but it looks like none are able..so i dunno where to go from here. Looks like we are stuck.
Sent from my LG-D631 using XDA Free mobile app
Msm8226 is the board for the d631. It is also the board for the v410 lte tablet. Is there any compatibility between the two
Sent from my LG-V410 using Tapatalk
Once rooted with one click, you can install the quick boot app from the Play store and use it to reboot into recovery.
oranget said:
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Click to expand...
Click to collapse
what is this is it hope
it's not a brick it's a wonderful egg i'm going to hatch into a beautiful budget-friendly princess
Issues step 6
djacks222 said:
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Click to expand...
Click to collapse
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Drake865 said:
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Click to expand...
Click to collapse
If you are rooted, you could try using flashify. It worked for me. It'll load cwm first and reboot, but after the second try you should be up and running.
Questions???Anything on the update for this device thanks
System Dump
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
How would I go about retrieving those two files
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
I have the 2 files that you need but I need a email address to send it to you
Any kdz file or anything how to update to 5.0
at&t d631 rom
Isaiah.E.Scott said:
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
Click to expand...
Click to collapse
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
piptravels said:
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
Click to expand...
Click to collapse
Can't you upload the update zip
Rican39 said:
Can't you upload the update zip
Click to expand...
Click to collapse
Where is the update zip? I have seen a lot of stuff about kdz and tot files but I don't see anything identifying if they're for the AT&T version of the LG G Vista or the Verizon version.
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Burs said:
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Click to expand...
Click to collapse
Root needs a custom kernel. Not something you are gonna do with a Windows setup the way you have it. Also you will most likely not find anything as that is most likely not an official version of Android as Google doesn't allow dual booting.
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Burs said:
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Click to expand...
Click to collapse
what su is doing is pulls the kernel and patches it. root access is defined in the kernel. what itnis doing in system is flashimg just the apk
Ok, I see. So if I ask someone who rooted the same model successfully to send me patched kernel, I could easily flash it in fastboot mode (my bootloader is unlocked). So only thing left to do would be to copy apk inside /system/app, and cross my fingers? I'll post my findings if I manage to do something worth writing about. Thanks.
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
bahuy2003 said:
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
Click to expand...
Click to collapse
I managed to root my Onda few days after my last post, but forgot to post my findings, sorry. I didn't used any of my hacker's skills lol, but I researched a bit more and found out what I was missing. The same issue is with you, so you have to disable verity before flashing recovery by typing in these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
After rebooting install supersu.zip, and the next boot won't hang on Onda logo anymore. Hope this helps you.
btw, note that not just any adb version has verity command line switch. You have to download newer adb version!
Thank you! I trie a lots times, but i can't make successfully!
Basic root procedure would be: unlock BL -> disable verity -> flash (temp) recovery -> install SuperSU
Here are the links containing all the files neccessary for rooting Onda V80 Plus: Mega | MediaFire
Note the ReadMe.txt inside archive. It contains list of adb/fastboot commands needed to be executed in order to successfully root the device.
Thank you very much! I download your file and root successfully my Onda V80 plus! It works well for me.
Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Hi, I am about the get one such box and just want to know any new progress you did. As such I am new and interested to know the firmware version and did you got any OTA update. Beelink GT1 Mini is similar hardware and they have posted new firmware in their site. May be you can patch that and use in your device to get what you are looking for.
I have a working TWRP I created for this box. I can share it. Just saw this. The Resolution is a bit garbled, I am trying to fix it so its clear, but it works as of now. - https://mega.nz/#!BAkAyYgS!FvpS0xNJtvLYkb2y3SSfGQp4yY-m_Lkz-BwfIlUTHvU
anyone has tried this box with atv experience rom?
X96 max ethernet fix
I bought the x96 max and the box came with an internet problem both over ethernet cable both over Wi-Fi ..
My home net is working properly ... I do the cable speed test and the box gives me the maximum values ... Then I will see some stream or download and simply do nothing ... How can I solve this problem
CyberSolid said:
Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Click to expand...
Click to collapse
foremost ,you need a suitable recovery.img for your device. then , flash it via adb command: "adb shell cat /sdcard/recovery.img > /dev/block/recovery"
CyberSolid said:
Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Click to expand...
Click to collapse
So, any news? Did you manage to flash custom recovery and root this device? If not. Maybe here you may find something or someone helpful: https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
Cross fingers. I just bought same box and would appreciate if someone could write tutorial how to do it. I just newbie in this matter. Cheers.
TWRP 3.2.2.0 S905X2 x96max
https://4pda.ru/forum/dl/post/14664327/TWRP_AML_3_22_X96MAX.zip
https://drive.google.com/file/d/1nJYas5bZZhtut0KWpd31_uGEpdWSxuR8/view?usp=drivesdk
partition table:
# mount point fstype device [device2]
/boot emmc /dev/block/boot /dev/block/mmcblk0p11 flags=backup=1;display=Boot
/recovery emmc /dev/block/recovery /dev/block/mmcblk0p6 flags=backup=1;display=Recovery
/param emmc /dev/block/param /dev/block/mmcblk0p10 flags=backup=1;display=Param
/system ext4 /dev/block/system /dev/block/mmcblk0p16 flags=backup=1;display=System
/vendor ext4 /dev/block/vendor /dev/block/mmcblk0p14 flags=backup=1;display=Vendor
/data ext4 /dev/block/data /dev/block/mmcblk0p17 flags=backup=1;display=Data
/cache ext4 /dev/block/cache /dev/block/mmcblk0p3 flags=backup=1;display=Cache
/bootloader emmc /dev/block/bootloader /dev/block/mmcblk0p1 flags=backup=1;display=Bootloader
/reserved emmc /dev/block/reserved /dev/block/mmcblk0p2 flags=backup=1;display=Reserved
/env emmc /dev/block/env /dev/block/mmcblk0p4 flags=backup=1;display=Env
/logo emmc /dev/block/logo /dev/block/mmcblk0p5 flags=backup=1;display=Logo;flashimg
/rsv emmc /dev/block/rsv /dev/block/mmcblk0p12 flags=backup=1;display=RSV
/tee emmc /dev/block/tee /dev/block/mmcblk0p13 flags=backup=1;display=Tee
/crypt emmc /dev/block/crypt /dev/block/mmcblk0p9 flags=backup=1;display=Crypt
/misc emmc /dev/block/misc /dev/block/mmcblk0p7 flags=backup=1;display=Misc
/odm emmc /dev/block/odm /dev/block/mmcblk0p15 flags=backup=1;display=ODM
/dto emmc /dev/block/dto /dev/block/mmcblk0p8 flags=backup=1;display=DTO
/external_sd auto /dev/block/mmcblk1p1 flags=wipeingui;storage;removable;display="External SD"
/usb-otg auto /dev/block/sda1 flags=display="USB OTG";removable;storage
A.S._id said:
https://4pda.ru/forum/dl/post/14664327/TWRP_AML_3_22_X96MAX.zip
partition table:
# mount point fstype device [device2]
/boot emmc /dev/block/boot /dev/block/mmcblk0p11 flags=backup=1;display=Boot
/recovery emmc /dev/block/recovery /dev/block/mmcblk0p6 flags=backup=1;display=Recovery
/param emmc /dev/block/param /dev/block/mmcblk0p10 flags=backup=1;display=Param
/system ext4 /dev/block/system /dev/block/mmcblk0p16 flags=backup=1;display=System
/vendor ext4 /dev/block/vendor /dev/block/mmcblk0p14 flags=backup=1;display=Vendor
/data ext4 /dev/block/data /dev/block/mmcblk0p17 flags=backup=1;display=Data
/cache ext4 /dev/block/cache /dev/block/mmcblk0p3 flags=backup=1;display=Cache
/bootloader emmc /dev/block/bootloader /dev/block/mmcblk0p1 flags=backup=1;display=Bootloader
/reserved emmc /dev/block/reserved /dev/block/mmcblk0p2 flags=backup=1;display=Reserved
/env emmc /dev/block/env /dev/block/mmcblk0p4 flags=backup=1;display=Env
/logo emmc /dev/block/logo /dev/block/mmcblk0p5 flags=backup=1;display=Logo;flashimg
/rsv emmc /dev/block/rsv /dev/block/mmcblk0p12 flags=backup=1;display=RSV
/tee emmc /dev/block/tee /dev/block/mmcblk0p13 flags=backup=1;display=Tee
/crypt emmc /dev/block/crypt /dev/block/mmcblk0p9 flags=backup=1;display=Crypt
/misc emmc /dev/block/misc /dev/block/mmcblk0p7 flags=backup=1;display=Misc
/odm emmc /dev/block/odm /dev/block/mmcblk0p15 flags=backup=1;display=ODM
/dto emmc /dev/block/dto /dev/block/mmcblk0p8 flags=backup=1;display=DTO
/external_sd auto /dev/block/mmcblk1p1 flags=wipeingui;storage;removable;display="External SD"
/usb-otg auto /dev/block/sda1 flags=display="USB OTG";removable;storage
Click to expand...
Click to collapse
Link is dead. Could you explain what are those strings for? Did you manage to unlock bootloader, flash working recovery and root this device? Thx
rsteelion said:
Link is dead.
Click to expand...
Click to collapse
just check - link is OK. you need to be registered to download from 4pda.
you may try second link from google drive instead (which is Ok too)
ayaromenok said:
just check - link is OK. you need to be registered to download from 4pda.
you may try second link from google drive instead (which is Ok too)
Click to expand...
Click to collapse
Thank you for second link. Could you tell what those strings from your first post are...? Forgive my ignorance...
Hi, i m not easy with forum and post by for hardaware x96max_v311 4gb ram 64gb intern and gigabit just new:with issues but last firmware no updates.
1/ gigabit wired port, link with the switch in place of old one h96+(3gb/32gb), the box stay info disconnect no gigabit port can communicate and menu Network and internet have no entry for setup cable wired, only wifi, all my infrastructure works fine.
2/ wifi 2/5 ghz works but onlyN can connect, 5 GHZ registreted never connect, but used my laptop and phone, 5ghz AC out order
3/ remote poor , power can be parameter but never wake up.
4/ menu interface poor, nedd change , and down new
my experience with no solution for gigabit
Thanks for your info correction for this product ( put my old in place and works )
I just posted a TWRP 3.2.3-0 build for the GT1 Mini (S905X2) that uses the same Amlogic u211 reference board, so it will likely work on this device too : twrp.u211-3.2.3-0.img
It's built with the twrp-8.1 minimum OMNI branch and is using a prebuilt 112N0 GT1 Mini kernel. Source is in the twrp-8.1 branch of my TWRP for Amlogic repository.
Systemdown666 said:
I bought the x96 max and the box came with an internet problem both over ethernet cable both over Wi-Fi ..
My home net is working properly ... I do the cable speed test and the box gives me the maximum values ... Then I will see some stream or download and simply do nothing ... How can I solve this problem
Click to expand...
Click to collapse
I am also having the exact same issues with the X96 Max TV Box 4GB/64GB.
Has anyone else come across this and found a fix?
Hello, I discover that the X96 max 4G/64/G is 8.1 android 32bit ! after issue on ethernet gigabit et wifi 5ghz OUT it s a big waste.
no original rom (name u311 is a 211 board too )can be found on web and no patch
It s a new plateform interresting but just the OS made quick for business , not to be full functionneley
It s direct now to the bin !
stock a firmware X96 Max - S905X2
Hello!
I have problem with may tv box, it is stuck on boot screen logo.
I tried to reset the box but it doesn't help.
I want stock firmware pls
best regards
ahmaduk8 said:
Hello!
I have problem with may tv box, it is stuck on boot screen logo.
I tried to reset the box but it doesn't help.
I want stock firmware pls
best regards
Click to expand...
Click to collapse
http://www.mediafire.com/file/ga6qtrj6df6cpsx/X96MAX--4+32G+4+64G.img
credit to
http://4pda.ru/forum/index.php?showtopic=925461
hello, the link does not work, can you resurrect it? Thank you
https://chinagadgetsreviews.com/download-android-oreo-8-1-firmware-for-x96-max-tv-box.html
Hi all, ive seen few posts where saying that libreelec can be flashed by using reset button placed behind AV connector, i'm really not sure if that applicable for amlogic s905x2 and 4gb ram
Anyone owning x96 max willing to test some of libreelec roms?
If anything stated wrong or u know the answer already, please tell
Btw im thinking about to get one x96 max, but just for having libreelec as standalone os there
Thanks